LMS + Nexus F2 linecards

I'm wondering if anyone else is using LMS 4.2 with the F2 series Nexus 7K linecards (N7K-F248XP-25).
I'm trying to but they show up as "Unsupported Card" in CiscoView (despite having the latest 7.1 version of the CiscoView Nexus 7K package).
At this point I'm not sure if it's a CiscoView- or VDC-related issue but I'm leaning towards the former.

You should be able to manage those cards in CiscoView once you update the CV package for the Nexus 7k to version 8.0. (Youll lneed the latest SwitchAddlets also.)
Per the package release notes:
WHAT IS NEW?
============
This 8.0 release of the Nexus7000 device package provides support for the following devices and modules:
Modules supported in this release
* N7K-F248XP-25

Similar Messages

LISP ESM Nexus F3 linecards

Trying to find out if anyone can confirm that the a Nexus 7700 running NX-OS v6.2(8) with only F3 cards can support LISP ESM Multihop where the Nexus 7700 is the first-hop router. We have layer 3 connected ASR1001x routers which will be the xTRs. I know that the Nexus 7700 as an xTR is only supported with either an M1 card or once 7.x code is released. Based on the document below, I believe this is exactly the design we are looking towards and just looking to confirm that we do NOT need the M1 card for the Nexus 7700 to act as the FHR.
http://lisp.cisco.com/docs/OTV_and_LISP-DC_Design_Recommendation-v1.2.pdf

Hello Heather,
the restriction comes from LISP encapsulation or decapsulation in hardware. Both the N7700 as well as the F3 linecard will have support for LISP encap/decap from 7.2 onwards.
As FHR functionality is "just" detecting you are fine.
If possible I would propose 6.2(10) or 6.2(12) (not sure the latter is out already). A couple of fixes went into 6.2(10) and a small number into 6.2(12).
Marc

IS Prime DCNM support for 2960 switches

Hi All,
There is a requirement for a NMS solution, Solution must have a single dashboard
but in the netwroks i am having 2960s, N2K, N5K, N7K, in order to mange this data-center network
do I need to quoted for Cisco LMS and DCNM or LMS is enough

The most comprehensive single product solution for those set of devices would be LMS. It does have limitations in managing the User Tracking, VLAN (provisioning primarily) and SAN aspects of the data center switches. Note Nexus 2ks are not separately managed, but rather viewed as an integral part of their controlling 7k or 5k.
LMS Catalyst 2960 support described here.
LMS Nexus support described here.
DCNM is not really designed for IOS-based devices. It has some very limited support for the Catalyst 6500 but other than that it is primarily focued on the NX-OS-based data center products. See the DCNM Release Compatibility Matrix for more details. (And add the DCNM 6.1 release notes updates.)

LMS 3.2: RME failed archive with Nexus 5010

Hi,
LMS 3.2, RME 4.3.1, dev packages updated, Windows.
We would like to archive the configuration of the Nexus 5010 switches. Due to authentication with Radius based on tokens we're not able to use telnet/SSH and therefore we only can use SNMP WRite in combination with TFTP. But, this is not working at all. Other systems like 3750 works fine. Is there a difference between Catalysts IOS and nexus NXOS?
I searched the forum and found this:
https://supportforums.cisco.com/message/663481#663481
upgrade to LMS 2.6, archive config not working anymore
We ship and start a TFTP server by default on Windows. You must have an SNMP read-write community string configured on your devices, and entered in DCR for TFTP config fetches to work. Additionally, udp/69 must be open between device and server.
The easiest way to troubleshoot this kind of problem is to start a sniffer trace on the LMS server (using Device Center > Packet Capture). Filter on all traffic to one of the failing devices. Then, run a Sync Archive job for that same device. When it fails, the sniffer trace will indicate what the problem is
Regards
Ad Olsthoorn

Hi Lavramov,
Yes I'm quite sure, I installed the required packages acoording to the Nexus.RME431.v2-2.readme.pdf manual. the manual tell me to install the following (see also attachement).
To install the Cisco Nexus Series Package, you must install the following dependent packages:
- SharedDcmaSS.RME431.v2-2.zip
- SharedInventoryMDS.RME431.v1-5-1.zip
- SharedSwimMDS9000.RME431.v1-6-1.zip
- SharedNetshowSS.RME431.v1-1.zip
regards
Ad

Can't archive nexus 5010 configs (LMS 3.2)

Using LMS 3.2 I can't archive configs from
our Nexus 5010 ( 4.2(1)N1(1) ) devices . I have installed
the   necessary device package Nexus.RME431.v2-4.zip. Following error occures:
*** Device Details for                          gf02na50050p                         ***
Protocol ==>                          Unknown / Not Applicable
Selected Protocols with order ==>                                                                                  SSH,SCP,TFTP,RCP,Telnet
Execution Result:
RUNNING
CM0151 PRIMARY RUNNING Config fetch failed for gf02na50050p Cause: Failed to fetch config using TFTPFailed to establish TELNET connection to 10.92.170.214 - Cause: Connection refused.
Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.
Telnet on device is disabled, SSH enabled.
with only SSH on RME   followig error:
*** Device Details for                          gf02na50050p                         ***
Protocol ==>                          Unknown / Not Applicable
Selected Protocols with order ==>                                                                                  SSH
Execution Result:
RUNNING
CM0151 PRIMARY RUNNING Config fetch failed for gf02na50050p Cause: Failed to get the start tag-Building Configuration ... in the configuration. Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.
Thanks
Igor

RME 4.3.1; windows platform
with one customer I have the same issue with a Nexus 5020. Software version is :
Software
BIOS:      version 1.3.0 [last: ]
loader:    version N/A
kickstart: version 4.2(1)N2(1)
system:    version 4.2(1)N2(1)
power-seq: version v1.2
BIOS compile time:       09/08/09 [last: ]
kickstart image file is: bootflash:///n5000-uk9-kickstart.4.2.1.N2.1.bin
kickstart compile time: 7/28/2010 18:00:00 [07/29/2010 03:10:19]
system image file is:    bootflash:/n5000-uk9.4.2.1.N2.1.bin
system compile time:     7/28/2010 18:00:00 [07/29/2010 07:18:12]
Hardware
cisco Nexus5020 Chassis ("40x10GE/Supervisor")
Intel(R) Celeron(R) M CPU    with 2074284 kB of memory.
===============
following RME packages are installed:
    SharedNetshowSS      1.1.2      SharedNetshowSS device package
    SharedSwimMDS9000    1.6.3      SharedSwimMDS9000 device package
    SharedInventoryMDS   1.5.1      SharedInventoryMDS device package
    SharedDcmaSS         2.2.2      SharedDcmaSS device package
    Nexus                2.4        Nexus device package
===============
>>> I see the following problems with SSH instrumentation of the Nexus Platform when looking into the debug file. The file I got is more or less the same then the one Marc posted.
The customer does not have a banner configured so the standard login procedure shows the following when login is done manually. RME automatically interpretes the first line after "Login as: " as a banner...
login as: Nexus
Nexus 5000 Switch
Using keyboard-interactive authentication.
Password:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
devicename#
>>> and RME wants to take the last line as the prompt, resulting in a non-fatal java exception:
[line 1471 ff.]
[ Mon Aug 30 08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Learning prompt: sA[0] == 'http://www.opensource.org/licenses/lgpl-2.1.php'
[ Mon Aug 30 08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Learning prompt: sA[1] == ''
[ Mon Aug 30 08:58:01 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,printStackTrace,51,stacktracecom.cisco.nm.lib.cmdsvc.CmdSvcException: Prompt learning failed: 'http://www.opensource.org/licenses/lgpl-2.1.php' && '' do not match.
    at com.cisco.nm.lib.cmdsvc.Session.tune(Session.java:904)
    at com.cisco.nm.lib.cmdsvc.Session.tune(Session.java:833)
    at com.cisco.nm.lib.cmdsvc.AuthHandler.connect(AuthHandler.java:267)
    at com.cisco.nm.lib.cmdsvc.OpConnect.invoke(OpConnect.java:56)
    at com.cisco.nm.lib.cmdsvc.SessionContext.invoke(SessionContext.java:299)
>> Ok, RME proceeds, but the SSH implementation (SharedDcmaSS ?) cannot extract the config and a java exception occures which leads to "Closing the session":
[ Mon Aug 30 08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Returning from Session.send('show startup-config
[ Mon Aug 30 08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,in trimPrompt(), prompt == ''
[ Mon Aug 30 08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator,fetchConfig,490,Failed to get the start tag-Building Configuration ... in the configuration.com.cisco.nm.xms.xdi.ags.config.ConfigTransportException: Failed to get the start tag-Building Configuration ... in the configuration.
    at com.cisco.nm.xms.xdi.pkgs.SharedDcmaSS.transport.SSCliOperator.extractConfig2Buffer(SSCliOperator.java:176)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator.fetchConfig(CliOperator.java:436)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.CliOperator.fetchConfig(CliOperator.java:510)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.SimpleFetchOperation.performOperation(SimpleFetchOperation.java:61)
    at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.ConfigOperation.doConfigOperation(ConfigOperation.java:111)
    at com.cisco.nm.xms.xdi.pkgs.SharedDcmaSS.transport.SSConfigOperator.fetchConfig(SSConfigOperator.java:65)
    at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.updateArchiveForDevice(ConfigManager.java:1315)
    at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.performCollection(ConfigManager.java:3291)
    at com.cisco.nm.rmeng.dcma.configmanager.CfgUpdateThread.run(CfgUpdateThread.java:27)
[ Mon Aug 30 08:58:06 CEST 2010 ],DEBUG,[Thread-38],com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.SimpleFetchOperation,performOperation,62,FetchStatus - FAILURE for Protocol SSH for device x.x.x.x
>> As telnet and tftp are not allowed the config cannot be archived (Customer reports no problems with telnet...)
The config itself starts and ends with the following lines:
devicename# show startup-config
!Command: show startup-config
!Time: Mon Sep 6 16:41:02 2010
!Startup config saved at: Mon Aug 16 15:41:39 2010
version 4.2(1)N2(1)
no feature telnet
no telnet server enable
no feature http-server
cfs eth distribute
feature udld
feature interface-vlan
feature lacp
feature vpc
feature lldp
feature vtp
interface mgmt0
shutdown force
shutdown force
no snmp trap link-status
no snmp trap link-status
clock timezone MEZ 1 0
clock summer-time MEZS 5 sun mar 02:00 5 sun oct 03:00 60
line console
boot kickstart bootflash:/n5000-uk9-kickstart.4.2.1.N2.1.bin
boot system bootflash:/n5000-uk9.4.2.1.N2.1.bin
ip route 0.0.0.0/0 172.16.4.1
vtp mode transparent
vtp domain sap
logging server x.x.x.x 7 use-vrf default
logging server y.y.y.y 7 use-vrf default
devicename#
For me it looks like as a bug in the ssh implementation in RME, but I cannot find a bug id on CCO ....

Cisco LMS 4.2.3 - Nexus VDC - SNMP

Hi All,
I am having some trouble with getting inventory collection work for the VDC's of a Nexus 7k from LMS 4.2.3.
The collection works for the main VDC, just not any of the others.
I have verified (using SNMPWALK) from the LMS server that the snmp credentials in use on the LMS for these VDC's is correct.
We are using SNMP V3.
The error I am getting when trying to run an inventory collection is:
Device Collection Failed. Failed to fetch Containment details.
Does anyone have any experience with getting VDC's to work in LMS and may have seen this error before?
Thanks in advance.

Hi ,
You are hitting the below BUG:
LMS 4.2.3 Inventory collection is failing for some of Nexus 7k devices
CSCuh49814
Development team is still working on the fix.
Thanks-
Afroz
[Do rate the useful post]

LMS 4.2 with Nexus C7010 Switch

Hi Guys,
I tried to add Nexus C7010 into my LMS 4.2, the SNMP work like charm but not for the archieve config.
It just show "Incorrect" under SSH, further checking I found this
"Failed to establish SSH connection to 10.152.xx.xx - Cause: Authentication failed on device 3 times."
I understand that Nexus is using Role-Based Account and there is no enable secret password anymore.
How do I add the Credential for Nexus? Other devices with IOS is no problem at all.
Please Help... Thank you.

Pls try this...
There is a legacy Button on top right corner, select DFM, then select Event sets and select the required triggering fields like flap, operationallydown etc... and make it as A (there is a tick mark available to group all these fields under 'A' group.
Secondly, go to email notification group and select all the devices which you want to monitor and select Alerts and over there select 'A', then select Critical, Warning etc, click next next...
For rest of it, pls go by the logic.
E-Mail Configuration Tasks
Managing E-Mail Notification Subscriptions
CiscoWorks LMS Portal > Device Fault Manager > Notification Services > E-Mail Configuration > E-Mail Notification
Admin > Network: Notification and Action Settings > Fault - Email notification
The E-Mail Notification Subscription page displays information about subscription, status and notification group.

LMS 4.2.2 Interface utilisation on Nexus 7000

Hi All,
I'm trying to poll some interfaces for their utilization on a nexus 7000 through LMS 4.2.2.
When I create a poller fot the specific instances, the LMS recognises the instances, but after activating the poller I get the error "No Such Instance - The specified instance is not available".
No info is displayed when I generate an interface utilization report for the specific nexus.
When I activate the automonitor for interface utilization, the interfaces on the nexus are polled.
On the cisco website there are some features listed which LMS does not support on the Nexus 7000, but polling is not in that list (neither in the supported feature list).
Any tips?
Thanks for your help.
Joris

Any Idea..??

LMS User Tracking for NEXUS 5548UP

Dear,
A while ago I received a ticket from one of our customers because User Tracking was not working for NEXUS 5548UP on LMS 3.2. I opened a TAC case for this but this was normal since it is a Datacenter switch. Now the customer came back on this because they really want to see which server is connected to which switch port. I understood from the TAC engineer this is not on the roadmap to integrate in LMS 4.x. They want to know if there exists another product (they thought about DCNM) and wanted to know how this integrates or works together with LMS...
Kind regards,
Sven Laureyssens

My latest understanding of User Tracking and Nexus 5K series is that it is not supported due to a limitation of the MIB support in the NX-OS.
The current DCNM (release 5.2) is distinct from the LMS and Cisco Prime umbrella but that wil be changing a bit moving forwad as DCNM is enhanced and rolled into the Cisco Prime family. Last I heard there should be some information coming out of Cisco Live this week and a new release will have some additional functionality and better integration. Still, I doubt we'll see UT for the 5K due to the NX-OS limitation.
One way to do what you're asking apart from use of any of the Cisco products is to enable LLDP on your Nexus and servers. That will at least give you the ability to pull the information from the NX-OS command line ("show lldp neighbor")

LMS 3.2 : Can't collect inventory from Nexus 5010

Hello,
I've added a Nexus 5010 to LMS, and it recognized it as such, and it was also able to archive its configuration.
But LMS is unable to collect inventory from it : the error message is "Device Sensed, but collection failed".
I am able to do an snmp walk of the device and I do see the ENTITY mib.
I am running LMS 3.2 with no RME patches or device package updates.
I've attached the relevant portion of IC_Server.log.
The Nexus 5010 is running NX-OS 4.1(3)N2(1a).
Thanks for the help,
Alex.

>> I am running LMS 3.2 with no RME patches or device package updates.
So why not update the dev pkgs, then try again?
The latest RME pkg for Nexus is apparently v2.4, whereas I'm collecting the 5010s fine with v2.3.
704.
1.3.6.1.4.1.9.12.3.1.3.798
Cisco Nexus 5010 Switch
Nexus
2.3

LMS 4.1 Los equipos 6500 y Nexus 7k aparecen unreacheble en Discovery

Buenas tardes,
Llevo días configurando un LMS 4.1 pero tengo 2 problemas principales.
Tengo equipos 6500 y Nexus 7k que al realizar el Discovery siempre aparecen "unreachable", a pesar de que al revisar el SNMP, telnel, ssh estos estan bien y además se recogen sus traps y configuraciones.
El otro problema es que tengo equipos 3600 que manejan VRF y la looback de snmp esta en VRF, el quipo es descubierto por el Discovery pero lo realiza por otra IP de otra VRF y luego si manda sus traps por la ip de la loopback adecuada.
Ya he aumentado los atributos del timeout snmp a 10
Alguien podría ayudarme?

MLD limitations M2 and F2e Nexus linecards

Dear all,
According to Cisco's IPv6 MLD configuration guide, the following limitations and guidelines are applicable for Nexus M2 and F2e lincards.
http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/multicast/configuration/guide/b_multicast_chapter_0100.html
Optimised-Multicast-Flooding must be disabled.
Does anyone know whether these MLD limitations are also applicable for the recently manufactered/released F3 linecards?
Many thanks in advance!
Kind regards,
Wim

With current software, the only way for F2E to be in the same chassis with the M1/M2/F1 cards is for the F2E to be in a different vDC. The only way to connect the F2E to get connected to different cards is to physically connect them either through copper or fibre.

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,
Mayank

Hi, 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.

LMS 4.0, Support for Nexus VDC

Hi everybody,
Does LMS 4.0 support the management of Nexus 7000 VDCs?
I don't need it do be able to do anything complex. I was just interested in syslog, polling, and config fetches. I can poll and ping the management IPs of the VDCs from the command line of the server itself, but it stays questioned and "UNKNOWN" in the device list.
The admin context of the Nexus 7000s are being added just fine. We recently built 4.0, coming from LMS 2.6. LMS 2.6 appears to add the VDC to the DCR without issue, but 4.0 does not. I just want to make sure that I'm not missing something.
Thanks for the help!
Tim

Hi everybody,
Does LMS 4.0 support the management of Nexus 7000 VDCs?
I don't need it do be able to do anything complex. I was just interested in syslog, polling, and config fetches. I can poll and ping the management IPs of the VDCs from the command line of the server itself, but it stays questioned and "UNKNOWN" in the device list.
The admin context of the Nexus 7000s are being added just fine. We recently built 4.0, coming from LMS 2.6. LMS 2.6 appears to add the VDC to the DCR without issue, but 4.0 does not. I just want to make sure that I'm not missing something.
Thanks for the help!
Tim

Cisco LMS 4.2.3 - Nexus VDC

Hi,
Does anyone know if its possible for LMS to pull all VDC configs via the Admin VDC or do we need to manage each VDC as seperate devices ? I know it can be done via CLI / DCNM but I`ve not seen a lot of infomation about support in LMS.
Thanks

Each VDC needs to be managed separately with LMS. They look like separate devices from all of the tools within LMS (Fault, Configuration, Performance, etc.)

LMS + Nexus F2 linecards

Similar Messages

Maybe you are looking for