cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
927
Views
5
Helpful
4
Replies

Problem With Paths VMWARE

Hi.

I have 2 switches MDS 9513 and 9506, 2 Storages HITACHI VSP and 9 Servers VMWARE.

All servers have 2 HBAs, 1 connect each switch.

One storage have 2 HBAs connect each switch, the other 1 HBA connect each switch.

Each Server's HBA have individual zone with individual Storage's HBA.

The problem:

3 Servers have all paths ok. All in vsan 20.

7 have some problem, don't have all the paths. Some have path problem with one storage or other.

All the problems are the connections with switch MDS 9506. the paths by switch MDS 9513 are ok.

I started debug zone and have this messages:

2016 Jul 21 20:45:56.785582 zone: mem1: [ FCID: 0xe408c0 ], mem2: [ FCID: 0xe40820 ] are in zone: HSTCLSRJ07_VSP_2C
2016 Jul 21 20:45:56.785620 zone: Mem1 device-type : 0 Mem2 device-type : 0
2016 Jul 21 20:45:56.785653 zone: mem1: [ FCID: 0xe408c0 ], mem2: [ FCID: 0xe40820 ] can communicate
2016 Jul 21 20:45:56.785705 zone: Event 3 queued on vsan 20, q len 1
2016 Jul 21 20:45:56.785741 zone: Tcam gen process event: got event 3 on vsan 20
2016 Jul 21 20:45:56.785774 zone: (TG)Rcvd event (LOCAL_NX_PORT_UP_DN) on vsan 20, current state = Ready, next state = Ready
2016 Jul 21 20:45:56.785817 zone: Programing TCAM Entries For Local Port UP/DOWN on vsan 20
2016 Jul 21 20:45:56.785864 zone: PARAMETERS-> Vsan: 20 UP/DOWN: 1 Interface: fc1/27 FCID: 0xe40820 WWN: 21:00:00:24:ff:48:6e:cc
2016 Jul 21 20:45:56.785927 zone: zs_tcam_process_request: event = Program_local_route, seq # 1389
2016 Jul 21 20:45:56.785966 zone: Adding req to active queue
2016 Jul 21 20:45:56.785998 zone: Starting timer
2016 Jul 21 20:45:56.786044 zone: Updating Local Route: VSAN: 20, DID: 0xe40820, DID_MASK: 0xffff00, Dest If: fc1/27
2016 Jul 21 20:45:56.786423 zone: Removing req from active queue
2016 Jul 21 20:45:56.786611 zone: Stopping timer
2016 Jul 21 20:45:56.786781 zone: Dup Entry : (nil), VMR: (nil), Compare Result: 0
2016 Jul 21 20:45:56.786828 zone: Inserting in Indexed Object: 0x102f4a8c
2016 Jul 21 20:45:56.786892 zone: qos api failed with retval 40300037
2016 Jul 21 20:45:56.786981 zone: Dup Entry : (nil), VMR: (nil), Compare Result: 0
2016 Jul 21 20:45:56.787016 zone: Inserting in Indexed Object: 0x102f458c
2016 Jul 21 20:45:56.787055 zone: No zone with bcast attr; not generating any broadcast entries
2016 Jul 21 20:45:56.787087 zone: No zone with bcast attr; not generating any broadcast entries
2016 Jul 21 20:45:56.787159 zone: Dup Entry : (nil), VMR: (nil), Compare Result: 0
2016 Jul 21 20:45:56.787194 zone: Inserting in Indexed Object: 0x103a9194
2016 Jul 21 20:45:56.787248 zone: qos api failed with retval 40300037
2016 Jul 21 20:45:56.787331 zone: Dup Entry : (nil), VMR: (nil), Compare Result: 0
2016 Jul 21 20:45:56.787365 zone: Inserting in Indexed Object: 0x103aade4
2016 Jul 21 20:45:56.787401 zone: No zone with bcast attr; not generating any broadcast entries
2016 Jul 21 20:45:56.787433 zone: No zone with bcast attr; not generating any broadcast entries
2016 Jul 21 20:45:56.787498 zone: Dup Entry : (nil), VMR: (nil), Compare Result: 0
2016 Jul 21 20:45:56.787532 zone: Inserting in Indexed Object: 0x103aafcc
2016 Jul 21 20:45:56.787585 zone: qos api failed with retval 40300037
2016 Jul 21 20:45:56.787668 zone: Dup Entry : (nil), VMR: (nil), Compare Result: 0
2016 Jul 21 20:45:56.787702 zone: Inserting in Indexed Object: 0x103ab09c
2016 Jul 21 20:45:56.787738 zone: No zone with bcast attr; not generating any broadcast entries
2016 Jul 21 20:45:56.787769 zone: No zone with bcast attr; not generating any broadcast entries
2016 Jul 21 20:45:56.787833 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.787889 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.787943 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.787998 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.788052 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.788097 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.788151 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.788197 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.788250 zone: Ignoring nonLUN Destination
2016 Jul 21 20:45:56.788305 zone: zs_tcam_process_request: event = Program_local, seq # 1390
2016 Jul 21 20:45:56.788338 zone: Adding req to active queue
2016 Jul 21 20:45:56.788368 zone: Starting timer
2016 Jul 21 20:45:56.788426 zone: Lc entry for fc1/27 at slot 0 not found
2016 Jul 21 20:45:56.788463 zone: Sending 3 input TCAM entries to i/f fc1/27
2016 Jul 21 20:45:56.788505 zone: LKPTYPE: 3 VSAN: 20 SID: 0xe40820 DID: 0xe40120
2016 Jul 21 20:45:56.788539 zone: Link: 1
2016 Jul 21 20:45:56.788568 zone: UP: 0
2016 Jul 21 20:45:56.788615 zone: LKPTYPE: 3 VSAN: 20 SID: 0xe40820 DID: 0xe408c0
2016 Jul 21 20:45:56.788648 zone: Link: 1
2016 Jul 21 20:45:56.788678 zone: UP: 0
2016 Jul 21 20:45:56.788713 zone: LKPTYPE: 3 VSAN: 20 SID: 0xe40820 DID: 0xe40900
2016 Jul 21 20:45:56.788745 zone: Link: 1
2016 Jul 21 20:45:56.788774 zone: UP: 0
2016 Jul 21 20:45:56.789125 zone: Lc entry for fc1/4 at slot 0 not found
2016 Jul 21 20:45:56.789172 zone: Sending 1 input TCAM entries to i/f fc1/4
2016 Jul 21 20:45:56.789211 zone: qos api failed with retval 40300037
2016 Jul 21 20:45:56.789347 zone: LKPTYPE: 3 VSAN: 20 SID: 0xe408c0 DID: 0xe40820
2016 Jul 21 20:45:56.789384 zone: Link: 1
2016 Jul 21 20:45:56.789413 zone: UP: 0
2016 Jul 21 20:45:56.789707 zone: Lc entry for fc1/48 at slot 0 not found
2016 Jul 21 20:45:56.789749 zone: Sending 1 input TCAM entries to i/f fc1/48
2016 Jul 21 20:45:56.789786 zone: qos api failed with retval 40300037
2016 Jul 21 20:45:56.789892 zone: LKPTYPE: 3 VSAN: 20 SID: 0xe40120 DID: 0xe40820
2016 Jul 21 20:45:56.789925 zone: Link: 1
2016 Jul 21 20:45:56.789954 zone: UP: 0
2016 Jul 21 20:45:56.790231 zone: Lc entry for fc1/42 at slot 0 not found

Any ideas.

Thks.

Paulo Mauricio

4 Replies 4

Walter Dey
VIP Alumni
VIP Alumni

Hi Paulo

- I assume you have 2 (at least) different VSAN's, one on 9513 resp. 9506 ?

- which SAN-OS version

- have the servers properly made flogi on the 9506 ? show flogi database vsan ....

- have the storage subsystem made proper flogi on the 9506 ?

- on the 9506: do you see any logging events ? show logging log ?

Vsan: 20 UP/DOWN: 1 Interface: fc1/27 doesn't look to be a zoning issue ?

Walter.

Hi Walter.

- Both have the same vsan 20. They don't interconnect.

- Ok. The servers made flogi on the 9506.

- 9506

Software
BIOS: version 1.0.10
loader: version N/A
kickstart: version 6.2(1)
system: version 6.2(1)

9513

Software
BIOS: version 1.0.10
loader: version N/A
kickstart: version 5.0(1a)
system: version 5.0(1a)

- I don't have errors messages in the log

- What drive me crazy is the server is ok with one path to storage and the other is "dead" , vmware message. After reboot the switch the situation change, the path dead back and the other go to dead situation. 

I hope my answers help to understand, because I don't.

- Did you ever investigate what the server differences are: 3 working ok 7 not ?

- is this a new installation ? has it ever worked ?

- do you have any FC multipathing software installed ?

- if you don't see any error log entries on the MDS, the problem cannot be the switch ?

- both fabrics same vsan identical ? weird ? not best practise ? could this be a hint ?

Hi Walter.

It's working.

I have downgrade in 9506 to 5.2, same problems.

Dowgrade to 5.0.1(A) the same switch 9513, everything ok.

I believe the switches must be in the same version. 

Waht do you think?

Thks for your help.