Nm Client - Alcatel-Lucent 5620 Troubleshooting Manual

9 — Troubleshooting 5620 SAM clients
3
Procedure 9-4 Problem: Cannot view 5620 SAM alarms using

5620 NM client

Possible causes include incorrectly configured param.cfg parameters on the 5620 NM to
allow the forwarding of alarms to those platforms from the 5620 SAM.
1
2
3
4
5
6
7
8
9-6
In a typical network, when collisions are greater than 5%, you may have a
serious congestion problem on the interface. Review your LAN topology and
design to reduce the number of network bottlenecks.
iv To stop the netstat command, press CTRL-C.
Check that the client platform is appropriately sized. See the 5620 SAM Planning
Guide for more information.
Open a command tool on the 5620 NM client station.
Navigate to the AS tool IM directory by typing:
/opt/netmgt/ALMAP/as/data/ascurim_0 ↵
Open the param.cfg file.
Ensure the NSP_USE_NSP and CORBA_SERVER_DISCOVERY parameters are set to
True.
Save the changes and close the file.
When the filters for CORBA are set to True, ensure the CORBA filter files are set
correctly. Navigate to the AS tool IM configuration directory by typing:
/opt/netmgt/ALMAP/as/data/ascurim_0/ASIMconfig ↵
Ensure the following filters are set in the ASIMconfig or ASIMFilter files:
CORBA_ROOT_NAME_FILTER="*/*/AlarmSynchronizer*";
CORBA_ROOT_NAME_FILTER="*/*/EventChannelFactory*";
CORBA_ROOT_NAME_FILTER="*/*/X733EventChannel*";
Save the changes and close the file.
Aug 2010
Troubleshooting Guide
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
8.0 R4