Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.
During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.
We apologize for the inconvenience while we perform important updates to the Community.
I have several WAAS units all WAE-512-K9 which are listed in RME device supported by Cisco Works, all running 4.1.X and above
How ever they have an OID:xx.9.1.760 where as Cisco Works only supports OID:xx.9.1.759 & 776. So the units are "unknown" in Ciscoworks. Are the Units that different.
Is there any way to update the OID to get the units fully supported by CiscoWorks to enable monitoring.
RME is 4.2.0
No, this device is not yet supported, and I do not have an ETA on when support will be available. I have, however, requested support get added.
What version of code is this device running? There is a question about whether this is an FE-512-K9 running WAFS code (which is EoL). The OE-512-K9 version should be supported now in RME.
Here is the info of the device any further info please let me know :
PID: WAE-512-K9 VID: 0 SN: KQZ6637
Cisco Wide Area Application Services Software (WAAS)
Copyright (c) 1999-2009 by Cisco Systems, Inc.
Cisco Wide Area Application Services Software Release 4.1.5b (build b7 Oct 27 2009)
Compiled 19:29:00 Oct 27 2009 by cnbuild
System was restarted on Sun Dec 13 14:52:41 2009.
The system has been up for 4 weeks, 1 day, 20 hours, 29 minutes, 23 seconds.
Just to provide you with some info here.
When we purchased our WAAS units, Cisco had just announced WAAS so we where right in the middle of WAFS and WAAS, going WAAS on the implementation and I have been maintaining it ever since.
Thought I would also add this snmpwalk of one of my units show the OID number, all units are the same.
SNMPv2-MIB::sysDescr.0 = STRING: Cisco Wide Area Application Services Software Hardware Version: fe512-4.1.5b.7
Cisco Wide Area Application Services Software Software Release 4.1.5b (build b7 Oct 27 2009)
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.760
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (275685900) 31 days, 21:47:39.00
SNMPv2-MIB::sysContact.0 = STRING: xxxxxxxxxxxxxxxxxxxxxxxxxxx
SNMPv2-MIB::sysName.0 = STRING: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
SNMPv2-MIB::sysLocation.0 = STRING: xxxxxxxxxxxxxxxxxxxxxx
SNMPv2-MIB::sysServices.0 = INTEGER: 72
IF-MIB::ifNumber.0 = INTEGER: 4
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifIndex.3 = INTEGER: 3
IF-MIB::ifIndex.4 = INTEGER: 4
IF-MIB::ifDescr.1 = STRING: GigabitEthernet2/0
IF-MIB::ifDescr.2 = STRING: GigabitEthernet1/0
IF-MIB::ifDescr.3 = STRING: Standby1
IF-MIB::ifDescr.4 = STRING: lo
IF-MIB::ifType.1 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.2 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.3 = INTEGER: other(1)
IF-MIB::ifType.4 = INTEGER: softwareLoopback(24)
IF-MIB::ifMtu.1 = INTEGER: 1500
IF-MIB::ifMtu.2 = INTEGER: 1500
IF-MIB::ifMtu.3 = INTEGER: 1500
IF-MIB::ifMtu.4 = INTEGER: 16436
IF-MIB::ifSpeed.1 = Gauge32: 1000000000
IF-MIB::ifSpeed.2 = Gauge32: 1000000000
IF-MIB::ifSpeed.3 = Gauge32: 0
IF-MIB::ifSpeed.4 = Gauge32: 0
Open a service request with TAC requesting WAAS help to change the sysObjectID. Have your engineer contact me directly, and I will put them in touch with a developer that can change the hardware cookie to get this WAE to advertise the OE-512 sysObjectID. That will make it manageable via RME.
Note: the procedure will require that you allow a WebEx session so the developer can access your device directly. Downtime will be involved.
Thanks for the reply, I only have one concern in that your reply implys that I have one unit, when in fact I have 7 units all with the same issue. As they where all brought at the same time.
The other issue will be getting time on each Server.
If the Developer is ok to plan the changes over a period, I will proceed.
Good news, you should be able to do this yourself using the WAAS recovery CD. See the steps under option 3 at http://www.cisco.com/en/US/partner/docs/app_ntwk_services/waas/waas/v413/configuration/guide/maint.html#wp1105207 .
Thanks for this, just fun bit now move a CD around the variuos Offices !
Just one question, there are two OID's for the 512, does it matter which one I use ?
9.1.759 or 9.1.776
One step forward and two back,
Just tried the process on my spare Unit with a 4.15c Recovery cd and got the following :
This is the rescue image. The purpose of this software is to let
you install a new system image onto your system's boot flash
device. This software has been invoked either manually
(if you entered `***' to the bootloader prompt) or has been
invoked by the bootloader if it discovered that your system image
in flash had been corrupted.
To download an image from network, this software will request
the following information from you:
- which network interface to use
- IP address and netmask for the selected interface
- default gateway IP address
- FTP server IP address
- username and password on FTP server
- path to system image on server
init: proc-proc.c:get_interface_list: unknown ethernet controller: 0x1374002c
rescue: PANIC, halting. Specific message: get_interface_list returned NULL
I suppose one option is try a different CD but which one, how far back do I need to go ?
Also this worry's me for future updates of the Core code, will my intrefaces be removed from the image !!
I can't say for certain what the problem here is (it could be that you have a bad disc or bad appliance). I am not that familiar with the WAE devices. However, here is a transcript of the developer performing the same steps to his WAE appliance. My understanding is that the only thing these steps should change is the hardware cookie. Other appliance attributes should not be affected.
Just to report back that all my issues are now resolved and I can move forward.
I have two units correctly registared to Ciscoworks, I can now do the others as when.
The OID became 776 on updating the Cookie.
Many thanks for all you help.