Procedure 9-5 Problem: All Snmp Traps From 7750 Srs Are Arriving At One 5620 Sam Server, Or No Snmp Traps Are Arriving - Alcatel 5620 Troubleshooting Manual

Procedure 9-5 Problem: All SNMP traps from 7750 SRs are arriving
at one 5620 SAM server, or no SNMP traps are arriving
When you install the 5620 SAM server, you specify a port where SNMP traps arrive. In
addition, two sets of configurations must be completed for SNMP trap notifications to
work:
1
2
3
Alcatel 5620 Service Aware Manager, Release 2.1 R2
May 2005 95-5887-01-00-B
•
Enable key SNMP parameters on the routers before managing them.
•
Ensure that a unique trapLogId is specified for each router to communicate with
the 5620 SAM. If the trapLogId is used by other applications or by another
5620 SAM, traps may be misdirected or directed to only one machine.
Note — You must have group and user permissions to configure the
managed devices.
Enable the system ID of the 7750 SRs to be managed by the 5620 SAM:
i Run the following CLI command on the 7750 SRs, in sequence:
configure router interface system
address <a.b.c.d>/32
where <a.b.c.d> is the system ID and /32 is the bitmask
ii Close CLI.
Run the following CLI command to enable the SNMP engine and configure at least
one SNMPv2 community on all 7750 SRs to be managed by the 5620 SAM:
configure system snmp no shutdown
configure system security snmp community name of community rwa
version both
where name of community is the SNMPv2 community name
admin save
Note — The command is used for the 5620 SAM write mediation policy.
If you are using SNMPv2, you must use this mediation policy for read as
well, or create another mediation policy that is also configured for rwa.
Run the following CLI command on all 7750 SRs to be managed by the 5620 SAM
to ensure that all get SNMP PDU commands are properly run:
system snmp packet-size 9216
admin save
9 — Troubleshooting 5620 SAM server issues
9-9