There are times the Nexus CPU goes high around 70% but its not a constant occurance. Is there something to worry. Quite hard to find out which process caused it as it happens very brief. [code]
View 3 RepliesHigh Utilization event generated for Nexus 7010 shows in LMS 4.0.1. share your input why its generated. We have checked up Nexus, it showed not utilization.
View 2 Replies View RelatedTrying to implement PBR in N7K? I found that there is not track mechanism can use in "set next-hop ip", so if the next-hop is unreachable that the route might be died.
View 0 Replies View Relatedi have a couple of nexus 7010 (5(2)3a) connected to a checkpoint in HA(active/active)I have now to configure multicast mac..i found this commmand: [code]
View 1 Replies View RelatedThis is regarding Nexus core switch 7010. We are already running two nexus 7K with ten Nexus 5k. Currently we are going to add two new Nexus 5k in our DC. In the 7K we already running two VDC's.
View 8 Replies View RelatedI cannot receive any OSPF route from Nexus to ASR1002 even they are both OSPF neighbour. I have attached the config for both, Both Nexus and ASR part of Area0.
Config
ASR1002#sh ip ospf neighbor
Neighbor ID Pri State Dead Time Address Interface10.165.117.12 1 FULL/BDR 00:00:35 10.231.175.226 GigabitEthernet0/0/0
[Code].....
I saw a push bottom below the fan module of the nexus 7010. What that is for?
View 3 Replies View RelatedIn our LAN network design, we have two Nexus 7010 switches on the core connected via vPC. Then LAN access switches are directly connected to the Core Nexus switches via regular port channels on the 3750's and vPC on Nexus. The core Nexus switches will be linked to an existing LAN network and the applications will be progressively migrated from the old to the new network.In this scenario, three VDCs are planned to be configured on the Nexus - One for the Interconnect (and WAN at a later stage), one for the LAN/local services and one for the building facilities/local services.
View 5 Replies View RelatedI'm about to perform an upgrade on two Nexus 7010 switches per above. Can I directly upgrade or, do I need to go from version 4 to 5.x and then to 6??
SA7001# dir bootflash:
518 Jan 10 00:37:51 2008 TBM14107479_136878179.lic
15830 Jun 06 11:50:11 2013 dcnm-10.25.32.10-ckpnt.cfg
16384 Jan 09 23:25:25 2008 lost+found(code)
We recently replaced our core switch from a non-cisco vendor with a Nexus 7010. With our old core switch, I had the ability to log changes to the ARP table. So if there was a dhcp conflict or a vMotion event, it would show up in the "show log" output. I've not found a way to do that with the Nexus switch - or at least no way to view the log. I have the command: logging level arp 6
View 8 Replies View RelatedI have to upgrade a Nexus 7010 with dual Sup engines from 4.2(4) to 5.2 and am hoping it could be an ISSU. We are fine with an outage window.To upgrade from 4.2(4) to 5.2(5) I'll have to do a multi hop upgrade from 4.2(4) - 4.2(6) - 5.2(5) and each hop would take 40-60 minutes.do I spend 40-60 minutes for each hop, or just do a disruptive upgrade straight from 4.2(4) to 5.2(5)? Like I said, we are fine with an outage window.
View 2 Replies View RelatedDoes Cisco Nexus 7010 supports NAT64; the image that I am using is :-
Software
BIOS: version 3.22.0
kickstart: version 5.2(4)
system: version 5.2(4)
BIOS compile time: 02/20/10
kickstart image file is: bootflash:///n7000-s1-kickstart.5.2.4.bin
kickstart compile time: 12/25/2020 12:00:00 [03/08/2012 03:58:13]
system image file is: bootflash:///n7000-s1-dk9.5.2.4.bin
I'm currently getting a Nexus hardware failure at present.
switch %MODULE-2-MOD_DIAG_FAIL: Module 8 reported failure due to DEVICE POST/DIAG FAILURE in device 48
I have two Nexus 7010 in the data center. I'm unable to poll SNMP data from one of the NEXUS 7010s. The other Nexus 7010 is working fine. I have compared the SNMP configurations, and they are identical. When I do "show snmp" on the non-working switch, I have SNMP packets in "Unknown Context name", not sure why. I have done show vdc and it matches the working switch output. Here is output of show snmp from the non-working switch: 133 SNMP packets input 0 Bad SNMP versions 0 Unknown community name 0 Illegal operation for community name supplied 0 Encoding errors 0 Number of requested variables 0 Number of altered variables 0 Get-request PDUs 0 Get-next PDUs 0 Set-request PDUs 0 No such name PDU 0 Bad value PDU 0 Read Only PDU 0 General errors 0 Get Responses 133 Unknown Context name0 SNMP packets output 0 Trap PDU 0 Too big errors 0 No such name errors 0 Bad values errors 0 General errors 0 Get Requests 0 Get Next Requests 0 Set Requests 0 Get Responses 0 Silent drops.
View 4 Replies View RelatedI want to know how to retrieve the complete configuration for a Nexus via the snmpwalk or snmpget commands...
View 6 Replies View RelatedWe have a Nexus 7010 running version 6.1(2).
I'd like to use IP SLAs and object tracking to define static routes for specific source/destination traffic across some WAN links we have. I've done this in IOS and it's worked fantastically, but I've not found where/how to do this on the Nexus 7010 platform (or any Nexus platform) as of yet. I could have sworn that this was going to be introduced in the 6.x code? Below is an example of how we do this in the IOS world:
track 11 ip sla 1 reachability
delay down 15 up 15
ip sla 1
[Code]....
Esentially this gives us the option of using a "failover" default route. I've attached a basic diagram to explain what we are trying to do with IP SLAs and object checking. The tracking should be configured against an SLA that uses icmp and the static routes should be configured against the tracking.
I just deployed a nexus 7010 switch at a server farm. after deployment, it was notices that there are surges in latency across the network. The default gateway was then moved to the nexus, with this pinging from an host on the same subnet there is intermitent burst is latency
NEXUS>>>>>Server
Ping of about 80ms and sometimes even times out.
To me, this is strange.
NX-OS Version is 5-02a
I'm looking to see if it is possible to run a vPC between to vDC's on a single 7010? We have a Production setup that runs dual 7010's with vPC's between the chassis but in our lab we only have a single 7010 with a 32 port 10gig module. I was thinking that maybe we could create 4 vDC's on the 7010 and run a vPC between the vDC's.
View 2 Replies View RelatedHow to get a summary of netflow statistics on NX-OS? On IOS you could do sh ip cache flow which would show what I need? Can't find a similar command on the Nexus Platform.
View 4 Replies View RelatedWe will install a new Supervisor Engine in our Nexus 7010.One Supervisor Engine is already installed an 1Year old.So the Problem is that both Supervisor Engines may have different NX-OS version.Could this lead to a problem?Does the installed Supervisor Engine "udate" the newer Supervisor engine?
View 3 Replies View Relatedi have a big problem because i configure a vlans with vrf and HSRP but, when i do "show hsrp brief", dont show this interfaces and, i can ping virtual IP. it seems hsrp dont work.
SWSERVSCAMILO_N7010_A#
interface Vlan405
description smsc-fwatlas1
no shutdown
[Code] ....
We have a couple of Nexus 7010's split into Core and Distribution VDCs. MGMT0 interfaces on each of the Nexus VDC's (including the Admin VDC) are configured with different IP address, but on the same subnet i.e 10.10.10.1/24 for admin, 10.10.10.2/24 for Core and 10.10.10.3/24 for Distribution. The MGMT 0 physical port on each Nexus is connected to a physical gig port on a 3750 X switch, and the 3750X has uplinks back to the Nexus configured for vPC.
When i ssh to the VDC MGMT0 IPs from the 3750X, i can access each of these VDCs without any problems. But if i enable routing on each of these links(OSPF) and advertise it to the WAN, i cannot see these routes advertised and also cannot see any of these routes in the local routing table.Just wondering if i have to enable these links on a VLAN and then advertise it to the WAN..But if this the case, VLANs cannot be created on the Admin(default VDC).
We have, for nearly 4 years, used EIGRP on our 6513 to make use of two unequal links to our branch offices. This worked because we could use the variance command and cause EIGRP to insert two routes into the table, one from each carrier. Thus it was we could balance the load to each one with a ratio similar to the ratio of the bandwidth of Link A to Link B.
We just purchased 2 Nexus 7010's to replace our single 6513 core.After much consternation we have found from our Ciscio SE that the Nexus 6.0.2 software rendition of EIGRP does not support variance.
Why would Cisco take their own propriatary protocol and then gut it by removing features? I'm quite ready to send these Nexus boxes back in favor of a newer 6500 series. MEC doesn't work like it is supposed to and the show-tech runs for over 24 hours without ever finishing (and this we can repeat on both boxes, multiple times).
We've opened a tac case but I just wondered for any work around for the 'variance' command?
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.
I am facing issue with nexus 7010 login authentication by radius server. I have two nexus 7010, one of them is working perfectly. Other taking long time to authenticate. If i use local database to login it works perfectly. It works fine also if i login from console using radius for authentication.
View 1 Replies View RelatedI use Nexus 7010 as our layer 3 router.I have ssh feature turned on so I can manage it from the management interface. I just found out that users can use putty to ssh to the local SVI interface of the NEXUS. Although they still need username and password to login but we dont want them even able to bring up the welcome screen.Example, user's IP is : 172.16.25.100 , they can ssh to 172.16.25.1 which is the NX SVI interface.
View 1 Replies View RelatedI believe i've enable jumbo frames on our Nexus 7010, one in each data-centre.
system jumbomtu 9216. Also on the interfaces mtu 9216. And can see MTU 9216 bytes, BW 20000000 Kbit, DLY 10 usec on the port-channel between them. Though when i ping between vlans at each site with large packets i get 30% drops and if i set the DF bit in IP header to yes - 100% loss.
8798 bytes from 10.200.12.2: icmp_seq=19 ttl=254 time=8.024 ms --- 10.200.12.2 ping statistics ---20 packets transmitted, 14 packets received, 30.00% packet loss
I have a senario where i'm going to have 2 Nexus 7010 connected as a core, and i'm going to have 4 5510's connected in a star formation. Each nexus 5510 will connect to the nexus core Via two 10Gb links. Each nexus 5510 will have 2 links attached to The core switches in vPc's.
Nexus 7010-1 = Core 1
Nexus 7010-2 = Core 2
Nexus 5510-1 = vPC = 100 2 Ports in vPc 100 -- > 7010-1, 7010-2
Nexus 5510-2 = vPC = 200 2 Ports in vPC 200 -- > 7010-1, 7010-2
Nexus 5510-3 = vPC = 100 2 Ports in vPc 300 -- > 7010-1, 7010-2
Nexus 5510-4 = vPC = 200 2 Ports in vPC 400 -- > 7010-1, 7010-2
The way I intend to configure the vPC's is this the best way. If i get a vPC dual active scenario what would happen. All ports will be forwarding all VLAN traffic this is how I intend to have it work.
I've got a pair of Nexus 7010's running vPC. I am having a Multicast issue with a cluster of Linux servers that need to talk Multicast for cluster/high-availability operation. All the servers need to talk to a single multicast address and I am having trouble getting them to communicate. I believe I need to enable IP IGMP Snooping Querier on the N7K's and it needs to be enabled on the VLAN where the servers reside. How to enable IP IGMP Snooping Querier on a VLAN ?
View 5 Replies View RelatedYesterday I configured the 7010 Nexus switch. I created a VDC and allocated few ports and configured VLAN for testing. After enabling feature interface-vlan i was allowed to configured L3 interface for the vlan. I assigned ip address and connected few server to check the reachability but it says Destination Host Unreachable.
NX OS Ver : n7000-s1-dk9.5.2.4.bin
Configuration of the VDC below.
feature telnet
feature udld
feature interface-vlan
feature lacp
[Code]....
Make a netflow template to get information about http code errors in a nexus 7010?
View 3 Replies View RelatedI've got two Nexus 7010's running HSRP north bound to a pair of ASA's, and BGP south bound to four 6509's. Is it possible to advertise default route to BGP neighbor (or prefer it via MED), only if the node is HSRP-active?
Essentially the goal is to create symmetry for inbound/outbound traffic. Only way I can think of so far is via an EEM script, so that when it sees HSRP go active via syslog, it would kick off an action to remove ASN prepend, or reduce MED, and the opposite if HSRP goes standby.
I am working on Nexus 7010 with NX-OS 5.1.5. I have to delete the static route 10.10.0.0/16 via 10.16.0.21. [code] I try to remove the route with the command "no ip route 10.10.0.0/16 10.16.0.21" and I have the message below % Route not deleted, it does not exist..I don't understand why I have this message because the static route exist.
View 9 Replies View Related