Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

mr
New Member

FCP ISL theoretical question

Hi,

I' ve got a theoretical question about the behaviour of ISL at Cisco MDS switches:

I heard, that during a transfer (a continuous sequence of frames) between a target and an initiator (each of them are on seperated switches, which are connected with only one ISL), no other end device can use the ISL. When the sequence of frames (same OX ID, RX ID) is transfered, another end device can use the ISL.

There is no "multiplexing" of the ISL.

Q1: Is this true?

Q2: If yes, what happend, if you tranfer a lot of data between one target & one initiator. Is there a congestion on the isl for all other devices?

Regards

Markus

1 ACCEPTED SOLUTION

Accepted Solutions
New Member

FCP ISL theoretical question

Markus,

The MDS doesn't transfer entire exchanges at a time on a given ISL.  Meaning OXID1, OXID2 etc... It will transmit the frames as they arrive.  Such that you could transfer over the ISL:

OXID1Frame1, OXID2Frame1, OXID1Frame2, OXID1Frame3

The second problem could occur in a situation in which the receiver's buffers were full and thereby the TX port on the switch egress frames out of the switch, then the Virtual Output Queue could fill up (for which there is one assigned to every input port for every output port) and eventually the TX side of the ISL would run out of buffers.  To completely avoid this, you would need per flow buffer 2 buffer credits.  As a note the number of and depth of VOQ was designed to help avoid this situation as explained in this whitepaper and illustrated below.

http://www.cisco.com/en/US/prod/collateral/modules/ps5991/images/prod_white_paper0900aecd8044c7e3-06.jpg

-Seth

2 REPLIES
New Member

FCP ISL theoretical question

Markus,

The MDS doesn't transfer entire exchanges at a time on a given ISL.  Meaning OXID1, OXID2 etc... It will transmit the frames as they arrive.  Such that you could transfer over the ISL:

OXID1Frame1, OXID2Frame1, OXID1Frame2, OXID1Frame3

The second problem could occur in a situation in which the receiver's buffers were full and thereby the TX port on the switch egress frames out of the switch, then the Virtual Output Queue could fill up (for which there is one assigned to every input port for every output port) and eventually the TX side of the ISL would run out of buffers.  To completely avoid this, you would need per flow buffer 2 buffer credits.  As a note the number of and depth of VOQ was designed to help avoid this situation as explained in this whitepaper and illustrated below.

http://www.cisco.com/en/US/prod/collateral/modules/ps5991/images/prod_white_paper0900aecd8044c7e3-06.jpg

-Seth

mr
New Member

FCP ISL theoretical question

Thanks, that was what I want to heard... I read this in an article and was not sure about this behaviour.

Regards Markus

439
Views
0
Helpful
2
Replies