2004-04-03
This mib is designed to send BBSM specific notifications. There are variables that contain detail data that are bind to a notification. The SNMP Manager that receives the notifications should look at the binding variables for further details of the notification data. BBSM stands for Building Broadband Service Manager. It is a software-based service platform that enables customers to create, market, and operate broadband access services, such as high-speed Internet access with plug-and-play, multiple authentication and billing options and Web-based management, reporting, and configuration.
Download CISCO-BBSM-MIB.txt Open CISCO-BBSM-MIB.txt in a new tab
| Name | OID |
|---|---|
| ciscoBbsmEvent | 1.3.6.1.4.1.9.9.358.0.1 |
END OF TOC
1.3.6.1.4.1.9.9.358.1.1.1
OCTET STRING
The cbbsmEventDescription binds with notification. It displays the description of an event that caused a notification to be sent. Examples of cbbsmEventDescription value would be 'Failed to connect to RADIUS server xx.yy.zz.aa' or 'Failed to connect to ICS server xx.yy.zz.aa'
1.3.6.1.4.1.9.9.358.1.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The cbbsmEventSource binds with a notification. It displays the source of an event that caused the notification to be sent. The cbbsmEventSource also binds with cbbsmEventDescription. Examples of cbbsmEventSource value would be 'BBSM_RADIUS' or 'BBSM_ICS'
1.3.6.1.4.1.9.9.358.1.1.3
Unsigned32
The cbbsmEventID binds with a notification. It displays event ID of an event that caused the notification to be sent. The cbbsmEventID also binds with cbbsmEventDescription. Examples of a cbbsmEventID would be 1, 2, ...
1.3.6.1.4.1.9.9.358.1.1.4
INTEGER1 = error2 = warning3 = information · Integer32
The cbbsmEventType binds with the notification. It displays the event type of an event that caused notification to be sent. The cbbsmEventType also binds with cbbsmEventDescription. error(1) : An Error event indicates a significant problem, such as loss of data or loss of functionality. warning(2): A Warning event is not necessarily significant, but may indicate a possible future problem. information(3): An Information event describes the successful operation of an application, driver, or service.
1.3.6.1.4.1.9.9.358.1.1.5
DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The cbbsmEventTime binds with the notification. It is a date and time string that displays the time of the event that caused notification to be sent.
1.3.6.1.4.1.9.9.358.0.1
Notification of a BBSM event. The details of the event is binded in variables listed. These variables are identical to the same event logged on the Microsoft Event Viewer. For example, if BBSM had problem connecting to RADIUS server and SNMP Service on BBSM is configured to send notifications, a notification of ciscoBbsmEvent will be sent and binded variables will have following values cbbsmEventDescription = 'Failed to connect to RADIUS server xx.yy.zz.aa' cbbsmEventSource = 'BBSM_RADIUS' cbbsmEventID = '1' cbbsmEventType = 2
1.3.6.1.4.1.9.9.358.1.1.1
OCTET STRING
The cbbsmEventDescription binds with notification. It displays the description of an event that caused a notification to be sent. Examples of cbbsmEventDescription value would be 'Failed to connect to RADIUS server xx.yy.zz.aa' or 'Failed to connect to ICS server xx.yy.zz.aa'
1.3.6.1.4.1.9.9.358.1.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The cbbsmEventSource binds with a notification. It displays the source of an event that caused the notification to be sent. The cbbsmEventSource also binds with cbbsmEventDescription. Examples of cbbsmEventSource value would be 'BBSM_RADIUS' or 'BBSM_ICS'
1.3.6.1.4.1.9.9.358.1.1.3
Unsigned32
The cbbsmEventID binds with a notification. It displays event ID of an event that caused the notification to be sent. The cbbsmEventID also binds with cbbsmEventDescription. Examples of a cbbsmEventID would be 1, 2, ...
1.3.6.1.4.1.9.9.358.1.1.4
INTEGER1 = error2 = warning3 = information · Integer32
The cbbsmEventType binds with the notification. It displays the event type of an event that caused notification to be sent. The cbbsmEventType also binds with cbbsmEventDescription. error(1) : An Error event indicates a significant problem, such as loss of data or loss of functionality. warning(2): A Warning event is not necessarily significant, but may indicate a possible future problem. information(3): An Information event describes the successful operation of an application, driver, or service.
1.3.6.1.4.1.9.9.358.1.1.5
DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The cbbsmEventTime binds with the notification. It is a date and time string that displays the time of the event that caused notification to be sent.