Cisco Nexus 7010

Hi,
Can any one please let me know how to enable http/https access on cisco nexus 7010
Regards
Asif Naveed

Following objects from conventional CISCO-PROCESS-MIB provides you details on CPU on devices:
cpmCPUTotal5secRev     1.3.6.1.4.1.9.9.109.1.1.1.1.6
cpmCPUTotal1minRev     1.3.6.1.4.1.9.9.109.1.1.1.1.7
cpmCPUTotal5minRev      1.3.6.1.4.1.9.9.109.1.1.1.1.8
Following document will be helpful as well:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a94.shtml
As many MIBs are not completely implemented on NX-OS so there is one more MIB which can help, i.e CISCO-SYSTEM-EXT-MIB :
cseSysCPUUtilization(1.3.6.1.4.1.9.9.305.1.1.1)
Unlike the averaged values from CISCO-PROCESS-MIB, cseSysCPUUtilization returns an un-smoothed value and typically shows more erratic results. It only shares the the average utilization of CPU on the active supervisor. So usually it is recommended to use the CISCO-PROCESS-MIB, ie. cpmCPUTotal5secRev instead.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Similar Messages

Logging of commands on syslog server (Cisco Nexus 7010)

Please help.
How to set up logging of commands on syslog server ? (cisco nexus 7010)

Hi Igor
Nexus has internal accounting log: sh accouting log
But it can be sent only to the accounting server, not to a syslog server.
If you want - you man manually export it to some log.
HTH,
Alex

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.

Data Center Hall Temperature for Cisco Nexus 7010

Hi,
I Have a Nexus 7010 that sometimes raise an alarm about temperature thresholds that are being exceeded.... I was wondering if Cisco has a recommendation (or best practice) about the correct temperature that the Nexus need in the cold and hot hall of the data room. I know that the operative temperature of nexus is 0 - 40°C but i´m not sure if my halls are in the best temperature.

Hi Salvador,
As long as you keep your Data Center environment in this operative range your N7K will be fine.
The usual is around 18°C and 24°C.
Richard

Monitoring optical level cisco nexus 7010, 5548.

Good day!
Please help me find oid for monitoring optical levels by snmp.

Hi ,
Have you tried to snmpwalk the entSensorValueTable
(.1.3.6.1.4.1.9.9.91.1.1.1) from the CISCO-ENTITY-SENSOR-MIB
It¹s indexed by entPhysicalIndex, so you¹ll need to snmpwalk the
entPhysicalDescr (.1.3.6.1.2.1.47.1.1.1.1.2) to map the index in the above
table to a name/entity indexed by the same # here.
what is the equivalent CLI for the same ?
Thanks-
Afroz

In reviewing the Cisco Licensing Guide, there is a license part number for MPLS on the Nexus 7010. Part Number is N7K-MPLS1K9.

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.

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

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
Hari

You can set an alert for Warning State. This is feasible.
Juke Chou
TechNet Community Support

Nexus 7010 upgrade path

We currently have two Nexus 7010 with 5.0(2a) as system images.
We would need to know the correct upgrade path to 6.1(1). On the release notes it reads the path is from 4.2(8), 5.0(5) or 5.1(6) to 5.2(5) then to 6.1(1).
Also if ISSU is possible or, because we may need to upgrade EPLD, if there is no upgrade path to do a non-disruptive upgrade.

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.

Cisco Nexus to use Radius AAA authentication using Microsoft 2008 NPS

I have a Nexus 7010 running
Just wondering if you can help me with something. I'm having an issue with command authorization thru our aaa config. We don't have a problem authenticating its command authorization that is not working. From what I have seen and read Nexus NX-OS 6.x does not have any commands for aaa authorization unless you are configuring TACACS+. My basic config is below if you can help it would be much appreciated.
>>ip radius source-interface mgmt 0
>>radius-server key XXXXX
>>radius-server host X.X.X.X key XXXXX authentication accounting
>>radius-server host X.X.X.X key XXXXX authentication accounting aaa
>>authentication login default group Radius_Group aaa authentication
>>login console local aaa group server radius Radius_Group
>>    server X.X.X.X
>>    server X.X.X.X
>>    source-interface mgmt0
Also does anyone know how to configure Microsoft 2008 NPS as a Raduis server to work with Nexus? I have read a few post that suggest changing the
shell:roles="vdc-admin" in the Attribute Value field in the RADIUS server
Does anyone know if this works????
Thanks

I have never done this before with ACS but not with NPS. However, you are in the right path. Nexus uses NX-OS which is different in some regards to regular IOS. One of those differences is the AAA setup. In NX-OS you assign users to roles. So for full access you will need to return the following attributes from your Radius server:
Attribute: cisco-av-pair
Requirement: Mandatory
Value: shell:roles*"network-admin vdc-admin"
For more information take a look at this link:
http://www.cisco.com/c/en/us/support/docs/security/secure-access-control-system/115925-nexus-integration-acs-00.html
Hope this helps
Thank you for rating helpful posts!

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 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 SUP OID

I like to monitored the status of both Nexus 7010 Supervisor Modules with my NMS (e.g., active, stand-by or failed...) Does anyone the OID that I should be monitoring?

Hi Norman,
     The MIB that contains the information you are after re Nexus 7000 Supervisor card status, is the CISCO-ENTITY-FRU-CONTROL-MIB. In particular the object cefcModuleOperStatus (.1.3.6.1.4.1.9.9.117.1.2.1.1.2) which belongs to cefcModuleTable. If you go to Cisco's SNMP Object Navigator at http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en , you'll be able to look up the list of values returned by cefcModuleOperStatus for the different statuses, plus you'll be able to see other objects in cefcModuleTable that may be of interest eg cefcModuleResetReason .
     Entries in cefcModuleTable are indexed by entPhysicalIndex which comes from entPhysicalTable. In order to relate entries in cefcModuleTable to modules in your Nexus 7kdo the following :
1.     Perform an snmpwalk of entPhysicalDescr (.1.3.6.1.2.1.47.1.1.1.1.2) and entPhysicalName (.1.3.6.1.2.1.47.1.1.1.1.7)
2.     Perform an snmpwalk of cefcModuleOperStatus
                      The relationship should be apparent , but if you need help with this please send me the output from these snmpwalks and I'll explain it to you.
Regards
Derek Clothier

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.

Ciscoview Package File for Nexus 7010

I found an old support modules table at
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_ciscoview/device_support/table/cvsdt.html
dated Feb 28, 2012. I cannot find one newer.
I have LMS 4.1 and I'm trying to render a Nexus 7010 in Ciscoview. I have downloaded the latest package files. The Sup2 and Fab2 modules (N7K-SUP2 and N7K-C7010-FAB-2) show as "unsupported card".
What packages and versions are required to recognize this card with LMS 4.1?

The Sup2 requires 9.0 of the package file (dated 1/2/2013). You can download it here. (Click all Releases, 6.1.0, then choose the Nexus 7000 package.)
The readme is here. It mentions the N7K-C7009-FAB2 is supported (since 7.0) but nothing about the 7010-FAB-2 so you may still be out of luck on that one.

Cisco Nexus 7010

Similar Messages

Maybe you are looking for