Migration from Nexus 7000 without VDC to VDC

Hi all
I am working on a DataCenter architecture where we would like to implement Nexus 7000.
For the time being, there only one "context" but we may take the opportunity to implement VDC in a later future
I was not able to find a clear answer on the following :
  Can we add the VDC licence & configure a new VDC on a Nexus 7000 running without VDC ?
  I suppose this is possible. but does it need to have the whole configuration changed or adding a VDC can be done without any interruption on the current environnement ?
Thanks in advance !

Hello
To have VDC support on n7k you will require following license:
LAN_ADVANCED_SERVICES_PKG
To configure new vdc you need to run:
Nexus(config)# vdc
This will create new VDC which is separate from the current one. It shouldn't affect productional environment since separate processes started for new VDC.
Then you can allocate some interfaces to it and configure.
But you need to be careful to check whether you allocate unused interfaces and don't add resource excessive configuration.
Here is a very good explanation of what is VDC and how it works:
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/ps9512/White_Paper_Tech_Overview_Virtual_Device_Contexts.html
And here is VDC config guide:
http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/virtual_device_context/configuration/guide/vdc_nx-os_cfg.html
HTH,
Alex

Similar Messages

  • Data Center Design: Nexus 7K with VDC-core/VDC-agg model

    Dear all,
    I'm doing with a collapsed VDC-core/VDC-agg model on the same chassis with 2  Redundant Cisco Nexus 7010 and a pair of Cisco 6509 used as a Service  Chassis without VSS. Each VDC Core have redundant link to 2 PE based on  Cisco 7606.
    After reading many design document of Cisco, I'm asking  what is the need of a Core Layer in a Data Center especially if it is  small or medium size with only 1 aggregation layer and dedicated for a Virtualized Multi-Tenanted environement? What is driving to have a core layer?
    Thanx

    If your data center is small enough to not require a core, then its fine to run with a collapsed core (distribution + core as the same device).  For a redundant design you need to uplink all your distribution switches to each of your cores.  If you have no cores, then you need full mess at your distribution layer (for full redundancy).
    Lets say you have only 4 distribution pairs...so 8 switches  For full redundancy each one needs uplink to each other.  This means you need 28 total ports used to connect all the switches together (n(n-1)/2).  Thats also assuming 1 link to each device.  However if you had redundant cores, the number of links used for uplinks reduces to 21 total links (this includes links between each distribution switch in a site, and link between the two cores).  So here you see your only saving 7 links.  Here your not gaining much by adding a core.
    However if you have 12 distribution pairs...so 24 switches.  Full redundancy means you have 276 links dedicated for this.  If you add a core, this drops to 61 links.  Here you see the payoff.

  • Nexus 7000 route leak from GRT (default VRF) to other VRF's

    Hello
    We have a Nexus 7000 infrastructure whereby we have had multiple VDC's and VRF's deployed. A requirement has now come about whereby one of these VRF's needs to be able to see our GRT (default VRF) so we need to leak the GRT routes into the VRF and vice versa.
    I have been doing a lot of reading and I am happy with the how this works with inter-VRF route leaking but I seem to missing a few things in respect of how this works with the GRT.
    I have also read on another forum that this is not supported. See link below.
    https://supportforums.cisco.com/document/133711/vrf-configuration-and-verification-nexus-7000
    Does anyone have experience of this? I can also see how this works in IOS and I have GNS3 and got this working.
    We use BGP currently so we are able to use MP-BGP if required.
    Any help would be very useful.

    Hi,
    In Table 14 of the Cisco Nexus 7000 Series NX-OS Verified Scalability Guide the verified limit is specified as 1000 per system i.e., across all VDCs for NX-OS release 5.2, 6.0 and 6.1.
    There is a footnote associated with this number which states:
    With each new VDC configured, the number of configurable VRFs per system is reduced by two as each VDC has a default VRF and management VRFs that are not removable. For example, with 8 configured VDCs on Cisco NX-OS Release 5.2, you can configure up to 984 VRFs per system (either all in one VDC or across VDCs).
    Regards

  • Catalyst 6500 - Nexus 7000 migration

    Hello,
    I'm planning a platform migration from Catalyst 6500 til Nexus 7000. The old network consists of two pairs of 6500's as serverdistribution, configured with HSRPv1 as FHRP, rapid-pvst and ospf as IGP. Futhermore, the Cat6500 utilize mpls/l3vpn with BGP for 2/3 of the vlans. Otherwise, the topology is quite standard, with a number of 6500 and CBS3020/3120 as serveraccess.
    In preparing for the migration, VTP will be discontinued and vlans have been manually "copied" from the 6500 to the N7K's. Bridge assurance is enabled downstream toward the new N55K access-switches, but toward the 6500, the upcoming etherchannels will run in "normal" mode, trying to avoid any problems with BA this way. For now, only L2 will be utilized on the N7K, as we're avaiting the 5.2 release, which includes mpls/l3vpn. But all servers/blade switches will be migrated prior to that.
    The questions arise, when migrating Layer3 functionality, incl. hsrp. As per my understanding, hsrp in nxos has been modified slightly to better align with the vPC feature and to avoid sub-optimal forwarding across the vPC peerlink. But that aside, is there anything that would complicate a "sliding" FHRP migration? I'm thinking of configuring SVI's on the N7K's, configuring them with unused ip's and assign the same virtual ip, only decrementing the prio to a value below the current standby-router. Also spanning-tree prio will, if necessary, be modified to better align with hsrp.
    From a routing perspective, I'm thinking of configuring ospf/bgp etc. similar to that of the 6500's, only tweaking the metrics (cost, localpref etc) to constrain forwarding on the 6500's and subsequently migrate both routing and FHRP at the same time. Maybe not in a big bang style, but stepwise. Is there anything in particular one should be aware of when doing this? At present, for me this seems like a valid approach, but maybe someone has experience with this (good/bad), so I'm hoping someone has some insight they would like to share.
    Topology drawing is attached.
    Thanks
    /Ulrich

    In a normal scenario, yes. But not in vPC. HSRP is a bit different in the vPC environment. Even though the SVI is not the HSRP primary, it will still forward traffic. Please see the below white paper.
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/white_paper_c11-516396.html
    I will suggest you to set up the SVIs on the N7K but leave them in the down state. Until you are ready to use the N7K as the gateway for the SVIs, shut down the SVIs on the C6K one at a time and turn up the N7K SVIs. When I said "you are ready", it means the spanning-tree root is at the N7K along with all the L3 northbound links (toward the core).
    I had a customer who did the same thing that you are trying to do - to avoid down time. However, out of the 50+ SVIs, we've had 1 SVI that HSRP would not establish between C6K and N7K, we ended up moving everything to the N7K on a fly during of the migration. Yes, they were down for about 30 sec - 1 min for each SVI but it is less painful and waste less time because we don't need to figure out what is wrong or any NXOS bugs.
    HTH,
    jerry

  • Migration from PC to Mac without losing application data (savegames etc.)

    Hello everyone,
    I am migrating from from my old Windows PC onto a MacBook Pro, and I'm having difficulties with iTunes and my iOS devices (iPhone 4, iPad 1). Maybe someone here can help me out, I'd be ever so grateful.
    I set up iTunes on my MBP yesterday and logged in to my account. I replaced the empty iTunes Media folder with my old one (which contains all my music, videos and applications) via an external hard drive.
    First problem: it wouldn't import these files into my new library automatically. Just showed me an empty library I think I imported the entire iTunes Media folder manually yesterday via "Add to folder". The status right now (after some experimentation) is old iTunes Media folder copied, but nothing imported (that is, I have an empty library).
    When I connected my iPhone and tried to synch, I first had to authorize the MacBook for the iPhone. So far, so good. However when I tried to synch iTunes warned me that if I synch, all data on the iPhone will be removed and replaced by the data from my new local library (which is, of couse a copy of my old library, but doesn't store application data like savegames).
    I tried to do it via "transfer purchased items from iPhone", which took forever, but yielded the same result: a warning that all data on the iPhone would be erased.
    So the question is: How do I connect my iPhone and iPad to iTunes on my new Mac without losing application data like settings and savegames? And why is this so complicated and intransparent? I should be able to just copy my media, say "authorize this Computer, then add iPhone to the registered devices" and then proceed like nothing ever changed.
    I searched the net until three in the morning yesterday, but couldn't find anything that sounded safe enough to give it a try.
    Thanks in advance and best Regards,
    Nate
    PS: I do have the backup-folders from my old PC on a USB stick - are those going to help?
    Message was edited by: Nathan1980 (Correction)
    Message was edited by: Nathan1980

    I was fighting this battle the past few days myself; but actually it is REALLY easy now. See here:
    http://www.macworld.com/article/146958/2010/03/moveitunes_windowsmac.html
    Then, once iTunes was on the Mac, I did this:
    1. On the Mac rename ...\iTunes\iTunes Library.itl as ...\iTunes\iTunes Library
    2. On the Mac delete ...\iTunes\iTunes Library Genius.itdb (Apparently the PC & Mac versions are not compatible - iTunes will just rebuild it later)
    3. Launch iTunes and immediately press & hold down the Option key until a dialog opens asking you to Choose a library. Navigate to the folder/drive you've copied from the PC and open ...\iTunes\iTunes Library.
    (thanks to turingtest2 for the above steps)
    That was it. Did it yesterday evening. All playlists, libraries, everything copied fine. No problems; no broken links. Perfect.

  • How can i transfer my whatsapp chat from iphone 3gs to google nexus 5 without losing any data?

    How can i transfer my whatsapp chat from iphone 3gs to google nexus 5 without losing any data? I want to swtich from my iphone to google nexus 5.could anyone help me for this?

    steve359 wrote:
    Please pardon the intrusion…
    Hi, FoxFifth!
    Congratulations on advancing to Level 6!
    At the Water Cooler in the Level 6 Lounge, we are preparing your welcome. Would you care to join us at the Water Cooler?
    On the Discussions Home Page (https://discussions.apple.com/welcome), down at the bottom, you will, hopefully, soon find the Lounge link available to you. It should show up for you within the next 24 hours if all goes as it should.
    Hope to see you there soon!
    Thanks! I'll check that out as soon as it becomes available.

  • Smart call home - HTTPS transport from the Nexus 7000 to Cisco

    hi
    i try configured call home on nexus 7000 with https transport and proxy server
    i follow this guide -
    http://www.cisco.com/en/US/docs/switches/lan/smart_call_home/QuickStart_NX7000.pdf
    and configured this :
    callhome
      email-contact XXXXXXXXXXX
      phone-contact XXXXXXXXXXX
      streetaddress XXXXXXXXXXXXXXXX
      destination-profile CiscoTAC-1 transport-method http
      destination-profile CiscoTAC-1 http https://tools.cisco.com/its/service/oddce/services/DDCEService
       transport http use-vrf management
      transport http proxy server XXXXXXXXXX port 8080                --------- XXXXXXXXX = my proxy server
      transport http proxy enable
      enable
      periodic-inventory notification interval  30
    i have a problem to install the security certificate , i follow thw guide but i get the error :
    failed to load or parse certificate
    could not perform CA authentication
    when i try test call home eith the command : callhome test
    trying to send test callhome message
    warning:no callhome message sent
    email configuration incomplete for destination profile:full_txt
    email configuration incomplete for destination profile:short_txt
    Error in transporting http message for CiscoTAC-1
    http: Received HTTP code 407 from proxy after CONNECT
    i guess the problem is because i didnt install the certificate , how can i install the certificate ?
    is this the real problem ?

    I agree with Bryan that the easiest proxy server to setup for the  nexus 7000 is the Transport Gateway. The documentation (certificates) is  setup to allow you to connect to a Cisco Transport Gateway or directly  into tools.cisco.com. Both have a Cisco certificate.
    But that doesn't explain your issue. To answer your issue, you need to look here
    http://www.cisco.com/en/US/docs/switches/lan/smart_call_home/SCH31_Ch6.html#wp1039385
    except  you need your proxy server's chained certificate in PEM format since  the Nexus 7000 is going to terminate at your proxy server. Take a look  at this line in the documentation.
    Input (cut & paste) the CA certificate (chain) in PEM format
    The error code 407 you indicated makes sense and  indicates "Proxy Authentication Required". You need the certificate  installed first. NX-OS uses the openssl crypto library to implement the  cert-pki feature if that helps. A complete certificate chain is required. Also,  you might make sure the CRL (certificate revocation list) is set to none  so it doesn't do that first.
    revocation-check none
    The 4 chained certificates given in the documentation are tools.cisco.com.cer, Verisign-G3-SSCA.cer, Verisign-G3-PRCA.cer,  Verisign-Root-CA.cer. The non-nexus 7000 devices just use the last one. Most likely you need a certificate that looks like
    your proxy server.cer,Verisign-G3-SSCA.cer, Verisign-G3-PRCA.cer,  Verisign-Root-CA.cer
    If you are using your own root CA (which typically are taken  off-line after authorizing subordinate CAs for security reasons) , then  make sure that their certificates are in the correct order to be  processed so each can be authenticated.
    Now you can see why a Cisco proxy server (Transport Gateway) is easier to setup.

  • Nexus 7k - Interface Statistics Across VDCs

    Is there anyway to get interface statistics from all interfaces regardless of what vdc they are in? Trying to setup solarwinds to monitor them all. 
    Thanks,
    Alex

    You can, but each VDC need its own interface to SolarWinds. Each VDC acts as a separate switch.
    HTH

  • How do I migrate from a 2008 MacBook Pro without a screen to new 2014 MacBook Pro?

    How do I migrate from a 2008 MacBook Pro without a video screen to a 2014 Macbook Pro?

    Use your backup drive instead. No backup drive, then get a monitor and connect it to your computer. Or take the whole shebang to the Apple Store for help with the transfer. Or you can remove the drive from the old MBP and put it in an external enclosure.

  • My new iMac is not shipping with Lion installed. Will I be able to do a Migration from my PC to my iMac without installing Lion first?

    My new iMac is not shipping with Lion installed. Will I be able to do a Migration from my PC to my new iMac? I only want to transfer photos and my music, currently on my PC (and on my iPod Touch & iPad).
    Can anyone give me a list of steps to follow or let me know if Migration Assistant is available prior to Lion for PC to Mac?
    Thank you so so so much!
    -SweetDee

    SweetDee,
    I'd be VERY surprised if your machine was not shipping with Lion installed. However even if it doesn't when you initally install Lion it will launch into Setup Assistant, if you follow the prompts it will ask if you are migrating from another machine. You can use Pondini's Lion Setup Assistant tips for help, look for the section(s) on MS Windows migration. Also I would strongly recommend bookmarking and studying the following sites:
    Switch 101
    Mac 101
    Find Out How Video tutorials
    In closing remember you have 90 days of free telephone support with AppleCare. If you run into trouble they will be happy to assist or if you have an Apple Store in your area you can book an appointment with a Genius and they can usually help you out.

  • Nexus 7000 Platform Logging

    Hello,
    We recently had a power supply failure in one of our Nexus 7000s, and I noticed that the syslog for the Platform is only present in the default VDC, and not in any of the other VDCs syslogs. Is this by design, or is there a logging level I can turn up in another VDC to capture this log? Thanks for any input
    syslog from default VDC -
    2013 Mar 18 23:10:34  %PLATFORM-2-PS_CAPACITY_CHANGE: Power supply PS3 changed i
    ts capacity. possibly due to power cable removal/insertion (Serial number xxxxxxxx)
    nothing in the VDC where I would like to get the logging
    default VDC logging level -
    xxx7K02# show log level platform
    Facility        Default Severity        Current Session Severity
    platform                5                       5
    0(emergencies)          1(alerts)       2(critical)
    3(errors)               4(warnings)     5(notifications)
    6(information)          7(debugging)
    xxx7K02#
    loggging from the specific VDC where we have management tools.
    xxx-LOW# show log level platform
    Facility        Default Severity        Current Session Severity
    platform                5                       5
    0(emergencies)          1(alerts)       2(critical)
    3(errors)               4(warnings)     5(notifications)
    6(information)          7(debugging)
    xxx-LOW#

    Hello Carl,
    What version of code are you running on your Nexus 7k?
    The expected behavior is:
    "When a hardware issue occurs, syslog messages are sent to all VDCs."
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/virtual_device_context/configuration/guide/vdc_mgmt.html#wp1170241
    Dave

  • Nexus 7000, 2000, FCOE and Fabric Path

    Hello,
    I have a couple of design questions that I am hoping some of you can help me with.
    I am working on a Dual DC Upgrade. It is pretty standard design, customer requires a L2 extension between the DC for Vmotion etc. Customer would like to leverage certain features of the Nexus product suite, including:
    Trust Sec
    VDC
    VPC
    High Bandwidth Scalability
    Unified I/O
    As always cost is a major issue and consolidation is encouraged where possible. I have worked on a couple of Nexus designs in the past and have levergaed the 7000, 5000, 2000 and 1000 in the DC.
    The feedback that I am getting back from Customer seems to be mirrored in Cisco's technology roadmap. This relates specifically to the features supported in the Nexus 7000 and Nexus 5000.
    Many large enterprise Customers ask the question of why they need to have the 7000 and 5000 in their topologies as many of the features they need are supported in both platforms and their environments will never scale to meet such a modular, tiered design.
    I have a few specific questions that I am hoping can be answered:
    The Nexus 7000 only supports the 2000 on the M series I/O Modules; can FCOE be implemented on a 2000 connected to a 7000 using the M series I/O Module?
    Is the F Series I/O Module the only I/O Module that supports FCOE?
    Are there any plans to introduce the native FC support on the Nexus 7000?
    Are there any plans to introduce full fabric support (230 Gbps) to the M series I/O module?
    Are there any plans to introduce Fabric path to the M series I/O module?
    Are there any plans to introduce L3 support to the F series I/O Module?
    Is the entire 2000 series allocated to a single VDC or can individual 2000 series ports be allocated to a VDC?
    Is Trust Sec only support on multi hop DCI links when using the ASR on EoMPLS pwire?
    Are there any plans to inroduce Trust Sec and VDC to the Nexus 5500?
    Thanks,
    Colm

    Hello Allan
    The only IO card which cannot co-exist with other cards in the same VDC is F2 due to specific hardware realisation.
    All other cards can be mixed.
    Regarding the Fabric versions - Fabric-2 gives much bigger throughoutput in comparing with Fabric-1
    So in order to get full speed from F2/M2 modules you will need Fab-2 modules.
    Fab2 modules won't give any advantages to M1/F1 modules.
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/data_sheet_c78-685394.html
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/prodcut_bulletin_c25-688075.html
    HTH,
    Alex

  • Nexus 7000 ERSPAN

    I have a question about ERSPAN on the Nexus 7000.
    I set up the necessary configuration for ERSPAN source on my 7000s, with a destination on a catalyst 6500. I went through all the standard ERSPAN configuration to see if there is a difference in Nexus vs. Catalyst.
    I saw that there is a command "monitor erspan origin ip-address <ip> global" that needs to be entered to make ERSPAN work correctly. I tried entering this on the VDC that has the source. I received a message that the origin command must be run only from the default VDC and wasn't allowed where I was trying to run it.
    So, I entered the command in the admin VDC, using the origin as the loopback address on the VDC with the actual source, and the ERSPAN immediately started working.
    Can someone explain what this command is doing, why it's needed and the flow of the ERSPAN traffic?
    Thanks.

    All can I please add another question can we have an ERSPAN on a nexus 7K set up as a source in one VDC and set as a destination in another VDC on the same N7K.
    Unfortunately I could find any documentation from Cisco Regarding Erspan on nexus 7K with multiple VDC
    Any help is much appreciated

  • NEXUS 7000 xcvrInval

    Hi,
    I have some Nexus 7000 with FET-10G with xcvrInval status
    Eth7/33          N5k-S1-3T-1/3   xcvrInval trunk     auto    auto    Fabric Exte
    and some other FET-10G with notconn status
    Eth7/8           FEX-101         notconnec 1         auto    auto    Fabric Exte
    If I inter exchange the position of both FET-10G the status port doesn´t change
    FET-10G from 7/8 to 7/33
    FET-10G from 7/33 to 7/8
    7/33 holds xcvrInval status
    7/8 holds notconnec status
    I have reconfigured from default interface with same results
    Next you´ll find the same serial number in deferent port, the diference is the current
    when is xcvrInva or when is notconnec
    What can I do to get FET10G in e7/33 validated?
    sh interface e7/33   transceiver details
    Ethernet7/33
          transceiver is present
          type is Fabric Extender Transceiver
          name is CISCO-FINISAR  
          part number is FTLX8570D3BCL-C2
          revision is A  
          serial number is FNS17201TE5    
          nominal bitrate is 10300 MBit/sec
          Link length supported for 62.5/125um fiber is 10 m
          Link length supported for 50/125um OM3 fiber is 100 m
          cisco id is --
          cisco extended id number is 4
          cisco part number is 10-2566-02
          cisco product id is FET-10G            
          cisco vendor id is V02
          number of lanes 1
                 SFP Detail Diagnostics Information (internal calibration)
                    Current              Alarms                  Warnings
                    Measurement     High        Low         High          Low
        Temperature   19.30 C        75.00 C      5.00 C     70.00 C       10.00 C
    [7m--More-- [m
        Voltage        3.31 V         3.63 V      2.97 V      3.46 V        3.13 V
        Current        0.06 mA  --     11.80 mA     4.00 mA    10.80 mA       5.00 mA
        Tx Power          N/A        22.69 dBm    8.69 dBm     18.69 dBm     12.69 dBm
        Rx Power          N/A        22.99 dBm    6.09 dBm     18.99 dBm     10.09 dBm
        Transmit Fault Count = 0
        Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    now in slot 7/8
    Ethernet7/8
          transceiver is present
          type is Fabric Extender Transceiver
          name is CISCO-FINISAR  
          part number is FTLX8570D3BCL-C2
          revision is A  
          serial number is FNS17201TE5    
          nominal bitrate is 10300 MBit/sec
          Link length supported for 62.5/125um fiber is 10 m
          Link length supported for 50/125um OM3 fiber is 100 m
          cisco id is --
          cisco extended id number is 4
          cisco part number is 10-2566-02
          cisco product id is FET-10G            
          cisco vendor id is V02
          number of lanes 1
                 SFP Detail Diagnostics Information (internal calibration)
                    Current              Alarms                  Warnings
                    Measurement     High        Low         High          Low
        Temperature   23.17 C        75.00 C      5.00 C     70.00 C       10.00 C
    [7m--More-- [m
        Voltage        3.30 V         3.63 V      2.97 V      3.46 V        3.13 V
        Current        7.50 mA       11.80 mA     4.00 mA    10.80 mA       5.00 mA
        Tx Power      17.65 dBm      22.69 dBm    8.69 dBm     18.69 dBm     12.69 dBm
        Rx Power     -12.21 dBm --   22.99 dBm    6.09 dBm     18.99 dBm     10.09 dBm
        Transmit Fault Count = 0
        Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    NX7K-1-VDC-3T-S1-L2FP# sh int e7/33
    Ethernet7/33 is down (Transceiver validation failed)
    admin state is up, Dedicated Interface
      Belongs to Po51
      Hardware: 1000/10000 Ethernet, address: 8478.ac23.6cec (bia 8478.ac23.6cec)
      Description: N5k-S1-3T-1/3
      MTU bytes (CoS values):  MTU  1500(0-2,4-7) bytes  MTU  2112(3) bytes
      BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, medium is broadcast
      Port mode is trunk
    auto-speed  auto-duplex,, media type is 10G
      Beacon is turned off
      Auto-Negotiation is turned on
      Input flow-control is off, output flow-control is off
      Auto-mdix is turned on
      Rate mode is dedicated
      Switchport monitor is off
      EtherType is 0x8100
      EEE (efficient-ethernet) : n/a
      Last link flapped never
      Last clearing of "show interface" counters 07:22:09
      0 interface resets
      Load-Interval #1: 30 seconds
        30 seconds input rate 0 bits/sec, 0 packets/sec
        30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        300 seconds input rate 0 bits/sec, 0 packets/sec
        300 seconds output rate 0 bits/sec, 0 packets/sec
      RX
        88 unicast packets  0 multicast packets  0 broadcast packets
        0 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC/FCS  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        88 unicast packets  0 multicast packets  0 broadcast packets
        0 output packets  0 bytes
        0 jumbo packets
        0 output error  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble  0 output discard
        0 Tx pause
    NX7K-1-VDC-3T-S1-L2FP# sh int e7/33
    Ethernet7/8 is down (Link not connected)
    admin state is up, Dedicated Interface
      Belongs to Po101
      Hardware: 1000/10000 Ethernet, address: 8478.ac23.6cd3 (bia 8478.ac23.6cd3)
      Description: FEX-101
      MTU bytes (CoS values):  MTU  1500(0-2,4-7) bytes  MTU  2112(3) bytes
      BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, medium is p2p
      Port mode is fex-fabric
    auto-speed  auto-duplex,, media type is 10G
      Beacon is turned off
      Auto-Negotiation is turned on
      Input flow-control is off, output flow-control is off
      Auto-mdix is turned on
      Rate mode is dedicated
      Switchport monitor is off
      EtherType is 0x8100
      EEE (efficient-ethernet) : n/a
      Last link flapped 5week(s) 1day(s)
      Last clearing of "show interface" counters never
      0 interface resets
      Load-Interval #1: 30 seconds
        30 seconds input rate 0 bits/sec, 0 packets/sec
    [7m--More-- [m
        30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        300 seconds input rate 0 bits/sec, 0 packets/sec
        300 seconds output rate 0 bits/sec, 0 packets/sec
      RX
        10588 unicast packets  0 multicast packets  0 broadcast packets
        4 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC/FCS  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        10588 unicast packets  1 multicast packets  0 broadcast packets
        4 output packets  5688 bytes
        0 jumbo packets
        0 output error  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble  0 output discard
        0 Tx pause

    Hi Ans,
    You are rigth, I have defaulted againt the port, now configured with switchport mode FEX, and now the FET-10G is validated
    NX7K-1-VDC-3T-S1-L2FP(config-if)#  description FEX-101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport mode fex-fabric
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   fex associate 101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   medium p2p
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   channel-group 101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   no shutdown
    NX7K-1-VDC-3T-S1-L2FP(config-if)#
    NX7K-1-VDC-3T-S1-L2FP(config-if)# sh int e7/33 status
    Port             Name            Status    Vlan      Duplex  Speed   Type
    Eth7/33          FEX-101         notconnec 1         auto    auto    Fabric Exte
    NX7K-1-VDC-3T-S1-L2FP(config-if)#
    Thanks for your help, and have a nice weekend.
    Atte,
    EF

  • EtherChannel problem on Nexus 7000

    Dear NetPro gurus,
    One of my customer is trying to setup an EtherChannel (LACP) on a pair of Nexus 7000.  However, doesn't matter what we do, the port Eth 1/17 always become suspended.  We have tried swapping fiber cables and also swapping SFPs, but no help.
    The 1st Nexus 7010 - called 'VIWLRCA'
    The 2nd Nexus 7010 - called 'VIWLRCB'
    Originally port eth 1/17 are left as 'normal' trunk port, and we can see eth 1/17 shows up fine under 'show interface brief'
    viwlrca-PROD# sh run int eth 1/17
    interface Ethernet1/17
      switchport
      switchport mode trunk
      udld disable
      no shutdown
    viwlrca-PROD# sh run int eth 1/18
    interface Ethernet1/18
      switchport
      switchport mode trunk
      udld disable
      channel-group 20 mode active
      no shutdown
    viwlrca-PROD# sh int brief
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/17       1       eth  trunk  up      none                        10G(S) --
    Eth1/18       1       eth  trunk  up      none                        10G(S) 20
    Eth1/19       --      eth  routed down    SFP not inserted           auto(S) --
    Eth1/20       --      eth  routed down    SFP not inserted           auto(S) --
    Eth1/21       --      eth  routed down    Administratively down      auto(S) --
    Eth1/22       --      eth  routed down    Administratively down      auto(S) --
    Eth1/23       --      eth  routed down    Administratively down      auto(S) --
    Eth1/24       --      eth  routed down    Administratively down      auto(S) --
    Eth2/25       --      eth  routed down    Administratively down      auto(D) --
    Eth2/26       --      eth  routed down    Administratively down      auto(D) --
    Eth2/27       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/28       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/29       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/30       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/31       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/32       --      eth  routed down    SFP not inserted           auto(D) --
    viwlrca-PROD#
    But as soon as I add the Eth 1/17 back onto PortChannel 20
    The Eth 1/17 becomes "Suspended" straight away
    viwlrca-PROD# sh int brief
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Por
    t
    Interface                                                                    Ch
    Eth1/17       1       eth  trunk  down    suspended                  auto(S) 20
    Eth1/18       1       eth  trunk  up      none                        10G(S) 20
    Eth1/19       --      eth  routed down    SFP not inserted           auto(S) --
    Eth1/20       --      eth  routed down    SFP not inserted           auto(S) --
    Eth1/21       --      eth  routed down    Administratively down      auto(S) --
    Eth1/22       --      eth  routed down    Administratively down      auto(S) --
    Eth1/23       --      eth  routed down    Administratively down      auto(S) --
    Eth1/24       --      eth  routed down    Administratively down      auto(S) --
    Eth2/25       --      eth  routed down    Administratively down      auto(D) --
    Eth2/26       --      eth  routed down    Administratively down      auto(D) --
    Eth2/27       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/28       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/29       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/30       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/31       --      eth  routed down    SFP not inserted           auto(D) --
    Eth2/32       --      eth  routed down    SFP not inserted           auto(D) --
    viwlrca-PROD#
    viwlrca-PROD# sh port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
            M - Not in use. Min-links not met
    Group Port-       Type     Protocol  Member Ports
          Channel
    20    Po20(SU)    Eth      LACP      Eth1/17(s)   Eth1/18(P)  
    viwlrca-PROD#
    Config on Primary Nexus:-
    viwlrca-PROD# sh run
    !Command: show running-config
    !Time: Tue Mar 22 06:04:26 2011
    version 5.1(1a)
    hostname PROD
    cfs eth distribute
    feature udld
    feature interface-vlan
    feature lacp
    feature vpc
    feature vtp
    username admin password 5 $1$pkJaKHZW$Sx4wpDG5xXYkD.QfDk/Cg.  role vdc-admin
    no ip domain-lookup
    ip domain-name vfc.com
    crypto key param rsa label viwlrca-PROD.vfc.com modulus 2048
    snmp-server user admin vdc-admin auth md5 0x05f7328e3b39a70be09abc3056ec2819 pri
    v 0x05f7328e3b39a70be09abc3056ec2819 localizedkey
    vrf context management
    spanning-tree pathcost method long
    spanning-tree port type edge bpduguard default
    spanning-tree loopguard default
    spanning-tree vlan 1-3967,4048-4093 priority 4096
    interface Vlan1
    interface Vlan161
      ip address 172.30.161.2/24
    interface Vlan162
      ip address 172.30.162.2/24
    interface Vlan163
      ip address 172.30.163.2/24
    interface Vlan164
      ip address 172.30.164.2/24
    interface Vlan165
      ip address 172.30.165.2/24
    interface Vlan190
      ip address 172.30.190.2/24
    interface port-channel20
      switchport
      switchport mode trunk
    interface Ethernet1/17
      switchport
      switchport mode trunk
      udld disable
      channel-group 20 mode active
      no shutdown
    interface Ethernet1/18
      switchport
      switchport mode trunk
      udld disable
      channel-group 20 mode active
      no shutdown
    interface Ethernet1/19
    interface Ethernet1/20
    interface Ethernet1/21
    interface Ethernet1/22
    interface Ethernet1/23
    interface Ethernet1/24
    interface Ethernet2/25
    interface Ethernet2/26
    interface Ethernet2/27
    interface Ethernet2/28
    interface Ethernet2/29
    interface Ethernet2/30
    interface Ethernet2/31
    interface Ethernet2/32
    interface Ethernet2/33
    interface Ethernet2/34
    interface Ethernet2/35
    interface Ethernet2/36
    interface Ethernet3/25
    interface Ethernet3/26
    interface Ethernet3/27
    interface Ethernet3/28
    interface Ethernet3/29
    interface Ethernet3/30
    interface Ethernet3/31
    interface Ethernet3/32
    interface Ethernet3/33
    interface Ethernet3/34
    interface Ethernet3/35
    interface Ethernet3/36
    line vty
    viwlrca-PROD#
    Config for Secondary Nexus 7000
    VIWLRCB-PROD# sh run
    !Command: show running-config
    !Time: Tue Mar 22 09:19:22 2011
    version 5.1(1a)
    hostname PROD
    cfs eth distribute
    feature interface-vlan
    feature lacp
    feature vpc
    feature vtp
    username admin password 5 $1$Lc486EOm$EtKhZWuxGjWWokfeuUsMk.  role vdc-admin
    no ip domain-lookup
    ip domain-name vfc.com
    crypto key param rsa label VIWLRCB-PROD.vfc.com modulus 2048
    snmp-server user admin vdc-admin auth md5 0xeb607b54234985ed6740c5fdbb8d84c6 pri
    v 0xeb607b54234985ed6740c5fdbb8d84c6 localizedkey
    vrf context management
    spanning-tree pathcost method long
    spanning-tree port type edge bpduguard default
    spanning-tree loopguard default
    spanning-tree vlan 1-3967,4048-4093 priority 8192
    interface Vlan1
    interface port-channel20
      switchport
      switchport mode trunk
    interface Ethernet1/17
      switchport
      switchport mode trunk
      channel-group 20 mode active
      no shutdown
    interface Ethernet1/18
      switchport
      switchport mode trunk
      channel-group 20 mode active
      no shutdown
    interface Ethernet1/19
    interface Ethernet1/20
    interface Ethernet1/21
    interface Ethernet1/22
    interface Ethernet1/23
    interface Ethernet1/24
    interface Ethernet2/25
    interface Ethernet2/26
    interface Ethernet2/27
    interface Ethernet2/28
    interface Ethernet2/29
    interface Ethernet2/30
    interface Ethernet2/31
    interface Ethernet2/32
    interface Ethernet2/33
    interface Ethernet2/34
    interface Ethernet2/35
    interface Ethernet2/36
    interface Ethernet3/25
    interface Ethernet3/26
    interface Ethernet3/27
    interface Ethernet3/28
    interface Ethernet3/29
    interface Ethernet3/30
    interface Ethernet3/31
    interface Ethernet3/32
    interface Ethernet3/33
    interface Ethernet3/34
    interface Ethernet3/35
    interface Ethernet3/36
    line vty
    VIWLRCB-PROD#
    Cheers,
    Hunt

    Quick troubleshoot:
    Default all interfaces in newly created port-channel as well as the port-channel interface, then delete port-channel interface.  Recreate port-channel without the LACP protocol:
    interface e1/17,e1/18
      switchport
      channel-group 20 mode on
      no shutdown
      exit
    interface port-channel20
      switchport
      switchport mode trunk
      no shutdown
      exit
    show port-channel summ
    show int trunk
    HTH,
    Sean

Maybe you are looking for