For what it's worth, you can model a Nexus switch in Spectrum, and get some information, and supposedly they will be adding more SNMP instrumentation into future versions of the firmware. Many incumbent customers with any sort of NMS were burned pretty badly by Nexus. They even realized they were pissing off their customers and added support into CiscoWorks to keep the natives from rising up.
On Tue, Nov 9, 2010 at 3:55 PM, Naiman, Eugen <[email protected]> wrote: > You have to play a bit with “Device Type Identification” (right-click > menu/Utilities/Device Type Identification) > > Copy System Object ID from “Spectrum Modelling Information”, open the Device > Type Identification then add a new entry and put in the correct device type > for that OID. > > That won’t solve everything but at least, the device will have the correct > type when modelled by IP. > > > > Regards, > > ============================================ > > Eugen NAIMAN > IT Officer > ICT Infrastructure > Department Health and Human Services > 5/99 Bathurst Street, Hobart, 7000 > (: (03) 6233 8565 > Ê: (03) 6233 6297 > [email protected] > ============================================ > > From: Sobrinho, John [mailto:[email protected]] > Sent: Wednesday, 10 November 2010 2:50 AM > To: spectrum > Subject: RE: [spectrum] Modeling Cisco Nexus devices > > > > Hi Cliff. > > > > This is not all due to CA's lack of support. > > > > When Nexus was developed, they thought XML (web service type) was the way to > go to manage these devices. As such SNMP was not a big deliverable when they > hit market. They are only playing catch up with SNMP instrumentation, of > course Cisco conveniently developed DCNM tool for nexus, but does go fairly > deep into the virtualized switching environment and other unique nexus > features. > > > > To date following are our issues we are pursuing with CA. > > > > support for entity and fru traps ( there is no env mon mib available on > nexus) which makes support for entity/fru critical for module/power/fan > status changes/faults > support for L3.. although we have installed SUP cards CA discovery does not > recognize that these are L2/L3 devices, therefore some of the routing models > are not being discovered > support for Multicast, there is no instrumentation available for PIM, but > is coming, there are other multicast mibs available, but since spectrum > can't discover device as L3, we believe this also a potential issue with > Multicast Manager. > > > > Our Ehealth team confirms that they are able to see limited CPU/MEM stats, > and confirmed that this too is a Cisco limitation, and need to wait for > proper mib support. > > > > Latest for nexus mib support > > ftp-sj.cisco.com/pub/mibs/supportlists/nexus7000/Nexus7000MIBSupportList.html > > > > Regards, > > John > > > > > > > > ________________________________ > > From: HUNGERFORD, CLIFF [AG/1000] [mailto:[email protected]] > Sent: 2010, November, 08 3:34 PM > To: spectrum > Subject: [spectrum] Modeling Cisco Nexus devices > > Has anyone successfully modeled any of the Nexus switches (running NX-OS) in > Spectrum? > > > > It seems as if they support only the most basic of Cisco’s normal MIB set. > We’re trying to get at the CPU and memory stats. > > > > Thanks, > > > > Cliff > > > > Cliff Hungerford > Global Infrastructure - Business Alignment and Strategy > [email protected] > 314-694-3439 (phone) > 314-409-6501 (mobile) > 314-694-8614 (fax) > > > > This e-mail message may contain privileged and/or confidential information, > and is intended to be received only by persons entitled > to receive such information. If you have received this e-mail in error, > please notify the sender immediately. Please delete it and > all attachments from any servers, hard drives or any other media. Other use > of this e-mail by you is strictly prohibited. > > All e-mails and attachments sent and received are subject to monitoring, > reading and archival by Monsanto, including its > subsidiaries. The recipient of this e-mail is solely responsible for > checking for the presence of "Viruses" or other "Malware". > Monsanto, along with its subsidiaries, accepts no liability for any damage > caused by any such code transmitted by or accompanying > this e-mail or any attachment. > > > The information contained in this email may be subject to the export control > laws and regulations of the United States, potentially > including but not limited to the Export Administration Regulations (EAR) and > sanctions regulations issued by the U.S. Department of > Treasury, Office of Foreign Asset Controls (OFAC). As a recipient of this > information you are obligated to comply with all > applicable U.S. export laws and regulations. > > --To unsubscribe from spectrum, send email to [email protected] with the > body: unsubscribe spectrum [email protected] > > _______________________________________________________________________ > > This e-mail may be privileged and/or confidential, and the sender does not > waive > any related rights and obligations. Any distribution, use or copying of this > e-mail or the information > it contains by other than an intended recipient is unauthorized. > If you received this e-mail in error, please advise me (by return e-mail or > otherwise) immediately. > > Ce courriel peut contenir des renseignements protégés et confidentiels. > L’expéditeur ne renonce pas aux droits et obligations qui s’y rapportent. > Toute diffusion, utilisation ou copie de ce courriel ou des renseignements > qu’il contient > par une personne autre que le destinataire désigné est interdite. > Si vous recevez ce courriel par erreur, veuillez m’en aviser immédiatement, > par retour de courriel ou par un autre moyen. > > --To unsubscribe from spectrum, send email to [email protected] with the > body: unsubscribe spectrum [email protected] > > CONFIDENTIALITY NOTICE AND DISCLAIMER > > The information in this transmission may be confidential and/or protected by > legal professional privilege, and is intended only for the person or persons > to whom it is addressed. If you are not such a person, you are warned that > any disclosure, copying or dissemination of the information is unauthorised. > If you have received the transmission in error, please immediately contact > this office by telephone, fax or email, to inform us of the error and to > enable arrangements to be made for the destruction of the transmission, or > its return at our cost. No liability is accepted for any unauthorised use of > the information contained in this transmission. If the transmission contains > advice, the advice is based on instructions in relation to, and is provided > to the addressee in connection with, the matter mentioned above. > Responsibility is not accepted for reliance upon it by any other person or > for any other purpose. > > --To unsubscribe from spectrum, send email to [email protected] with the > body: unsubscribe spectrum [email protected] -- david t. klein Cisco Certified Network Associate (CSCO11281885) Linux Professional Institute Certification (LPI000165615) Redhat Certified Engineer (805009745938860) Quis custodiet ipsos custodes? --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
