Config ethernet interface on Nexus 7010

                   Hi all,
    Please help to config the ethernet interface port 1 on slot 7. The old 6500 command "interface 7/1" does not work, got message "invalid range". Thank you.
   Also I have the 1/10 Gbps Ethernet module (N7K-F248XP-25E), please educate me how to choose between 1 or 10 Gbps for the end devices ? Thanks.

Wouldnt it be interface ethernet7/1  ?  
interface Ethernet3/5  is a interface configured on my switch. It is a 7009

Similar Messages

  • Port-channel L2 problem with Fabric Interconnect and Nexus 7010

    Hi,
    i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
    but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
    I was trying :
    1. I using non dedicated port in Nexus 7010.
          - rate-mode share
          - channel-group 1 mode active
          - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    2. I using non dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode on
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
    3. I using dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    4. I using dedicated port in Nexus 7010
         - rate-mode dedicated
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up and running well.
    but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
    is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
    i attach the topology of N7K with Fabric interconnect.
    regards,
    Berwin H

    Hi Manish,
    the issue was solved, i was fix it last week.
    the solution is:
    i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2)  so i allocate the interface on all module
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
    i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
    So here the result of my port-channel :
    SVRN7KFARM-HO-01# show 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)
    Group Port-       Type     Protocol  Member Ports
          Channel
    1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                         Eth1/4(P)    Eth1/25(P)  
    2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                         Eth1/12(P)   Eth1/26(P)  
    3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)  
    4     Po4(SU)     Eth      NONE      Eth10/32(P)  Eth10/34(P)  Eth10/35(P)
                                         Eth10/36(P)
    Thanks.
    Berwin H

  • Nexus 5000 - Odd Ethernet interface behavior (link down inactive)

    Hi Guys,
    This would sound really trivial but it is very odd behavior.
    - We have a server connected to a 2, Nexus 5000s (for resiliancy)
    - When there is no config on the ethernet interfaces whatsoever, the ethernet interface is UP / UP, there is minimal amount of traffic on the link etc. E.g.
    Ethernet1/16 is up
      Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
      Description: shipley-p1.its RK14/A13
      MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is access
      full-duplex, 10 Gb/s, media type is 1/10g
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      Last link flapped 00:00:07
      Last clearing of "show interface" counters 05:42:32
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 96 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 0 bps, 0 pps; output rate 8 bps, 0 pps
      RX
        0 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  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
        0 unicast packets  163 multicast packets  0 broadcast packets
        163 output packets  15883 bytes
        0 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble
        0 Tx pause
      1 interface resets
    - As soon as I configure the link to be an access port, the link goes down, flagging "inactivity" E.g.
    sh int e1/16
    Ethernet1/16 is down (inactive)
      Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
      Description: shipley-p1.its RK14/A13
      MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is access
      auto-duplex, 10 Gb/s, media type is 1/10g
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      Last link flapped 05:38:03
      Last clearing of "show interface" counters 05:41:33
      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)
        input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
      RX
        0 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  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
        0 unicast packets  146 multicast packets  0 broadcast packets
        146 output packets  13083 bytes
        0 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble
        0 Tx pause
      0 interface resets
    - This behavior is seen on both 5Ks
    - I've tried using a different set of ports, changed SFPs, and fibre cabling to no avail
    - I can't seem to understand this behavior?!  In that, why would configuring the port cause the link to go down?
    - If anyone has experience this before, or could shed some light on this behavior, it would be appreciated.
    sh ver
    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 herein are owned by
    other third parties and are used and distributed under license.
    Some parts of this software are covered under the GNU Public
    License. A copy of the license is available at
    http://www.gnu.org/licenses/gpl.html.
    Software
      BIOS:      version 1.2.0
      loader:    version N/A
      kickstart: version 4.2(1)N1(1)
      system:    version 4.2(1)N1(1)
      power-seq: version v1.2
      BIOS compile time:       06/19/08
      kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin
      kickstart compile time:  4/29/2010 19:00:00 [04/30/2010 02:38:04]
      system image file is:    bootflash:/n5000-uk9.4.2.1.N1.1.bin
      system compile time:     4/29/2010 19:00:00 [04/30/2010 03:51:47]
    thanks
    Sheldon

    I had identical issue
    Two interfaces on two different FEXes were INACTIVE. I have two Nexus 5596 in vPC and A/A FEXes.
    I also use config-sync feature.
    Very same configuration was applied to other ports on other FEXes and they were working with no problems.
    interface Ethernet119/1/1
      inherit port-profile PP-Exchange2003
    I checked VLAN status associated with this profile and it was active (of course it was, other ports were ok).
    I solved it by removing port profile from this port and re-applied it... voila, port changed state to up!
    Very very strange.

  • MGTM0 Interface only in Admin VDC in Nexus 7010

       Hi guys,
          I created two new VDCs in a Nexus 7010 (NX-OS 6.2.6) and I can see the MGTM0 interface only in the Admin VDC
          I wanted to see the MGTM0 in all VDCs.
        Does someone get this problem too ?
        My Best Regards,
        Andre Gustavo Lomonaco

     Hi Reza,
          Thanks for your reply.
          If the user run the setup wizard, the interface mgtm0 will be created in VDC.
          If the user don't run the setup wizard, the interface mgtm0 will not be created and you will need
          to only use the interface mgtm 0 command to create the interface.
          Thanks a lot

  • How to config management interface to an ethernet interface?

    we have an ASA 5540 that require LAN port for failover. And the only available interface left is the management port. How to config management interface to an ethernet interface?

    You can disable the management-only mode on that interface to make it as regualr routable port and use for any other purpose including LAN base failover purposes.
    About management interface - 5510 but generally applies to management0/0 itself including 5540
    http://www.cisco.com/en/US/docs/security/asa/asa80/configuration/guide/intparam.html#wp1057800
    configuring LAN base failover
    http://www.cisco.com/en/US/docs/security/asa/asa80/configuration/guide/intparam.html#wp1057800
    Rgds
    -Jorge

  • Nexus 7010 Loses Config after power off

    Recently we installed a pair of Nexus 7010's and we recently moved them to an APC rack better suited for their size. Upon powering them up we found out that the VDC's lost their configurations. The VDC's and the alloated resources were still there as well as the default VDC configuration but the other 2 we have configured had their configurations missing. We have been observing best practices and saving the configuration to NVRAM with the copy run start comand as well as the copy run start vdc-all commands yet the configurations were still lost.
    Can anyone shed some light on what the problem may be?
    Thank you in advance for your help!

    We had the same issue TAC told us to reset the supv
    ,,,,, you might want to save your config ;-)  it worked for us

  • Does the F2 linecard (N7k-F248XP-25) on Nexus 7010 support Layer 3?

    Hi All,
    I am sure that F1 linecards on Nexus weren’t able to support L3 functionality, so my query is does the F2 linecard (N7k-F248XP-25) on Nexus 7010 support Layer 3?
    Regards,
    Mayank

    Hi, Im know that this is resolved but i have a f2e Card
    Model:                 N7K-F248XP-25E
    Type (SFP capable):    1000base-SX
    and i can not configure an interface as l3
    NX7K-1-VDC-3T-S1-L3FP(config)# interface ethernet 7/2
    NX7K-1-VDC-3T-S1-L3FP(config-if)# no switchport
    ERROR: Ethernet7/2: requested config change not allowed
    whats the problem??
    Software
      BIOS:      version 2.12.0
      kickstart: version 6.2(2)
      system:    version 6.2(2)
      BIOS compile time:       05/29/2013
      kickstart image file is: bootflash:///n7000-s2-kickstart-npe.6.2.2.bin
      kickstart compile time:  7/9/2013 20:00:00 [08/22/2013 04:51:27]
      system image file is:    bootflash:///n7000-s2-dk9.6.2.2.bin
      system compile time:     7/9/2013 20:00:00 [08/22/2013 08:07:03]
    Hardware
      cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor Module-2")
      Intel(R) Xeon(R) CPU         with 12224956 kB of memory.

  • Disruptive ISSU 6.1.4a- 6.2.8 on Nexus 7010 sup1 because of LACP timers.

    Hi all.
    The problem.
    Today I updated my Nexus 7010 sup1 from 6.1.4a to 6.2.8.
    I want did it in ISSU mode, but after impact check I got this:
    Compatibility check is done:
    Module  bootable          Impact  Install-type  Reason
         1       yes  non-disruptive       rolling  
         2       yes  non-disruptive       rolling  
         3       yes  non-disruptive       rolling  
         4       yes  non-disruptive       rolling  
         5       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         6       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         7       yes  non-disruptive       rolling  
         8       yes  non-disruptive       rolling  
         9       yes  non-disruptive       rolling  
        10       yes  non-disruptive       rolling  
    Additional info for this installation:
    Service "lacp" in vdc 1: LACP: Upgrade will be disruptive as 6 switch ports and 0 fex ports are not upgrade ready!!
          Issue the "show lacp issu-impact" cli for more details.
    (modified the impact to <Hitful>  for module <6>)
    Do you want to continue with the installation (y/n)?  [n] y
    I went on with yes and update script reboot both sups after updated all modules.
    It was quite a surprise for me (yes I know I must see word "disruptive" opposite my sups 5 and 6). Because I already had done two ISSU updates on two nexuses (from 5.1.* ->5.2.7 and 5.2.7 -> 6.1.4a) and didn`t have any trouble with LACP timers. Is it a new feature of the 6.* train?
    I have another Nexus that I want to update. And it also has same problem with LACP timers.
    show install all impact give me the same disruptive result because of LACP.
    Can I somehow suppress such ISSU behavior? In case of LACP. I don`t have vPC, just ordinal PC.
    It is a way better if some LACP interfaces flap in process, than an almost 14 minutes of all 7010 chassis reboot that I had.
    Although problem with LACP timers is that they must be the same on the switch side and on the other side. And in case of switches, linux boxes or HP VCs changing LACP timers isn`t a big problem. IT is a biggg problem in case of the Windows Server.
    sh lacp interface ethernet 8/13
    Interface Ethernet8/13 is up
      Channel group is 13 port channel is Po13
    Local Port: Eth8/13   MAC Address= 40-55-39-23-1e-c1
      System Identifier=0x8000,  Port Identifier=0x8000,0x80d
      Operational key=12
      LACP_Activity=active
      LACP_Timeout=Long Timeout (30s)
    Neighbor: 0x1
      MAC Address= ac-16-2d-a4-f2-54
      System Identifier=0xffff,  Port Identifier=0xff,0x1
      Operational key=17
      LACP_Activity=active
      LACP_Timeout=short Timeout (1s)
    They must be the same and equal 30s for successful ISSU

    You probably need to dig a little deeper to get a definitive answer (sup1 or 2, type of cards, etc..) but here is a diagram in the release notes for 6.1 found here:
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/61_nx-os_release_note.html
    If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

  • Nexus 7010 - redistribute host routes in to OSPF

    In my Nexus 7010 infrastructure, I have a requirement to redistribute host routes in to OSPF so that the other connected sites receive the host routes through OSPF.
    These hosts are part of the connected network (192.168.100.0/24) on Nexus, I dont want this network to be advertised in to OSPF but I want the hosts inside this subnet (192.168.100.11 and 192.168.100.12) to be advertised.
    I tried to create a prefix list with these two hosts and added them to a route-map and then using the "redistribute direct" command called this route-map in to OSPF, but this is not working.
    However, if I add the entire subnet (the connected network) in to this route-map, it shows up in OSPF.
    Is there a way I could have only the hosts to be part of the OSPF database?

    Hello, There is no need for VDC or VRF I think. are we missing a trick here. I also just tested for my own sanity. (Or am I completely under-thinking this)
    N7K-1 has vlan 24 and the host route will be to 172.25.24.20
    N7K-1 Config:
    conf t
    ip route 172.25.24.20/32 Vlan24
    ip prefix-list TEST seq 5 permit 172.25.24.20/32
    route-map STATIC_TO_OSPF permit 10
      match ip address prefix-list TEST
    router ospf 1
      bfd
      router-id 192.168.101.1
      redistribute static route-map STATIC_TO_OSPF
    here is what I see on its neighbour N7K2:
    DC1-N7K2# show ip route 172.25.24.20
    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>
    172.25.24.20/32, ubest/mbest: 1/0
        *via 192.168.102.5, Eth8/1, [110/20], 00:00:07, ospf-1, type-2
    DC1-N7K2#
                    Type-5 AS External Link States
    Link ID         ADV Router      Age        Seq#       Checksum Tag
    172.25.24.20    192.168.101.1   479        0x80000002 0x0eed    0
    So in essence point the host routes statically to the directly connected interface.
    hth.
    Bilal

  • Cisco Nexus 7010 Port-Channel

    Hi all,
    Hi have install a cisco nexus 7010 with the following modules :
    Mod  Ports  Module-Type                         Model              Status
    1    48     1000 Mbps Optical Ethernet XL Modul N7K-M148GS-11L     ok
    2    48     10/100/1000 Mbps Ethernet XL Module N7K-M148GT-11L     ok
    5    0      Supervisor Module-2                 N7K-SUP2           active *
    6    0      Supervisor Module-2                 N7K-SUP2           ha-standby
    9    48     10/100/1000 Mbps Ethernet XL Module N7K-M148GT-11L     ok
    10   48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
    After trying to build a port-channel with a 1G port on slot 1 and a 1G port on slot 10 i get a messague with incompatible port.
    Can any one tell me if its supported a port-channel with ports on the following modules :
    N7K-M148GS-11L
    N7K-F248XP-25E
    Thanks
    Patrício

    Hi Particio,
    The port-channel/vPC features require that all uplinks are connected to the same type of
    module. You can refer to the following document.
    http://www.cisco.com/en/US/partner/docs/switches/datacenter/sw/6_x/nx-os/interfaces/configuration/guide/if_portchannel.html#wp1888267
    HTH
    Regards
    Inayath
    *Plz rate if this is helpfull and mark as Answerd if this answerd your query.

  • Nexus 7010 fabric extender timing out

    Hello -
    We have a Nexus 7010 and we are testing out using the fabric extenders for a need.  We have a demo 2224 unit and have it connected to our M132XP-12 10G blade in the 7K but the FEX won't come online.  I would have figured a possible software incompatability but looking at the supported list for that as well as hardware everything seems to be in order.  This is what the status shows after it spends about 15 mins in the image download state.
    FEX: 111 Description: FEX0111   state: Offline
      FEX version: 4.2(1)N2(1a) [Switch version: 5.1(2)]
      FEX Interim version: 4.2(1)N2(1a)
      Switch Interim version: 5.1(2)
      Module Sw Gen: 21  [Switch Sw Gen: 21]
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth2/20
      Fabric interface state:
        Po11 - Interface Up. State: Active
        Eth2/20 - Interface Up. State: Active
      Fex Port        State  Fabric Port  Primary Fabric
    This is looped in the log details until it times out:
    04/25/2011 15:31:41.986978: Module register received
    04/25/2011 15:31:41.987713: Registration response sent
    04/25/2011 15:31:41.987889: Requesting satellite to download image
    04/25/2011 15:32:00.105031: Module register received
    04/25/2011 15:32:00.105779: Registration response sent
    04/25/2011 15:32:00.105956: Requesting satellite to download image
    04/25/2011 15:32:20.191181: Module register received
    04/25/2011 15:32:20.191957: Registration response sent
    04/25/2011 15:32:20.192144: Requesting satellite to download image
    We ran a debug during this and these entries are displayed when looking for errors.
    2011 Apr 25 15:30:31.443745 fex: Reg resp: Failed to get card info for swcardid 132
    2011 Apr 25 15:30:35.472721 fex: Cardinfo: Unknown card id to get (132)
    2011 Apr 25 15:30:35.472753 fex: Reg resp: Failed to get card info for swcardid 132
    2011 Apr 25 15:30:41.495302 fex: Cardinfo: Unknown card id to get (132)
    I'm still doing some more searching which so far hasn't turned up much, wanted to see if anyone has some other insight??
    Thanks!

    Hi Jack -
    Thanks for the response.  Unfortunately, yes that is already complete.  I was hoping that would be an easy fix.  When we upgraded to 5.1(2) we did the 5.1 EPLD.  I ran the install all impact command noted below for the 5.1 EPLD just to make sure it didn't report anything else as needing upgrade.
    sho install all impact epld bootflash:n7000-s1-epld.5.1.1.img
    Compatibility check:
    Module  Type  Upgradable        Impact   Reason
         1    LC         Yes    disruptive   Module Upgradable
         2    LC         Yes    disruptive   Module Upgradable
         5   SUP         Yes    disruptive   Module Upgradable
         1  Xbar         Yes    disruptive   Module Upgradable
         2  Xbar         Yes    disruptive   Module Upgradable
         3  Xbar         Yes    disruptive   Module Upgradable
         1   FAN         Yes    disruptive   Module Upgradable
         2   FAN         Yes    disruptive   Module Upgradable
         3   FAN         Yes    disruptive   Module Upgradable
         4   FAN         Yes    disruptive   Module Upgradable
    Copy complete, now saving to disk (please wait)...
    Retrieving EPLD versions... Please wait.
    Images will be upgraded according to following table:
    Module  Type           EPLD      Running-Version   New-Version  Upg-Required
         1    LC  Power Manager              4.008       4.008           No
         1    LC  IO                         1.006       1.006           No
         1    LC  Forwarding Engine          1.006       1.006           No
         1    LC  SFP                        1.004       1.004           No
         2    LC  Power Manager              4.008       4.008           No
         2    LC  IO                         1.016       1.016           No
         2    LC  Forwarding Engine          1.006       1.006           No
         2    LC  FE Bridge(1)              186.006      186.006           No
         2    LC  FE Bridge(2)              186.006      186.006           No
         2    LC  Linksec Engine(1)          2.006       2.006           No
         2    LC  Linksec Engine(2)          2.006       2.006           No
         2    LC  Linksec Engine(3)          2.006       2.006           No
         2    LC  Linksec Engine(4)          2.006       2.006           No
         2    LC  Linksec Engine(5)          2.006       2.006           No
         2    LC  Linksec Engine(6)          2.006       2.006           No
         2    LC  Linksec Engine(7)          2.006       2.006           No
         2    LC  Linksec Engine(8)          2.006       2.006           No
         5   SUP  Power Manager              3.009       3.009           No
         5   SUP  IO                         3.028       3.028           No
         5   SUP  Inband                     1.008       1.008           No
         5   SUP  Local Bus CPLD             3.000       3.000           No
         5   SUP  CMP CPLD                   6.000       6.000           No
         1  Xbar  Power Manager              2.010       2.010           No
         2  Xbar  Power Manager              2.010       2.010           No
         3  Xbar  Power Manager              2.010       2.010           No
         1   FAN  Fan Controller (1)         0.007       0.007           No
         1   FAN  Fan Controller (2)         0.007       0.007           No
         2   FAN  Fan Controller (1)         0.007       0.007           No
         2   FAN  Fan Controller (2)         0.007       0.007           No
         3   FAN  Fan Controller (1)         0.007       0.007           No
         3   FAN  Fan Controller (2)        0.007       0.007           No
         4   FAN  Fan Controller (1)         0.007       0.007           No
         4   FAN  Fan Controller (2)         0.007       0.007           No

  • Question about Nexus 7010.

    Hello everybody,
    Just a quick question, how do you restore a running-config (or a Nexus .bin file) to a Nexus 7010. Is it thesame process as the IOS base scenario. Please explain and help. Thank you in advance.
    --chie                  

    Copy tftp: running-config should work. See below there are other options as well.
    NX7K02-agg# copy ?
      bootflash:      Select source filesystem
      core:           Select source filesystem
      debug:          Select source filesystem
      ftp:            Select source filesystem
      log:            Select source filesystem
      logflash:       Select source filesystem
      nvram:          Select source filesystem
      running-config  Copy running configuration to destination
      scp:            Select source filesystem
      sftp:           Select source filesystem
      slot0:          Select source filesystem
      startup-config  Copy startup configuration to destination
      system:         Select source filesystem
      tftp:           Select source filesystem
      usb1:           Select source filesystem
      usb2:           Select source filesystem
      volatile:       Select source filesystem
    NX7K02-agg# copy tftp: ?
      bootflash:      Select destination filesystem
      debug:          Select destination filesystem
      log:            Select destination filesystem
      logflash:       Select destination filesystem
      nvram:          Select destination filesystem
      running-config  Copy from source to running configuration
      slot0:          Select destination filesystem
      startup-config  Copy from source to startup configuration
      system:         Select destination filesystem
      usb1:           Select destination filesystem
      usb2:           Select destination filesystem
      volatile:       Select destination filesystem
    NX7K02-agg# copy tftp: running-config

  • Nexus 7010 mgmt0 useage opinion

    As a Senior Network Engineer I have entered into a bit of a debate with our Architect about the use of the mgmt0 interfaces on the nexus 7010 switch (dual-sups, M2 and F2 linecards).
    I would like to know opinion of the Cisco support network.
    I believe the mgmt0 interface should left alone for control plane traffic only and Out Of Band management access (ie ssh).  At the moment I have made a subnet for all VDCs with the mgmt0 (vrf management) sitting in a common subnet.  The physical mgmt0 interfaces from both SUPs are connected a management hand off switch.  The mgmt0s also serves as our control plane for VPCs. The VPC peer-link however is using main interfaces of the line-cards.
    The opinions;
    - The Architect thinks we should use all the mgmt0 interfaces for snmp, ntp, tacacs netflow-analysis and switch management.
    - However, I think I should use a traditional Loopback to perform these functions within the linecards.  The mgmt0 should only be used if traditional restricted switch access has failed.
    My Basis;
    the Loopback never goes down, uses multiple paths (the OOB hand off switch could fail closing switch management access completely).  The mgmt0 should be used as a last resort of management access to CMP.
    Thoughts please - Cheers

    I see your point about wanting to mitigate the impact of losing the OOB switch. I don't think the mgmt0 interface going down is considered the level of failure that will trigger a Supervisor switchover though. That's the way I read the Nexus 7000 HA whitepaper (and what I've seen based on some limited experience with taking apart a 7k pair).
    So, no the 7k can't send you an SNMP trap or syslog message if it's configured management path is offline. Mitigation of that could be via your NMS polling the devices's mgmt0 addresses. No response = trouble in paradise. Investigation step would be to log into the 7ks using the loopback IP and local authentication since your TACACS source-interface (mgmt0) is offline and going from there.
    The handful I've built (mostly 5k setups) I go for a Cat 3k switch with dual power supplies as the OOB switch. Once one of those is setup and seen not to be DOA, it's generally going to stay up until someone goes in and uplugs it or initiates a system reload.

  • Nexus 7010 No route to host

    Hi,
    I needed to add vlans on the bladecenter, So added to ports on the bladecenter and then to the main trunk port of BC as well as i created the vlan on BC.
    This BC connects to two main NEXUS 7010 core switch, I added to trunk port of these switches as well and vlan was already created in the nexus core switch.
    but i was unable to ping the subnet gateway from the nexus core switch and gets the error as "no route to host"
    Is this something there is no routing define for this subnet. As OSPF is running on the core switch.
    Thanks
    Sagar

    Thanks Alex
    VLAN was allowed on the trunk, everything related vlan is fine.
    but there was no static route defined on the switch as the routing for the subnet was done on the firewall
    so what i thought is to give a static route for network with next hop as firewall interface and guess what it started to work
    Thanks
    Sagar

  • Nexus 7010 with F3 line modules. The modules are not "powering on" ?

    Hi,
    Just tried installing a new Nexus 7010, With a couple of F3 line modules.
    I cant seem to figure out how to get them to come online.
    They flash with red LED and from a "show module" they show as powered down.
    Its a fresh nexus install, What could I be missing here? Do I need to "provision them somehow?
    Thanks
    L

    Hi,
    Its 6. something  ( Im not in front of it right now )
    And im certain its these ones.
    http://www.cisco.com/c/en/us/products/collateral/switches/nexus-7000-series-switches/datasheet-c78-730273.html
    They are 48 port , 1/10G fiber. with "8 port groups.."
    No idea if this helps at all.
    Its a new install,
    It contains the default VDC and an admin user. No other config has been done.

Maybe you are looking for