Fcip on nx-os 5.2 (6a) MDS9513

I have an fcip connection to our DR site that is working just fine. There are 4, 1 Gb connections in a port-channel. I've taken 2 of the connections out to use them for a connection to our new datacenter.  ip layer appears to be fine, pings work great. Fcip interfaces will not come up. I've been through all the standard check this, check that guides and I'm good. 
I'm starting to look at the Cisco debug ips fcip feature. Anyone have some hints on this? So far I get no output. 

Can you please post the proper show commands for the fcip interfaces, resp. pc.
what is the error message of the fcip interfaces (also show logging log in general)

Similar Messages

  • Strange FCIP Issue (# of connections)

    Is anyone aware of the number of FCIP connections you can have on an MDS9513 with
    Sup (Gen2) 3.2(2c)
    14+2 (Gen1) 3.2(2c)
    18+4 (Gen2) 3.2(2c)
    We are in the process of replacing the 14+2 with the 18+4 - However it would seem I have encountered a strange restriction/failure when I come to configure the 18+4 GigE ports with the 14+2 GigE ports still configured (FCIP profiles, Tunnels etc) and Linecard installed (though admin down)
    Though we have managed to configure at least 1 GigE Port on the 18+4 linecard, the issue is when trying to configure an additional FCIP channel on the 18+4. One side of the physical direct connected Pairing indicates as up and operational ie (GigE 5/1 to GigE 5/1). Its PEER FAILS to become Operational (Up) and continues to maintain in an Initialisation state and thus preventing a Tunnel to be created regardless of which GigE port is used. The following as been investigated:
    •Change SFP - Fault still apparent
    •Change Cable - Fault still apparent
    •Change GigE Port pairing (ie 5/4<-->5/4) - Fault still apparent
    •Investigate/Debug FCIP Profile for mis-configuration (ie PEER IP, passive mode, listening Port etc) - No mis-configuration found between pairing
    •Investigate/Debug FCIP Interface for mis-configuration (ie PEER IP etc) - No mis-configuration found between pairing
    •Licensing Checked - SAN_EXTN_OVER_IP_18_4 - Installed and in use on all switches
    Since we have a dual Fabric Design - Fabric B exhibited the same symptoms with no additional configuration having been applied (ie no additional FCIP tunnels created), would seem to indicate at this moment in time that it maybe its a Gen1/Gen2 and/or Licensing issue.
    The only thing left is to actually remove the 14+2 linecard.
    Any thoughts?

    Thanks Vijay for respond..
    I am not using any transformation or Mapping. I configured a DB Adapter first. Then make a BPEL Process having input and output according to DB Adapter XSD file. then i just invoked and copied the output of procedure to output of payload.
    Thanks
    Nasir

  • Connecting an IP RJ45 Device to an MDS9513

    Is the following possible:
    Site_A
    Netapp filer (RJ45-IP Traffic)<------> MDS9513 (module ???-RJ45 SFP) <------> MDS9513 DS-X9304-18K9 (Gen2) (GigE LCC) <---------> DWDM Mux <------> to Site B
    Site_B
    From Site_A <-------> DWDM Mux <-------> MDS9513 DS-X9304-18K9 (Gen2) (GigE LCC) <------> MDS9513 (module ???-RJ45 SFP) <------> Netapp filer (RJ45-IP Traffic)
    In Essence - Connecting a Netapp Filer via its RJ45 port with IP Traffic to an MDS9513. Then Routing the IO out via a Shared DWDM Link to another Netapp filer at a different Site..
    Purpose to share an already exsisting SAN Fabric DWDM Link between MDS9513 at 2 sites.
    Or does the MDS9513 only support IP Protocols via FCIP
    Kind Regards,
    MD

    Hi Dynamoxxx,
    Yes you are absolutely right - it is for Netapp Replication "SnapMirror".... and Yes normally you would like to connect over an exsisting IP Network, but the current  Linki is highly Utilised and the Client would like to investigate all avenues to reduce TCO...
    Hence because we already have an exsisting SAN Storage connection which goes:
    EMC Array <----> MDS9513(FCIP) <----> CISCO 3560 <----> DWDM Mux <-------> DWDM Mux <----> CISCO 3560 <-----> MDS9513(FCIP) <----> EMC Array
    It was questioned can we use could we utilise the SAN Link.... 2 Options seemed to devople from this
    Opt 1- Connect via the CISCO 3560. But this would mean we have No method of controlling or putting QoS to ensure SAN IO traffic get prioirty over SnapMirror.
    Opt 2 - Connect via the MDS9513 - Which may give us the QoS control..... But how that is achieved is what I am trying to get to grips with to see if its viable.

  • Total time to FCIP Tunnel be disconnected

    I use MDS9222i to Extend SAN with FCIP.
    In my FCIP profile,
    tcp min-retransmit-time is 300ms,
    tcp max-retransmission is default(Maximum number of re-transmissions is 4).
    With these two value,
    Can I calculate the time that the FCIP tunnel to be disconnected when WAN circuit is down ?
    I think it is 4.5s(0.3s+0.6s+1.2s+2.4s). Is that right?

    Hi,
    Please try this.
    Define three user variables - StartTime, EndTime and Duration.
    At the start of the quiz ('On Slide Enter' of the first Question Slide). have an advanced action with the following actions.
    Assign: StartTime with cpInfoElapsedTimeMS  
    Continue
    At the end of the quiz ('On Success' or 'On Failure' of the last Question Slide or 'On Slide Enter' of Result Slide), have this advanced action.
    Assign: EndTime with cpInfoElapsedTimeMS
    Expression: Duration = EndTime - StartTime
    Expression: Duration = Duration / 1000
    Continue
    The variable 'Duration' will have the time taken by the user for the Quiz in seconds.
    Let me know if you have any queries.
    Thanks,
    Thejas

  • FCIP tunnels configuration and validation

    Hello,
    I have configured FCIP tunnels before where each tunnel is placed in its own subnet.  I couldn't find any documentation that would show that this has to be the case or this is best practice. 
    I am configuring a scenario where there are two pairs of MDS, one pair per Data Center (Fabric A and B)
    So for DC01
    Fabric A switch ip address for each interface (there are four gigabit interfaces) are the following (IPs have been changed but concept should remain the same):
    Switch A - DC01
    GigabitEthernet6/1 - 1.1.1.1
    GigabitEthernet6/2 - 1.1.1.2
    GigabitEthernet6/3 - 1.1.1.3
    GigabitEthernet6/4 - 1.1.1.4
    Switch B - DC01
    GigabitEthernet6/1 - 1.1.1.5
    GigabitEthernet6/2 - 1.1.1.6
    GigabitEthernet6/3 - 1.1.1.7
    GigabitEthernet6/4 - 1.1.1.8
    Switch A - DC02
    GigabitEthernet6/1 - 2.2.2.1
    GigabitEthernet6/2 - 2.2.2.2
    GigabitEthernet6/3 - 2.2.2.3
    GigabitEthernet6/4 - 2.2.2.4
    Switch B - DC02
    GigabitEthernet6/1 - 2.2.2.5
    GigabitEthernet6/2 - 2.2.2.6
    GigabitEthernet6/3 - 2.2.2.7
    GigabitEthernet6/4 - 2.2.2.8
    Does anyone see any issues that might arise if tunnels are not necessarily placed in their own subnet? 
    I have added the full configuration of Switch A and B for DC01 at the very bottom for further clarification.
    Switch DC01_A
    fcip profile 1
    ip address 1.1.1.1
    fcip profile 2
    ip address 1.1.1.2
    fcip profile 3
    ip address 1.1.1.3
    fcip profile 4
    ip address 1.1.1.4
    vsan database
    vsan 10
    interface port-channel 10
    switchport trunk allowed vsan 10
    interface fcip1
    channel-group 10 force
    no shutdown
    use-profile 1
    peer-info ipaddr 2.2.2.1
    interface fcip2
    channel-group 10 force
    no shutdown
    use-profile 2
    peer-info ipaddr 2.2.2.2
    interface fcip3
    channel-group 11 force
    no shutdown
    use-profile 3
    peer-info ipaddr 2.2.2.3
    interface fcip4
    channel-group 10 force
    no shutdown
    use-profile 4
    peer-info ipaddr 2.2.2.4
    interface GigabitEthernet6/1
    ip address 1.1.1.1 255.255.255.0
    switchport mtu 3000
    no shutdown
    interface GigabitEthernet6/2
    ip address 1.1.1.2 255.255.255.0
    switchport mtu 3000
    no shutdown
    interface GigabitEthernet6/3
    ip address 1.1.1.3 255.255.255.0
    switchport mtu 3000
    no shutdown
    interface GigabitEthernet6/4
    ip address 1.1.1.4 255.255.255.0
    switchport mtu 3000
    no shutdown
    Switch DC01_B
    fcip profile 1
    ip address 1.1.1.5
    fcip profile 2
    ip address 1.1.1.6
    fcip profile 3
    ip address 1.1.1.7
    fcip profile 4
    ip address 1.1.1.8
    vsan database
    vsan 10
    interface port-channel 10
    switchport trunk allowed vsan 10
    interface fcip1
    channel-group 10 force
    no shutdown
    use-profile 1
    peer-info ipaddr 2.2.2.5
    interface fcip2
    channel-group 10 force
    no shutdown
    use-profile 2
    peer-info ipaddr 2.2.2.6
    interface fcip3
    channel-group 11 force
    no shutdown
    use-profile 3
    peer-info ipaddr 2.2.2.7
    interface fcip4
    channel-group 10 force
    no shutdown
    use-profile 4
    peer-info ipaddr 2.2.2.8
    interface GigabitEthernet6/1
    ip address 1.1.1.5 255.255.255.0
    switchport mtu 3000
    no shutdown
    interface GigabitEthernet6/2
    ip address 1.1.1.6 255.255.255.0
    switchport mtu 3000
    no shutdown
    interface GigabitEthernet6/3
    ip address 1.1.1.7 255.255.255.0
    switchport mtu 3000
    no shutdown
    interface GigabitEthernet6/4
    ip address 1.1.1.8 255.255.255.0
    switchport mtu 3000
    no shutdown

    I forgot to mention that I will have host static routes for reachability
    So from Switch A DC01
    ip route 2.2.2.1 255.255.255.255 interface gigabitethernet 6/1
    ip route 2.2.2.2 255.255.255.255 interface gigabitethernet 6/2
    ip route 2.2.2.3 255.255.255.255 interface gigabitethernet 6/3
    ip route 2.2.2.4 255.255.255.255 interface gigabitethernet 6/4

  • What is the best practice for QOS in an MDS 9000 environment for the FCIP traffic?

    Our storage group is implementing an MDS 9000 FCIP environment.  The person configuring the Nexus equipment is asking what QOS markings and bandwidth requirements should be used for the FCIP traffic.
    Is there a document that describes the QOS recommendations for MDS FCIP?

    Hello
    You can change the DB isolation level to Read uncommitted
    http://technet.microsoft.com/en-us/library/ms378149(v=sql.110).aspx
    or use WITH (NOLOCK)
    I do use NOLOCK option for the dirty reads to avoid locks on the tables
    Javier Villegas |
    @javier_vill | http://sql-javier-villegas.blogspot.com/
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

  • FCIP interface stuck at initializing on 9216i v2.1a (vsan segmented)

    Following the instructions in both the config guide and troubleshooting guide to configure the FCIP profile and interface, my fcip2 interface status is stuck at initializing. Looking in FM events tab, I can see that the 9216i's are cycling between these states: vsan merged; N_Port unmanageble; vsan segmented and N_Port Up. show fcdom domainlist on the higher priority switch shows it flip-flopping between [local] and principal] [local] states. Using show zoneset active, I can see the zoneset being transfered over to the 2nd switch. Despite all this, the fcip interface does not stay up. Thanks for helping.

    Just going from your info, it sounds like the interface comes up for a little bit of time. More than likely then, the issue is MTU. You have an MTU configured larger than somewhere in the network can handle it. If you get the show log output and it shows alot of TCP retransmissions, this is the problem.

  • FCIP Peer in the same VLAN

    Hi,
    I will have 2 data centre connected with a 1gb possibly 2 x 1gb ethernet link.
    There will be some 802.q trunking between location and some traffic will be routed.
    I have the option of having my FCIP peer in the same vlan and carried in the trunk. Or have them in different VLAN and routed between location.
    Initiallay I though routed would be good because I can use QoS to prioritise FCIP traffice.
    But could I still achieve this using single vlan. and is it allowed.
    both site are connect using 6509 with sup720s
    Thanks
    John

    Hi John,
    For the FCIP link it is just an IP connectivity. So, you can do in both ways as you describe. You can route it or use a vlan. Just make sure that you have no too hign RTT. And also there RTT timout setting on FCIP you can play with that according to your RRT in your network.
    Thanks,
    Hakan.

  • Fcip link flapping priodically

    We have a 9509 at the HQ site and a 9216 in the DR site connected via a DS3.
    There are preiodic times when the fcip link will flap and come back up, sometimes it will continue for minutes and has happened for several hours with this error:
    %PORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: %$VSAN 50%$ Interface fcip1 is down(TCP conn. closed - retransmit failure)
    originally the fcip profile was configured for 1000 max bandwidth and it was suggested to change it to something closer to the DS3 and this change was made:
    fcip profile 1
    ip address 10.1.2.1
    tcp max-bandwidth-mbps 41 min-available-bandwidth-mbps 30 round-trip-time-ms 4
    tcp send-buffer-size 5000
    It made no difference at all. There is connectivity to the DR site during the flapping, I can see the bandwidth spike up, but there should be plenty to handle the load during the flapping.
    Last night the serial interface of the DS3 was showing the tx load 65/255 and rx was 5/255 during the problem.
    I am wondering, would the "min bandwidth" setting cause a "retransmit failure"?
    That seems like more of a tcp/ip issue that an interface configuration issue, but I cannot find any reason for the flap.
    No interface errors, but I have seen the ping response times go from 3ms to 25ms during this time, an indication of congestion somewhere.
    Does anyone have any ideas?
    There ar no errors on any of the interfaces for the DS3 or the fcip.

    thanks for the reply,
    Where do I make these changes and can you explain the logic behind them?
    "enabling ip compression" I think compression is enabled in mode1 if I remember correctly
    "and disabled fccit" what does this do?
    "change the Rx buffer to defaults 16" is this in place of:
    tcp send-buffer-size 5000
    Are you talking about 16K rather than 5K?

  • FCIP link issues

    We have a 9509 at the HQ site and a 9216 in the DR site connected via a DS3.
    There are periodic times when the fcip link will flap and come back up, sometimes it will continue for minutes and has happened for several hours with this error:
    %PORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: %$VSAN 50%$ Interface fcip1 is down(TCP conn. closed - retransmit failure).
    My manager is telling me it is a setting on the FCIP profile and it is impossible the DS3 could be congested because it is a point to point link.
    Verizon is also telling me it is a Cisco problem having to do with fragmentation.
    Originally the fcip profile was configured for 1000 max bandwidth and it was suggested to change it to something closer to the DS3 and this change was made:
    fcip profile 1
    ip address 10.1.2.1
    tcp max-bandwidth-mbps 41 min-available-bandwidth-mbps 30 round-trip-time-ms 4
    tcp send-buffer-size 5000
    It made no difference at all. There is connectivity to the DR site during the flapping, I can see the bandwidth spike up, but there should be plenty to handle the load during the flapping.
    The time I had this problem the serial interface of the DS3 was showing the tx load 65/255 and rx was 5/255.
    No interface errors, but I have seen the ping response times go from 3ms to 25ms during this time, an indication of congestion somewhere.
    There are no errors on any of the interfaces for the DS3 or the fcip.
    I have tried numerous different profile settings and nothing has made a differnce.
    I have opened a TAC case and Cisco could find no reason for the flapping and suggested a carrier issue.
    Does anyone have any ideas?
    Any suggestion would be appreciated.

    what version of SAN-OS are you running?
    Are you using IP Compression and if so what mode?
    what alerts are the peer switch sending when the link flaps?
    we ran into a new bug when upgrading to SAN-OS 3.1(3a). if using IP compression set to (auto). 'auto' uses a combination of both software and hardware based compression depending on the type of traffic, load, bandwidth, etc.. the software portion of the ip compression in SAN-OS 3.1(3a) wiggs out dealing with packet buffers. this would cause our fcip profile to bounce randomly anywhere from 10-20 times a day. EMC SAC and Cisco TAC had me enable IPS full core dumps to a tftp server. from there they were able to determine that it was specifically the 'auto' setting in IP compression on the MPS 14/2 blades on the MDS 9216i's. we then set the IP compression to 'mode1', which is all hardware based compression, on all switches and that resolved our issue with the fcip profile flapping.

  • Write Acceleration on FCIP tunnels degrading Mirrorview performance

    Disaster Recovery(DR)for storage:
    Odd fabric:MDS1 (fcip1)----> MDSDR(fcip1)
    Even fabric: MDS1(fcip3)----> MDSDR (fcip3)
    Link details: b/w=2.0g,latency(7ms)
    fcip Link on the MDS is on 14+2 card.
    Ip compression mode=1 turned on.
    WriteAcceleration turned on.
    Without WA enabled, fcip1 traffic is in MB consistently.
    With WA enabled, fcip1 traffic degrades to < 5KB. Lots of small 100-300B pkts seen on the Source TX and receive RX of fcip1.

    So I would leave WA off if there is no performance gain. So, you have 2G total BW for 2 FCIP links? So, what are the min/max values on the tcp profile? If this is more than 100MB/sec, I would suggest leaving compression off as more than likely it takes longer to compress than just to send it. Compression is done in HW in mode1 on the 14/2 and 9216i cards and done in SW for the IPS4 and IPS8 cards. Above 100M you will see more gain from setting the MTU from end to end to 2300.

  • IPSEC w/ 2 FCIP tunnels using a single gigE port

    A gig1/1 interface on a 9216i is servicing 2 FCIP tunnels (port 3225 & 3737) from 2 other 9216i switches. The FCIP ISL connecting to port 3225 has IPSEC configured and is working (trunking). The FCIP ISL connecting to port 3737 was trunking prior to configuring IPSEC for it, but now with IPSEC configured it is now broken. Looking through the IPSEC trouble shooting section, I'm not seeing any conflicting IPSEC/IKE parameters.
    Is it possible to have IPSEC services working for 2 FCIP ISLs connecting to a single gig port? If so, I'm at a loss on how to properly configure it.
    Thanks, Craig

    Understand and that is the case there is only one crypto map assigned with the appropriate ACL, but still the connecution using port 3737 will not establish a connection. Here cmap definintion.
    Crypto Map "cmap30" 10 ipsec
    Peer = 211.175.105.69
    IP ACL = acl30
    permit ip 87.61.121.2 255.255.255.255 211.175.105.69 255.255.255.255
    permit ip 87.16.121.2 255.255.255.255 211.175.105.85 255.255.255.255
    Transform-sets: tfs30,
    Security Association Lifetime: 450 gigabytes*/3600 seconds*
    (* global configuration value)
    PFS (Y/N): Y
    PFS Group: group5
    Crypto Map "cmap30" 20 ipsec
    Peer = 211175.105.85
    IP ACL = acl30
    permit ip 87.61.121.2 255.255.255.255 211.175.105.69 255.255.255.255
    permit ip 87.16.121.2 255.255.255.255 211.175.105.85 255.255.255.255
    Transform-sets: tfs30,
    Security Association Lifetime: 450 gigabytes*/3600 seconds*
    (* global configuration value)
    PFS (Y/N): Y
    PFS Group: group5
    Interface using crypto map set cmap30:
    GigabitEthernet1/1

  • Cisco MDS9216i VSAN not merging and FCIP up but not trunking

    I have configured FCIP between DC and DR IPSAN switches. FCIP is up but not trunking. On both switches trunk mode is on. Hence my VSAN (id 20 on both switches) not merging.
    See below FCIP interface status...
    fcip1 is up
    Hardware is GigabitEthernet
    Port WWN is 20:10:00:0d:ec:35:68:40
    Peer port WWN is 20:10:00:0d:ec:34:d6:80
    Admin port mode is auto, trunk mode is on
    snmp traps are enabled
    Port mode is E, FCID is 0x9a0002
    Port vsan is 1
    Speed is 1 Gbps
    Using Profile id 1 (interface GigabitEthernet1/1)
    Peer Information
    Peer Internet address is 10.128.1.95 and port is 3225
    Write acceleration mode is configured off
    Tape acceleration mode is configured off
    Tape Accelerator flow control buffer size is automatic
    Ficon Tape acceleration configured off for all vsans
    IP Compression is disabled
    Special Frame is disabled
    Maximum number of TCP connections is 2
    Time Stamp is disabled
    QOS control code point is 0
    QOS data code point is 0
    B-port mode disabled
    TCP Connection Information
    2 Active TCP connections
    Control connection: Local 10.132.1.95:65260, Remote
    10.128.1.95:3225
    Data connection: Local 10.132.1.95:65262, Remote 10.128.1.95:3225
    138 Attempts for active connections, 16 close of connections
    TCP Parameters
    Path MTU 1420 bytes
    Current retransmission timeout is 200 ms
    Round trip time: Smoothed 22 ms, Variance: 4 Jitter: 661 us
    Advertized window: Current: 2412 KB, Maximum: 2412 KB, Scale: 5
    Peer receive window: Current: 2047 KB, Maximum: 2047 KB, Scale: 5
    Congestion window: Current: 1170 KB, Slow start threshold: 1950 KB
    Current Send Buffer Size: 2412 KB, Requested Send Buffer Size: 0 KB
    CWM Burst Size: 50 KB
    5 minutes input rate 328 bits/sec, 41 bytes/sec, 0 frames/sec
    5 minutes output rate 256 bits/sec, 32 bytes/sec, 0 frames/sec
    3551 frames input, 419612 bytes
    3443 Class F frames input, 406076 bytes
    108 Class 2/3 frames input, 13536 bytes
    8 Reass frames
    0 Error frames timestamp error 0
    3572 frames output, 324264 bytes
    3464 Class F frames output, 312996 bytes
    108 Class 2/3 frames output, 11268 bytes
    0 Error frames
    I have one more pair of IPSAN switches. I configured them which are working fine. FCIP interface is showing "trunking". I have compared the configuration of working and non-working pairs and both are same (except the IP address of locate and remote and VSAN ids).
    Please suggest what can be done. If I get the FCIP port in trunking, I hope VSAn will start merging.

    The problem is here -
    Port mode is E, FCID is 0x9a0002
    Port vsan is 1
    What it says is yes, it is a trunk , but only an E port. So it is only trunking the port VSAN 1. What you want to do is change it to a Trunking E port, which allows it to carry multiple vsans over the link.
    The other option is to change the port VSAN to 20. That will get you up, but if you need to trunk more vsans in the future you will still have to change the FCIP to a TE port.
    When everything is right it should look something like this -
    P28-MDS-9216# sho interface fcip 2
    fcip2 is trunking
    Hardware is GigabitEthernet
    Port WWN is 20:42:00:0d:ec:0c:e6:40
    Peer port WWN is 20:42:00:0d:65:6a:18:40
    Admin port mode is auto, trunk mode is on
    snmp traps are enabled
    Port mode is TE
    Port vsan is 1
    Speed is 1 Gbps
    Trunk vsans (admin allowed and active) (1,20)
    Trunk vsans (up) (1,20)
    Trunk vsans (isolated) ()
    Trunk vsans (initializing) ()
    Using Profile id 1 (interface GigabitEthernet2/1)
    Peer Information
    Peer Internet address is 10.2.28.2 and port is 3225
    Write acceleration mode is configured off
    Tape acceleration mode is configured off
    Tape Accelerator flow control buffer size is automatic
    Ficon Tape acceleration configured off for all vsans
    IP Compression is disabled
    Special Frame is disabled
    Maximum number of TCP connections is 2
    Time Stamp is disabled
    The document for configuring FCIP trunks on the MDS is available here -
    http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/3_0/clicnfg/part6/cfcip.htm
    If you found this helpful please rate it -
    -- Colin McNamara

  • 5428-2 , brocade switches and ql2200 with fcip

    I keep on getting these messages when I connect a Qlogic ql2200 adapter to 5428 that's using FCIP between two SAN's that are using Brocade 3800 switches:
    Mar 13 08:21:06: %FC-5-PortOperChange: PortOperChange;2959;0;0;1
    I assume that I don't have the 5428 setup correctly for the ql2200 and I understand that there's a CISCO white paper describing how to set up the 5428 for interoperability with the Brocade switches and Adapaters. Could I please get a copy. Thanks

    I'm trying the vary basics. I disconnected the GE ports from each 5428. I cleared the configuration on one of the 5428's with the "clear conf" command. I then setup the basic information and did a "setup". I plug the fibre cable from the ql2200 into fibre channel port 1. Here's what I get when I run the nameserver command:
    [sm542802]# show fcswitch nameserver all
    0 entries found
    [sm542802]#
    So my problem is that the qlogic adapter is just not seen by the 5428 when I use the default settings.
    If I set the 5428 fc1 port to 1Gb/sec, then I get the following messages...
    Mar 15 17:14:22: %FC-5-PortOperChange: PortOperChange;670;0;0;1
    Mar 15 17:14:24: %FC-5-PortOperChange: PortOperChange;671;0;0;1
    Mar 15 17:14:26: %FC-5-PortOperChange: PortOperChange;672;0;0;1
    Mar 15 17:14:28: %FC-5-PortOperChange: PortOperChange;673;0;0;1
    Mar 15 17:14:30: %FC-5-PortOperChange: PortOperChange;674;0;0;1
    Mar 15 17:14:32: %FC-5-PortOperChange: PortOperChange;675;0;0;1
    Mar 15 17:14:34: %FC-5-PortOperChange: PortOperChange;676;0;0;1
    Mar 15 17:14:36: %FC-5-PortOperChange: PortOperChange;677;0;0;1
    Mar 15 17:14:45: %FC-5-PortOperChange: PortOperChange;678;0;0;1

  • Port channelling on two MDS9513's

    Hi, I have two MDS9513's running SANOS 3.3. I have four ISL's between the switches but when i try and set up port channelling i get the message 'no ISL's available between MDS switches'. As yet the network is not live in our new data centre so i was wondering if SNMP is used at some point when setting up port channelling to identify switch type??? Enterprise license is installed on both switches.

    A couple of questions:
    - What sort of line cards are you using?
    - What VSAN's have you got configured?
    - What zoning policy do you have and have you got any active zonesets on either switch?
    - Have you setup switch priorities?
    It is probably a defect identified as CSCsg27664.

Maybe you are looking for