| TROUBLESHOOTING |
Network Manager stations and ensure the interval is set to a value of 30 seconds or more. This will significantly reduce the number of nuisance failures.
15.14 IMC DETECTED LINK FAILURES
Problem:
The IMC reports a link failure.
Solution:
For link fail tests involving all controller types (MIM, PIM, etc.), the steps below will help to identify the defective controller board.
∙On the CEC/IMC Manager For NT, display the nodes map. All boards managed by this IMC should appear on the screen with the appropriate status icon. For example, to perform a MIM fail link trap test, click on the MIM icon. Another menu appears when the user selects the “controller” box and then “send.” Next, go to the switch and determine which controller board’s LED is flashing. This step is useful only when boards and cables are not properly tagged or labeled.
∙After finding the correct board, go to the back of the switch and carefully pull the cable to that controller board. Within 10 seconds, the status of the appropriate controller board icon on the CEC/IMC Manager node map will change (turn red) and a trap should be received at the workstation where the Network Manager is running. The trap will appear as an EDACS event if it is correctly categorized as an EDACS event.
∙If the trap is not received, make sure that the MIB object associated with the trap enable/disable is not set to “disable.” If the MIB object is “enabled,” then make sure that the trap is properly configured to be an EDACS event. To check this condition, enter the
15.15MSM/SM OUT OF COLOR MAP ENTRIES
Problem:
The Multisite Monitor or Site monitor application errors out with one on the following X messages:
∙Warning: Cannot allocate colormap entry for “xxxx”. (Where xxxx is a color name.)
∙Warning: Cannot parse default background color spec.
∙X error of failed request: Bad Access (attempt to access private resource denied.)
∙Major opcode of failed request: 88(X_FreeColors)
∙Serial number of Failed request: stream: 16747
The X server will not recover from these errors and must be killed manually. It will restart automatically. NOTE: These errors should not occur if MSM or SM is started before the graphic intensive submaps are opened.
If the MSM is executed from the command line after the OpenView submaps have been opened, the MSM application will execute without “X” messages, but the colors are confused. The
Solution:
This problem is results from all software colormap entries in use. The MSM must allocate approximately 30 color entries to execute. The 712 workstations have a maximum of 256 color entries, therefore only 256 different colors/shades can be displayed or used on the system at any given time.
76
