For more details, please see ourCookie Policy.


Fibre Channel (SAN)

Reply
Anonymous
Posts: 0

Re: 48K ISL-Trunk problem

hi Andreas,

sorry for my late answer, i was on holiday........

About our SAN infrastructure:

we've 2 CORE and 5 edge switches.

There are ISL-TRUNKING connections from Edges to Cores , of course, and there are a isl-Trunk between the Cores (not between the edges)

The probelm is,

Randomically, we've a problem on ISL from es.

from edge 1 to core 1

in the meatime we find a FC connection timeout in  OS log messages on a host linked on another edge (es. edge 5)

here below there are  errors in log switch

thanks again

Max

16:27:40.740 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:27:41.250 SCN Port Offline;g=0x2734e                  A2,P0  A2,P0  23    NA  

16:27:41.250 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:27:53.977 SCN LR_PORT (0);g=0x2734e                   A2,P0  A2,P0  23    NA  

16:27:53.977 SCN Port Online;g=0x2734e                   A2,P0  A2,P1  23    NA  

16:27:53.978 Port Elp engaged                            A2,P1  A2,P0  23    NA  

16:27:53.978 SCN Port F_PORT                             A2,P1  A2,P0  23    NA  

16:27:53.978 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:27:54.448 SCN Port Offline;g=0x27350                  A2,P0  A2,P0  23    NA  

16:27:54.448 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:28:07.141 SCN LR_PORT (0);g=0x27350                   A2,P0  A2,P0  23    NA  

16:28:07.141 SCN Port Online;g=0x27350                   A2,P0  A2,P1  23    NA  

16:28:07.141 Port Elp engaged                            A2,P1  A2,P0  23    NA  

16:28:07.141 SCN Port F_PORT                             A2,P1  A2,P0  23    NA  

16:28:07.142 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:28:07.680 SCN Port Offline;g=0x27352                  A2,P0  A2,P0  23    NA  

16:28:07.680 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:28:20.543 SCN LR_PORT (0);g=0x27352                   A2,P0  A2,P0  23    NA  

16:28:20.543 SCN Port Online;g=0x27352                   A2,P0  A2,P1  23    NA  

16:28:20.544 Port Elp engaged                            A2,P1  A2,P0  23    NA  

16:28:20.544 SCN Port F_PORT                             A2,P1  A2,P0  23    NA  

16:28:20.544 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:28:21.068 SCN Port Offline;g=0x27354                  A2,P0  A2,P0  23    NA  

16:28:21.068 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:28:33.717 SCN LR_PORT (0);g=0x27354                   A2,P0  A2,P0  23    NA  

16:28:33.717 SCN Port Online;g=0x27354                   A2,P0  A2,P1  23    NA  

16:28:33.717 Port Elp engaged                            A2,P1  A2,P0  23    NA  

16:28:33.717 SCN Port F_PORT                             A2,P1  A2,P0  23    NA  

16:28:33.717 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:28:34.184 SCN Port Offline;g=0x27356                  A2,P0  A2,P0  23    NA  

16:28:34.184 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:28:46.868 SCN LR_PORT (0);g=0x27356                   A2,P0  A2,P0  23    NA  

16:28:46.868 SCN Port Online;g=0x27356                   A2,P0  A2,P1  23    NA  

16:28:46.868 Port Elp engaged                            A2,P1  A2,P0  23    NA  

16:28:46.868 SCN Port F_PORT                             A2,P1  A2,P0  23    NA  

16:28:46.868 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

16:28:47.326 SCN Port Offline;g=0x27358                  A2,P0  A2,P0  23    NA  

16:28:47.326 *Removing all nodes from port               A2,P0  A2,P0  23    NA  

Number of entries: 16384

Max number of entries: 16384

External Moderator
Posts: 5,654
Registered: ‎02-23-2004

Re: 48K ISL-Trunk problem

This is very interesting Error.

Are the EDGE Switch ISL to 48K Core connected as Single ISL or DUAL ISL ?

TechHelp24
Anonymous
Posts: 0

Re: 48K ISL-Trunk problem

If you have many lines which point to port 23 with the same pattern in you fabric log then you have a so called flapping port.

You have to make sure that SFPs and cables on both ends are OK.

These link resets cause IO errors on the devices.

As well this can cause frame drops randomly in the fabric which includes the ISLs.

Very often you can see a problem on the ISL but the ISL is only the point where it gets visible. In such a case can you change all ISL related components but the error will still remain and jump to the next port.

You have to find the device which is causing the errors. Please use porterrshow command and statsclear to reset the counter and check for dicard C3 frames or any other errors on the ports on the entire fabric.

Andreas

Anonymous
Posts: 0

Re: 48K ISL-Trunk problem

hit techelp24,

there are 4 trunking link from edges to cores (all switchs are 48k). Every trunking has 3 isl links

Anonymous
Posts: 0

Re: 48K ISL-Trunk problem

Hi Andreas,

thanks for your help

i'm going to ask to my customer of i can (!!!!) execute your advices.

i'll let you know ASAP (it depends of my customer)

thanks again

/max

External Moderator
Posts: 5,654
Registered: ‎02-23-2004

Re: 48K ISL-Trunk problem

I ask a bit different,

--->>>....of course, and there are a isl-Trunk between the Cores (not between the edges)

between the EDGE - accordly you preview Post, you wrote is not in a Trunk, ( I inderstand those EDGE are connected ) is any ISL connection active ?

TechHelp24
Anonymous
Posts: 0

Re: 48K ISL-Trunk problem

hi,

no i haven't any ISL link between the edges.

Max

Anonymous
Posts: 0

Re: 48K ISL-Trunk problem

Hi Andreas,

my customer said to me that during the temporary isl down, the problem affects entire fabric , entire fabric seems to go down.

I don't know to find the solution because, fromn edge to core, i have 4 trunking with 3 ISL link per trunking.

It's seems just one ISL link down is enough to get down the entire fabric.

i'm trying to gain a window to do

porterrshow

statsclear

Thanks again

Max

Anonymous
Posts: 0

Re: 48K ISL-Trunk problem

max,

A window for non disruptive manamgement tasks sound like a customer without any knowledge and without any pain ;-)

If the ISL are overloaded and you disable a single ISL will cause more porblems due to less buffers avaliable. So add additional ISLs into the SAN.

Andreas

Anonymous
Posts: 0

Re: 48K ISL-Trunk problem

infact Andreas,

this is MY REAL MAIN problem.

i've already tried to explain it to him  MANY TIMES... :-(

i'mo going to suggest to him increasing isl link into the trunking.....

Join the Broadcom Support Community

Get quick and easy access to valuable resources across the Broadcom Community Network.