Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 8
Registered: ‎01-10-2014

Can anyone explain why we get duplicate trunk masters when creating ISL Trunk between switches

we are trying to create a two port ISL Trunk between an DCX8510-4 FC16-48 Blade and SW4100 .

 

when we bring up the two ISLs we get two seperate Trunk Masters. The DCX is on FOS 7.1.0c and the SW4100 is on FOS 6.3.2b

 

 The details are below:

 

Does anyone know what is causing this issue?

 

This is holding up our project now so any advice etc is most welcome.

 

thanks

 

KIRK_B32_SW12:admin> islshow   
  1:  0->  0 10:00:00:05:1e:34:9d:4a  18 kirk_b32_sw18   sp:  4.000G bw: 16.000G TRUNK
  2:  8->  0 10:00:00:05:1e:02:65:49  20 kirk_b32_sw20   sp:  4.000G bw: 16.000G TRUNK
  3: 24-> 23 10:00:00:27:f8:71:9a:00  53 FSWKIRKD53      sp:  4.000G bw:  4.000G TRUNK
  4: 25-> 47 10:00:00:27:f8:71:9a:00  53 FSWKIRKD53      sp:  4.000G bw:  4.000G TRUNK
KIRK_B32_SW12:admin> trunkshow
  1:  0->  0 10:00:00:05:1e:34:9d:4a  18 deskew 16 MASTER
      4->  4 10:00:00:05:1e:34:9d:4a  18 deskew 15
      1->  1 10:00:00:05:1e:34:9d:4a  18 deskew 15
      5->  5 10:00:00:05:1e:34:9d:4a  18 deskew 16

  2:  8->  0 10:00:00:05:1e:02:65:49  20 deskew 16 MASTER
     12->  4 10:00:00:05:1e:02:65:49  20 deskew 15
     13->  5 10:00:00:05:1e:02:65:49  20 deskew 16
      9->  1 10:00:00:05:1e:02:65:49  20 deskew 16

  3: 24-> 23 10:00:00:27:f8:71:9a:00  53 deskew 15 MASTER

  4: 25-> 47 10:00:00:27:f8:71:9a:00  53 deskew 15 MASTER

KIRK_B32_SW12:admin> fabricshow
Switch ID   Worldwide Name           Enet IP Addr    FC IP Addr      Name
-------------------------------------------------------------------------
 12: fffc0c 10:00:00:05:1e:34:9f:6d 10.10.200.59    0.0.0.0        >"KIRK_B32_SW12"
 18: fffc12 10:00:00:05:1e:34:9d:4a 10.10.188.11    0.0.0.0         "kirk_b32_sw18"
 20: fffc14 10:00:00:05:1e:02:65:49 10.10.188.19    0.0.0.0         "kirk_b32_sw20"
 24: fffc18 10:00:00:05:1e:35:a4:e5 10.10.200.81    0.0.0.0         "kirk_b32_sw24"
 53: fffc35 10:00:00:27:f8:71:9a:00 10.10.207.39    0.0.0.0         "FSWKIRKD53"

The Fabric has 5 switches

 24  24   0c1800   id    4G   Online      FC  E-Port  10:00:00:27:f8:71:9a:00 "FSWKIRKD53" (downstream)(Trunk master)  
 25  25   0c1900   id    4G   Online      FC  E-Port  10:00:00:27:f8:71:9a:00 "FSWKIRKD53" (Trunk master)  

FSWKIRKD53:e400022> islshow
  1: 23-> 24 10:00:00:05:1e:34:9f:6d  12 KIRK_B32_SW12   sp:  4.000G bw:  4.000G TRUNK
  2: 47-> 25 10:00:00:05:1e:34:9f:6d  12 KIRK_B32_SW12   sp:  4.000G bw:  4.000G TRUNK
FSWKIRKD53:e400022> fabricshow
Switch ID   Worldwide Name           Enet IP Addr    FC IP Addr      Name
-------------------------------------------------------------------------
 12: fffc0c 10:00:00:05:1e:34:9f:6d 10.10.200.59    0.0.0.0        >"KIRK_B32_SW12"
 18: fffc12 10:00:00:05:1e:34:9d:4a 10.10.188.11    0.0.0.0         "kirk_b32_sw18"
 20: fffc14 10:00:00:05:1e:02:65:49 10.10.188.19    0.0.0.0         "kirk_b32_sw20"
 24: fffc18 10:00:00:05:1e:35:a4:e5 10.10.200.81    0.0.0.0         "kirk_b32_sw24"
 53: fffc35 10:00:00:27:f8:71:9a:00 10.10.207.39    0.0.0.0         "FSWKIRKD53"

The Fabric has 5 switches

FSWKIRKD53:e400022> trunkshow
  1: 23-> 24 10:00:00:05:1e:34:9f:6d  12 deskew 15 MASTER

  2: 47-> 25 10:00:00:05:1e:34:9f:6d  12 deskew 15 MASTER


 23    1   23   351700   id    4G         Online      FC  E-Port  10:00:00:05:1e:34:9f:6d "KIRK_B32_SW12" (upstream)(Trunk master)
  47    1   47   352f00   id    4G         Online      FC  E-Port  10:00:00:05:1e:34:9f:6d "KIRK_B32_SW12" (Trunk master)  

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Valued Contributor
Posts: 761
Registered: ‎06-11-2010

Re: Can anyone explain why we get duplicate trunk masters when creating ISL Trunk between switches

Hi,

 

The trunk is not being correctly created because the ports do not meet the requirements to stablish a 2-ISL trunk:

 

The ports must belong to the same port group, and in this case ports 24 and 25 belong to the same port group, whereas ports 23 and 47 on the other end, do not belong to the sme port group.

 

FSWKIRKD53:e400022> trunkshow
  1: 23-> 24 10:00:00:05:1e:34:9f:6d  12 deskew 15 MASTER

  2: 47-> 25 10:00:00:05:1e:34:9f:6d  12 deskew 15 MASTER

 

You must connect these two ports in FSWKIRKD53 to the same port group: Ports 16-23 or 40-47. 

 

Please, correct the ports and let us know if it works.

 

 

Rgds,

Felipon

 

 

Occasional Contributor
Posts: 8
Registered: ‎01-10-2014

Re: Can anyone explain why we get duplicate trunk masters when creating ISL Trunk between switches

Hi Felipon,

 

thanks for your reply.

 

we suspected that it may have been something to do with port groups but we couldnt find any documentation to confirm that.

 

We will arrange to have the connections change as per the info you sent.

 

I will let you know if this resolves our problem.

 

we have tight change control windows so it will be next week before I can confirm.

 

thanks again

 

Tom

Regular Visitor
Posts: 1
Registered: ‎05-05-2016

Re: Can anyone explain why we get duplicate trunk masters when creating ISL Trunk between switches

I have similar situation where all ISLs on the switch is marked as Trunk Master. Groups of 2 are on the same port group (on both switches B and C). I've tried disabling/enabling ports with no luck, speed is fixed 8Gbps. Worth mentioning these are ELWL Gbics with ~20KM distance to each other. Trunking license is present and trunk is enabled on both switches. One switch (B) has 2 trunks configured with the other (switch A) ant it functions as it should. I cannot get switch B<->C ISLs work as a trunk.

 

Index Slot Port Address Media Speed State Proto
============================================================
0 1 0 070000 id 8G Online FC LS E-Port 10:00:00:05:1e:6a:70:00 "swB" (Trunk master)
1 1 1 070100 id 8G Online FC LS E-Port 10:00:00:05:1e:6a:70:00 "swB" (Trunk master)

 

trunkshow
1: 0-> 22 10:00:00:05:1e:6a:70:00 3 deskew 15 MASTER

2: 1-> 23 10:00:00:05:1e:6a:70:00 3 deskew 15 MASTER

 

long distance is configured as LS with 75km range on both sides.

 

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.