Configuring NTP on the nexus 7010
Hi All,
I'm a little confused about how to configure NTP on the nexus 7010. I have an admin VDC and four working VDCs. I read that you can only configure NTP on the admin VDC but the commands are also available on the other VDCs. As the admin VDC is setup as an admin VDC it doesn't allow any commands other than those used to configure the other VDCs. If I configure 'clock protocol ntp vdc X' from the admin vdc conf t cli it doesn't appear to apply that command to the individual VDCs. If I try that command on each of the VDCs I get an error message. If I do a 'show ntp peer-status' I get a message stating 'the clock is not controlled by ntp' with an explanation teling me to use the 'clock protocol ntp vdc X' command however as already explained that doesn't appear to work. I'm running nxos 6.2
Any help, documentation etc would be greatly appreciated.
An update.
I have now configured NTP. The 'clock protocol ntp vdc X' command is accessed from the conf t Cli within the admin VDC. From my reading of the NXOS documentation from 6.2 you should be able to run NTP in multiple VDCs however this does not appear to be the case. I've configured the admin VDC as the NTP master.
Similar Messages
-
In reviewing the Cisco Licensing Guide, there is a license part number for MPLS on the Nexus 7010. Part Number is N7K-MPLS1K9. Is there a corresponding part number for the Nexus 7710?
For the benefit of others, here is what we found. The N7K was hitting the bug CSCtg95381.
Symptom
Nexus 7000 may punt traffic to CPU; so that the traffic may experience random delay or drop.
Further looking, ARP is learned and FIB adjacency is in FIB adjacency table.
Conditions
The problem is caused by race condition. Some hosts have not responded to the ARP refresh sent by
N7k which in turn trigger to delete ARP entry due to expiry. As a result the route delete notification is
sent to URIB from the process. However there is still traffic coming to given IP address as a result the next packet that hit glean resulting in triggering ARP and hope ARP is learnt from the host this time.
Workaround
(s):
Clear ip route < host>.
Not totally explains why it was working for certain client-server combination but yet the workaround is holding well for end-points when implemented.
There would be no host route for the destination server in the adjacency manager on N7K-01. The only thing thats there is the subnet route pointing towards the vlan gateway address. Implementing the work-around, a new /32 route can now be seen in the adjacency manager for the server.
The bug is fixed in releases starting 5.1(5). Planning to upgrade to 5.2(3a).
Regards, Rashid. -
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 - CheersI 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. -
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,
MayankHi, 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. -
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
LHi,
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. -
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.
--chieCopy 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 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 -
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?????
ToddHave you found a solution to this?
-Jeremy -
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 () -
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ícioHi 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. -
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 HHi 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 -
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... -
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,
AshutoshHello
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 -
Nexus 7010 bgp state change alert not triggered to NNM
Hi ,
BGP state change alert not triggered to NNM on Nexus -7010 for Monitoring.
Details of the Device:
Nexus 7010 :
Software
BIOS: version 3.22.0
kickstart: version 5.1(3)
system: version 5.1(3)
BGP neighbor status :
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
172.16.1.2 4 65505 5089234 5194515 51359 0 0 6w2d 391
172.16.1.3 4 65505 5044293 5146859 51359 0 0 30w4d 378
172.31.11.3 4 15404 120744 114811 51359 0 0 1w6d 1
172.31.42.3 4 65501 5261796 5264413 51359 0 0 2d06h 0
Snmp trap enabled:
snmp-server user admin network-admin auth md5 0x690c4ede8a88ba7f2de791dbe7a77f0a
priv 0x690c4ede8a88ba7f2de791dbe7a77f0a localizedkey
snmp-server host 172.30.0.55 traps version 2c xxxx
snmp-server enable traps bgp
Downloaded cisco-bgp4-mib version, bgp4-mib tried and performed snmpwalk as given below
nnmsnmpwalk.ovpl -c xxx 172.31.15.130 .1.3.6.1.4.1.9.9.187.0.6
Error : No MIB objects contained under subtree
nnmsnmpwalk.ovpl -v 2 -c xxx 172.31.15.130 .1.3.6.1.2.1.15.3.
No MIB objects contained under subtree
Kindly advise to resolve the issue
Regards
HariYou can set an alert for Warning State. This is feasible.
Juke Chou
TechNet Community Support -
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
Maybe you are looking for
-
Sims 2 not working with QT 7.6. Will there be a fix?
The Sims 2 is not working with QT 7.6. The Sims 2 (Aspyr) web site acknowledges this problem and state they are working with Apple to fix this. This game is not cheap so rather disappointed at the moment. Anybody know if this fix will really happen?
-
Users created in CUA does not distribute to child systems
Hi I searched this forum and after pulling my hair for 2 days I am asking this question. I created a user in CUA and gave him child system access with the necessary roles. I was under the impression that the user will get replicated / distributed aut
-
Once again hlp Plez... How do I modify this code so that
the photo wilL be displayed only when the Photo button is clicked? The code as it is right now .... works just fine. It displays the photo at first however.... NOT WHAT I WANT!! * @version * @author import java.awt.*; import java.awt.event.*; import
-
Find the page name with page sid?
Because my top_page is dislpaying the page id instead of the name of the page and the output of the id is something like this page_id = 2,11,6_23 Had any idea on where to find the page name? Thank you very much for the help
-
Photoshop keeps crashing only seconds after starting, any ideas why?
Every time I open photoshop it works for a few seconds, maybe just long enough to open something, then it comes up saying something is wrong and it needs to close... I have no idea why!! Any ideas would be much appreciated!