![]() ![]() ![]() |
1. Why there are no alerts from the
device?
You
might not have received alerts from the device if the trap host is not
configured in the source Router. Make sure you configure the
routers
to send traps to OpManager. Telnet the router and type the following
command:
snmp-server host <opmanager server
IP> traps <host community string> rtr
For instance, if the OpManager host IP Address is 192.168.18.128, and
the community string is private, the command would be:
snmp-server host 192.168.18.128 traps private rtr
2. Why should i give Snmp Write
community to the router?
Both,
the SNMP read and write community string needs to be set on the source
router. The write community is used to configure the IPSLA agent on the
device while the read community is used by OpManager to gather
performance data from the router.
3. Why I am getting 'Source
router SNMP write community may be wrong' error message?
OpManager
uses SNMP to gather data from the Cisco IP SLA agent. This
error is displayed when wrong SNMP read / write community string is
configured for the Source router of the WAN Monitor in OpManager.
To
configure the correct SNMP write community string in OpManager, go to
the snapshot page of the source router and change the SNMP credentials
by clicking on the 'Click
here to change' corresponding to the "Passwords"
field. In the pop-up enter the appropriate credentials and submit it.
After successfully submiting the correct SNMP credentials, try to add
the WAN Monitor again for the Source device (Maps > WAN Monitor >
Settings).
![]() ![]() ![]() |