RME 4.3.1 & Nexus 7000 device package

I am have 27 devices that RME reports as "Out-of-Sync", among those some are Nexus 7K devices, with the sysObjectId .1.3.6.1.4.1.9.12.3.1.3.612, which according to the "Supported Device Table for LMS 3.2" is supported in RME 4.3.1.
Searching for device package with that sysObjectId I get no result in Common Services. However, when performing a "Device Update" with my CCO account, Ciscoworks tells me that "All the available package(s) at source location are already installed."
What do I have to do to get that device package?

Hi,
To check / download the latest RME Device Package for Nexus 7k support, please do the following :
1. Go to Common Services -> Software Centre -> Device Update and click on the hyperlink for 'CiscoWorls Common Services'
* You should see 2 packages listed - Device Data and MDF.
* The latest versions of these are 1.10 and 1.48 respectively.
* If you don't have the lateset versions installed, please run an update to install these.
2. Once you have the most up to date packages for Common Services installed, go to Common Services -> Software Centre -> Device Update and click on the number in the 'Device Type Count' collumn for Resource Manager Essentials. Filter the list of devices by Package Name = Nexus.
* Do you see sysObjectId .1.3.6.1.4.1.9.12.3.1.3.612 displayed ?
* What version of the Nexus device package do you have installed ? (The latest version is 2.5)
3. Even if you have the latest Nexus package installed, run a device update for RME so that you loaded the latest versions of all packages (I see there were some new updates for shared packages eg LibCommon as recent as 21st January 2011.
In terms of the devices being reported as 'Out-of-sync' , this means that RME has detected that the running configuration and the startup configuration on the device are different. This could be because RME doesn't have the most recent copy of either config or it is a real situation of the startup and running config being out of sync on the device. If you go to the Out-of-Sync Summary page, select the Nexus 7k's and click on 'Sync on Device' RME will run a job to login to the devices and execute a copy run start.
* If your Nexus 7k's are still reported as 'Out-of-Sync' after the job completes then we'll need to investigate further.
Regards
Derek Clothier

Similar Messages

Smart call home - HTTPS transport from the Nexus 7000 to Cisco

hi
i try configured call home on nexus 7000 with https transport and proxy server
i follow this guide -
http://www.cisco.com/en/US/docs/switches/lan/smart_call_home/QuickStart_NX7000.pdf
and configured this :
callhome
email-contact XXXXXXXXXXX
phone-contact XXXXXXXXXXX
streetaddress XXXXXXXXXXXXXXXX
destination-profile CiscoTAC-1 transport-method http
destination-profile CiscoTAC-1 http https://tools.cisco.com/its/service/oddce/services/DDCEService
transport http use-vrf management
transport http proxy server XXXXXXXXXX port 8080 --------- XXXXXXXXX = my proxy server
transport http proxy enable
enable
periodic-inventory notification interval 30
i have a problem to install the security certificate , i follow thw guide but i get the error :
failed to load or parse certificate
could not perform CA authentication
when i try test call home eith the command : callhome test
trying to send test callhome message
warning:no callhome message sent
email configuration incomplete for destination profile:full_txt
email configuration incomplete for destination profile:short_txt
Error in transporting http message for CiscoTAC-1
http: Received HTTP code 407 from proxy after CONNECT
i guess the problem is because i didnt install the certificate , how can i install the certificate ?
is this the real problem ?

I agree with Bryan that the easiest proxy server to setup for the nexus 7000 is the Transport Gateway. The documentation (certificates) is setup to allow you to connect to a Cisco Transport Gateway or directly into tools.cisco.com. Both have a Cisco certificate.
But that doesn't explain your issue. To answer your issue, you need to look here
http://www.cisco.com/en/US/docs/switches/lan/smart_call_home/SCH31_Ch6.html#wp1039385
except you need your proxy server's chained certificate in PEM format since the Nexus 7000 is going to terminate at your proxy server. Take a look at this line in the documentation.
Input (cut & paste) the CA certificate (chain) in PEM format
The error code 407 you indicated makes sense and indicates "Proxy Authentication Required". You need the certificate installed first. NX-OS uses the openssl crypto library to implement the cert-pki feature if that helps. A complete certificate chain is required. Also, you might make sure the CRL (certificate revocation list) is set to none so it doesn't do that first.
revocation-check none
The 4 chained certificates given in the documentation are tools.cisco.com.cer, Verisign-G3-SSCA.cer, Verisign-G3-PRCA.cer, Verisign-Root-CA.cer. The non-nexus 7000 devices just use the last one. Most likely you need a certificate that looks like
your proxy server.cer,Verisign-G3-SSCA.cer, Verisign-G3-PRCA.cer, Verisign-Root-CA.cer
If you are using your own root CA (which typically are taken off-line after authorizing subordinate CAs for security reasons) , then make sure that their certificates are in the correct order to be processed so each can be authenticated.
Now you can see why a Cisco proxy server (Transport Gateway) is easier to setup.

LMS 2.6 / RME 4.0.6 : Update device packages

Hi All,
I want update device packages for the device Unknow c3560v2 and ME2400 on ciscoworks lms 2.6.
CCS= version 3.0.6
CM= version 4.0.10
CV = 6.1.5
DFM = 2.0.7
IPM = 2.6.0
RME = 4.0.6
The server doesn't have access internet so i downloaded files and copy this on directory psu.
1) I've tried directely upgrading the device package in RME, but it failed. He want file mdf v1.22 and the version is V1.20.
2) I've upgrading CiscoView for device, it's ok
3) I've upgrading Campus Manager with version 4.0.13, it's ok
4) I've tried upgrading the device package in RME, but it failed. He want file mdf v1.27 and the version is V1.25 after upgrade Campus.
I don't find on site cisco the version 1.27 of mdf, where i can found this file ?
I have the version 1.56 but it's compatible for LMS 2.6 and RME 4.0.6 ?
How can uninstall a version of mdf if I have a problem with this version?
thanks

Indeed. It does look like the only MDF available is 1.52 for CS 3.0
I also saw the note:
You must install Campus Manager 4.0.13 and MDF 1.27 before installing CMDeviceUpdates 2.0.
RME 4.0.6 Release Notes
FYI. LMS 2.6 is EOL. As such I suggest you contact your account team to see if they can acquire it for you.
Thanks.

Ask the Expert: Basic Introduction and Troubleshooting on Cisco Nexus 7000 NX-OS Virtual Device Context

With Vignesh R. P.
Welcome to the Cisco Support Community Ask the Expert conversation.This is an opportunity to learn and ask questions of Cisco expert Vignesh R. P. about the Cisco® Nexus 7000 Series Switches and support for the Cisco NX-OS Software platform .
The Cisco® Nexus 7000 Series Switches introduce support for the Cisco NX-OS Software platform, a new class of operating system designed for data centers. Based on the Cisco MDS 9000 SAN-OS platform, Cisco NX-OS introduces support for virtual device contexts (VDCs), which allows the switches to be virtualized at the device level. Each configured VDC presents itself as a unique device to connected users within the framework of that physical switch. The VDC runs as a separate logical entity within the switch, maintaining its own unique set of running software processes, having its own configuration, and being managed by a separate administrator.
Vignesh R. P. is a customer support engineer in the Cisco High Touch Technical Support center in Bangalore, India, supporting Cisco's major service provider customers in routing and MPLS technologies. His areas of expertise include routing, switching, and MPLS. Previously at Cisco he worked as a network consulting engineer for enterprise customers. He has been in the networking industry for 8 years and holds CCIE certification in the Routing & Switching and Service Provider tracks.
Remember to use the rating system to let Vignesh know if you have received an adequate response.
Vignesh might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community discussion forum shortly after the event. This event lasts through through January 18, 2013. Visit this forum often to view responses to your questions and the questions of other community members.

Hi Vignesh
Is there is any limitation to connect a N2K directly to the N7K?
if i have a an F2 card 10G and another F2 card 1G and i want to creat 3 VDC'S
VDC1=DC-Core
VDC2=Aggregation
VDC3=Campus core
do we need to add a link between the different VDC's
thanks

RME 4.0.6 Device Package update failure

Hi,
i have downloaded a lot of new device packages for the RME 4.0.6. If i install this packages i get the following error message.
Installation failed for product [Resource Manager Essentials] with message : com.cisco.nm.xms.psu.packagemgmt.InstallerException: Repository in use.
Another Package Support Updater client session may be modifying device support.
I searched for the psu.lock file but i couldn't find this file. How can i fix this without reinstalling the lms?
AndrÃ©

Hi,
i have attached the psu.log file. There is no .lock file, i've checked this again. I tried again to update the device packages
After 1 hour i stopped the update.( normaly an update take max. 10 minutes. During the device package update i could see the the psu.log file was going into a loop. It starts at 0 kbytes -> growing to nearly 950kbytes and than it starts again at 0 kbytes
Andre

Uploading/Installing procedure for device packages in Cisco View/RME

Hi,
Running LMS3.2 with HUM 1.2.
In cisco view when we tried for below mwntioned devices it says "Device Package for these device is not available".
WS-C2960S
CISCO2921
CISCO3945E.
Please let me know the link to download the device packages for above devices and the procedure to install it on LMS.
Thanks & Regards,
Krishna

Hi Krishna,
Replace the attached file (vds.properties) in the below location :
NMSROOT\CSCOpx\lib\classpath\com\cisco\nm\xms\vds
then Restart the Daemon Manager ..
NOTE : Please take the Bcakup of your Existing file (vds.properties)
--Then go to common service > software center > device update >> check for the Device Pcakages , you will be able to see the Device Packages now..
Thanks--
Afroj
If this post answers your question, please click the "Correct Answer" button"

Ciscoworks 2.6 and Nexus 7000 issues

Running LMS 2.6 with RME version 4.0.6, and DFM 2.0.13.
We keep getting false alerts in DFM on the temperature in our Nexus 7000 switches. The alert says that the high temp threshold is 45C, and it's being exceeded at 46C. The thing that bothers me is that the actual switch reads that the threshold is around 100C or more. Any ideas as to why DFM would be picking up a temperature so far off the mark?
Also, in regards to RME, I cannot pull configs from the Nexus 7000's. The check box in "archive config" is blanked out to where I can't check it. I download the device packages for the 7000 into RME but it will not pull configs. Is this not supported under our version of RME, or would there be some other reason that I can't do this?
Thanks for any assistance with these issues!

UPDATE:
I fixed the RMA config pull issue. I thought I had previously downloaded the Nexus device packages so that RMA could work with them, but upon checking again, it looks like I just didn't have them installed. Got that piece fixed and now I can pull configs from the switches just fine.
Still having problems with the temperature reading in DFM not accurately reflecting what is actually on the switches. Any suggestions as to where to start hunting down the issue for this are greatly appreciated. Thanks!

Nexus monitoring, device recource metrics

Hello
I'm looking for Nagios/Nexus Plugins and lesson learned is, that there seams to be currently (2011/10/20) nothing at all.
So I want to start with this and want to ask the experts about the basics of Nexus monitoring.
What is the best practice to monitor Nexus device recource metrics? NetConfig, SNMP, SSH with preshared key?
For Netconfig are there any documentation how to can use it with Perl?
If SNMP should be still the best, are this OIDs known or what should be the best method to get them out?
Are there SNMPv3 issues e.g. with views?
How to find out the Nexus OID's for its IOS-equivalents, e.g.
"Voltage" => ".1.3.6.1.4.1.9.9.13.1.2",
"Temperature" => ".1.3.6.1.4.1.9.9.13.1.3",
"Fan" => ".1.3.6.1.4.1.9.9.13.1.4",
"PSU" => ".1.3.6.1.4.1.9.9.13.1.5"
ModuleState ?
How to find out OIDs for special CLI commands, e.g. traffic class violations:
sh policy-map interface control-plane | egrep "class-map|violated"
    class-map copp-system-class-normal (match-any)
        violated 5394687638 bytes; action: drop
If Netconfig is to complicated and finding Nexus SNMP-OIDs is an unresolveable neightmare, can SSH with preshared key could be an oportunity for permanent monitoring?
many thx in advance for your hints and ideas,
Steffen

Though Nexus 7004 is supported from LMS 4.2.2 onwards, but it is in a restricted support :
The following features are supported:
Fault Management
Network Topology Layer 2 Services
The following features are not supported:
Inventory Collection , User Tracking, VLAN Management, VRF Lite, LANE Management
Configuration Deploy Protocols: HTTPS, SCP, RCP, TELNET, TFTP, SSH
Configuration Fetch Protocols: HTTPS, SCP, RCP, TELNET, TFTP, SSH
Software Distribution by: Advanced flow, Image, Remote Staging
Software Repository Synchronization
CiscoView
Software Image Types for Distribution: System Software, Bootloader
Software Images Import from: Cisco.com, Device, File System, Network, URL
Upgrade Analysis from: Cisco.com, Repository
Software Image Import Connection Protocols: SNMP
Software Image Import Transfer Protocols: TFTP, TELNET
Software Image Distribution Transfer Protocols: TFTP, TELNET
Software Image Distribution Connection Protocols: SNMP
If this is not working, it is only that the essential device package seems to be missing. please do the following :
1. Download all device packages available for LMS server :
     Step 1: Open command prompt on server.
     Step 2: Run following cli command :
psucli -p rme,cmf,dfm,cvw,upm,cm -download -dst C:\test_download -all
**Created test_download dir or name some existing.
     Step 2: Check the downloaded files, if they are in diffrent folders inside download dir, copy all of them to a common folder and run this command :
psucli -p rme,cmf,dfm,cvw,upm,cm -install -src D:\test_download -all
**use directory you downloaded packages to
     Step 4: Check the device if it shows nexus 7004 information or not.
Share results.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

LMS 4.2 fails Device Package Update

Hallo,
Device Package Update fails with this error:
Error while downloading package information from Cisco.com for the selected products. See the d:/CSCOpx/log/psu.log file for details.
PSU.log shows:
ERROR [RemoteRepSync : downloadPsuHeadersAsXml] : VDSException thrown com.cisco.nm.xms.vds.VDSException: CcoDownloadAdapter::getXmlFileList():IOException:connect timed out
best regards
Alex

What is the exact model of 3850 switch you're trying to monitor?
Following are the supported models :
Device Name
sysObjectID
Supported Software Version
Support Type
Device Name
sysObjectID
Supported Software Version
Support Type
Cisco Catalyst 3850-48P-E Switch
1.3.6.1.4.1.9.1.1641
Device Update
Cisco Catalyst 3850-48P-S Switch
1.3.6.1.4.1.9.1.1643
Device Update
Cisco Catalyst 3850-24P-E Switch
1.3.6.1.4.1.9.1.1642
Device Update
Cisco Catalyst 3850-24P-S Switch
1.3.6.1.4.1.9.1.1644
Device Update
Cisco Catalyst 3850-24U-E Switch
1.3.6.1.4.1.9.1.1767
03.11.35.EMP
Device Update
Cisco Catalyst 3850-48U-E Switch
1.3.6.1.4.1.9.1.1768
03.11.35.EMP
Device Update
If it is 3850-24p-L, it can be :
CSCuj61704 No support for 3850-24p-L in LMS 4.2.3
Try updating your mdf device package as well. Device package for Common Services.
For current Nexus device package issue, each device package is not individual, but has some dependant packages. Without which they are tend to fail during installation check.
You can select all the available device packages and try to install. It seems you dont have SharedDcmaIOS (3.1.7) installed and hence the package is failng due to pre-requisite.
You have to install each package which fails which consistancy check on other packages.
For mdf package update, you can select common service as well and check for update.
There may be some 3850 device packages already available, please share output of following command for us to see :
NMSROOT/bin/psucli -p rme -q -all
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Device package error for switch Cat2960

Hi,,
We are installing device package for switch Cat2960. But we get below error message when trying to install the same.
WARNING : Cat2960(6.1):Consistency check failed for base package SharedDcmaIOS
When trying to updgrade the SharedDcmaIOS to higher version we get the below error message.
SharedDcmaIOS, SharedNetshowIOS, SharedSwimIOS
WARNING : SharedSwimIOS(2.5.1):Consistency check failed for base package LibSwim
WARNING : SharedNetshowIOS(2.2.1):Major versions are incompatible for base package [SharedNetshowIOS]. Required version = 1.0, Found version = 2.2
Kindly guide us in resolving the above issue related to device pacakage installation.
License Info:
Bundle             Installed/Updated on
LMS2.6            18 Jun 2009
Name      Version      Size         Status        Expiration Date
1.CM         4.0       Unlimited    Purchased      Never
2.DFM       2.0       Unlimited    Purchased      Never
3.IPM        2.6      Unlimited     Purchased      Never
4.RME       4.0      Unlimited     Purchased      Never

Hi,
We are using LMS2.6 and you have provided solution to install / upgrade to LMS 2.5.1
We are installing the device package Cat2960.RME43.v6-1 for switch 2960
Supporting device package we are installing are
SharedSwimIOS.RME43.v2-5-1
SharedDcmaIOS.RME43.v2-4-1
SharedNetshowIOS.RME43.v2-2-1
When installing we get the error Consistency check failed for base package.
Regards,
Rakesh Prasad

Using SNMP to monitor Nexus 7000 Series Supervisor Module

Hello,
I got a Nexus 7000 supervisor module recently, I met a SNMP problem for this module
I would like to know which specific OIDs to use to monitor the following using SNMP on a Nexus 7000 supervisor module:
- Port status
- CPU total utilization
- Power Supply status
- Chassis Fan status
etc.
The Nexus is quite different from other Cisco devices - any help will be appreciated!

hope help, and
port status OID is ifOperStatus
CPU total utilization OID is 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifDescr.83886080
.1.3.6.1.2.1.2.2.1.2.83886080 = STRING: mgmt0
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifOperStatus.83886080
.1.3.6.1.2.1.2.2.1.8.83886080 = INTEGER: up(1)
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
.1.3.6.1.4.1.9.9.109.1.1.1.1.6.1 = Gauge32: 21
[root@NET-MONITOR-1 ~]#

Log configuration changes to syslog on Nexus 7000?

I need to be able to log any configuration changes to syslog on our Nexus switches. On IOS this is easy with the archive commands, but I'm a little stuck trying to do this on our Nexus gear. On the IOS gear I run the commands:
archive
log config
logging enable
logging size 100
hidekeys
notify syslog
How do I do the equivalent on NX-OS?

Cisco NX-OS can log configuration change events along with the individual changes when AAA command accounting is enabled.
With command accounting enabled, all CLI commands entered, including configuration commands, are logged to the configured AAA server. Using this information, a forensic trail for configuration change events along with the individual commands entered for those changes can be recorded and reviewed.
Because of this capability, it is strongly advised that AAA command accounting be enabled and configured.
Refer to the “TACACS+ Command Accounting” section of this document for more information.
The Nexus 7000, by default keeps a local accounting log of all the configuration commands entered on the device; you can view this with the 'show accounting log' command.
In NX-OS, we changed the way logging works. We keep a local accounting log of all the
configuration changes ("show accounting log"), but if you want to send those logs to a
server, it must be done with through a TACACS server. Please see the below documentation:
Configuring AAA on Nexus
TACACS command accounting
-Thanks
Vinod
**Encourage Contributors. RATE Them.**

DCNM for LAN Enterprise License for one Nexus 7000 Chassis

if i have just DCNM-N7K-K9 (DCNM for LAN Enterprise License for one Nexus 7000 Chassis) installed on a server, i can manage all nexus switches like 5k and 2k??

You can manage 2K & 5K devices but a $0 cost license is required. A purchase order for DCNM-NXACC-100-K9 should do the trick.
Thanks.

Nexus 7000-Error Message

Hi
We are having 2 nexus switches configured in the network as core with HSRP configured between them..The access switches are connected withdual 10G links to both core switches with VPC configured in Nexus..In both core switches 10G module is used for uplink termination..In one of the core switch for this 10 G module we get the follwoing error
Module-1 reported minor temperature alarm. Sensor=20 Temperature=101 MinThreshold=100 2011 Dec 22 08:10:19 CORE-SEC %PLATFORM-2-MOD_TEMPOK:
Module-1 recovered from minor temperature alarm. Sensor=20 Temperature=99 MinThreshold=100 even though the room temprature is 23 Degree still we get this error wherein as per the nexus documenation allowed room temparature is 0-40 Degree (Operating temperature: 32º to 104ºF (0º to 40ºC) `
show module`
Mod Ports Module-Type                      Model                            Status
1    8      10 Gbps Ethernet XL Module      N7K-M108X2-12L        ok
2    32    1/10 Gbps Ethernet Module        N7K-F132XP-15          ok
3    48    10/100/1000 Mbps Ethernet XL Mod N7K-M148GT-11L    ok
5    0      Supervisor module-1X            N7K-SUP1                      active *
As per the nexus module documentation for module1 the allwed temparature is 0-40degree wherein the actual room temparatue is 23degree..below is the exception message for module1
exception information --- exception instance 1 ----
Module Slot Number: 1
Device Id         : 49
Device Name       : Temperature-sensor
Device Errorcode : 0xc3114203
Device ID         : 49 (0x31)
Device Instance   : 20 (0x14)
Dev Type (HW/SW) : 02 (0x02)
ErrNum (devInfo) : 03 (0x03)
System Errorcode : 0x4038001e Module recovered from minor temperature alarm
Error Type       : Minor error
PhyPortLayer     :
Port(s) Affected :
DSAP             : 39 (0x27)
UUID             : 24 (0x18
Same module exists in second Nexus 7000 which is in same datacenter but not getting this alarm..
can anyone please suggest on the same..Software details are as below
Software
BIOS:      version 3.22.0
kickstart: version 5.1(3)
system:    version 5.1(3)
BIOS compile time:       02/20/10
kickstart image file is: bootflash:///n7000-s1-kickstart.5.1.3.bin
kickstart compile time: 12/25/2020 12:00:00 [03/11/2011 07:42:56]
system image file is:    bootflash:///n7000-s1-dk9.5.1.3.bin
system compile time:     1/21/2011 19:00:00 [03/11/2011 08:37:35]

Hi Sameer
Temperature alarm means that one particular sensor on the linecard warms up to 101 degree.
This can be caused by damaged sensor or problems with cooling in that particular part of chassis.
You can check temperature on the module using following command:
show environment temperature module 1
Tru to move the module to another slot. If the issue reoccure - open a TAC case.
HTH,
Alex

AAA problems Nexus 7000 %AUTHPRIV-3-SYSTEM_MSG: Unable to create temporary user

Hi,
I'm having problems getting our Nexus 7000 to authenticate users from our Windows domain. If I set up a user within the ACS server and use the CiscoSecure database for password authentication it works fine.
In the logs on the nexus I receive the following messages when logging on using my windows account.
%AUTHPRIV-3-SYSTEM_MSG: Unable to create temporary user 16894. Error 0x404a0036 - login[20923]
%AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication failed for user 16894 from 10.128.45.44 - login[20923]
We can log on to all other Cisco OS devices using windows domain accounts, its just the Nexus.
Any help much appreciated.
Thanks
Darren

No errors the autnetication on the ACS is showing as passed. The problem is I get an access denied message from the nexus switch,

RME 4.3.1 & Nexus 7000 device package

Similar Messages

Maybe you are looking for