Newly Inserted NEM is Not Discovered

A newly inserted NEM in the chassis does not appear in the Sun Blade Zone Manager web interface, or is not present in the CLI under /STORAGE/sas_zoning.

What to look for:

The following table provides examples of how the web interface and CLI might look like if you installed a second NEM for dual path support and wanted to check that the second NEM was seen by the Sun Blade Zone Manager.

CMM ILOM If NEM is Not Discovered Web interface In Sun Blade Zone Manager configuration window. CLI -> show –level all /STORAGE/sas_zoning Targets: BL0 BL1 BL2 BL3 BL4 BL5 BL6 BL7 BL8 BL9 NEM0 <-- Only one NEM is listed. Properties: zone_management_state = enabled reset_password_action = (Cannot show property) reset_access_action = (Cannot show property)

The above example does not list the second NEM, even though it was installed.

Things to check:

Check the CMM ILOM event log (see Viewing the CMM ILOM Event Log) for messages relating to the NEM.

Actions to perform:

• If no messages about the newly installed NEM have been logged, wait 5 minutes for the CMM to properly discover and integrate the new NEM into the SAS-2 fabric. Use the CMM ILOM web interface or CLI to run the Sun Blade Zone Manager again.

• Either press the NEM Attention button, or perform a return_to_service action.

• If you see “/CH/NEMx failed to join SAS2 fabric" (where x is the slot number of the NEM), do the following:

  1. Pull out the failed NEM.

  2. Wait until the removal is processed.

     You will see that the removal is processed when a "Hot removal of /CH/NEMx" message (where x is the slot number of the NEM) is logged.

  3. Once the removal message is seen, it is safe to reinsert the NEM.

• If you see "/CH/NEMx successfully added to SAS2 fabric" (where x is the slot number of the NEM), this means that the NEM is now ready to be configured by the Sun Blade Zone Manager. Use the CMM ILOM web interface or CLI to run the Sun Blade Zone Manager again.