26 Posts

May 31st, 2007 07:00

Curious if you have checked the steps in the "Installation Roadmap
for CX3-Series, CX-Series, AX-Series, and FC-Series
Storage Systems Guide" for Linux Multipath and verified the Failovermode and arraycommonpath setting for the initiators...

2.2K Posts

May 31st, 2007 08:00

Not sure if there is a way to delete initiator records through the cli, but in Navisphere you can right click on the array, select properties, and select Connectivity Status. Select the stale initiator records and click on the Deregister button.

If that still does not remove the initiator records then restart the Navisphere Manager Server.

76 Posts

May 31st, 2007 12:00

By the way, you can get loads of CLI commands from
EMC Navisphere Command Line Intereface Reference

9 Legend

 • 

20.4K Posts

May 31st, 2007 12:00

this is strange because they should not show up as logged-in, but if you want to delete them anyway you will need to enter into engineering mode. Before you do this make sure you are de-registering correct HBAs. Also what did you change in multipath.conf ? We had the same issue and had to boot into single user mode to fix a typo.

76 Posts

May 31st, 2007 12:00

Try using the naviseccli command port with option -removeHBA

naviseccli -h [ip address of sp] -user [username] -password [password] port -removeHBA -hbauid [hba id number]

I think the hbauid is the WWN, though I've never used the command this way...you could try -hostip [ip address of host] or -host [hostname] but in the manual it says those options remove records where the initiator is logged out

2.2K Posts

June 1st, 2007 07:00

That's right, records that show the host as logged in cannot be Deregistered via the GUI unless you are engineering mode. Thanks for the catch on that.

Message was edited by:
AranH

17 Posts

June 8th, 2007 03:00

hi james,

you can try to remove the navisphere client agent on the host and then take a reboot and then see wats the status of HBA is in the navisphere manager.

what changes you have done in conf file.
As it has been suggested above, there cud be a typo in the conf file, please check for that.

Thanks & Regards,
Munish
No Events found!

Top