1-- *****************************************************************
2-- CISCO-BBSM-MIB.my:  Cisco BBSM MIB file
3--
4-- April 3 2004, Ting Wu
5--
6-- Copyright (c) 2004 by cisco Systems, Inc.
7-- All rights reserved.
8--
9-- *****************************************************************
10
11
12CISCO-BBSM-MIB DEFINITIONS ::= BEGIN
13
14IMPORTS
15   NOTIFICATION-TYPE,
16   MODULE-IDENTITY,
17   OBJECT-TYPE,
18   Unsigned32
19      FROM SNMPv2-SMI
20   MODULE-COMPLIANCE,
21   OBJECT-GROUP,
22   NOTIFICATION-GROUP
23      FROM SNMPv2-CONF
24   DateAndTime
25      FROM SNMPv2-TC
26   SnmpAdminString
27      FROM SNMP-FRAMEWORK-MIB
28   ciscoMgmt
29      FROM CISCO-SMI;
30
31ciscoBbsmMIB MODULE-IDENTITY
32   LAST-UPDATED    "200404030000Z"
33   ORGANIZATION    "Cisco Systems, Inc."
34   CONTACT-INFO
35                "       Cisco Systems
36                        Customer Service
37
38                Postal: 170 W Tasman Drive
39                        San Jose, CA  95134
40                        USA
41
42                   Tel: +1 800 553-NETS
43
44                E-mail: cs-bbsm@cisco.com"
45   DESCRIPTION
46      "This mib is designed to send BBSM specific
47       notifications.  There are variables that contain detail data
48       that are bind to a notification. The SNMP Manager that
49       receives the notifications should look at the binding
50       variables for further details of the notification data.
51
52       BBSM stands for Building Broadband Service Manager.  It is a
53       software-based service platform that enables customers to
54       create, market, and operate broadband access services,
55       such as high-speed Internet access with plug-and-play,
56       multiple authentication and billing options and Web-based
57       management, reporting, and configuration."
58
59   REVISION        "200404030000Z"
60   DESCRIPTION
61       "Initial revision of this MIB module."
62   ::= { ciscoMgmt 358 }
63
64--object definitions
65ciscoBbsmNotifications OBJECT IDENTIFIER ::= { ciscoBbsmMIB 0 }
66ciscoBbsmMIBObjects OBJECT IDENTIFIER ::=  { ciscoBbsmMIB 1 }
67
68ciscoBbsmEventInfo OBJECT IDENTIFIER ::= { ciscoBbsmMIBObjects 1}
69
70cbbsmEventDescription OBJECT-TYPE
71       SYNTAX      OCTET STRING
72       MAX-ACCESS  accessible-for-notify
73       STATUS      current
74       DESCRIPTION
75          "The cbbsmEventDescription binds with notification.
76           It displays the description of an event that caused
77           a notification to be sent.
78
79           Examples of cbbsmEventDescription value would be
80           'Failed to connect to RADIUS server xx.yy.zz.aa' or
81           'Failed to connect to ICS server xx.yy.zz.aa'"
82       ::= { ciscoBbsmEventInfo 1 }
83
84cbbsmEventSource OBJECT-TYPE
85       SYNTAX      SnmpAdminString
86       MAX-ACCESS  accessible-for-notify
87       STATUS      current
88       DESCRIPTION
89          "The cbbsmEventSource binds with a notification. It displays
90           the source of an event that caused the notification to be
91           sent.  The cbbsmEventSource also binds with
92           cbbsmEventDescription.
93
94           Examples of cbbsmEventSource value would be
95           'BBSM_RADIUS' or
96           'BBSM_ICS' "
97       ::= { ciscoBbsmEventInfo 2 }
98
99cbbsmEventID OBJECT-TYPE
100       SYNTAX      Unsigned32
101       MAX-ACCESS  accessible-for-notify
102       STATUS      current
103       DESCRIPTION
104          "The cbbsmEventID binds with a notification. It displays
105           event ID of an event that caused the notification to be
106           sent. The cbbsmEventID also binds with
107           cbbsmEventDescription.
108
109           Examples of a cbbsmEventID would be 1, 2, ..."
110       ::= { ciscoBbsmEventInfo 3 }
111
112cbbsmEventType OBJECT-TYPE
113       SYNTAX      INTEGER
114           {   error       (1),
115               warning     (2),
116               information (3)
117           }
118       MAX-ACCESS  accessible-for-notify
119       STATUS      current
120       DESCRIPTION
121          "The cbbsmEventType binds with the notification. It displays
122           the event type of an event that caused notification to be
123           sent.  The cbbsmEventType also binds with
124           cbbsmEventDescription.
125
126           error(1) : An Error event indicates a significant problem,
127           such as loss of data or loss of functionality.
128
129           warning(2): A Warning event is not necessarily significant,
130           but may indicate a possible future problem.
131
132           information(3): An Information event describes the
133           successful operation of an application, driver, or service."
134       ::= { ciscoBbsmEventInfo 4 }
135
136cbbsmEventTime OBJECT-TYPE
137       SYNTAX      DateAndTime
138       MAX-ACCESS  accessible-for-notify
139       STATUS      current
140       DESCRIPTION
141          "The cbbsmEventTime binds with the notification. It is a
142           date and time string that displays the time of the event
143           that caused notification to be sent."
144       ::= { ciscoBbsmEventInfo 5 }
145
146-- notification definitions
147
148ciscoBbsmEvent NOTIFICATION-TYPE
149       OBJECTS  {cbbsmEventDescription,
150                  cbbsmEventSource,
151                  cbbsmEventID,
152                  cbbsmEventType,
153                  cbbsmEventTime
154                }
155       STATUS   current
156       DESCRIPTION
157          "Notification of a BBSM event.  The details of the
158           event is binded in variables listed.  These variables
159           are identical to the same event logged on the Microsoft
160           Event Viewer.
161
162           For example, if BBSM had problem connecting to RADIUS
163           server and SNMP Service on BBSM is configured to send
164           notifications, a notification of ciscoBbsmEvent will
165           be sent and binded variables will have following values
166           cbbsmEventDescription = 'Failed to connect to RADIUS server
167           xx.yy.zz.aa'
168           cbbsmEventSource = 'BBSM_RADIUS'
169           cbbsmEventID = '1'
170           cbbsmEventType = 2
171           "
172       ::= { ciscoBbsmNotifications 1 }
173
174-- conformance information
175
176ciscoBbsmMIBConformance OBJECT IDENTIFIER ::= { ciscoBbsmMIB 2 }
177
178ciscoBbsmMIBCompliances OBJECT IDENTIFIER
179       ::= { ciscoBbsmMIBConformance 1 }
180ciscoBbsmMIBGroups      OBJECT IDENTIFIER
181       ::= { ciscoBbsmMIBConformance 2 }
182
183-- Compliance
184ciscoBbsmMIBCompliance MODULE-COMPLIANCE
185        STATUS current
186        DESCRIPTION
187                "The compliance statement for entities which implement
188                the Cisco BBSM MIB"
189        MODULE        -- this module
190                MANDATORY-GROUPS { ciscoBbsmMIBGroup,
191                                   ciscoBbsmMIBNotificationGroup }
192        ::= { ciscoBbsmMIBCompliances 1 }
193
194-- Conformance
195ciscoBbsmMIBGroup OBJECT-GROUP
196        OBJECTS {
197            cbbsmEventDescription,
198            cbbsmEventSource,
199            cbbsmEventID,
200            cbbsmEventType,
201            cbbsmEventTime  }
202        STATUS current
203        DESCRIPTION
204                "A set of objects providing details of a event
205                to a Cisco agent."
206        ::= { ciscoBbsmMIBGroups 1 }
207
208ciscoBbsmMIBNotificationGroup NOTIFICATION-GROUP
209        NOTIFICATIONS { ciscoBbsmEvent }
210        STATUS  current
211        DESCRIPTION
212                "Set of notifications implemented in this module."
213        ::= { ciscoBbsmMIBGroups 2 }
214
215END
216