OID defination for the WCS ver7.0

Answered Question
Aug 5th, 2010

Hi, All,

I need to get the full OID defination for the SNMP Trap of WCS ver7.0  when it send traps to the configured notification receiver which I think should be included in Cisco-WCS-Notification-MIB, however I can't find it,  I have checked http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml and
ftp://ftp-sj.cisco.com/pub/mibs/oid/, however it is not there. In WCS v7 configuration guide, there's a table "Table 16-3Cisco-WCS-Notification-MIB to WCS Alert/Event Mapping ", however only name been put there, no really OID such as .1.3.6.1.4.1.9.9.199991.1.1.2.1.7.

Could anyone help on it? Thanks!

I have this problem too.
0 votes
Correct Answer by Rollin Kibbe about 6 years 5 months ago

Hi bbxie:

Unfortunately, the Object Navigator hasn't been updated yet with that MIB, but the lookup type answers you're looking for are in the text of the MIB file.  I'm surprised the OpenView engineer didn't know to look at it.

CwNotificationHistoryEntry ::= SEQUENCE {
    ::= { cwNotificationHistoryEntry 1 }
    ::= { cwNotificationHistoryEntry 2 }
    ::= { cwNotificationHistoryEntry 3 }
    ::= { cwNotificationHistoryEntry 4 }
    ::= { cwNotificationHistoryEntry 5 }
    ::= { cwNotificationHistoryEntry 6 }
    ::= { cwNotificationHistoryEntry 7 }
    ::= { cwNotificationHistoryEntry 8 }
    ::= { cwNotificationHistoryEntry 9 }
    ::= { cwNotificationHistoryEntry 10 }
    ::= { cwNotificationHistoryEntry 11 }
    ::= { cwNotificationHistoryEntry 12 }
    ::= { cwNotificationHistoryEntry 13 }
    ::= { cwNotificationHistoryEntry 14 }

CwNotificationHistoryEntry ::= SEQUENCE {
        cWNotificationIndex                    Unsigned32,
        cWNotificationTimestamp                DateAndTime,
        cWNotificationUpdatedTimestamp         DateAndTime,
        cWNotificationKey                      SnmpAdminString,
        cWNotificationCategory                 CWirelessNotificationCategory,
        cWNotificationSubCategory              OCTET STRING,
        cWNotificationManagedObjectAddressType InetAddressType,
        cWNotificationManagedObjectAddress     InetAddress,
        cWNotificationSourceDisplayName        OCTET STRING,
        cWNotificationDescription              OCTET STRING,
        cWNotificationSeverity                 CiscoAlarmSeverity,
        cWNotificationSpecialAttributes        OCTET STRING,
        cWNotificationType                     CWirelessNotificationType,
        cWNotificationVirtualDomains           OCTET STRING
}

That's the purpose in having the MIB file.

Sincerely,

Rollin Kibbe

Network Management Systems Team

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Rollin Kibbe Thu, 08/12/2010 - 06:52

Hi bbxie:

The name of the MIB is actually CISCO-WIRELESS-NOTIFICATION-MIB.my.  I checked the posted MIBS_7.0.zip file from the Wireless Software Center and this MIB isn't in there.  I'll address the zip file and the typo in the Configuration Guide internally, but in the meantime, here's CISCO-WIRELESS-NOTIFICATION-MIB.my attached.

Sincerely,

Rollin Kibbe

Network Management Systems Team

bbxie Thu, 08/12/2010 - 16:56

Hi Rollin,

Thanks for your help! However I not only need that MIB, but also want to know what exactly digits(for example .1.3.6.1.4.1.9.9.199991.1.1.2.1.2) means and how many kind of these digits will the notification receiver received, for example, we can use a MIB reader configured as a notification receiver, it received some notifications from WCS7 like following:

.1.3.6.1.2.1.1.3.0:  TimeTicks:  0 hours, 32 minutes, 38 seconds.:
.1.3.6.1.6.3.1.1.4.1.0:  Object ID:  .1.3.6.1.4.1.9.9.199991.0.1:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.2:  07 da 08 05 09 26 1d 02 2b 0a 00:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.3:  07 da 08 05 0e 33 0f 09 2b 0a 00:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.4:  OperStatus_LradIf!00: 3a: 98: bb: a1: 20!0:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.5:  INTEGER:  2:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.6:  Radio administratively up and operationally down:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.7:  INTEGER:  1:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.8:  IpAddress:  150.166.20.240:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.9:  AP TestLabAP-f01-lab, Interface 802.11b/g:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.10:  802.11b/g interface of AP TestLabAP-f01-lab is down:  Controller 150.166.20.240:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.11:  INTEGER:  3:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.12:  alertType=LRADIF_DOWN:
.1.3.6.1.4.1.9.9.199991.1.1.2.1.14:

What our NMS engineer want to know is the defination of  .1.3.6.1.4.1.9.9.199991.1.1.2.1.2/3/4/5..../14. and all the list of these OIDs(not name but the digits). I have tried to search those digits in Cisco's SNMP Object Navigator (http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?objectInput=.1.3.6.1.4.1.9.9.199991.1.1.2.1.2&translate=Translate&submitValue=SUBMIT), but the system told me following:

Unfortunately we could not translate the object 1.3.6.1.4.1.9.9.199991.1.1.2.1.2 you were looking for. We could however translate a part of your object. This is the partial translation:

So we want to know what does 199991 . 1 . 1 . 2 . 1 . 2 mean and how many kind of these OIDs the Notification Receiver can receive. Actually the customer has a Cisco WLAN environment which managed by WCS version 7, now they have a managed service to another company that all their network equiments(both wireless and wired) need to send notification to HP Openview which will be configured as notification receiver in WCS v7. The HP Openview engineer need us to provide all the OIDs that will be sent from WCS to HP Openview, we had done some testing by using another MIB Reader SW instead of HP Openview(we don't have Openview yet) and found it received the above listed notifications, so we need to prepare a document to include all those OIDs(.1.3.6.1.4.1.9.9.199991.1.1.2.1.2, etc) and send it to HP Openview engineer so he can do some customization based on the received OIDs.

Correct Answer
Rollin Kibbe Tue, 08/17/2010 - 08:21

Hi bbxie:

Unfortunately, the Object Navigator hasn't been updated yet with that MIB, but the lookup type answers you're looking for are in the text of the MIB file.  I'm surprised the OpenView engineer didn't know to look at it.

CwNotificationHistoryEntry ::= SEQUENCE {
    ::= { cwNotificationHistoryEntry 1 }
    ::= { cwNotificationHistoryEntry 2 }
    ::= { cwNotificationHistoryEntry 3 }
    ::= { cwNotificationHistoryEntry 4 }
    ::= { cwNotificationHistoryEntry 5 }
    ::= { cwNotificationHistoryEntry 6 }
    ::= { cwNotificationHistoryEntry 7 }
    ::= { cwNotificationHistoryEntry 8 }
    ::= { cwNotificationHistoryEntry 9 }
    ::= { cwNotificationHistoryEntry 10 }
    ::= { cwNotificationHistoryEntry 11 }
    ::= { cwNotificationHistoryEntry 12 }
    ::= { cwNotificationHistoryEntry 13 }
    ::= { cwNotificationHistoryEntry 14 }

CwNotificationHistoryEntry ::= SEQUENCE {
        cWNotificationIndex                    Unsigned32,
        cWNotificationTimestamp                DateAndTime,
        cWNotificationUpdatedTimestamp         DateAndTime,
        cWNotificationKey                      SnmpAdminString,
        cWNotificationCategory                 CWirelessNotificationCategory,
        cWNotificationSubCategory              OCTET STRING,
        cWNotificationManagedObjectAddressType InetAddressType,
        cWNotificationManagedObjectAddress     InetAddress,
        cWNotificationSourceDisplayName        OCTET STRING,
        cWNotificationDescription              OCTET STRING,
        cWNotificationSeverity                 CiscoAlarmSeverity,
        cWNotificationSpecialAttributes        OCTET STRING,
        cWNotificationType                     CWirelessNotificationType,
        cWNotificationVirtualDomains           OCTET STRING
}

That's the purpose in having the MIB file.

Sincerely,

Rollin Kibbe

Network Management Systems Team

bbxie Tue, 08/17/2010 - 17:03

Thanks Rollin, appreciate your help! I will forward this mesg to the HP Openview engineer.

Actions

This Discussion

 

 

Trending Topics - Security & Network