Nexus 7010 10G Ports

As many 10G ports may have a nexus 7010? I read documentation who speaks in some 256 ports, but each module has a throughput of only 80G. This means that I can really only have 64 10G ports because 10G are shared by groups of 4?
Thanks

5596's L3 throughput is limited to 160G one way per chassis. However the N7K depends on the type of line card, number of fabric and the fabric speed, which you can said it will increase when Cisco release a newer fabric and line card. With the current M1 line card, the N7K can perfrom 80G one way per line card for L3.
The F132 line card doesn't support L3, but it supports fabric path. The F1 will rely on the M1 to forward L3 traffic.
HTH,
jerry

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

  • 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

  • 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.

  • Nexus 7010 and ESX Host

    Hi,
    We are currently seeing issues on a ESX Host using 10G Fibre dual connectivity to a pair of Nexus 7010's using vPC for the port channel to this ESX host which was working fine , up to this weekend. No changes had been made on the Nexus or ESX host.
    We have changed the hardware path for the believed fault on a vmnic which when part of the virtual switch cause VM's on the Host to stop pinging, although we still see a CDP neighborship with the ESX from the Nexus, but changing fibre and Nexus ports has not worked.
    As part of the testing , the vmware guy was removing this 'faulty' vmnic from the Virtual switch , which is part of an ether channel bundle his end. My first question is, how does the Nexus detect a link leaving the bundle for the ESX host , when the actual physical link is still up , and all they have done is software removed it from on the ESX, as the Nexus will still attempt to push traffic across both bundled links. I know there is the Cisco 1000V software , which can be used at an extra price, but is this the only option.
    Any help will be gladly welcome.

    Hi
    How the switch detects a link 'moving out' of the Etherchannel would depend on how you have configured it...
    If you have used 'channel-group x mode on' under the physical ports in the channel, then it will not detect the change, and you will get problems. The solution is to ensure the config of the channel on both ends (server/switch) is consistent in this case. An inconsistent config will cause you connectivity issues.
    If the switch automatically negotiates the Etherchannel (i.e. you are using LACP, and the server supports LACP) then it should detect the change.
    Regards
    Aaron
    Please rate helpful posts...

  • How to download MIB for NXOS or platform Nexus 7010 and Nexus 7004

    Hello,
    I need to monitor my Nexus 7004 and 7010 by my SNMP Agent, but I can't find the way to donload the required MIBs.
    For information I'm running the folling images:
    bootflash:///n7000-s2-dk9.6.2.6b.bin
    bootflash:///n7000-s1-dk9.6.1.5.bin
    By advance thanks for the support
    Gildas

    The module you are running requires a minimum software version of 5.1.
    You are currently running 5.0.3 which is why the module is not
    recognized.
    Below is a link that explains this:
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/data_s
    heet_c78-605482.html
    Product Specification
    Table 3 lists the specifications for the Cisco Nexus 7000 32-Port 10 Gigabit Ethernet
    Module with XL Option.
    Table 3. Product Specifications
    Item
    Specifications
    System
    Product compatibility
    Supported in all Cisco Nexus 7000 Series chassis
    Software compatibility
    Cisco NX-OS Software Release 5.1 or later (minimum requirement)
    You would need to upgrade you software.
    Hope this helps.
    Regards
    Muhammed M

  • 10g ports with redundancy

    Hi all. I hope this is the right section to post this kind of question.
    Basically I need to know which switch should I buy to achieve the customer's needs.
    Each floor will have 1 x 2960 with 2 10GB uplink to the core switch. The problem is I don't know which switch should I buy acting as a CORE. The customer needs at least 16 x 10G ports for each switch and the core must be redundant in some way. So the 3750 is not an option and I thought about the 4500-x with VSS but actually I'm not sure this is the best idea. Servers will be attached directly to the core switch (I know, this is not the best idea but this is what the customer want to do).
    Thanks for you replies / help
    Regards

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    Yes, VSS with the 4500-X is one possibility, as would be the new 6880.
    Or, instead of VSS, you could use a 4500, 6500 or 6807 with dual sups and dual line cards.
    With VSS, your single point of failure is the IOS.  With the (redundant card) chassis, your single point of failure is the chassis, itself.  There's not much of a difference in MTBF.
    Any of the above (or Nexus) would likely work well for you.  Selection depends on your budget and feature requirements.

  • 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.

  • How to do routing on N7K-F248XP-25E (Nexus 7010) ?

                       Hi all,
         Please educate me the following scenario : I have Nexus 7010 with 2 L3 modules, N7K-M132XP-12L and N7K-M148GT-11L. Now to increase more ports for end devices, I add in the module N7K-F248XP-25E and believe it's for Layer 2 switching only. Is there a way to do routing on these L2 modules without having to go to the L3 modules ? Thanks for all help.

    Is there a way to do routing on these L2 modules without having to go to the L3 modules ?
    No.  If you have an M1/M2 card and routing is enabled, the F2E card will "step down" and do Layer 2 work.  All Layer 3 work will be done by the M1/M2 card.

  • 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

  • Private-VLAN using Nexus 7010 and 2248TP FEX

    I have a Nexus 7010 with several 2248TP FEX modules.
    I am trying to configure a Private VLAN on one of the FEX host ports.
    I see in the documentation you can't do promiscous but I can't even get the host only configuration to take.
    Software
      BIOS:      version 3.22.0
      kickstart: version 6.0(2)
      system:    version 6.0(2)
    sho run | inc private
    feature private-vlan
    vlan 11
      name PVLAN_Primary
      private-vlan primary
      private-vlan association 12
    vlan 12
      name PVLAN_Secondary
      private-vlan isolated
    7010(config)# int e101/1/48
    7010(config-if)#
    7010(config-if)# switchport mode ?
      access        Port mode access
      dot1q-tunnel  Port mode dot1q tunnel
      fex-fabric    Port mode FEX fabric
      trunk         Port mode trunk
    Switchport mode private-vlan doesn't even show up!!!!!!
    If I try this command it says its not allowed on the FEX port.
    7010(config-if)# switchport private-vlan host-association 11 12
    ERROR: Requested config not allowed on fex port
    What am I doing wrong?????
    Todd

    Have you found a solution to this?
    -Jeremy

  • Nexus 7010 Slot 3 problem

    Hello everyone,
     Here is my issue. We have a Nexus 7010 and for the third time now slot 3 will not allow a module to run in it. This is what we have done so far. RMA'd the module and the chassis. When the module is put into another slot it comes up without any issue. The only difference between this chassis and the other one we have is that we only have 2 of the 3 power supplies in it. The chassis itself has 2 sup mods and 3 48 port 10 gig mods. On a side note after we RMA'd the chassis slot 3 worked fine until we configured the new VDC and allocated the card to it. Any help will be appreciated.

    Yes I am still have this issue. Here is the output you asked for.
    show diagnostic result module all
    Current bootup diagnostic level: complete
    Module 1: 1/10 Gbps Ethernet Module  
            Test results: (. = Pass, F = Fail, I = Incomplete,
            U = Untested, A = Abort, E = Error disabled)
             1) ASICRegisterCheck-------------> .
             2) PrimaryBootROM----------------> .
             3) SecondaryBootROM--------------> .
             4) EOBCPortLoopback--------------> .
             5) OBFL--------------------------> .
             6) PortLoopback:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  .  .  
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                     .  .  .  .  .  .  .  .  .  .  .  U  U  U  .  U  
             7) RewriteEngineLoopback:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
                     .  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
             8) SnakeLoopback:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
             9) FIPS:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
            10) BootupPortLoopback:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
    Current bootup diagnostic level: complete
    Module 5: Supervisor Module-2  (Active)
            Test results: (. = Pass, F = Fail, I = Incomplete,
            U = Untested, A = Abort, E = Error disabled)
             1) ASICRegisterCheck-------------> U
             2) USB---------------------------> .
             3) NVRAM-------------------------> .
             4) RealTimeClock-----------------> .
             5) PrimaryBootROM----------------> .
             6) SecondaryBootROM--------------> .
             7) CompactFlash------------------> .
             8) ExternalCompactFlash----------> U
             9) PwrMgmtBus--------------------> .
            10) SpineControlBus---------------> .
            11) SystemMgmtBus-----------------> .
            12) StatusBus---------------------> .
            13) StandbyFabricLoopback---------> U
            14) ManagementPortLoopback--------> .
            15) EOBCPortLoopback--------------> .
            16) OBFL--------------------------> .
    Current bootup diagnostic level: complete
    Module 6: Supervisor Module-2  (Standby)
            Test results: (. = Pass, F = Fail, I = Incomplete,
            U = Untested, A = Abort, E = Error disabled)
             1) ASICRegisterCheck-------------> .
             2) USB---------------------------> .
             3) NVRAM-------------------------> .
             4) RealTimeClock-----------------> .
             5) PrimaryBootROM----------------> .
             6) SecondaryBootROM--------------> .
             7) CompactFlash------------------> .
             8) ExternalCompactFlash----------> U
             9) PwrMgmtBus--------------------> U
            10) SpineControlBus---------------> .
            11) SystemMgmtBus-----------------> U
            12) StatusBus---------------------> U
            13) StandbyFabricLoopback---------> .
            14) ManagementPortLoopback--------> .
            15) EOBCPortLoopback--------------> .
            16) OBFL--------------------------> .
    Current bootup diagnostic level: complete
    Module 8: 1/10 Gbps Ethernet Module  
            Test results: (. = Pass, F = Fail, I = Incomplete,
            U = Untested, A = Abort, E = Error disabled)
             1) ASICRegisterCheck-------------> U
             2) PrimaryBootROM----------------> .
             3) SecondaryBootROM--------------> .
             4) EOBCPortLoopback--------------> .
             5) OBFL--------------------------> .
             6) PortLoopback:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
                     U  U  U  U  .  .  U  U  U  U  U  U  .  .  U  .  
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                     U  U  .  .  .  .  .  .  .  .  .  .  .  .  .  .  
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                     .  .  .  .  .  .  .  .  U  U  U  U  U  U  U  U  
             7) RewriteEngineLoopback:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
                     .  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
             8) SnakeLoopback:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                     .  .  .  .  .  .  .  .  U  U  U  U  U  U  U  U  
             9) FIPS:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                     U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  U  
            10) BootupPortLoopback:
              Port   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16
              Port  17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
              Port  33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                     .  .  .  .  .  .  .  .  U  U  U  U  U  U  U  U 
    show module
    Mod  Ports  Module-Type                         Model              Status
    1    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
    3    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     testing
    5    0      Supervisor Module-2                 N7K-SUP2           active *
    6    0      Supervisor Module-2                 N7K-SUP2           ha-standby
    8    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
    Mod  Sw              Hw
    1    6.2(2a)         1.0     
    3    6.2(2a)         1.0     
    5    6.2(2a)         1.1     
    6    6.2(2a)         1.0     
    8    6.2(2a)         1.0     
    ISSCSW7010RE-4# show module
    Mod  Ports  Module-Type                         Model              Status
    1    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
    3    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     testing
    5    0      Supervisor Module-2                 N7K-SUP2           active *
    6    0      Supervisor Module-2                 N7K-SUP2           ha-standby
    8    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
    Mod  Sw              Hw
    1    6.2(2a)         1.0     
    3    6.2(2a)         1.0     
    5    6.2(2a)         1.1     
    6    6.2(2a)         1.0     
    8    6.2(2a)         1.0     
    Mod  Online Diag Status
    1    Pass
    3    Untested
    5    Pass
    6    Pass
    8    Pass
    Xbar Ports  Module-Type                         Model              Status
    1    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    2    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    3    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    4    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    5    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    Xbar Sw              Hw
    1    NA              1.5     
    2    NA              1.5     
    3    NA              1.5     
    4    NA              1.5     
    5    NA              1.5     
    3    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     testing
    3    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     initializing
    Mod  Ports  Module-Type                         Model                                Status
    1    48     1/10 Gbps Ethernet Module    N7K-F248XP-25E          ok
    3    48     1/10 Gbps Ethernet Module                                              pwr-cycld
    5    0      Supervisor Module-2                 N7K-SUP2                      active *
    6    0      Supervisor Module-2                 N7K-SUP2                      ha-standby
    8    48     1/10 Gbps Ethernet Module    N7K-F248XP-25E         ok
    Mod  Power-Status  Reason
    3    pwr-cycld      Unknown. Issue show system reset mod ...
    Mod  Sw              Hw
    1    6.2(2a)         1.0     
    5    6.2(2a)         1.1     
    6    6.2(2a)         1.0     
    8    6.2(2a)         1.0     
    Mod  MAC-Address(es)                         Serial-Num
    1    e4-c7-22-17-c0-8c to e4-c7-22-17-c0-bf  JAF1802ANEA
    5    84-78-ac-1c-fa-0f to 84-78-ac-1c-fa-21  JAF1721AQPC
    6    84-78-ac-14-cb-16 to 84-78-ac-14-cb-28  JAF1713BAKS
    8    e8-ed-f3-38-7b-08 to e8-ed-f3-38-7b-3b  JAF1733ARPG
    Mod  Online Diag Status
    1    Pass
    5    Pass
    6    Pass
    8    Pass
    Xbar Ports  Module-Type                         Model              Status
    1    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    2    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    3    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    4    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    5    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
    Xbar Sw              Hw
    1    NA              1.5     
    2    NA              1.5     
    3    NA              1.5     
    4    NA              1.5     
    5    NA              1.5     
    2014 Aug  5 11:49:19 -MAF %$ VDC-2 %$ %PLATFORM-2-MOD_DETECT: Module 3 detected () Module-Type 1/10 Gbps Ethernet Module Model N7K-F248XP-25E
    2014 Aug  5 11:49:19 MAF %$ VDC-2 %$ %PLATFORM-2-MOD_PWRUP: Module 3 powered up (
    2014 Aug  5 11:49:19 %$ VDC-1 %$ %PLATFORM-2-MOD_DETECT: Module 3 detected ) Module-Type 1/10 Gbps Ethernet Module Model N7K-F248XP-25E
    2014 Aug  5 11:49:19 %$ VDC-1 %$ %PLATFORM-2-MOD_PWRUP: Module 3 powered up ()

  • Nexus 7010 problem

    Nexus 7010 got hanged after entering command
    spanning-tree portfast trunk
    Please suggest why it got hanged?

    I don't think that is a legal NX-OS command, but ti shouldn't hang the entire switch, or hang anything at all.
    To put a port in port fast mode you have to device the port type in NX-OS. The equivlent command in NX-OS that you are trying to enter would be:
    spanning-tree port type edge trunk

  • Critical Alarm for Nexus 7010 device

    Hi Team,
    We are getting Critical Alarm for the Data center device Nexus 7010 continuously from 28-Oct.
    error (device hde1) in start_transaction: Journal has aborted - kernel
    2012 Oct 29 10:00:18.227 DC-Core-Switch2 29 10:00:18 %KERN-2-SYSTEM_MSG: EXT3-fs
    error (device hde1) in start_transaction: Journal has aborted - kernel
    2012 Oct 29 10:28:37.497 DC-Core-Switch2 29 10:28:37 %KERN-2-SYSTEM_MSG: EXT3-fs
    error (device hde1) in start_transaction: Journal has aborted - kernel
    2012 Oct 29 10:28:42.398 DC-Core-Switch2 29 10:28:42 %KERN-2-SYSTEM_MSG: EXT3-fs
    Also attaching the complete logs collected for this device and suggest if there is any Hardware related issue or some Software related issue.
    Regards,
    Ashutosh

    Hello
    hde1 is the logflash device. Looks like there were IO errors and the kernel mounted the fs read-only. You can try to reload the device and if logflash will come back up fine after the reload, its a transient issue; if the issue comes back, the logflash device most likely is damaged bad and needs to be replaced. You will need to open a service request with TAC to get it replaced.
    HTH,
    Alex

Maybe you are looking for

  • Problem in class moving to next method

    thank you to all those who helped me with dealing with time in my Movie class. My other problem is I can't return the charges (val) once a movie is hired. I need my Movie class to output the following when applied to the TestMovie class. Movie MOV456

  • How do I get the split screen effect?

    How do I get the split screen effect?

  • Can't advance photos in slideshow

    I have a slideshow of 325 photos to illustrate a lecture; some are timed series and others manually advanced. In several slideshows I have experienced the problem of being unable to advance the slides manually after about two-thirds of the show. When

  • Is Stationery Leopard-only?

    Are the stationery templates Leopard-specific, or will other users (those using PCs or previous Mac OS) be able to view letters I have formatted with Stationery?

  • Language codes for 'english' and 'english-2' must differ?

    I am trying to build my project but as I do I get the following pop up: Compiler: Language codes for 'english' and 'english-2' must differ. What do I need to change?