This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>
Enterprise products, solutions & services
Publication Date: 2020-07-07 | Views: 451 | Downloads: 0 | Author: a84141210 | Document ID: EKB1100052361
l AP alarms doesn’t appear at Fault current alarms tab
l AP alarms doesn’t appear at fault current alarms, meanwhile; we can see it under the AC itself
l eSight version was checked
l AC SW version was checked
l After checking we found the compatibility as per below, so we are confirming on the effect of that with HQ
l eSIght server is reachable from AC
l There is no FW exist in the path between the AC and eSight, and as a result; there is no policies block passing of trap messages.
l AP alarms doesn’t appear at fault current alarms, meanwhile; we can see it under the AC itself
l Checked the alarm masking rule on eSight, masked alarms and traps of the device are recognized as events and stored in the event list
- Telnet and SNMP test were done, and it was successful
- SNMP configuration was checked, SNPv3 is used but trap wasn't sent to esight
- Trap wasn't sent to esight, below command was missed
**snmp-agent target-host trap-paramsname xxx v3 securityname xxx privacy**
- Trap wasn't sent to esight, below command was missed
**snmp-agent target-host trap-paramsname xxx v3 securityname xxx privacy**
