CISCO-ENTITY-VENDORTYPE-OID-MIB missed OID
Hi,
We use CISCO-ENTITY-VENDORTYPE-OID-MIB in our HW Inventory application and I found, that there are missing one OID in this MIB.
It is "cevContainerC7200CCPA" "1.3.6.1.4.1.9.12.3.1.5.172". I can find it via SNMP object navigator, but when I look at MIB file, that there are only .171 and .173 OIDs and .172 is missing.
Do you have idea if it is broken MIB file or it is my fault?
Thank you very much.
Pavel
Seems like there is an older version of the MIB posted. Thanks for poitning it out. I have alerted the downstream teams to poke at it. Thanks to Joe Clarke for chasing them down.
Similar Messages
-
This is frustrating... trying to import CISCO-ENTITY-SENSOR-MIB
Well, really trying to import CISCO-ENTITY-SENSOR-EXT-MIB in order to process traps from ASA with "snmp-server enable traps entity power-supply-failure" configured. Figures that CISCO-ENTITY-SENSOR-MIB is a prerequisite. After painstakingly loading up the MIB dependencies listed at http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-ENTITY-SENSOR-MIB, it fails at the last juncture with
CISCO-ENTITY-SENSOR-MIB itself:
snmpttconvertmib --in=CISCO-ENTITY-SENSOR-MIB.my --out=/etc/snmp/snmptt.conf.cisco --debug
***** Processing MIB file *****
snmptranslate version: NET-SNMP version: 5.3.1
severity: Normal
File to load is: ./CISCO-ENTITY-SENSOR-MIB.my
File to APPEND TO: /etc/snmp/snmptt.conf.cisco
MIBS environment var: ./CISCO-ENTITY-SENSOR-MIB.my
mib name: CISCO-ENTITY-SENSOR-MIB
Processing MIB: CISCO-ENTITY-SENSOR-MIB
skipping a TRAP-TYPE / NOTIFICATION-TYPE line - probably an import line.
Line: 631
NOTIFICATION-TYPE: entSensorThresholdNotification
Variables: entSensorThresholdValue entSensorValue
Enterprise: entitySensorMIBNotifications
Looking up via snmptranslate: CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotification
No log handling enabled - turning on stderr logging
Cannot find module (ENTITY-MIB): At line 27 in ./CISCO-ENTITY-SENSOR-MIB.my
Cannot find module (CISCO-TC): At line 29 in ./CISCO-ENTITY-SENSOR-MIB.my
Cannot find module (CISCO-SMI): At line 31 in ./CISCO-ENTITY-SENSOR-MIB.my
Did not find 'entPhysicalIndex' in module #-1 (./CISCO-ENTITY-SENSOR-MIB.my)
Did not find 'EntPhysicalIndexOrZero' in module #-1 (./CISCO-ENTITY-SENSOR-MIB.my)
Did not find 'ciscoMgmt' in module #-1 (./CISCO-ENTITY-SENSOR-MIB.my)
Unlinked OID in CISCO-ENTITY-SENSOR-MIB: ciscoEntitySensorMIB ::= { ciscoMgmt 91 }
Undefined identifier: ciscoMgmt near line 33 of ./CISCO-ENTITY-SENSOR-MIB.my
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBConformance ::= { ciscoEntitySensorMIB 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBNotificationPrefix ::= { ciscoEntitySensorMIB 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBObjects ::= { ciscoEntitySensorMIB 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBNotifications ::= { entitySensorMIBNotificationPrefix 0 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValueEntry ::= { entSensorValueTable 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorNotifCtrlGlobalGroup ::= { entitySensorMIBGroups 5 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorValueGroupSup1 ::= { entitySensorMIBGroups 4 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorThresholdNotificationGroup ::= { entitySensorMIBGroups 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorThresholdGroup ::= { entitySensorMIBGroups 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorValueGroup ::= { entitySensorMIBGroups 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdTable ::= { entSensorThresholds 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorMeasuredEntity ::= { entSensorValueEntry 8 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValueUpdateRate ::= { entSensorValueEntry 7 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValueTimeStamp ::= { entSensorValueEntry 6 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorStatus ::= { entSensorValueEntry 5 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValue ::= { entSensorValueEntry 4 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorPrecision ::= { entSensorValueEntry 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorScale ::= { entSensorValueEntry 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorType ::= { entSensorValueEntry 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdEntry ::= { entSensorThresholdTable 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThreshNotifGlobalEnable ::= { entSensorGlobalObjects 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: ciscoEntitySensorMIB ::= { ciscoMgmt 91 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorGlobalObjects ::= { entitySensorMIBObjects 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholds ::= { entitySensorMIBObjects 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValues ::= { entitySensorMIBObjects 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdNotificationEnable ::= { entSensorThresholdEntry 6 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdEvaluation ::= { entSensorThresholdEntry 5 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdValue ::= { entSensorThresholdEntry 4 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdRelation ::= { entSensorThresholdEntry 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdSeverity ::= { entSensorThresholdEntry 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdIndex ::= { entSensorThresholdEntry 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorThresholdNotification ::= { entitySensorMIBNotifications 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entSensorValueTable ::= { entSensorValues 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBGroups ::= { entitySensorMIBConformance 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBCompliances ::= { entitySensorMIBConformance 1 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBComplianceV04 ::= { entitySensorMIBCompliances 4 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBComplianceV03 ::= { entitySensorMIBCompliances 3 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBComplianceV02 ::= { entitySensorMIBCompliances 2 }
Cannot adopt OID in CISCO-ENTITY-SENSOR-MIB: entitySensorMIBComplianceV01 ::= { entitySensorMIBCompliances 1 }
Unknown object identifier: CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotification
OID:
Done
Total translations: 1
Successful translations: 0
Failed translations: 1
Those three allegedly missing MIBs are right there in the same directory, and have been imported earlier (though some had no "translation"):
ls
CISCO-ENTITY-SENSOR-EXT-MIB.my CISCO-TC.my RFC-1212.my SNMPv2-CONF.my SNMPv2-TC-V1SMI.my
CISCO-ENTITY-SENSOR-MIB.my ENTITY-MIB.my RFC-1215.my SNMPv2-SMI.my v1
CISCO-SMI.my RFC1155-SMI.my SNMP-FRAMEWORK-MIB.my SNMPv2-TC.my
snmpttconvertmib --in=CISCO-SMI.my --out=/etc/snmp/snmptt.conf.cisco --debug
***** Processing MIB file *****
snmptranslate version: NET-SNMP version: 5.3.1
severity: Normal
File to load is: ./CISCO-SMI.my
File to APPEND TO: /etc/snmp/snmptt.conf.cisco
MIBS environment var: ./CISCO-SMI.my
mib name: CISCO-SMI
Processing MIB: CISCO-SMI
Done
Total translations: 0
Successful translations: 0
Failed translations: 0
snmpttconvertmib --in=CISCO-TC.my --out=/etc/snmp/snmptt.conf.cisco --debug
***** Processing MIB file *****
snmptranslate version: NET-SNMP version: 5.3.1
severity: Normal
File to load is: ./CISCO-TC.my
File to APPEND TO: /etc/snmp/snmptt.conf.cisco
MIBS environment var: ./CISCO-TC.my
mib name: CISCO-TC
Processing MIB: CISCO-TC
Done
Total translations: 0
Successful translations: 0
Failed translations: 0
snmpttconvertmib --in=ENTITY-MIB.my --out=/etc/snmp/snmptt.conf.cisco --debug
***** Processing MIB file *****
snmptranslate version: NET-SNMP version: 5.3.1
severity: Normal
File to load is: ./ENTITY-MIB.my
File to APPEND TO: /etc/snmp/snmptt.conf.cisco
MIBS environment var: ./ENTITY-MIB.my
mib name: ENTITY-MIB
Processing MIB: ENTITY-MIB
skipping a TRAP-TYPE / NOTIFICATION-TYPE line - probably an import line.
Line: 1142
NOTIFICATION-TYPE: entConfigChange
Enterprise: entityMIBTrapPrefix
Looking up via snmptranslate: ENTITY-MIB::entConfigChange
OID: .1.3.6.1.2.1.47.2.0.1
Done
Total translations: 1
Successful translations: 1
Failed translations: 0
What am I missing?I've successfully tried to stay clear of this type of thing as much as I could so my response might be silly.
But one of the things I recall was that a 'somemib.my' file needed 'thatothermib', that was actually there in the directory as 'thatothermib.my', just like I downloaded it, but the mibcompiler was smart enough to look for 'thatothermib.mib'.
Not sure if is was referenced in the other mibfile with a specific extension of if it was the compiler trying to stop me.
Never understood how they managed to make something so simple so complicated.
Cheers,
Michel -
Need the Cisco ASA5520 SYS OID for the LLDP protocol
Hi :
I need the Cisco ASA5520 SYS OID for the LLDP protocol so that I can create the network connection between Cisco ASA5520 and the 3rd party networking device in this 3rd party network management management system.
Can anyone help on this?
I tried to search the web and got some LLDP MIB files but they all cannot solve the problem. What I think and I need to have now is the SYS OID number for this Cisco ASA5520.
I know that the SYS OID for ASA5520 is 1.3.6.1.4.1.9.1.670. Now I need is the SYS OID for its LLDP protocol. Can someone help on this?
Many thanks!
tangsuanHi Afroj Ahmad:
I think it is not due with command line. It is the lack of OID information for Cisco ASA5520 to be able discovered by 3rd party Network Management System.
If I am not wrong, the ASA5520 should have been configured correctly for providing SNMP to the 3rd party network management system (NMS) and as such, the NMS is then able to capture the the SYS OID for ASA5520 is 1.3.6.1.4.1.9.1.670 from the ASA5520.
The SNMP configuration is as below:
snmp-server host inside 172.16.0.82 community public version 2c
snmp-server host inside 172.16.8.50 community public version 2c
no snmp-server location
no snmp-server contact
snmp-server community public
snmp-server enable traps snmp authentication linkup linkdown coldstart
snmp-server enable traps syslog
snmp-server enable traps ipsec start stop
snmp-server enable traps entity config-change fru-insert fru-remove
snmp-server enable traps remote-access session-threshold-exceeded
The 3rd party NMS can capture the product OID from ASA5520 after given the ASA IP address to the NMS. It is the LLDP OID that is not included in the product OID to cause the 3rd NMS cannot link up the LAN connction between the ASA and the 3rd party switch. There is no LLDP configuration in ASA command. I believe the LLDP should be provide externally either by key in manually or upload the MIB file to the 3rd party NMS. I have tried also uploading few MIB files but all not succesfully done.
I think the direct method is just key in the LLDP OID inside the 3rd party NMS system so that the 3rd NMS can embed the LLDP information into its operation kernel then the NMS can link up the LAN connection between the Cisco ASA and its switch.
Many thanks!
tangsuan -
Does the Catalyst 2960x-48TD support Cisco's IGMP Snooping MIB?
Does the Catalyst 2960x-48TD support Cisco's IGMP Snooping MIB? We have a number of switches from different vendors and have recently begun switching to Cisco's, however unlike the other brands I am unable to audit the IGMP Snooping settings via SNMP. It appears that while the switch supports IGMP Snooping it does not support the CISCO MIB for IGMP Snooping. Is this a known bug and is it fixed in any of the later releases?
Our company is purchasing and deploying C2960X-48TD's and I am tasked with updating our system audit softwareHi Sean,
Nov 21 15:40:42.390: %MCAST-SPSTBY-6-ETRACK_STATS_LIMIT_EXCEEDED: Number of entries in IGMP snooping explicit-tracking statistics has exceeded the maximum limit (32000)
The above log message is written because the number of explicit-tracking statistics entries is bounded to avoid monopolizing of system resources by IGMP/MLD snooping. The explicit-tracking statistics database maximum size is set to the same as that of explicit-tracking limit.
The statistics are split into two banks: permanent and volatile. The statistics entries will be stored permanently (volatile) until the permanent entries threshold is reached, after which the statistics will be stored temporarily up to the database maximum size. When the size of the database exceeds the permanent threshold, a group will be removed on receiving an IGMP/MLD leave. Groups can be removed whether they were installed above or below the permanent threshold. If the number of statistics entries grows beyond the maximum size of the database, then no statistics will be stored for any newly formed groups.
You can disable ip igmp snooping explicit-tracking by the following
1) Configure "no ip igmp snooping explicit-tracking"
2) Configure "ip igmp snooping limit track 0" on global.
3) After ET is disabled, please do a "clear ip igmp snooping statistics".
Here is a reference URL (please make sure you copy and paste the entire link to the browser):
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/snooigmp.html#wp1062242
HTH
Luke -
CISCO-UNIFIED-COMPUTING-TC-MIB won't compile
Hello,
I'm trying to monitor my UCS C260 using SNMP traps sent to HP SIM. In order do import the Cisco MIBs into SIM, you compile a .cfg file. One of the MIBs, CISCO-UNIFIED-COMPUTING-TC-MIB, will not compile. When running the mcompile command, I get the following error message:
C:\Program Files\HP\Systems Insight Manager\mibs>mcompile CISCO-UNIFIED-COMPUTING-tc-MIB.mib
HP Systems Insight Manager Mib Compiler, Version 5.0.2.1
Copyright (c) 2003-2006 Hewlett Packard Corporation
Compiling CISCO-UNIFIED-COMPUTING-tc-MIB.mib
Line: 128: Error defining object: expected a label, found reserved symbol {
Mib compilation failed.
All of the other MIBs compile just fine and I don't see anything wrong with the MIB I downloaded from Cisco.
Any idea what might be going on here?
Attached is the MIB as well.Chaps, i had the same issue, spoke with the chaps from Castle Rock and they confirmed this was due to bad coding within the MIB file.
I have succesfully compiled the version kindly amended by castlerock, they were quick to resolve this, their explanation as to the problem as below:
The problems with the MIB were that they are trying to enumerate the values with gauge and counter types. Only INTEGER/Integer32 types may have enumerated values (RFC2578, 7.1.1). There isn't a 64 bit integer type so they can't enumerate the Counter64 bit values. There were also problems trying to enumerate a textual-convention type (snmpAdminString) which is wrong in two ways - you can't enumerate a string value, and you can't nest a textual convention macro as a syntax in another (RFC1903, 3.5).
Please find the version i used attached.
Please feed back to the forum if this resolves the issue for your type of platform.....
Cheers
Barry -
I have load CISCO-ENVMON-MIB and initiate walk in it but unable to find OID of Cisco 2960 temperature monitor..
I have search over net and found .1.3.6.1.4.1.9.9.13.1.3.1.3.1 for temperature but this OID is not responding in this mib.
Regards,
Arshad AhmedHi,
What is the version of IOS you are using? What is your SNMP config?
Here is an example output:
snmpwalk -v2c -c public 10.12.12.12 .1.3.6.1.4.1.9.9.13
SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.1 = STRING: "chassis"
SNMPv2-SMI::enterprises.9.9.13.1.3.1.6.1 = INTEGER: 5
SNMPv2-SMI::enterprises.9.9.13.1.4.1.2.1 = STRING: "chassis"
SNMPv2-SMI::enterprises.9.9.13.1.4.1.3.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1 = STRING: "internal power supply"
SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.13.1.6.0 = Hex-STRING: 00
SNMPv2-SMI::enterprises.9.9.13.2.1.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.13.2.3.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.13.2.4.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.13.2.5.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.13.2.6.0 = INTEGER: 2
To verify that the MIB exists in your image please navigate to:
http://tools.cisco.com/Support/SNMP/do/MIBSupport.do?local=en&step=3
Once there, issue a 'sh ver' on your device and copy and paste the entire name into the tool.
Thanks -
image :c7600rsp72043-ipservicesk9-mz.122-33.SRE2.bin
i want monitor cisco 7606 information .but i only found some mib from cisco site .
i want to oid for cisco 7606-s so that i can monitor cpu memory and temperature.
thanks!Hi Winm,
http://tools.cisco.com/ITDIT/MIBS/MainServlet?IMAGE_NAME=c7600rsp72043-ipservicesk9-mz.122-33.SRE2.bin
...show you which OIDs are supported by your software version.
Try the following:
CPU under:
OLD-CISCO-CPU-MID
eg: 1.3.6.1.4.1.9.2.1.58
Memory under :
CISCO-MEMORY-POOL-MIB
eg: 1.3.6.1.4.1.9.9.48
Temperature:
CISCO-ENVMON-MIB
eg: 1.3.6.1.4.1.9.9.13.1.3.1.3
cheers,
Seb. -
Cisco 3650 supports OID "1.0.8802.1.1.2.1.4.1"
Hello All
I would like to know that the Cisco 3650 series switch supported the OID "1.0.8802.1.1.2.1.4.1" ?
Thanks in advance .
VelavanThere is one metalink note 403522.1 which talks about migrating from 32 bit to 64 bit on 10g but it is meant for 10gR2. So I am not very sure if this is applicable from 10gR1 as well.
If you have your 64 bit server ready, you could install 10.2.0.4 64 bit on that and try the steps from this note. -
Cisco ASA SNMP OIDs (show name, show vpn-sessiondb l2l)
Hi all,
I am trying to figure out the SNMP OIDs that is equivalent to the following ASA commands:
show name
show vpn-sessiondb l2l
Thanks!im looking for the solution ? did u ever find out if this was possible?
-
Dear All,
I know this might have discussed here million times.. but still i am behind this to get this done due to BU pressure to do the capacity management.
I am trying to get the following using SNMP
1) Real Server
2) Real Server Current Connection
3) Real Server IP address
I tried it with following MIBs and OIDs
CISCO-SLB-MIB
slbRealServerFarmName .1.3.6.1.4.1.9.9.161.1.3.1.1.1
slbRealIpAddress .1.3.6.1.4.1.9.9.161.1.3.1.1.2
slbRealNumberOfConnections .1.3.6.1.4.1.9.9.161.1.3.1.1.5
CISCO-ENHANCED-SLB-MIB
cesRserverName .1.3.6.1.4.1.9.9.470.1.1.1.1.1
cesRserverIpAddress .1.3.6.1.4.1.9.9.470.1.1.1.1.4
cesRserverCurrConns .1.3.6.1.4.1.9.9.470.1.1.1.1.19
Either of these MIBs /OIDs return any value.
When i raise a TAC case i got the information saying these cannot be retrieved.
Is there any way i can get these values from ACE MODULE , because this is very much required for the BU and they are behind us since long time.
Apppreciate support from all.
thanks,
ParveesHi Parvees,
I wasn't looking for values you're interested in, but everything you can get with show command you can get via HTTP(s) request in XML using .
For example, here's a "sh serverfarm ServerFarm1" query:
$ curl --user USER:PASSWD -d "xml_cmd=CONTEXT\">xml-show on%0A show serverfarm ServerFarm1" http://ACE_IP_ADDRESS/bin/xml_agent
I'm running curl on linux box, but I think it is available on other platforms. The code above is a one-line command, but you can write scripts/lists of commands and send them to your ACE with curl.
Here's a link provided in a neighbour discussion that gives more information: https://supportforums.cisco.com/docs/DOC-17849
Hope this help,
Alex -
Cisco IP SLA - RTTMON MIB - Problem setting values
Hi,
I am trying to use Cisco IP SLA to monitor QOS for voice data. I want to create a SLA operation from my NMS. I am using the RTTMON-MIB for this purpose. I was testing it out by creating an ICMP Echo operation, and I set the below values
rttMonCtrlAdminRttType.1 -Integer 9
rttMonEchoAdminProtocol.1 -Integer 27
rttMonEchoAdminTargetAddress.1 -OctetString "172.22.202.12"
rttMonEchoAdminTargetPort.1 -Integer 8000
rttMonEchoAdminInterval.1 -Integer 20
rttMonEchoAdminNumPackets.1 -Integer 100
rttMonCtrlAdminStatus.1 -Integer 4
rttMonScheduleAdminRttStartTime.1 -TimeTicks 1
rttMonScheduleAdminRttLife.1 -Integer 2147483647
I have set these values for an INDEX 1, using snmpset_requests. Can anyone tell me as to how do I go about with the indexing. I just chose 1 for the above eg and set the values. But I see the rttMonCtrlAdminIndex oid has not been updated with the new entry. Neither am I able to set the value of index as 1 for this oid using snmpset.
Can anyone please tell me how the indexing is done? Should I set the value of the index?
The other question is the format for the target ipadress? This OID accepts IP address as an Octet String. So '172.22.202.24' is ok? or should I convert it into some other format.
Regards
RoyceyThe admin index is a random number which you must generate. It can be between 1 and 2147483647. Use your management station's pseudo-random number generator to pick an initial value. Then test it by polling rttMonCtrlAdminStatus for that index. If a row exists, pick a new index.
Yes, the IP address is of type OCTET STRING. You are setting it correctly. -
How to load a boot image to cisco aironet 1140 series after missing boot image
Hi all,
I need a solution for this. When i switch my cisco aironet 1140 , it s blinking with red light .and gives a message "no boot image to load".
When i tried next time, by pressing escape it shows this message that i have mentioned below.
ap:
ap:
using eeprom values
WRDTR,CLKTR: 0x83000800 0x40000000
RQDC ,RFDC : 0x80000035 0x00000208
using ÿÿÿÿ ddr static values from serial eeprom
ddr init done
Running Normal Memtest...
Passed.
IOS Bootloader - Starting system.
FLASH CHIP: Numonyx P33
Checking for Over Erased blocks
Xmodem file system is available.
DDR values used from system serial eeprom.
WRDTR,CLKTR: 0x83000800, 0x40000000
RQDC, RFDC : 0x80000035, 0x00000208
PCIE0: link is up.
PCIE0: VC0 is active
PCIE1: link is NOT up.
PCIE1 port 1 not initialized
PCIEx: initialization done
flashfs[0]: 1 files, 1 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 32385024
flashfs[0]: Bytes used: 1536
flashfs[0]: Bytes available: 32383488
flashfs[0]: flashfs fsck took 16 seconds.
Reading cookie from system serial eeprom...Done
Base Ethernet MAC address: 28:94:0f:d6:c8:62
Ethernet speed is 100 Mb - FULL duplex
The system is unable to boot automatically because there
are no bootable files.
C1140 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Compiled Tue 18-Oct-11 14:51 by prod_rel_team
ap:
So , now my question is how to load the boot image ? From where will we get this ? OR
I m also having another Cisco aironet 1140 , Can i get bootimage from that . Kindly let me know the solution from genius ?Take a look at this link as it should have the info you need
https://supportforums.cisco.com/docs/DOC-14636
Sent from Cisco Technical Support iPhone App -
Cisco Works Enable username credential missing
I have tried to deploy a configuration out as well as running a Device Credential Verification Job and they both fail because of "Enable username credential missing." I can not seem to pin point the problems because there is no place to add this, also our switches do not asking for a username while going into enable mode. Would TACACS+ have anything to do with this?
Apologies for resurrecting this old thread... I have found myself in a similar situation. And I have run a wireshark capture to review the entire telnet session. Obviously I am using generic passwords here, but this what I get when I follow the TCP stream. And yes, I did indicate that this is an IOS device, not CatOS (which is why I'm confused about that "set" command).
Username: ciscoworks
Password: sample_password
Switch6513>
Switch6513>
Switch6513>
Switch6513>
Switch6513>_tune_
Switch6513>
Switch6513> set length 0
Switch6513>
Switch6513>
Switch6513> enable
Password: sample_password
Switch6513#
Switch6513#
Switch6513#
Switch6513# _tune_
Switch6513#
Switch6513#
Switch6513# _tune_
Switch6513#
Switch6513#
Switch6513# enable
Switch6513#
Switch6513#
Switch6513# _tune_
Switch6513#
Switch6513#
And Ciscoworks still reports "Enable username credential missing" even though the switch is obviously in enabled state.
Needless to say I'm trying to push the upgrade to NCS, but it's kinda difficult when the existing installed software isn't working as advertised. -
Finding interface media type and transceiver type via SNMP
I need to find out, with SNMP, what media type (RJ45, FO) and transceivers (SFP, XenPak ...) do ports on my Catalysts 6500's use. What MIB should I look at? I tried to find this info by browsing MIBs with SNMP Object Navigator, but no luck so far.
Hi ,
for media type use this:
Object cevcSIMatchCriteriaType OID 1.3.6.1.4.1.9.9.613.1.4.6.1.4
Object portType OID 1.3.6.1.4.1.9.5.1.4.1.1.5
for transceiver :
CISCO-ENTITY-VENDORTYPE-OID-MIB::cevSensorTransceiverTemp
CISCO-ENTITY-VENDORTYPE-OID-MIB::cevSensorTransceiverVoltage
CISCO-ENTITY-VENDORTYPE-OID-MIB::cevSensorTransceiverCurrent
hope it will help
Thanks-
Afroz
***Ratings Encourages Contributors *** -
"Missing" MIBs on Nexus platform ??
Attempting to leverage SNMP to monitor some Nexus switches. Running into problems...
Looking at Cisco-Entity-FRU-Control MIB, (tree starts at .1.3.6.1.4.1.9.9.117)
I browsed the Nexus switch looking at the root and it failed. It goes from .....109.x to ....118.x skipping over .117 in the MIB.
Entity Sensor is suppose to be at .1.3.6.1.4.9.9.91.x, the Nexus goes from .....82.x to .....106.x
Cisco-entity-ext-mib is at .195, again not seeing this on the Nexus
The documentation says it is supported, but I can not find the specific OIDs on the device.
Anyone else experiencing the same issue ?? Are the OIDs different than those documented ?? Does something have to be enabled on the switch to see these OIDs ?? Is licensing required ?
Any help is greatly appreciated.
- B. Taylor
P.S. Posting on CSC as I am not getting anywhere with Cisco support... Being told that they "should be there", but they are not.
AAAAAAAaaaaaaahhhhhhh !! (sorry I am done now)Here is what I am seeing.
Multiple queries using show snmp traps, snmpwalk remotely confirm the presence of some entity MIBS in the 5020.
Only these for entity:
# sh snmp tr | inc ntity
Trap type Enabled
entity : entity_mib_change Yes
entity : entity_module_status_change Yes
entity : entity_power_status_change Yes
entity : entity_module_inserted Yes
entity : entity_module_removed Yes
entity : entity_unrecognised_module Yes
entity : entity_fan_status_change Yes
Similar for the 5548, 7010.
Commands used from linux of the form: snmpwalk -Ofn -v 2c snmpstring_pwd 192.168.0.1 | grep 1.3.6.1.4.1.9.9.91
It does not appear to be a Feature which is not on. It does appear to have the MIB not the Cisco temperature extensions. It is unclear if a temperature sensor is in the Cisco 5020 or 5548.
Temperature sensor health monitoring diagnostics are referenced for the 5548 here with very little detail:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/system_management/502_n1_1/Cisco_n5k_system_mgmt_cg_rel_502_n1_1.pdf
Show environment does give temperature information, so it could be scripted to be retrieved, however SNMP is more desirable. It's unclear if NX-OS upgrade would resolve this.
I tend to believe these MIBs are in the device or some of them, perhaps not in others. Perhaps a TAC case on the board will yeild one where the MIBs are able to be queried by snmpwalk...
Anyone who can provide insight would be welcome.
Maybe you are looking for
-
While streaming music from my i-phone 4s, it stops working after 2 miutes and so does music from my i-tunes after about two songs, very frustrating! Have tried allsorts!!!
-
Hi all, we are having two systems, in which we are trying to send Idoc from one system to another. Now, we created a Vendor Invoice in system1. We are getting successful creation of Idoc Message as well as stated below: "Idoc '0000000083307310' was c
-
I was told G4 Tower was slower than G3 mini tower?
Hi all, I was told that the G4 tower was slower than the G3 mini tower. Isn't 400mhz vs the 266mhz suppose to be faster? Or is this not a true factor? Let me know. Thanks for your help Web dude.
-
TS3988 How to cancel iCloud storage upgrade within 15 days
Misunderstood the whole storage thing, and want to cancel.
-
I have a problem, i want to use a extend to arraylist to implement different validation to objects. So i added a method add(Person person), dynamic binding, but it has a incorrect behavior, i think import java.util.ArrayList; import java.util.Collect