Uplink-ID 0 in Nexus 5500 with FEX 2248.

Hi all,
I've got 2 Nexus 5548 and a fex 2248 connected to both of them via a vPC. 1 Uplink port goes to N5K-01 e1/10 and a second Uplink port goes to N5K-02 to port e1/10.
On the log of the first Nexus 5500 I see this:
N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
N5K-01 1 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
On the log of the second nexus 5500, I see this:
N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
What is the difference between Uplink-ID 0, 1 and 2? If I only have 2 uplink ports, why is there a third one?
Thanks in advace for your assistance.

Hi Sonu,
I see the similar problem on my nexus5ks. show cfs peer does not display the peer information. I have been waiting for hours now.
sw01# sh cfs peerCFS Discovery is in Progress ..Please waitCould not get response. The network topology may be under going change.Please try after about 30 seconds
Did you find the fix7workaround of this problem ?
Regards,
Umair

Similar Messages

  • Connecting the nexus 5500 with multiple vsans

    Hi,
    it's my first experience in the fibre channel world and i have a few doubts about the best way to connect the nexus 5500 to a EMC storage.
    This is my scenario
    this is my configuration:
    vsan database
    vsan 2
    vsan 2 interface fc 1/1
    vsan 3
    vsan 3 interface fc 1/2
    interface fc1/1
    switchport mode f
    no shut
    interface fc1/2
    switchport mode f
    no shut
    now I don't know how can I connect the port fc1/3 to the vnx storage, I think I can't make a trunk like ethernet, can anyone help me?
    Or i only can do this with zoning
    Thanks
    Fred

    Hello Fred,
    All interfaces must be in the same vsan for them to see each other
    vsan database
    vsan 2 interface fc1/1, fc1/2, fc1/3
    exit
    Then you can zone each separately
    example:
    zone name host1 vsan 2
    member pwwn 11:11:11:11:11:11:11:11    (host1 pwwn)
    member pwwn 33:33:33:33:33:33:33:33    (VNX)
    zone name host2 vsan 2
    member pwwn 22:22:22:22:22:22:22:22    (host2 pwwn)
    member pwwn 33:33:33:33:33:33:33:33    (VNX)
    zoneset name Zoneset1 vsan 2
    mem host1
    mem host2
    zoneset activate name Zoneset1 vsan 2
    Thanks

  • Layer 3 config design on Nexus 5500 with Fabric Path

    I trying to Network deisgn for new data Center ,  i am new to DataCenter desgin, i attached the network diagram
    i would like to know if can configure my layer3 on 5500 and configure Fabric path to uplink switch
    please help give your suggestions on this design 

    You can configure layer-3 on the 5500 series, but you need to install a daughter cards in each 5500.
    See this link:
    Layer 3 Daughter Card and Expansion Module Options for Cisco Nexus 5548P, 5548UP, 5596UP, and 5596T Switches
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html
    HTH

  • Fabricpath with FEX topology

    I am currently deploying Nexus 5500 with Fabric path & deploying FEX as well. If you look at the FEX data sheet they talked about 4 different topology.
    I have 2 question.
    Please see link below:
    http://www.cisco.com/c/en/us/products/collateral/switches/nexus-2000-series-fabric-extenders/data_sheet_c78-507093.html
    With Fabricpath vPC+ I am seeing only Single Home FEX.
    1 Does this mean only Single home FEX supported with Fabricpath vPC+ ?
    2 Also I am seeing lot of debate on Single Home FEX vs Dual Home FEX & there is no right answer to the question what is better but for the design simplicity & troubleshooting I like the Single home FEX with Servers dual homed to the different FEX.
    Thank in Advance
    Sincerely
    Viral Patel

    Simens,
    Please check the below link if this is helpfull:
    http://adamraffe.com/2013/08/23/anycast-hsrp-4-way-hsrp-with-fabricpath/

  • NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX

    Hi All,
             Please tell me how to do "NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX" without downtime for FEX.
    The Server are connected to FEX.
    Attached the diagram.

    Hi,
    If the 5500s are layer-2 with vPC running between them than you can use ISSU to upgade.
    here is doc to follow:
    ISSU Support for vPC Topologies
    An ISSU is completely supported when two switches are paired in a vPC configuration. In a vPC configuration, one switch functions as a primary switch and the other functions as a secondary switch .They both run the complete switching control plane, but coordinate forwarding decisions to have optimal forwarding to devices at the other end of the vPC. Additionally, the two devices appear as a single device that supports EtherChannel (static and 802.3ad) and provide simultaneously data forwarding services to that device.
    While upgrading devices in a vPC topology,you should start with the switch that is the primary switch. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue their control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).
    This example shows how to determine the vPC operational role of the switch:
    link:
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/513_N1_1/n5k_upgrade_downgrade_513.html
    HTH

  • NEXUS 56128 and FEX with beakout cable

    Hello,
    using two NEXUS 56128 , I wish to create enhanced VPC architecture with FEX 2248TP.
    My question is : can I use 40Gbs ports on NX56128 with QSFP breakout DAC cable (40G to 4x10G) to connect FEX 2248 ?
    regards

    Hi Yallies,
    For the Nexus 56128 (http://cs.co/9002c2aC) , it supports 8 true 40 GE QSFP ports and up to 96 10GE ports ( of which 48 are UP). Since the Nexus 5600 supports high density fabric extender aggregation platform, they can be used with the Nexus 2248PQ, 2248TP. Feel free to message me directly for further assistance. Hope this helps! :)
    Thanks,
    Angela ([email protected])

  • Nexus 5500 to Nexus 5500 Fiber Etherchannel with different lengths

    Hi,
    I'm in the very first phase of designing a small datacenter infrastructure based on the Nexus 5500 series. I haven't got any hands-on nexus experience yet so please forgive me if I'm asking a silly question here...
    What I would like to build is a 4 unit, redundant datacenter design. Two units in one DC, and two units in the other. I would like to connect both DCs together using a redundant darkfiber. One link is 10 miles, the other is 20 miles.
    The Nexus switches are going to be connected "back-to-back" with and the redundant etherchannel between the DCs, like this http://www.netcraftsmen.net/component/content/article/69-data-center/859-configuring-back-to-back-vpcs-on-cisco-nexus-switches.html
    Can I expect any problems with this design? In particular with the different lengths of fiber, like buffering issues or failing transmissions?
    Thanks!

    That should not be an issue.  You will need single mode fiber and single mode optics, and as long as all your optics support distance of 20 miles or more, then you should be fine.
    HTH

  • Cannot InterVlan on Cisco Nexus 5500

    Dear All,
    I have problem with my nexus 5500,
    Intervlan on my nexus not work,
    i dont know why..
    Before i have only this kind of license:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         No    -   Unused        -
    LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
    and feature i used is :
    - feature privilege
    - feature telnet
    - feature interface-vlan
    - feature hsrp
    - feature dhcp
    - feature lldp
    I make few vlan on nexus and then i check the interface status and the result is all vlan Interface is UP but intervlan is not work.
    And then, i install license for LAN_BASE_SERVICES_PKG, this is result for install licensed:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         Yes   -   In use Never       -
    LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
    I used vlan configuration vlan before, but the interface VLAN is DOWN/DOWN.
    and then i read this article:
    http://www.layerzero.nl/blog/2012/10/nexus-5000-non-routable-vdc-mode/
    Yes, thats solution work for 1 Vlan with "management" command on interface VLAN.
    But, the other vlan is still DOWN. and Intervlan is not work to.
    Anyone, can help me please?
    I have experience configure Nexus 5000 with VPC, FEX, Storage, etc, and everything fine without isue in intervlan.
    Thanks.

    Marvin,
    This is the output.
    `show module`
    Mod Ports Module-Type                       Model                  Status
    1   48    O2 48X10GE/Modular Supervisor     N5K-C5596UP-SUP        active *
    Mod  Sw              Hw      World-Wide-Name(s) (WWN)
    1    5.2(1)N1(1b)    1.0     --
    `show interface brief`
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        1       eth  trunk  up      none                        10G(D) --
    Eth1/2        1       eth  trunk  up      none                        10G(D) --
    Eth1/3        1       eth  trunk  up      none                        10G(D) --
    Eth1/4        1       eth  trunk  up      none                        10G(D) --
    Eth1/5        1       eth  trunk  down    Link not connected          10G(D) --
    Eth1/6        1       eth  trunk  up      none                        10G(D) --
    Eth1/7        1       eth  trunk  up      none                        10G(D) --
    Eth1/8        1       eth  trunk  down    Link not connected          10G(D) --
    Eth1/9        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/10       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/11       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/12       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/13       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/14       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/15       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/16       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/17       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/18       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/19       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/20       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/21       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/22       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/23       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/24       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/25       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/26       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/27       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/28       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/29       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/30       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/31       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/32       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/33       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/34       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/35       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/36       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/37       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/38       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/39       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/40       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/41       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/42       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/43       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/44       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/45       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/46       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/47       1       eth  trunk  down    SFP not inserted            10G(D) --
    Eth1/48       1       eth  trunk  down    SFP not inserted            10G(D) --
    Port   VRF          Status IP Address                              Speed    MTU
    mgmt0  --           down   --                                      --       1500
    Interface Secondary VLAN(Type)                    Status Reason                
    Vlan1     --                                      down   Administratively down 
    Vlan199   --                                      up     --       
    Vlan999   --                                      down   Non-routable VDC mode 
    sh ip int bri
    IP Interface Status for VRF "default"(1)
    Interface            IP Address      Interface Status
    Vlan199              192.168.36.10   protocol-up/link-up/admin-up      
    Vlan999              192.168.99.1    protocol-down/link-down/admin-up  
    sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/9, Eth1/10, Eth1/11
                                                    Eth1/12, Eth1/13, Eth1/14
                                                    Eth1/15, Eth1/16, Eth1/17
                                                    Eth1/18, Eth1/19, Eth1/20
                                                    Eth1/21, Eth1/22, Eth1/23
                                                    Eth1/24, Eth1/25, Eth1/26
                                                    Eth1/27, Eth1/28, Eth1/29
                                                    Eth1/30, Eth1/31, Eth1/32
                                                    Eth1/33, Eth1/34, Eth1/35
                                                    Eth1/36, Eth1/37, Eth1/38
                                                    Eth1/39, Eth1/40, Eth1/41
                                                    Eth1/42, Eth1/43, Eth1/44
                                                    Eth1/45, Eth1/46, Eth1/47
                                                    Eth1/48
    5    A                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    199  B                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    391  C                     active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    392  D                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    393  E                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    394  F                        active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    395  G                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    500  H                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    526  I                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    VLAN Type  Vlan-mode
    1    enet  CE    
    5    enet  CE    
    199  enet  CE    
    391  enet  CE    
    392  enet  CE    
    393  enet  CE    
    394  enet  CE    
    395  enet  CE    
    500  enet  CE    
    526  enet  CE    
    Remote SPAN VLANs
    Primary  Secondary  Type             Ports

  • Mix of Nexus 5500 & Catalyst 6500

    Hi there,
    Does Nexus 5500 series require a Nexus 7000 parent device? or it will be supported with Catalyst 6509?
    If this is the scenario :
    CAT6509 - Core Layer 3
    CAT6509 - Distribution Layer 2/3
    NX-5548 - Access Layer 2
    And FYI, no VSS on Catalyst 6509.
    Thanks in advance,
    Gerard

    Hello Chad,
    Cool thanks ... that is perfect. We're eventually moving towards NX at the Core and Distribs really soon. Yeah, that's what I've known with the Extenders requirement with parent 5k or 7k too ... 
    Gerard

  • DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

    When trying to discover a newly setup fabric we have set the SVI of one of the Nexus 5500 switches as seed device in DCNM SAN server. Problem do seem to be the same in DCNM 6.2 as in DCNM 5.x, one can not use a SVI.... After adding the seed switch with the IP adress of the SVI it appears in the Admin->Data sources->Fabric with the ip address of the mgmt interface. Thing is that this ip address can not be reached from the DCNM SAN server since we have only used a cross over ethernet cable for peer-keepalive over the mgmt interfaces.
    Is there a way in DCNM SAN 6.2 to force SAN management over a SVI instead of the mgmt interface?

    Here is the solution:
    in the menubar on the top, in the lower one go to Admin > Server Properties
    scroll to the middle of the list, locate “fabric.managementIpOverwrite” and set it to false 
    restart the DCNM Servers

  • Nexus 5500 FCoE

    Hi,
    If I use a SFP-10G-SR transceiver in a Nexus 5500, can I have FCoE in this port?
    Sorry for the question but i'm begining in the FCoE world
    Thanks

    Thanks Vinayak
    I'm very excited to be working with Nexus switches. Currently we only going to use ethernet, but with the new servers will be able to use FCoE.

  • Air3.2 CameraRoll on a Nexus S with Ice Cream Sandwich doesn't work!

    Hi,
    When trying to use cameraRoll on a Nexus S with Ice Cream Sandwich I get a message "No External Storage Available" and then it cancels out and returns to my app. I can see the camera roll loading behind the message. I just can't get to it...
    Is anyone else having this problem?
    I've got a Nexus S that hasn't been updated to Ice Cream Sandwich and the cameraRoll works like it should.
    We were meant to be deploying this app tommorow but this is a big problem.
    Has anyone else experience this? Got any fixes?
    Thanks,
    Matt

    Uhm.. i got the same problem (allmost). Can not confirm that it is External storage problem since i only get this error:
    [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Error #2038: File I/O Error." errorID=2038]
    2038 probably means something with storage.
    this is just amazing, client will be expecting to test the application within few days, and im stuck with AIR which doesnt communicate with ICS.
    btw im on air 3.3...

  • Nexus 5500 duplicate ICMP echo-replay

    I am experiencing inconsistent echo-replay from devices connected via VPC to Nexus 5500s while pinging from the Nexus exec prompt.
    In some cases I receive normal response when pinging from one Nexus,  but no response when pinging from the other switch. In other instance I receive normal response to one Nexus, and duplicate replays to the other. It looks like a VPC related bug. NXOS is 5.1.3.N2.1
    5501# ping 10.12.12.232
    PING 10.12.12.232 (10.12.12.232): 56 data bytes
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=253 time=8.585 ms
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=9.227 ms (DUP!)
    64 bytes from 10.12.12.232: icmp_seq=1 ttl=253 time=1.011 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=253 time=8.097 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=9.429 ms (DUP!)
    64 bytes from 10.12.12.232: icmp_seq=3 ttl=253 time=18.195 ms
    64 bytes from 10.12.12.232: icmp_seq=4 ttl=253 time=8.807 ms
    5502# ping 10.12.12.232
    PING 10.12.12.232 (10.12.12.232): 56 data bytes
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=0.985 ms
    64 bytes from 10.12.12.232: icmp_seq=1 ttl=254 time=0.884 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=0.875 ms
    64 bytes from 10.12.12.232: icmp_seq=3 ttl=254 time=3.105 ms
    64 bytes from 10.12.12.232: icmp_seq=4 ttl=254 time=8.378 ms
    Thanks
    Jarek

    Hi
    I found this in the configuration guide for the Nexus 7000 configuring VPCs
    "When you enable this feature (peer-gateway), Cisco NX-OS automatically disables IP redirects on all interface VLANs mapped over a vPC VLAN to avoid generation of IP redirect messages for packets switched through the peer gateway router."
    However this is not happening automatically on the 5K, so you need to manually add "no ip redirects" on each VPC vlan interface to prevent duplicate pings.

  • Nexus 5500 - inband via default vrf and out-of-band via management vrf

    Nexus 5548 with no layer 3 module.  Want to manage the device via 10.122.122.5 9 (inband) and 10.122.123.58 (out-of-band)
    Currently i can get to the device using 10.122.123.58 via management vrf but can't get to 10.122.122.5 via default vrf.
    A couple of questions please:
    1) Is this design support? or do i need a layer 3 module + licensing to use the default vrf?
    2) What does "pending" in the default vrf routing table indicate?
    interface Vlan12
      no shutdown
      ip address 10.122.122.5/25
    ip route 0.0.0.0/0 10.122.122.1
    interface mgmt0
      vrf member management
      ip address 10.122.123.58/26
    vrf context management
      ip route 0.0.0.0/0 10.122.123.1
    sh ip route vrf all 
    IP Route Table for VRF "default"
    '*' denotes best ucast next-hop
    '**' denotes best mcast next-hop
    '[x/y]' denotes [preference/metric]
    '%<string>' in via output denotes VRF <string>
    0.0.0.0/0, ubest/mbest: 1/0, pending
        *via 10.122.122.1, [1/0], 3w1d, static
    10.122.122.0/25, ubest/mbest: 1/0, attached, pending
        *via 10.122.122.5, Vlan12, [0/0], 3w1d, direct
    10.122.122.5/32, ubest/mbest: 1/0, attached, pending
        *via 10.122.122.5, Vlan12, [0/0], 3w1d, local
    IP Route Table for VRF "management"
    '*' denotes best ucast next-hop
    '**' denotes best mcast next-hop
    '[x/y]' denotes [preference/metric]
    '%<string>' in via output denotes VRF <string>
    0.0.0.0/0, ubest/mbest: 1/0
        *via 10.122.123.1, [1/0], 3w1d, static
    10.122.123.0/26, ubest/mbest: 1/0, attached
        *via 10.122.123.58, mgmt0, [0/0], 3w1d, direct
    10.122.123.58/32, ubest/mbest: 1/0, attached
        *via 10.122.123.58, mgmt0, [0/0], 3w1d, local

    Hi,
    Yes, it is possible.  When you login as admin and you want to get to another vdc, you just use this command:
    switchto vdc
    This will take to the that vdc.  If you want to switch back to the admin vdc, you just type "switchback"
    HTH

  • Connecting two Nexus switches with link

    Hi,
    I would like to connect two nexus switches with a link. Like one c5020 and one c5548p. How do i need to configure the ports at both the switches which will be joined with a fiber cable.
    For MDS switches such links becomes E-port and fabric is merged. Not sure what happenes at the Nexus swictches. Any input will be appreciated.
    Thanks,

    Do you have fc modules in each nexus? If so, they act much like the MDS 9148. All ports should be default auto speed and auto switchport mode. Insert fc-sfp's and a regular multimode fc cable between them. Default mode is fc switch.
    If that doesn't work, configure the mode on each port as E.
    Once done, the fc switch portion of each nexus will merge.
    Dave

Maybe you are looking for