WAAS OID in Ciscoworks

Unanswered Question
Dec 29th, 2009

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


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Tue, 12/29/2009 - 13:24

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.

Joe Clarke Mon, 01/11/2010 - 22:49

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.

Ian Beck Tue, 01/12/2010 - 03:25

Hi Jo,

Here is the info of the device any further info please let me know :

UKHSL-WAAS01#sh inv

PID: WAE-512-K9 VID: 0 SN: KQZ6637
UKHSL-WAAS01#sh ver
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)
Version: fe512-4.1.5b.7

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.



Joe Clarke Tue, 01/12/2010 - 09:20

This code is certainly not EoL.  I'm rechecking with development for support.

Ian Beck Wed, 01/13/2010 - 04:12

Hi Jo,

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.


Ian Beck Thu, 01/14/2010 - 04:45

Hi Jo,

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

Joe Clarke Fri, 01/15/2010 - 14:02

Yeah, this appears to be a file engine running WAAS code which should be supportable.  I am still talking with development.

Joe Clarke Sat, 01/23/2010 - 17:34

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.

Ian Beck Tue, 01/26/2010 - 06:19

Hi Jo,

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.

Many thanks


Joe Clarke Tue, 01/26/2010 - 16:22

The developer seemed to indicate that he would help given one affected device.  I've asked if he can assist with the changing of seven.

Ian Beck Thu, 01/28/2010 - 04:09

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


Ian Beck Thu, 01/28/2010 - 06:38

Hi Jo,

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 !!


Joe Clarke Thu, 01/28/2010 - 07:57

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.

Ian Beck Fri, 01/29/2010 - 04:37

Hi Jo,

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.



This Discussion