cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3016
Views
5
Helpful
16
Replies

Booting from SAN-SAN Target Paths are not showing

isaac anish
Level 1
Level 1

Hi community,

Here i configure in UCS booting from SAN,We created 2 vHBA-1 and vHBA-2

In vHBA-1(PRI)

Primary SAN traget-xx.xx.xx.xx.xx.xx

Secondary SAN target-xx.xx.xx.xx.xx.xx

In vHBA-2(SEC)

 Primary SAN traget-xx.xx.xx.xx.xx.xx

Secondary SAN target-xx.xx.xx.xx.xx.xx

So here i am able to see only 2 paths that to also secondary target paths of both vHBA in UCS.And in host windows MPIO that two paths are  showing the Active/unoptimized path.

Here i attached the screen shot also,Please help me!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

 

 

16 Replies 16

Marcin Latosiewicz
Cisco Employee
Cisco Employee

Isaac, 

 

Check out two things.

Some framework around troubleshooting. 

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ts/guide_old_FM/TS_SANBootAndConnect.html

 

This is probably the best external writeup about lunmap/lunlist commands, which is where you should start. 

http://jeffsaidso.com/2012/02/ucs-boot-from-san-troubleshooting-with-the-cisco-vic-part-2/

 

M.

Walter Dey
VIP Alumni
VIP Alumni

Can you please post a picture of the physical setup !

- storage connected via a SAN ? or direct to FI ?

- cabling of SAN switches (or FI) to storage controller ?

Hi walter,

 

Thanks for the reply,storage  

-connected to via FI to SAN switch to netapp storage controller.

-And cabling of SAN is SAN switch to storage controller..

i dont have the  physical connectivity details,Usually how to connect for the active/active controller in netapp....?

And why its not showing the primary path of the 2 vHBA's....?is that mistake in configuration  in UCS end...?

 

vHBA-2

Controller 1:

50:0a:09:82:80:21:18:54

50:0a:09:82:90:21:18:54

 

vHBA-1

Controller 2:

50:0a:09:81:80:21:18:54

50:0a:09:81:90:21:18:54

Hi Isaac

I would think it should be wired like this

vhba-1 - SAN-A - Controller -A (primary)

vhba-1 - SAN-A - Controller -B (secondary)

 

vhba-2 - SAN-B - Controller -B (primary)

vhba-2 - SAN-B - Controller -A (secondary)

 

Q. did you do the zoning accordingly; 2 zones per fabric !

Walter.

yes we did the zoning accordingly 2 zones per fabric.

Here i attached the lamap screen shot

Why are the node wwn all 0 ? very strange ?

Can you please also post screenshot of "configured boot order" ; I see actual boot order !

Please find the deatils.

Will server is boot from active/unoptimized path...?

Q. did you install a OS ? does your multipath software see 4 paths ?

Seems to me, that the primary path doesn't see the boot lun; this is always the first choice.

Yes i installed OS,and in MPIO also configured but its showing only 2 paths that to also active/unoptimized.its not showing the 4 paths...

 

So where i need to check in SAN or UCS end....?

How to trouble shoot it...?

Here i attached  the screenshot of MPIO

Hi Isaac

Very clear now: it's not only a boot issue, but also a MPIO issue; you only see 2 paths, not 4 !

You seem to have 2 storage controller A and B, each having 2 ports: A1, A2 and B1, B2

Your boot policy says

vhba 1 - primary path - A1

vhba1 - secondary path - A2

Q. is your cabling from the SAN switch to storage controller done in exactly this way ?

Above should be

vhba 1 - primary path - A1

vhba 1 - secondary path - B2

If primary and secondary path of vhba 1 go to controller A, it might be, that only one port has control over the lun; therefore you see what you see, namely 2 path, not 4.

Walter.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

vhba-1 - SAN-A - Controller -A (primary)

vhba-1 - SAN-A - Controller -B (secondary)

- See more at: https://supportforums.cisco.com/discussion/12517616/booting-san-san-target-paths-are-not-showing#comment-10530361

vhba-1 - SAN-A - Controller -A (primary)

vhba-1 - SAN-A - Controller -B (secondary)

- See more at: https://supportforums.cisco.com/discussion/12517616/booting-san-san-target-paths-are-not-showing#comment-10530361

Hi Walter,

But in server  bios is detecting only 2 wwpn number then it wiil show only 2 paths in MPIO rit.

so were i need to check weather UCS or SAN end.

 

Here i attached bios screen shot.

Hi Isaac

I'm fairly convinced its a stroage controller issue, not UCS !

Currently the indicated ports seem showing the lun; I would try to disconnect the cables for this ports on Controller 1 and 2; and see, if the lun is then seen on the other ports ?

 

Controller 1:

50:0a:09:82:80:21:18:54

50:0a:09:82:90:21:18:54 <=======

 

vHBA-1

Controller 2:

50:0a:09:81:80:21:18:54

50:0a:09:81:90:21:18:54 <=======

Walter.

Hi,

Can get recommended Connectivity diagram of CISCO UCS FI to SAN switch..?

So that i will verify it with my current setup  

Have a look at

http://www.cisco.com/c/en/us/products/collateral/storage-networking/mds-9500-series-multilayer-directors/white_paper_c11_586100.html

eg. Figure 1

or https://www.youtube.com/watch?v=aUECbrYi8Oo

or http://www.vce.com/asset/documents/infrastructure-platforms.pdf

which has a picture, of what you would like to do (see also attachment)

 

http://www.techrepublic.com/blog/the-enterprise-cloud/learn-how-san-fibre-mesh-works/

has a nice picture which explains, how the cabling between your MDS and storage processors should be done (same as I tried too explain before)

see also attachment

Review Cisco Networking for a $25 gift card