This problem is related to the EMX driver, binding the 9960's luns to a target ID greater than 7. This is only an issue under Tru64 4.0. When the HBA driver sees a new WWN name, it binds that name to the lowest available target Id. The system will keep this reservation between reboots, regardless of whether the device is removed from the system. What has happened is that more than 8 WWN have been detected prior to the 9960 being connected to HBA. They are no longer connected, but they still have a hold on a particular target id

The solution is to remove the outdated entries from HBA database.

Remove the following files:

  /etc/emx.info
  /etc/emx.info.bk
  /etc/emx.db
  /etc/emx.db.bk                        

Then reboot the server.

Upon reboot, the driver will rebuild the target ID list using only devices which it can currently see. If you need to reassign the target IDs, the preferred method is to use the /usr/sbin/emxmgr utility.

Here is an example through emxmgr:

  Select Option (against "emx0"):
  1. View adapter's current Topology
  2. View adapter's Target Id Mappings
  3. Change Target ID Mappings
  d. Display Attached Adapters
  a. Change targeted adapter
  x. Exit
  ----> 3
  Enter input method - interactive/file/help: (i/f/h) -> i
  Enter adapter instance [emx0] ->
  Enter FC Port Name -> 5000-1fe1-0000-0770
  Enter FC Node Name -> 5000-1fe1-0000-0770
  Enter target id -> 2
  Continue with the change in id mappings (y/n) [n] ? y                        

The server should now be rebooted.

The HDS luns are not visible via the >>>show dev utility in the SRM since they have not yet been set an udid.

However, the luns can be seen in the wwidmgr by executing

>>>wwidmgr -show wwid                        

Internal Section

ndusa@east