OSM Service Connection or TSM Service Application Views Show Wrong CRU or FRU State

OSM Service Connection or TSM Service

Application Views Show Wrong CRU or FRU

State

Symptom

Customer-replaceable units (CRUs) such as batteries and fans and

field-replaceable units (FRUs) such as ServerNet/FX adapters sometimes

do not appear in the OSM Service Connection or TSM Service Application

views.

Version

All

Problem

Could be one of the following:

The window is not refreshing properly.●

The OSM or TSM server is not receiving events from the service

processor (SP).

●

There is a problem with the TSM server software.●

These problems are possible only for G06.01 or earlier RVUs and servers

using the SNMP client/server management protocol

SNMP messages are being lost, affecting the discovery process (for

servers using SNMP client/server protocol).

●

An SNMP trap error is occurring (for servers using SNMP

client/server protocol).

●

Fix

To correct the problem, perform each step below until the problem has

been corrected. The order is based on the degree of likelihood as well as

the ease of the recovery procedure.

1 Is the window refreshing properly?

Select Display>Refresh, or try switching to a different view

(Physical View, Inventory View, or Connection View) to see if the

CRU or FRU appears.

PAGE 1
OSM Service Connection or TSM Service Application Views Show Wrong CRU or FRU State Symptom Customer-replaceable units (CRUs) such as batteries and fans and field-replaceable units (FRUs) such as ServerNet/FX adapters sometimes do not appear in the OSM Service Connection or TSM Service Application views. Version All Problem Could be one of the following: ● The window is not refreshing properly. ● The OSM or TSM server is not receiving events from the service processor (SP).
PAGE 2
Are the service processors (SPs) failing to report the existence of the CRU or FRU? Establish a low-level link connection and look for the missing CRU or FRU in any of the views (Physical View, Inventory View, Connection View, or Logical View, System View, depending on your client software version). If the missing CRU or FRU appears, proceed to Step 3. If the missing CRU or FRU does not appear in the low-level link, the SPs might not be reporting the existence of the CRU or FRU.
PAGE 3
4.8 Exit the TSM Configuration Application. 4.9 Log back on to the TSM Service Application. If the CRU or FRU still does not appear, proceed to the next step. 5 Is there a problem with the TSM server software? To recover from a possible TSM server problem, copy the contents of the ZSERVICE subvolume to tape or diskette and send it to the GCSC along with a description of which CRU or FRU is missing. Then stop and restart $ZTSM. 5.