Uplink Nexus 5010 to 6509 and management

I have looked around online on Cisco's site and scanned over the Nexus 5000 document and I cant seem to find the answers Im looking for. The document I am referring to can be found at http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli_rel_4_0_1a/CLIConfigurationGuide.html
I have two questions:
1) Are there any guides to connecting the 5000's to 6509's which would be serving as the core? If not can someone point me in the right direction.
2) I have configured the management port on the 5000. In order to access the CLI of the switch without a console cable do I need to have the management port connected to my infrastructure or can I ssh/telnet to the switch by just having it uplinked via Fiber back to the 6509's?
Thank you kindly

Mod Ports Card Type                              Model              Serial No.
  1   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL12330BKM
  4    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      SAL123418MN
  5    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      SAL11370JSY
  6    2  Supervisor Engine 720 (Active)         WS-SUP720-BASE     SAL1201BZUC
  9   16  SFM-capable 16 port 1000mb GBIC        WS-X6516A-GBIC     SAL08196XHD
Mod MAC addresses                       Hw    Fw           Sw           Status
  1  0022.55ec.69a8 to 0022.55ec.69d7   3.0   12.2(18r)S1  12.2(18)SXF1 Ok
  4  0023.045e.fbe8 to 0023.045e.fbef   1.6   12.2(18r)S1  12.2(18)SXF1 Ok
  5  001d.4542.17b0 to 001d.4542.17b3   2.6   12.2(14r)S5  12.2(18)SXF1 Ok
  6  0019.e7d4.3e5c to 0019.e7d4.3e5f   4.0   8.4(2)       12.2(18)SXF1 Ok
  9  000f.f780.d2bc to 000f.f780.d2cb   4.1   7.2(1)       8.5(0.46)RFW Ok
Mod  Sub-Module                  Model              Serial       Hw     Status
  1  Centralized Forwarding Card WS-F6700-CFC       SAL1230Y8RY  4.1    Ok
  4  Distributed Forwarding Card WS-F6700-DFC3C     SAL123304FZ  1.0    Ok
  5  Distributed Forwarding Card WS-F6700-DFC3B     SAL1115LPP0  4.6    Ok
  6  Policy Feature Card 3       WS-F6K-PFC3A       SAL1201C3KH  2.6    Ok
  6  MSFC3 Daughterboard         WS-SUP720          SAL1201C1TQ  3.1    Ok
Mod  Online Diag Status
  1  Pass
  4  Pass
  5  Pass
  6  Pass
  9  Pass
#sh ver
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF15a, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Tue 21-Oct-08 00:04 by kellythw
Image text-base: 0x40101040, data-base: 0x42DDBE30
ROM: System Bootstrap, Version 12.2(17r)S4, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF15a, RELEASE SOFTWARE (fc1)
pa-core-6509 uptime is 1 year, 11 weeks, 2 days, 23 hours, 49 minutes
Time since pa-core-6509 switched to active is 1 year, 11 weeks, 2 days, 23 hours, 48 minutes
System returned to ROM by s/w reset at 08:16:27 UTC Tue Oct 28 2008 (SP by bus error at PC 0x401A4578, address 0x0)
System image file is "disk0:s72033-advipservicesk9_wan-mz.122-18.SXF15a.bin"

Similar Messages

  • LMS 3.2 : Can't collect inventory from Nexus 5010

    Hello,
    I've added a Nexus 5010 to LMS, and it recognized it as such, and it was also able to archive its configuration.
    But LMS is unable to collect inventory from it : the error message is "Device Sensed, but collection failed".
    I am able to do an snmp walk of the device and I do see the ENTITY mib.
    I am running LMS 3.2 with no RME patches or device package updates.
    I've attached the relevant portion of IC_Server.log.
    The Nexus 5010 is running NX-OS 4.1(3)N2(1a).
    Thanks for the help,
    Alex.

    >> I am running LMS 3.2 with no RME patches or device package updates.
    So why not update the dev pkgs, then try again?
    The latest RME pkg for Nexus is apparently v2.4, whereas I'm collecting the 5010s fine with v2.3.
    704.
    1.3.6.1.4.1.9.12.3.1.3.798
    Cisco Nexus 5010 Switch
    Nexus
    2.3

  • Nexus 1010 and Management

    it is the first time that i install and configure a Nexus 1010.
    After unpackaging, i have upgrade the BIOS, CMC and Firmware of the nexus 1010 (like a classical C-serie server)
    The CIMC 's @IP is 10.10.0.100 ; I have connected the 10/100 Ethernet CIMC management port to my OOB  network where we have all OOB interfaces from Nx7k and Nx5k.
    Now i would want configure the Nx1010 in the topology "uplink type 3".
    port 1 and 2 : mangement Vlan
    port 3 to 6 : Control/packt Vlan and Data Vlan.
    In the setup wizard, we have to configure the int Mgmt0 of Nx 1010.
    In which network must be the Mgmt0 ; i am confused and mix up :
    - CIMC mgmt from the C-series server
    - mgmt0 int from nexus 1010 : by which physical interface goes throught this traffic : via "10/100 Ethernet CIMC management port" or via "Management vlan" ???
    - Vlan management : this Vlan will allow to manager the VSB VSM-1 et VSM-2....
    The Vlan management must not be the OOB network, must it ?
    It is not clear for my mind ; i mix up all this mgmt
    please help me !!!
    many thank in advance.
    NB : All the devices in our DC (Nx5k and Nx5K/Nx2K) have two management interface :
    1 - OOB management via the pysical OOB port
    2 - Inb management via a dedicated Vlan ; each device have 1 @IP in this Vlan (even the L2 Nx7k (without M1 card) via the cli "management")
    How could i have the these mgmt for Nexus 1010 / CIMC / VSM ???
    Last question : in order to upgrade the nx 1010, then download the nexus-1000v*.iso to bootflash:repository, which network/mgmt i have to used ???

    Hi Delahais, could you resolve your concern? .. I have the same doubt

  • Private Vlan, Etherchannel and Isolated Trunk on Nexus 5010

    I'm not sure if I'm missing something basic here however i though that I'd ask the question. I recieved a request from a client who is trying to seperate traffic out of a IBM P780 - one set of VIO servers/clients (Prod) is tagged with vlan x going out LAG 1 and another set of VIO server/clients (Test) is tagged with vlan y and z going out LAG 2. The problem is that the management subnet for these devices is on one subnet.
    The infrastructure is the host device is trunked via LACP etherchannel to Nexus 2148TP(5010) which than connects to the distribution layer being a Catalyst 6504 VSS. I have tried many things today, however I feel that the correct solution to get this working is to use an Isolated trunk (as the host device does not have private vlan functionality) even though there is no requirement for hosts to be segregated. I have configured:
    1. Private vlan mapping on the SVI;
    2. Primary vlan and association, and isolated vlan on Distribution (6504 VSS) and Access Layer (5010/2148)
    3. All Vlans are trunked between switches
    4. Private vlan isolated trunk and host mappings on the port-channel interface to the host (P780).
    I haven't had any luck. What I am seeing is as soon as I configure the Primary vlan on the Nexus 5010 (v5.2) (vlan y | private-vlan primary), this vlan (y) does not forward on any trunk on the Nexus 5010 switch, even without any other private vlan configuration. I believe this may be the cause to most of the issues I am having. Has any one else experienced this behaviour. Also, I haven't had a lot of experience with Private Vlans so I might be missing some fundamentals with this configuration. Any help would be appreciated.

    Hello Emcmanamy, Bruce,
    Thanks for your feedback.
    Just like you, I have been facing the same problematic last months with my customer.
    Regarding PVLAN on FEX, and as concluded in Bruce’s previous posts I understand :
    You can configure a host interface as an isolated or community access port only.
    We can configure “isolated trunk port” as well on a host interface. Maybe this specific point could be updated in the documentation.  
    This ability is documented here =>
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/layer2/513_N2_1/b_Cisco_n5k_layer2_config_gd_rel_513_N2_1_chapter_0101.html#task_1170903
    You cannot configure a host interface as a promiscuous  port.
    You cannot configure a host interface as a private  VLAN trunk port.
    Indeed a pvlan is not allowed on a trunk defined on a FEX host interface.
    However since NxOS 5.1(3)N2(1), the feature 'PVLAN on FEX trunk' is supported. But a command has to be activated before => system private-vlan fex trunk . When entered a warning about the presence of ‘FEX isolated trunks’ is prompted.
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/layer2/513_N2_1/b_Cisco_n5k_layer2_config_gd_rel_513_N2_1_chapter_0101.html#task_16C0869F1B0C4A68AFC3452721909705
    All these conditions are not met on a N5K interface.
    Best regards.
    Karim

  • LACP port channel between 6509 and Nexus 7K

    We are in the process of migrating from dual 6509's to dual 7010's.  We have moved our 5k/2K's behind the 7K and have layer 2 up between the 6509 and 7K.  This link is configured as a port channel with 2 1gig links using LACP.  The port channel is up and working and traffic is passing but it doesn't appear the load it equally distributed between the links.  Both the 7K and 6K are setup for src-dst-ip for the load balancing.  The links have been in place for over 12 hours and I would have expected them to "equal" out.  Has anyone had this issue in or is this to be expected?  For clarification there is not VPC inolved in this configuration it is simply a port-channel between one 6509 and a 7010.
    Thanks,
    Joe

    We are in the process of migrating from dual 6509's to dual 7010's.  We have moved our 5k/2K's behind the 7K and have layer 2 up between the 6509 and 7K.  This link is configured as a port channel with 2 1gig links using LACP.  The port channel is up and working and traffic is passing but it doesn't appear the load it equally distributed between the links.  Both the 7K and 6K are setup for src-dst-ip for the load balancing.  The links have been in place for over 12 hours and I would have expected them to "equal" out.  Has anyone had this issue in or is this to be expected?  For clarification there is not VPC inolved in this configuration it is simply a port-channel between one 6509 and a 7010.
    Thanks,
    Joe

  • Connecting a WS-C4948 to a Nexus 5010

    is it possible to connect a WS-C4948 switch to a Nexus 5010? I have a flat network with no vlans.I know you are suppose to use the first 8 ports of the Nexus to get it to be on a 1GB port. What gbic am i to use on the ws-c4948 switch? if using a fiber cable or a rj45 cable?

    I was able to get it to work.....thank  you for the guys who responded!!
    configuration on the WS-C4948:
    interface GigabitEthernet1/48
    description connection to nexus5010
    media-type rj45
    interface Vlan1
    ip address 10.x.x.226 255.0.0.0
    ip default-gateway 10.x.x.1
    configuration on the Nexus 5010:
    vrf context management
    vlan 1
    interface Vlan1
      no shutdown
      ip address 10.x.x.223/8
    interface Ethernet1/1
      switchport mode trunk
      speed 1000
    steps on adding vlan 1 and adding an IP address on the Nexus 5010:
    - remove int mgmt 0, ip address and vrf context management
    nexus5010(config)# int mgmt 0
    nexus5010(config-if)# no ip address
    nexus5010(config-if)# vrf context management
    nexus5010(config-vrf)# no ip route 0.0.0.0/0 10.x.x.1
    nexus5010(config-vrf)# exit
    - turn on feature interface-vlan, create int vlan 1, add IP address, no shut, add vrf context default
    nexus5010(config)# feature interface-vlan
    nexus5010(config)# int vlan 1
    nexus5010(config-if)# ip address 10.x.x.223/8
    nexus5010(config-if)# no shut
    nexus5010(config-if)# exit
    nexus5010(config)# vlan 1
    nexus5010(config-vlan)# exit
    nexus5010(config)# vrf context default
    nexus5010(config)# ip route 0.0.0.0/0 10.x.x.1
    nexus5010(config)# exit

  • Nexus 1000v, VMWare ESX and Microsoft SC VMM

    Hi,
    Im curious if anybody has worked up any solutions managing network infrastructure for VMWare ESX hosts/vms with the Nexus 1000v and Microsoft's System Center Virtual Machine Manager.
    There currently exists support for the 1000v and ESX and SCVMM using the Cisco 1000v software for MS Hyper-V and SCVMM.   There is no suck support for VMWare ESX.
    Im curious as to what others with VMWare, Nexus 1000v or equivalent and SCVMM have done to work around this issue.
    Trying to get some ideas.
    Thanks

    Aaron,
    The steps you have above are correct, you will need steps 1 - 4 to get it working correctly.  Normally people will create a separate VLAN for their NLB interfaces/subnet, to prevent uncessisary flooding of mcast frames within the network.
    To answer your questions
    1) I've seen multiple customer run this configuration
    2) The steps you have are correct
    3) You can't enable/disable IGMP snooping on UCS.  It's enabled by default and not a configurable option.  There's no need to change anything within UCS in regards to MS NLB with the procedure above.  FYI - the ability to disable/enable IGMP snooping on UCS is slated for an upcoming release 2.1.
    This is the correct method untill the time we have the option of configuring static multicast mac entries on
    the Nexus 1000v.  If this is a feature you'd like, please open a TAC case and request for bug CSCtb93725 to be linked to your SR. 
    This will give more "push" to our develpment team to prioritize this request.
    Hopefully some other customers can share their experience.
    Regards,
    Robert

  • Fex 1 Nexus 2148 to 2 Nexus 5010 problem?

    hi all
    I'm having trouble when fex(ing) 1 nexus 2000 to 2 nexus 5000.
    I've configured as dual home from 1 nexus 2k. But after success config, just 1 nexus 5k can see 48 port on it. other cannot see it and it showed as module offline
    Here's is results:
    N5K-01(config-if)# sh int e1/4 fex-intf
    Fabric           FEX
    Interface        Interfaces
    Eth1/4        
    N5K-01(config-if)#
    N5K-02# sh int e1/4 fex-intf
    Fabric           FEX
    Interface        Interfaces
    Eth1/4          Eth100/1/48   Eth100/1/47   Eth100/1/46   Eth100/1/45 
                     Eth100/1/44   Eth100/1/43   Eth100/1/42   Eth100/1/41 
                     Eth100/1/40   Eth100/1/39   Eth100/1/38   Eth100/1/37 
                     Eth100/1/36   Eth100/1/35   Eth100/1/34   Eth100/1/33 
                     Eth100/1/32   Eth100/1/31   Eth100/1/30   Eth100/1/29 
                     Eth100/1/28   Eth100/1/27   Eth100/1/26   Eth100/1/25 
                     Eth100/1/24   Eth100/1/23   Eth100/1/22   Eth100/1/21 
                     Eth100/1/20   Eth100/1/19   Eth100/1/18   Eth100/1/17 
                     Eth100/1/16   Eth100/1/15   Eth100/1/14   Eth100/1/13 
                     Eth100/1/12   Eth100/1/11   Eth100/1/10   Eth100/1/9  
                     Eth100/1/8    Eth100/1/7    Eth100/1/6    Eth100/1/5  
                     Eth100/1/4    Eth100/1/3    Eth100/1/2    Eth100/1/1
    ===============================
    N5K-01(config-if)# sh fex 100 detail
    FEX: 100 Description: FEX0100   state: Offline
      FEX version: 4.1(3)N2(1a) [Switch version: 4.1(3)N2(1a)]
      FEX Interim version: 4.1(3)N2(1a)
      Switch Interim version: 4.1(3)N2(1a)
      Extender Model: N2K-C2148T-1GE,  Extender Serial: JAF1405CKHC
      Part No: 73-12009-06
      Card Id: 70, Mac Addr: 00:0d:ec:fd:48:82, Num Macs: 64
      Module Sw Gen: 12594  [Switch Sw Gen: 21]
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth1/4
      Fabric interface state:
        Eth1/4 - Interface Up. State: Active
      Fex Port        State  Fabric Port  Primary Fabric
           Eth100/1/1  Down      Eth1/4      Eth1/4
           Eth100/1/2  Down      Eth1/4      Eth1/4
           Eth100/1/3  Down      Eth1/4      Eth1/4
           Eth100/1/4  Down      Eth1/4      Eth1/4
           Eth100/1/5  Down      Eth1/4      Eth1/4
           Eth100/1/6  Down      Eth1/4      Eth1/4
           Eth100/1/7  Down      Eth1/4      Eth1/4
           Eth100/1/8  Down      Eth1/4      Eth1/4
           Eth100/1/9  Down      Eth1/4      Eth1/4
          Eth100/1/10  Down      Eth1/4      Eth1/4
          Eth100/1/11  Down      Eth1/4      Eth1/4
          Eth100/1/12  Down      Eth1/4      Eth1/4
          Eth100/1/13  Down      Eth1/4      Eth1/4
          Eth100/1/14  Down      Eth1/4      Eth1/4
          Eth100/1/15  Down      Eth1/4      Eth1/4
          Eth100/1/16  Down      Eth1/4      Eth1/4
          Eth100/1/17  Down      Eth1/4      Eth1/4
          Eth100/1/18  Down      Eth1/4      Eth1/4
          Eth100/1/19  Down      Eth1/4      Eth1/4
          Eth100/1/20  Down      Eth1/4      Eth1/4
          Eth100/1/21  Down      Eth1/4      Eth1/4
          Eth100/1/22  Down      Eth1/4      Eth1/4
          Eth100/1/23  Down      Eth1/4      Eth1/4
          Eth100/1/24  Down      Eth1/4      Eth1/4
          Eth100/1/25  Down      Eth1/4      Eth1/4
          Eth100/1/26  Down      Eth1/4      Eth1/4
          Eth100/1/27  Down      Eth1/4      Eth1/4
          Eth100/1/28  Down      Eth1/4      Eth1/4
          Eth100/1/29  Down      Eth1/4      Eth1/4
          Eth100/1/30  Down      Eth1/4      Eth1/4
          Eth100/1/31  Down      Eth1/4      Eth1/4
          Eth100/1/32  Down      Eth1/4      Eth1/4
          Eth100/1/33  Down      Eth1/4      Eth1/4
          Eth100/1/34  Down      Eth1/4      Eth1/4
          Eth100/1/35  Down      Eth1/4      Eth1/4
          Eth100/1/36  Down      Eth1/4      Eth1/4
          Eth100/1/37  Down      Eth1/4      Eth1/4
          Eth100/1/38  Down      Eth1/4      Eth1/4
          Eth100/1/39  Down      Eth1/4      Eth1/4
          Eth100/1/40  Down      Eth1/4      Eth1/4
          Eth100/1/41  Down      Eth1/4      Eth1/4
          Eth100/1/42  Down      Eth1/4      Eth1/4
          Eth100/1/43  Down      Eth1/4      Eth1/4
          Eth100/1/44  Down      Eth1/4      Eth1/4
          Eth100/1/45  Down      Eth1/4      Eth1/4
          Eth100/1/46  Down      Eth1/4      Eth1/4
          Eth100/1/47  Down      Eth1/4      Eth1/4
          Eth100/1/48  Down      Eth1/4      Eth1/4
    Logs:
    [11/24/2010 03:16:20.624283] Module register received
    [11/24/2010 03:16:20.627639] Registration response sent
    [11/24/2010 03:16:21.115021] Module Online Sequence
    [11/24/2010 03:16:22.379395] Module Online
    [11/24/2010 03:52:09.779773] Module disconnected
    [11/24/2010 03:52:09.781691] Offlining Module
    [11/24/2010 03:52:09.782231] Module Offline Sequence
    [11/24/2010 03:52:11.735462] Module Offline
    [11/24/2010 04:06:25.258659] Module disconnected
    [11/24/2010 04:06:25.259890] Offlining Module
    =================
    N5K-02# sh fex 100 detail
    FEX: 100 Description: FEX0100   state: Online
      FEX version: 4.1(3)N2(1a) [Switch version: 4.1(3)N2(1a)]
      FEX Interim version: 4.1(3)N2(1a)
      Switch Interim version: 4.1(3)N2(1a)
      Extender Model: N2K-C2148T-1GE,  Extender Serial: JAF1405CKHC
      Part No: 73-12009-06
      Card Id: 70, Mac Addr: 00:0d:ec:fd:48:82, Num Macs: 64
      Module Sw Gen: 12594  [Switch Sw Gen: 21]
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth1/4
      Fabric interface state:
        Eth1/4 - Interface Up. State: Active
      Fex Port        State  Fabric Port  Primary Fabric
           Eth100/1/1  Down      Eth1/4      Eth1/4
           Eth100/1/2  Down      Eth1/4      Eth1/4
           Eth100/1/3  Down      Eth1/4      Eth1/4
           Eth100/1/4  Down      Eth1/4      Eth1/4
           Eth100/1/5  Down      Eth1/4      Eth1/4
           Eth100/1/6  Down      Eth1/4      Eth1/4
           Eth100/1/7  Down      Eth1/4      Eth1/4
           Eth100/1/8  Down      Eth1/4      Eth1/4
           Eth100/1/9  Down      Eth1/4      Eth1/4
          Eth100/1/10  Down      Eth1/4      Eth1/4
          Eth100/1/11  Down      Eth1/4      Eth1/4
          Eth100/1/12  Down      Eth1/4      Eth1/4
          Eth100/1/13  Down      Eth1/4      Eth1/4
          Eth100/1/14  Down      Eth1/4      Eth1/4
          Eth100/1/15  Down      Eth1/4      Eth1/4
          Eth100/1/16  Down      Eth1/4      Eth1/4
          Eth100/1/17  Down      Eth1/4      Eth1/4
          Eth100/1/18  Down      Eth1/4      Eth1/4
          Eth100/1/19  Down      Eth1/4      Eth1/4
          Eth100/1/20  Down      Eth1/4      Eth1/4
          Eth100/1/21  Down      Eth1/4      Eth1/4
          Eth100/1/22  Down      Eth1/4      Eth1/4
          Eth100/1/23  Down      Eth1/4      Eth1/4
          Eth100/1/24  Down      Eth1/4      Eth1/4
          Eth100/1/25  Down      Eth1/4      Eth1/4
          Eth100/1/26  Down      Eth1/4      Eth1/4
          Eth100/1/27  Down      Eth1/4      Eth1/4
          Eth100/1/28  Down      Eth1/4      Eth1/4
          Eth100/1/29  Down      Eth1/4      Eth1/4
          Eth100/1/30  Down      Eth1/4      Eth1/4
          Eth100/1/31  Down      Eth1/4      Eth1/4
          Eth100/1/32  Down      Eth1/4      Eth1/4
          Eth100/1/33  Down      Eth1/4      Eth1/4
          Eth100/1/34  Down      Eth1/4      Eth1/4
          Eth100/1/35  Down      Eth1/4      Eth1/4
          Eth100/1/36  Down      Eth1/4      Eth1/4
          Eth100/1/37  Down      Eth1/4      Eth1/4
          Eth100/1/38  Down      Eth1/4      Eth1/4
          Eth100/1/39  Down      Eth1/4      Eth1/4
          Eth100/1/40  Down      Eth1/4      Eth1/4
          Eth100/1/41  Down      Eth1/4      Eth1/4
          Eth100/1/42  Down      Eth1/4      Eth1/4
          Eth100/1/43  Down      Eth1/4      Eth1/4
          Eth100/1/44  Down      Eth1/4      Eth1/4
          Eth100/1/45  Down      Eth1/4      Eth1/4
          Eth100/1/46  Down      Eth1/4      Eth1/4
          Eth100/1/47  Down      Eth1/4      Eth1/4
          Eth100/1/48  Down      Eth1/4      Eth1/4
    Logs:
    [11/24/2010 03:49:38.824900] Module timed out
    [11/24/2010 03:54:08.225000] Module register received
    [11/24/2010 03:54:08.226093] Registration response sent
    [11/24/2010 03:54:08.540805] Module Online Sequence
    [11/24/2010 03:54:10.7287] Module Online
    Anyone can help me with this?
    Thanks.

    I already configured vPC between 2 Nexus 5010
    N5K-01# sh vpc brief
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                   : 1  
    Peer status                     : peer adjacency formed ok     
    vPC keep-alive status           : peer is alive                
    Configuration consistency status: success
    vPC role                        : primary                     
    vPC Peer-link status
    id   Port   Status Active vlans   
    1    Po1    up     1                                                      
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    100    Po100       down   success     success                    - 
    N5K-02# sh vpc
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                   : 1  
    Peer status                     : peer adjacency formed ok     
    vPC keep-alive status           : peer is alive                
    Configuration consistency status: success
    vPC role                        : secondary                   
    vPC Peer-link status
    id   Port   Status Active vlans   
    1    Po1    up     1                                                      
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    100    Po100       down*  success     success                    -        
    N5K-02#
    may i miss some config ?

  • LMS 3.2: RME failed archive with Nexus 5010

    Hi,
    LMS 3.2, RME 4.3.1, dev packages updated, Windows.
    We would like to archive the configuration of the Nexus 5010 switches. Due to authentication with Radius based on tokens we're not able to use telnet/SSH and therefore we only can use SNMP WRite in combination with TFTP.  But, this is not working at all. Other systems like 3750 works fine. Is there a difference between Catalysts IOS and nexus NXOS?
    I searched the forum and found this:
    https://supportforums.cisco.com/message/663481#663481
    upgrade to LMS 2.6, archive config not working anymore
    We ship and start a TFTP server by default on Windows.  You must have an SNMP read-write community string configured on your devices, and entered in DCR for TFTP config fetches to work.  Additionally, udp/69 must be open between device and server.
    The easiest way to troubleshoot this kind of problem is to start a sniffer trace on the LMS server (using Device Center > Packet Capture).  Filter on all traffic to one of the failing devices.  Then, run a Sync Archive job for that same device.  When it fails, the sniffer trace will indicate what the problem is
    Regards
    Ad Olsthoorn

    Hi Lavramov,
    Yes I'm quite sure, I installed the required packages acoording to the Nexus.RME431.v2-2.readme.pdf manual. the manual tell me to install the following (see also attachement).
    To install the Cisco Nexus Series Package, you must install the following dependent packages:
    - SharedDcmaSS.RME431.v2-2.zip
    - SharedInventoryMDS.RME431.v1-5-1.zip
    - SharedSwimMDS9000.RME431.v1-6-1.zip
    - SharedNetshowSS.RME431.v1-1.zip
    regards
    Ad

  • Can't archive nexus 5010 configs (LMS 3.2)

    Using LMS 3.2 I can't archive configs from
    our Nexus 5010 ( 4.2(1)N1(1) ) devices . I have installed
    the   necessary device package Nexus.RME431.v2-4.zip. Following error occures:
    *** Device Details for                          gf02na50050p                         ***
    Protocol ==>                          Unknown / Not Applicable
    Selected Protocols with order ==>                                                                                  SSH,SCP,TFTP,RCP,Telnet
    Execution Result:
    RUNNING
    CM0151 PRIMARY RUNNING Config  fetch failed for gf02na50050p Cause: Failed to fetch config using  TFTPFailed to establish TELNET connection to 10.92.170.214 - Cause:  Connection refused.
    Action: Check if protocol is  supported by device and required device package is installed. Check  device credentials. Increase timeout value, if required.
    Telnet on device is disabled, SSH enabled.
    with only SSH on RME   followig error:
    *** Device Details for                          gf02na50050p                         ***
    Protocol ==>                          Unknown / Not Applicable
    Selected Protocols with order ==>                                                                                  SSH
    Execution Result:
    RUNNING
    CM0151 PRIMARY RUNNING Config  fetch failed for gf02na50050p Cause: Failed to get the start  tag-Building Configuration ... in the configuration.  Action: Check if  protocol is supported by device and required device package is  installed. Check device credentials. Increase timeout value, if  required.
    Thanks
    Igor

    RME 4.3.1; windows platform
    with one customer I have the same issue with a Nexus 5020. Software version is :
    Software
      BIOS:      version 1.3.0 [last: ]
      loader:    version N/A
      kickstart: version 4.2(1)N2(1)
      system:    version 4.2(1)N2(1)
      power-seq: version v1.2
      BIOS compile time:       09/08/09 [last: ]
      kickstart image file is: bootflash:///n5000-uk9-kickstart.4.2.1.N2.1.bin
      kickstart compile time:  7/28/2010 18:00:00 [07/29/2010 03:10:19]
      system image file is:    bootflash:/n5000-uk9.4.2.1.N2.1.bin
      system compile time:     7/28/2010 18:00:00 [07/29/2010 07:18:12]
    Hardware
      cisco Nexus5020 Chassis ("40x10GE/Supervisor")
      Intel(R) Celeron(R) M CPU    with 2074284 kB of memory.
    ===============
    following RME packages are installed:
        SharedNetshowSS      1.1.2      SharedNetshowSS device package
        SharedSwimMDS9000    1.6.3      SharedSwimMDS9000 device package
        SharedInventoryMDS   1.5.1      SharedInventoryMDS device package
        SharedDcmaSS         2.2.2      SharedDcmaSS device package
        Nexus                2.4        Nexus device package
    ===============
    >>> I see the following problems with SSH instrumentation of the Nexus Platform when looking into the debug file. The file I got is more or less the same then the one Marc posted.
    The customer does not have a banner configured so the standard login procedure shows the following when login is done manually. RME automatically interpretes the first line after "Login as: " as a banner...
    login as: Nexus
    Nexus 5000 Switch
    Using keyboard-interactive authentication.
    Password:
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
    The copyrights to certain works contained in this software are
    owned by other third parties and used and distributed under
    license. Certain components of this software are licensed under
    the GNU General Public License (GPL) version 2.0 or the GNU
    Lesser General Public License (LGPL) Version 2.1. A copy of each
    such license is available at
    http://www.opensource.org/licenses/gpl-2.0.php and
    http://www.opensource.org/licenses/lgpl-2.1.php
    devicename#
    >>> and RME wants to take the last line as the prompt, resulting in a non-fatal java exception:
    [line 1471 ff.]
    [ Mon Aug 30  08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Learning prompt: sA[0] == 'http://www.opensource.org/licenses/lgpl-2.1.php'
    [ Mon Aug 30  08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Learning prompt: sA[1] == ''
    [ Mon Aug 30  08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,printStackTrace,51,stacktracecom.cisco.nm.lib.cmdsvc.CmdSvcException: Prompt learning failed: 'http://www.opensource.org/licenses/lgpl-2.1.php' && '' do not match.
        at com.cisco.nm.lib.cmdsvc.Session.tune(Session.java:904)
        at com.cisco.nm.lib.cmdsvc.Session.tune(Session.java:833)
        at com.cisco.nm.lib.cmdsvc.AuthHandler.connect(AuthHandler.java:267)
        at com.cisco.nm.lib.cmdsvc.OpConnect.invoke(OpConnect.java:56)
        at com.cisco.nm.lib.cmdsvc.SessionContext.invoke(SessionContext.java:299)
    >> Ok, RME proceeds, but the SSH implementation (SharedDcmaSS ?) cannot extract the config and a java exception occures which leads to "Closing the session":
    [ Mon Aug 30  08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Returning from Session.send('show startup-config
    [ Mon Aug 30  08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,in trimPrompt(), prompt == ''
    [ Mon Aug 30  08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator,fetchConfig,490,Failed to get the start tag-Building Configuration ... in the configuration.com.cisco.nm.xms.xdi.ags.config.ConfigTransportException: Failed to get the start tag-Building Configuration ... in the configuration.
        at com.cisco.nm.xms.xdi.pkgs.SharedDcmaSS.transport.SSCliOperator.extractConfig2Buffer(SSCliOperator.java:176)
        at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator.fetchConfig(CliOperator.java:436)
        at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator.fetchConfig(CliOperator.java:510)
        at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.SimpleFetchOperation.performOperation(SimpleFetchOperation.java:61)
        at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.ConfigOperation.doConfigOperation(ConfigOperation.java:111)
        at com.cisco.nm.xms.xdi.pkgs.SharedDcmaSS.transport.SSConfigOperator.fetchConfig(SSConfigOperator.java:65)
        at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.updateArchiveForDevice(ConfigManager.java:1315)
        at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.performCollection(ConfigManager.java:3291)
        at com.cisco.nm.rmeng.dcma.configmanager.CfgUpdateThread.run(CfgUpdateThread.java:27)
    [ Mon Aug 30  08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.SimpleFetchOperation,performOperation,62,FetchStatus - FAILURE for Protocol SSH for device x.x.x.x
    >> As telnet and tftp are not allowed the config cannot be archived (Customer reports no problems with telnet...)
    The config itself starts and ends with the following lines:
    devicename# show startup-config
    !Command: show startup-config
    !Time: Mon Sep  6 16:41:02 2010
    !Startup config saved at: Mon Aug 16 15:41:39 2010
    version 4.2(1)N2(1)
    no feature telnet
    no telnet server enable
    no feature http-server
    cfs eth distribute
    feature udld
    feature interface-vlan
    feature lacp
    feature vpc
    feature lldp
    feature vtp
    interface mgmt0
      shutdown force
      shutdown force
      no snmp trap link-status
      no snmp trap link-status
    clock timezone MEZ 1 0
    clock summer-time MEZS 5 sun mar 02:00 5 sun oct 03:00 60
    line console
    boot kickstart bootflash:/n5000-uk9-kickstart.4.2.1.N2.1.bin
    boot system bootflash:/n5000-uk9.4.2.1.N2.1.bin
    ip route 0.0.0.0/0 172.16.4.1
    vtp mode transparent
    vtp domain sap
    logging server x.x.x.x 7 use-vrf default
    logging server y.y.y.y 7 use-vrf default
    devicename#
    For me it looks like as a bug in the ssh implementation in RME, but I cannot find a bug id on CCO ....

  • Nexus 5010 VPC noOperMem

    I'm trying to set up a vpc between two Nexus 5010s going to an HP VMware chassis..
    I'm getting the error no operational members and am not sure what I did wrong.
    I've attached the configs for VPC121, if anyone has any ideas I'd really appreciate it.

    Try rebuilding the Portchannel again
    interface Ethernet1/11
    no switchport mode trunk
    no switchport trunk allowed vlan 4,8,10,12,14,16-17,19-21,24-25,27,64,72,80,88,96,124,190,200,209,257-258,420,900,1102
    no channel-group 121 mode active
    no int po121
    new config:
    int e1/11
    channel-group 121 mode active
    The command above should create po 121 for you
    int po121
    switchport mode trunk
    switchport trunk allowed vlan 4,8,10,12,14,16-17,19-21,24-25,27,64,72,80,88,96,124,190,200,209,257-258,420,900,1102
    no sh
    now test again
    HTH

  • Nexus 5010 vlan supported limits

    Hi,
    Just wanted to know whether the configuration  limits of 512 vlan on Nexus 5010 specified in the document below are software limitation which can be removed by adding enhanced image etc or hard limits which cannot be removed.
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configuration_limits/limits_503/nexus_5000_config_limits_503_n1_1b.html
    Regards
    Vijay Sequeira

    Hard limits. There is no special license that can increase the numbers. Nexus doesnt have the concept of enhanced images either there is a single OS image and you just unlock specific features (eg fibre channel/fcoe  features) by applying licences.

  • Cisco Nexus 5010 FCOE Interconnection

    Hi, i would really apreciate your help on this  doubt.
    Is it possible to create a link between two cisco nexus 5010
    using  CNA interfaces ?
    I've already configured the ethernet interfaces(where the cna is plugged in),
    i've binded the E1/2, mapped the vsan, created specific traffic vlan, and so on ...
    I have  tried everything what's written in the manual but the vcf interface won't set up, keeps telling me "vcf is down" .
    What am i doing wrong ? or this connection is imposible ...
    Thanks in advance.

    5020A.1# show vlan fcoe
    Original VLAN ID        Translated VSAN ID      Association State
          100                       100              Operational
    5020A.1# sho feature | grep np
    npiv                  1         disabled
    npv                   1         enabled
    5020A.1# sho interface brief | grep -i fc
    fc2/3      100    NP     off     up               swl    NP      4    --
    fc2/4      100    NP     off     up               swl    NP      4    --
    vfc15      100    F      on      trunking         --     TF      auto --
    !!!here's vfc15 and it's associated interface
    5020A.1# sho run int vf15
    !Command: show running-config interface vfc15
    !Time: Thu Feb 17 12:45:29 2011
    version 5.0(2)N2(1)
    interface vfc15
      bind interface Ethernet1/15
      no shutdown
    5020A.1# show inter e1/15 status
    Port          Name               Status    Vlan      Duplex  Speed   Type
    Eth1/15       FCoE ports  connected trunk     full    10G     1/10g     
    5020A.1# sho run int e1/15
    !Command: show running-config interface Ethernet1/15
    !Time: Thu Feb 17 12:45:33 2011
    version 5.0(2)N2(1)
    interface Ethernet1/15
      description FCoE ports
      switchport mode trunk
      switchport trunk allowed vlan 1,10,30,100
      spanning-tree port type edge trunk
      load-interval counter 2 30
      load-interval counter 3 30
    5020A.1#
    5020A.1#
    5020A.1#
    I'd use this to get a look at FIP
    ethanalyzer local sniff-interface inbound-hi detailed-dissection display-filter vlan.etype==0x8914 limit-captured 200 write bootflash:fipcap1.pcap
    This is assuming that your eth1/2 is working and up.
    reply w/your associated show commands
    show fcoe vlan
    show feature | grep np
    show interface brief | grep -i fc
    show vsan
    sho run inter vfc x
    show run inter eth x/y
    show inter eth x/y status
    other questions
    1. what OS?
    2. what vendor of CNA card?
    Joe

  • Nexus (5010) To FEX Distance Limitations

    Hello,
    My question is concerning the software-imposed distance limitations for Nexus-to-Fex connections.
    With a Nexus 5010 running 4.2 (1) N1 (1) code, I believe there is a software limitation on the distance the FEX can be located from the Nexus.  I have two questions concerning this:
    Is there any log data, or a cli command, to verify that the fex connection has exceeded that distance?
    What symptoms are produced when the fex is too far from the Nexus (ie, does the link come up but the image not load?)
    I would like to determine that the reason I have a FEX, located in a second data centre, that is not coming up is actually related to the distance from the FEX to the Nexus and not related to some other problem.
    Thanks for any suggestions/info offerred.
    Simon

    I have not seen any reference to a software limitation for the distance between a N5K and a FEX.
    The release notesfor 4.2(1)N1) listed si not showing it unless, my first cup of coffee has not kicked in
    http://http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5000/sw/configuration_limits/limits_421/Cisco_Nexus_5000_Series_Configuration_Limits_for_Cisco_NX_OS_Release_421_N1_1_and_421_N2_1_chapter1.html
    As far as believe the only distance limitation would be the type of cable used. Either the distance limitation of the SMF SFP or the MMF SFP, or the CX ethernet cable which has reletively short distance spans.
    Where is you here about this limitation?
    And more importantly, what issues are you have towards the FEX?

  • Nexus 5010 to Cat 6506 Sup720 using 1GB ports

    Hi,
    Our budget just got cut in half--sign of the times! Can I connect a Nexus 5010 to a 6506 with 6724-SFP module using a 6GB etherchannel? The 6506 has a Sup 720 and will only be used to route the VLANs. All server swithing will be done through the Nexus 5010 and 2148T.
    Thanks,

    hi Isabel,
    >> Jul 5, 2009, 9:14am PST
    >> Both the Nexus 5000 and Nexus 7000 will add support for a
    >> feature called Virtual Port Channels (VPC) which allows
    >> the formation of multi-chassis ether channels like that
    >> with VSS on the Catalyst 6500.
    Nexus 7000 has had virtual Port Channel (vPC) since the release of NX-OS 4.2 around January this year.
    see http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/white_paper_c11-516396.html
    you are correct that Nexus 5000 doesn't yet have this. N5K will gain vPC when NX-OS 4.2 is released on N5K in/on/around Q3 CY2009.
    cheers,
    lincoln.

Maybe you are looking for