Unsolved

This post is more than 5 years old

1 Rookie

 • 

19 Posts

2258

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

6 Operator

 • 

2K Posts

July 2nd, 2013 16:00

Firstly let me apologize to Dynamox for jumping in.

Ron_Payne wrote:

Chris:

I will physically make sure that the SP's are physically plugged into the data movers tomorrow when I get in...


Thanks guys

No don't worry about anything going to/from the SP's and the Data Movers; connectivity status shows those are logged in, registered and healthy.  You will want to confirm that SPA0 and SPB0 are connected to the corresponding switches.  Pay close attention to the WWN of the HBA that was registered with SPA0 and similarly for SPB0.  A common issue can be swapping cables to opposite switches after they've been registered already (not an issue for you since we simply don't see either logged into the switch).

For a diagram, you can refer to the "EMC VNX VNX5300 Unified Installation Guide"

https://support.emc.com/search/?resource=DOC_LIB&AlloftheseWrds=VNX5300%20Unified%20Installation%20Guide&SearchWithin=true&adv=y

I have circled in red what would be SPB0:

SPB0.png

6 Operator

 • 

2K Posts

July 2nd, 2013 16:00

So this is what you need to confirm.

1) The HBA's were each originally registered with SPA0 and SPB0 as seen from Connectivity Status

HBA.png

2) The switch output (from 1 of 2 switches) you provided only shows what turns out to be an AUX port on one of the data movers (you likely have 2-way NDMP setup).  Ignore this.  However, what is missing SPB0 from the switch output

a) Note that the HBA logged into this switch is:

    10:00:00:90:fa:0a:80:90

b) From Connectivity Status, this was registered with SPB0.

3) You need to identify SPB0 and determine why they aren't logging into the switch (physically not connected?)


a) From Unisphere:

> Settings > Network > Settings for Block

b) Search for B-0 in the column "SP-Port"

c) In the column: "IQN/WWN", the second half of that is what you should see in the switch output

4) Map the logical port SPB0 to the physical port on the array

a) In the column: "Physical Location" this will show you the physical port that it corresponds to (would be an onboard port)

b) Verify physically (SP and *not* the data mover) that this port is cabled to the switch.  From the switch output, I would suspect you should focus on port 16

16  16  011000  idN8  No_LightFC

c) For a picture of the SP, within Unisphere you can see this as follows:

- > System > Hardware > Storage Hardware

It will show you a picture of the SPE (SP Enclosure) and from the rear which it is showing, SPB would be on the left.

Then repeat for SPA0.

6 Operator

 • 

2K Posts

July 2nd, 2013 17:00

Simply as an FYI, from a data mover perspective (please do not interrupt this cabling though as we aren't troubleshooting the NAS portion), you will see the following connections:

SPA.png

SPB.png

Now, based on the switch output:

  0  0  010000  idN8  OnlineFC  F-Port  50:06:01:6a:47:20:0d:e3

This port corresponds to:

DM3.png

You would see this by running the following command:

server_sysconfig server_3 -p

Also, I recognize the WWN (except for the unique middle character in the second half of the initiator name) from the initiator records of the data movers as seen in the following output:

connectivity.png

This is typically cabled for 2-way NDMP setups to a tape drive (but more often on server_2; maybe you'll also see the corresponding port connected on the other switch).  Let's not touch that though but I bring this all up since you will see it cabled as suchAgain, we aren't troubleshooting the NAS portion of the configuration, simply why isn't SPB0 showing logged in in the switch output you pasted (and SPA0 on the other switch).

1 Rookie

 • 

19 Posts

July 3rd, 2013 05:00

Chris:

I verified that cabling is correct for the SPB side and SPA side....

Also our fiber that goes to the brocade is plugged into the port you highlighted red....

I have also attached the fiber swtich for the other brocade


SPB0 isnt cabled up anywhere......

Index Port Address Media Speed State     Proto

==============================================

  0   0   010000   id    N8   Online      FC  F-Port  50:06:01:62:47:20:0d:e3

  1   1   010100   cu    N8   Online      FC  F-Port  10:00:00:90:fa:0a:7f:85

  2   2   010200   cu    N8   Online      FC  F-Port  10:00:00:90:fa:0a:80:91

  3   3   010300   cu    AN   No_Sync     FC

  4   4   010400   cu    AN   No_Sync     FC

  5   5   010500   cu    AN   No_Sync     FC

  6   6   010600   cu    AN   No_Sync     FC

  7   7   010700   cu    AN   No_Sync     FC

  8   8   010800   cu    AN   No_Sync     FC

  9   9   010900   cu    AN   No_Sync     FC

10  10   010a00   cu    AN   No_Sync     FC

11  11   010b00   cu    AN   No_Sync     FC

12  12   010c00   cu    N8   Online      FC  F-Port  10:00:00:00:c9:ea:05:19

13  13   010d00   cu    N8   Online      FC  F-Port  10:00:00:00:c9:ce:62:59

14  14   010e00   cu    AN   No_Sync     FC

15  15   010f00   --    N8   No_Module   FC

16  16   011000   id    N8   No_Light    FC

17  17   011100   --    N8   No_Module   FC

18  18   011200   --    N8   No_Module   FC

19  19   011300   --    N8   No_Module   FC

Not sure what the next steps should be....

I looked up B-0 and it says Mirrorview with a WWN as 50:06:01:68:3E;A0:4E:7D

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 3rd, 2013 06:00

I looked up B-0 and it says Mirrorview with a WWN as 50:06:01:68:3E;A0:4E:7D  <- we dont see this WWN logged-in to the switch so you either cables SPB0 or figure out what port is actually plugged-in to VNX.

No Events found!

Top