HPE EVA Storage
1822724 Members
3862 Online
109644 Solutions
New Discussion юеВ

RP4440 fibre can not log in EMC CX500.

 
SOLVED
Go to solution
Isaac Loven_4
Advisor

RP4440 fibre can not log in EMC CX500.

Hi all,
I have a production RP4440 (wodu001) connected to a CX500. We have bought 2 more RP4440's.
I have ignited new servers, wodu002 and wodu002, from wodu001. (using make_tape_recovery -Av ). The servers are identical HP's RP4440 with 4 CPUs and 16 Gigs mem.
( The only difference now is IP address, and hosts name. )
I have added the new servers to the Zone in the Brocades. I have confirmed that this is fine.
The SAN can see the fibres: The fibres have registered, but not logged in. (as shown on the Navisphere web ) THIS IS THE CORE OF THE PROBLEM.
( I have even tried to register the fibre manually, but still the host is not added. )
I have bounced the fibre ( pulled it out and in ) and rebooted the servers too. ( many times )
The servers are connected to the network.

I have just added the following Navi s/w to wodu002, But the fibre is Still not logged in.

NAVIAGENT 6.7.0.4.7 Navisphere Disk Array Management Tool (AGENT)
NAVICLI 6.7.0.4.7 Navisphere Disk Array Management Tool (CLI)

( One wodu001 the s/w is :
NAVIAGENT 6.6.0.3.8 Navisphere Disk Array Management Tool (AGENT)
NAVICLI 6.6.0.3.8 Navisphere Disk Array Management Tool (CLI)
)

I also ran on wodu002 and on wodu003:
navicli -h apcx01p1 register
Error: register command failed
Command not Supported


Any ideas ??

7 REPLIES 7
D Anderton
Advisor
Solution

Re: RP4440 fibre can not log in EMC CX500.

I had a similar problem with a CX400 and found it was due to using an ignite image.

Check for a file : HostIdFile.txt in /etc/log

If it exists remove it and reboot or restart the navisphere software on your HPUX server this will generate a new and unique hostidfile.

Bill Rothanburg
Trusted Contributor

Re: RP4440 fibre can not log in EMC CX500.

When you clone a system with the NaviAgent already installed, you will need to remove /etc/log/HostIdFile.txt. It's best to stop the agent first, remove the file, and restart the agent.

/sbin/init.d/agent stop
rm /etc/log/HostIdFile.txt
/sbin/init.d/agent start

The HBA's should then show with the correct hostnames in Navisphere Manager. You can then group edit them for the correct failover mode and place the host into a storage group.
Isaac Loven_4
Advisor

Re: RP4440 fibre can not log in EMC CX500.

I stopped the agent, removed /etc/log/HostIdFile.txt, and restarted the agent. The file appears to have been regenerated correctly, but The fibre still does Not log in to the SAN. I then rebooted too, but the fibre still does Not login. ( I also reset the fibre cards, ioscan-ed, etc ) Why should I need reboot, in is not windows?

Are there any "Fibre Parameters" I need to set in the Tachyon Fibre card ???

Below shows "DVS_UNOPENED": is this significant?

fcmsutil /dev/td0 get remote all

Target N_Port_id is = 0x010600
Target state = DVS_UNOPENED
Symbolic Name = DGC CX500 HP03
Port Type = N_PORT
Target Port World Wide Name = 0x500601603020004a
Target Node World Wide Name = 0x50060160b020004a

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 20 Version_Low: 9
BB_Credit: 8 Ciro: 1
Alt_BBcred: 0 Rxsz: 800
Conseq: ff RO_Bitmap: fe
Resolution: 0 EDTOV(ms): 7d0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------


Target N_Port_id is = 0x010700
Target state = DVS_UNOPENED
Symbolic Name = DGC CX500 HP03
Port Type = N_PORT
Target Port World Wide Name = 0x500601683020004a
Target Node World Wide Name = 0x50060160b020004a

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 20 Version_Low: 9
BB_Credit: 8 Ciro: 1
Alt_BBcred: 0 Rxsz: 800
Conseq: ff RO_Bitmap: fe
Resolution: 0 EDTOV(ms): 7d0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------


Isaac Loven_4
Advisor

Re: RP4440 fibre can not log in EMC CX500.

You Guys were right,

/sbin/init.d/agent stop
rm /etc/log/HostIdFile.txt
/sbin/init.d/agent start

After I did this, I was able to add the Host to the Storage Group in the Navisphere.
( That was the step that I needed to do, but could not.)
Then I did an ioscan, insf.
Now I can see the disks on SAN.

THANKS for your help.
Isaac.
Eric Castaneda_1
Occasional Advisor

Re: RP4440 fibre can not log in EMC CX500.

Hey everybody,
I have a similar problem where I can get the fiber to login but the only way i can register is if I do so manualy. Once you cleared up your Host$.txt file how long did it take for the fiber to login? I've talked with emc support and they suggues that I wait for up to 2 hours before the host will register. I've gone thru moving the Host$.txt file and adding agentID.txt.
Thanks,
Mike Rodgers
Isaac Loven_4
Advisor

Re: RP4440 fibre can not log in EMC CX500.

Hi, I just had the EMC Engineer here all day.
Try to remove the Luns and Host from the storage group. Delete & recreate the storage group. Add the Luns and host to the storage group. Restart the navicli agent ( before & after ):
/sbin/init.d/agent stop
then /sbin/init.d/agent start
Also check that there a no errors in the Navisphere browser.

skt_skt
Honored Contributor

Re: RP4440 fibre can not log in EMC CX500.

here is the another thread i am working on. Your suggetions would be appreciated.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1210720