Unsolved

This post is more than 5 years old

1 Rookie

 • 

19 Posts

2254

July 2nd, 2013 13:00

Issues with Inititators

All:

We had a scheduled power down and were able to power back up the system on Monday.

We ran into issues though with our initiators for some reason they are yellow triangles

The brocade on the IBM Blade Center is wide open, no zoning etc.

We had this working before the shut down and now it doesnt want to see it. We have created the storage group, and assigned the IP to the virtual machine, and have used the correct WWN.


I need the system up ASAP, and I have worked with Federal tech support with little to no answers.


Thanks,

Ron

1 Rookie

 • 

19 Posts

July 2nd, 2013 13:00

Yes sorry dynamox, correct the ESX Servers, so i am using the WWN's from the vmhba1 and vmhba2


Sorry about that little bit of confusion

1 Rookie

 • 

19 Posts

July 2nd, 2013 13:00

emc_error.jpg

See attached.... hope this helps

9 Legend

 • 

20.4K Posts

July 2nd, 2013 13:00

can you post screen shot from Connectivity Status/Initiator screen (scramble host names)

9 Legend

 • 

20.4K Posts

July 2nd, 2013 13:00

and VNX ports plug-in directly to that Brocade ?

1 Rookie

 • 

19 Posts

July 2nd, 2013 13:00

nothing changed to my knowledge from the HBA's... cabling stayed the same... We arent using a FC switch, just the Brocade on the IBM Blade side. It shows the port is up and active when I log into the brocade.

9 Legend

 • 

20.4K Posts

July 2nd, 2013 13:00

Logged-in column has "No", did anything change in terms of HBAs, cabling ? Is it direct connect or you are going through another FC switch ?

9 Legend

 • 

20.4K Posts

July 2nd, 2013 13:00

you assigned IP to the virtual machine - what do you mean by that, are you connecting ESX servers, Hyper-V servers ?

9 Legend

 • 

20.4K Posts

July 2nd, 2013 14:00

VNX ports show up Online on the switch ?

switchshow

9 Legend

 • 

20.4K Posts

July 2nd, 2013 14:00

cfgshow on the switch

Management server - in your web browser enter http://SPA_IP/setup

1 Rookie

 • 

115 Posts

July 2nd, 2013 14:00

Did both VNX fc ports and esx vmhba wwns are logged into switch ??  just to reconfirm do nodefind  on those hba wwns

nodefind xx:xx   , if they come up fine then bounce the zone ( delete from active zoneset , wait for min , add it back and activate it on brocade ).

1 Rookie

 • 

19 Posts

July 2nd, 2013 14:00

i have a vnx5300... if that makes sense VG2/8 NAS head not sure what that means Sorry

9 Legend

 • 

20.4K Posts

July 2nd, 2013 14:00

cable the right port, although you said cabling did not change.

4 Operator

 • 

2K Posts

July 2nd, 2013 14:00

Actually, looking even closer you have B2 associated with the data movers which is showing logged in and registered.  So I assume you have a VG2/8 NAS head? 

If this is the case, so don't necessarily replace SPB2 which is associated with the data movers, it appears you simply don't have SPB0 logging in.

4 Operator

 • 

2K Posts

July 2nd, 2013 14:00

Or you could reregister the host.  Might not be a bad idea to free up the MirrorView port; however, the easiest thing would be to recable it the way it was originally.  Comparing Connectivity Status with the Switch output suggests that cables were swapped (unless someone else sees something differently). 

1 Rookie

 • 

19 Posts

July 2nd, 2013 14:00

no configurations in effect for defined or effective

Top