QBSYS-SYSTEM-MIB: View SNMP OID List / Download MIB

This module defines objects for the management of Quantum Bridge devices.

The current date and time of the system. Note that this can also be used to set and reset the current date and time.

The current operational status of the Quantum Bridge IOAS System as a whole. A value 'unknown(1)' indicates that the current state of the system could not be determined. The value 'running(2)' indicates that the system is up and running and that no unusual error conditions have been detected. The 'warning(3)' state indicates that the agent has been informed of an unusual error condition by the operational software (e.g., a device driver) but that the system is still 'operational'. (The qbSysBootDiagsCode object may provide more information.) A value of 'testing(4)', indicates that the system is not available for use because it is in the testing state. Enumeration: 'unknown': 1, 'running': 2, 'warning': 3, 'testing': 4.

This is the 'software reset button' of the agent. When read, this object always returns the value 'ready(1)'. When set to 'reset(2)', the system will reset and reload its configuration from FLASH/NVRAM. Note that when this object is set, the object qbSysResetVersion will be used to get the software version to be booted from. Enumeration: 'ready': 1, 'reset': 2.

An error code giving more details about a boot diagnostics failure indicated by qbSysOperStatus 'warning(1)' or 'down(2)'. The value 0 indicates no failure detected.

The number of seconds between watchdog timer updates. A watch dog reset will occur if the timer is not updated within one cycle. A value of 0 disables the watchdog timeout. The valid range of a functioning update is 1-60 seconds.

The running image version.

The type of power supply. Enumeration: 'internal': 1, 'external': 2.

The object allows to set the ACO (alarm cut off) function. When is set to clear(2) will turn off the ACO LED and supress visible alarms.Functionally it is equivalent to pushing the ACO button. Any new alarm causes the ACO button LED to illuminate. When read, this object always returns the value 'on(1)' Enumeration: 'on': 1, 'clear': 2.

The object enables or disables alarms at the CLI (when a user logged in). If on, autonomous alarms will display at CLI. If off, they will not be displayed. Enumeration: 'on': 1, 'off': 2.

A list of discrete inputs entries. This table contains information specifying discrete inputs that are configured for this system. Each entry in the table with a status of 'active' identifies a discrete input that is currently enabled.

Information about a single Discrete Entry.

The user defined type of the discrete input.

The user defined discrete input name.

The value determines the desired administrative status of a discrete input. If enabled, the The enabled and disabled states indicate that the discrete-input is enabled or disabled respectively. The unknown state indicates that the discrete input was not configured. Enumeration: 'disabled': 3, 'unknown': 1, 'enabled': 2.

The value determines the operational status of a discrete input. The on and off states indicate that the discrete-input is enabled or disabled respectively. The unknown state indicates that the discrete input was not configured. Enumeration: 'unknown': 1, 'off': 3, 'on': 2.

The revision number of the SNMP agent implementation. The first two bytes indicate major revision number, the second two bytes indicate the minor revision number

Active IP Address for SNMP Management of this chassis. This is the IP address used for network mangement.

This is the IP network mask associated with the Management interface.

This is a machine, connected to the same subnet as the sysctl management interface, which is capable of routing IP packets

This object is the read community string for the SNMP, see RFC1157.

This object is the read-write community string for the SNMP,see RFC1157. The read-write community string is required to modify this object.

This table contains information specifying which traps will be transmitted to a given destination address. The table is indexed by the destination address. Each entry in the table with a status of 'active' identifies a set of traps which, when generated, will be transmitted to the corresponding destination address listed in that entry.

Information relating to a set of traps and a destination address to which each trap in this set will be transmitted when it is generated. To create a new entry, a non-existent instance of qbSysAgentTrapDestAddr must be created. To remove an entry, an instance of qbSysAgentTrapDestEntryStatus of the entry must be set to destroy(6).

The destination address to which traps are to be transmitted.

Indicates which traps are sent to the destination address. Note that, currently,for Release 1, the only object 'all' can be set Enumeration: 'major': 2, 'critical': 3, 'all': 4, 'minor': 1.

Community string used for trap messages to this destination.

The status of this conceptual row. This OBJECT can be set to: createAndGo(4) destroy(6) Setting this object to active(1) when its value is already active(1) is a no-op. Setting this object to createAndGo(4) causes the agent to attempt to create and commit the row based on the contents of the objects in the row. If all necessary information is present in the row and the values are acceptable to the agent, the agent will change the status to active(1). If any of the necessary objects are not available, the agent will reject the creation request. Setting this object to destroy(6) will remove the corresponding entry in this table. The following values may be read: active(1). The following objects cannot be modified while the value of this object is active(1): qbSysAgentTrapDestAddr.

The destination port number for this trap address.

This indicates the kind of the management port associated with the default gateway. Enumeration: 'unknown': 0, 'atmmgt': 2, 'enetmgt': 1.

This object is the read-write community string for the SNMP,see RFC1157. The read-write community string is required to modify this object.

This is a singular object in qbSysAgentGroup and is for enabling or disabling RIP Configuration system wide Enumeration: 'enable': 1, 'disable': 2.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

Not used.

not used.

Not used.

notused.

not used.

The version used by the system controller when remotely reset.

inidcates which features of OAS software are administratively enabled on this system. If a bit is set, then the corresponding feature is enabled. Note: unlimited number of features can be enabled or disabled via this object. Bits: 'qbSysTdmKey': 1, 'qbSysAtmKey': 0.

This object shows and controls the bandwidth allocation between Au-1 and au-2. If it is set to 622, then there is no port sharing enabled between the ports. Any other setting will enable port sharing, and the 622 Mbis/sec of bandwidth is split between the 2 ports. Note. If protection is being used, then the bandwidth should be set to 622.

This object tests the system LEDs. If the object is read it should return ready. Setting the value test will initiate the LED test. Enumeration: 'ready': 1, 'test': 2.

if true, the software in the switch is accepted.

The chassis system type. Enumeration: 'other': 1, 'qb5000': 2, 'qb3000': 3.

The chassis backplane type. Enumeration: 'giga5': 3, 'other': 1, 'giga2': 2.

The number of slots in the chassis available for plug-in modules. QB3000 contains 7 slots, QB5000 contains 15 slots

The object allows to enable and disable bulk statistics collection on the OAS. Enumeration: 'enable': 1, 'disable': 2.

The last time any configuration parameter value was written to flash memory. A zero-length value indicates that no changes have been made and that the system is running using all defaults. Note that this parameter must be saved in non-volatile memory across re-initializations of the system.

The source address of the entity that made the last configuration change to the system. The value 127.0.0.1 (the loopback address) indicates the local console. This value must also be saved in non-volatile memory across re-initializations of the system.

The type of provisioning that occured to the system. provIot indicates that an IOT added/removed, or changed state. provConn indicates that a connection added/removed, or changed state. Enumeration: 'provConnection': 2, 'provIot': 1.

A table of events in the order that they were generated. An event may or may not be added to this (conceptual) table based on whether it passes all of the input filter criteria identified below. When the table is retrieved via SNMP operations, it may or may not include a specific event based on the current output filter criteria.

Information about a single event.

Indicates the number of the event. Events are numbered sequentially from 1 - n. A management station can keep track of the last event it uploaded and periodically GET-NEXT from there to determine if there have been any new events. This means that, as events are removed from the table their indices are not reused until the next reset to default configuration (which loses all stored events). The agent must store the 'next available event number' value across re-initializations of the system, resetting it to 1 only when the configuration is reset to defaults.

The date and time when this event was generated.

The subsystem that generated this event.

Describes whether the event was service affecting.

The severity of the event.

The identifier of the event. This id is unique within a system. This id maps to a qbSysEventIdEntry. It is used to lookup the event description in the qbSysEventIdTable.

Textual message associated with the event.

The maximum number of entries in the qbSysEventHistoryTable. When the number of entries gets larger than this size, older entries are discarded. The event level is considered when discarding old events because the log is full (old debug or trace messages are discarded before even older warning or fatal messages).

obsolete.

obsolete.

Setting this object to 'clear(2)' removes all entries from the qbSysAlarmHistoryTable, the qbSysEventHistoryTable and the qbSysNotificationHistoryTable. When read, this object always returns the value 'ready(1)'. Enumeration: 'ready': 1, 'clear': 2.

A table that conatins the currently triggered alarms in the order that have not been cleared yet. The index is incremented for each new alarm entry put onto the ring. When an alarm is cleared this entry is removed from the table.

Information about a single alarm that is currently triggered.

The internal index into the Alarm Table. The index is incremented for each new alarm entry put into the ring. When the alarm is cleared the entry is removed from the table. On a node reset, the object is reset to 0.

The date and time when this alarm was generated.

The subsystem that generated this alarm.

The type of the alarm. Can be 2 different modes: Service affecting and nonservice affecting.

The severity of the alarm.

The condition of the alarm.

The identifier of the alarm. This id is unique within a system. This id maps to a qbSysAlarmIdEntry. This is used to lookup the alarm description in the qbSysAlarmIdTable.

Textual message associated with the alarm.

The Resource to which this alarm corresponds. For example, if the alarm refers to Module removal, the resource would be the OID 'qbSysModuleOperStatus', including the instance ID of the Module removed.

A table of alarms in the order that they were generated.

Information about a single alarm.

Indicates the number of the alarm. Alarms are numbered sequentially from 1 - n. A management station can keep track of the last event it uploaded and periodically GET-NEXT from there to determine if there have been any new events. This means that, as alarms are removed from the table their indices are not reused until the next reset to default configuration (which loses all stored alarms). The agent must store the 'next available alarm number' value across re-initializations of the system, resetting it to 1 only when the configuration is reset to defaults.

The date and time when this alarm was generated.

The subsystem that generated this alarm.

Describes whether the event was service affecting.

The severity of the alarm.

The condition of the alarm.

The identifier of the alarm. This id is unique within a system. This is used to lookup the alarm description in the qbSysAlarmIdTable

Textual message associated with the alarm.

The maximum number of entries in the AlarmHistoryTable. When the number of entries gets larger than this size, older entries are discarded.

obsolete.

obsolete.

Setting this object to 'clear(2)' removes all entries from the qbSysAlarmHistoryTable, the qbSysEventHistoryTable and the qbSysNotificationHistoryTable. When read, this object always returns the value 'ready(1)'. Enumeration: 'ready': 1, 'clear': 2.

A table of event information for each identifier.

Information for a particular event id.

The unique event identifier.

The textual name of the event.

The severity of the event.

The severity of the alarm when it is Service Affecting.

If true, this Event initiates an SNMP Trap.

A table of alarm information for each identifier

Information for a particular alarm id.

The unique alarm identifier.

The textual name of the alarm.

The severity of the alarm.

The severity of the alarm when it is Service Affecting.

If true, this Alarm initiates an SNMP trap.

A table of Notifications in the order that they were generated. Currently these Notifications include qbSysUnsolicitedEvents and qbSysConfigurationEvents.

Information about a single Notification.

A unique number of the entry.

Indicates OID of the Notifcation that this entry refers. Though primarily intended to be the qbSysUnsolicitedEvent or qbSysConfigurationEvent OID, this value could also be another NOTIFICATION OID, for example a standard SNMP NOTIFICATION.

The type of Resource Event this notification represents. If this is a qbAlarm Notification, then the qbSysNotificationHistoryId refers to an entry in the qbSysAlarmIdTable. If it is of type qbEvent, the qbSysNotificationHistoryId refers to an entry in the qbSysEventIdTable.

This Id can optioanlly refer to a structure that augments the Notification.

The resource action that caused this event.

The Resource to which this entry corresponds. For example, if the Notication refers to Module removal, the resource would be the OID 'qbSysModuleOperStatus', including the instance ID of the Module removed.

This cookie is used to store augmenting information pertaining to this Notification. By convention, the cookie contains the value of the object 'pointed' to by qbSysNotificationHistoryResource. If this value is not syntactically consistent with the qbSysNotificationHistoryResource, then it is by convention set to '0'.

The time when this Notification was generated.

The alarm condition of the Notification.

If this Notification's QbNotificationType is an alarm or event, then this obejct identifies whether the corresponding alarm or event was service affecting. Otherwise, it is nonServiceAffecting.

The maximum number of entries in the NotificationHistoryTable. When the number of entries gets larger than this size, older entries are discarded.

obsolete.

obsolete.

obsolete. Enumeration: 'ready': 1, 'clear': 2.

The index of the last entry in the qbSysAlarmHistoryTable, in time-order.

The index of the last entry in the qbSysEventHistoryTable, in time-order.

This is a currently private value that can be used to retrieve the last entry in the qbSysNotificationHistoryTable, in time-order.

A list of IOAS's cards. The number of entries is the number of cards in the IOAS chassis.

Entry containing information about one module in the chassis.

This value is determined by the OAS slot number where the module is located. Valid range is from 1 to 15 for QB5000 and from 1 to 7 for QB3000.

The module type. Enumeration: 'q155': 5, 'q155-T': 9, 't1E1-16': 26, 'syscon': 17, 's622-T': 11, 'es24-10-100': 25, 'dws155s': 22, 'switchGiga2': 15, 'enhSwitchProc': 20, 'dws': 2, 'q155LR-T': 31, 'dws622s': 24, 'vt155-T': 10, 'dws155sw': 29, 'dws622w': 21, 'unknown': 1000, 'dws622sw': 8, 'other': 18, 'vt155': 6, 'main': 1, 'empty': 19, 's622': 7, 'sysconII': 23, 'gigesw': 32, 's622LR-T': 28, 'q155LR': 30, 'switchProc': 3, 'switch': 4, 's622LR': 27.

A descriptive string used by network administrator to name the module.

The operational status of the module. If the status is not ok, the value of the moduleTestResult gives more detailed information about the module's failure condition(s). Enumeration: 'recovery': 4, 'failed': 7, 'init': 3, 'other': 1, 'removed': 6, 'empty': 2, 'inService': 5.

This object, when read, returns one of the following results: other(1): module permanently enabled enable(3): module currently enabled disable(4): module currently disabled clearslot(5): used to clear slot Setting this object to one of the acceptable values gives the following results: other(1): gives an error reset(2): resets the module enable(3): if the module status is configurable, enables the module, else gives error disable(4): if the module status is configurable, disables the module, else gives error Setting this object to any other value results in an error. Note that, currently, this object 'readonly' Enumeration: 'reset': 2, 'enable': 3, 'other': 1, 'clearslot': 5, 'disable': 4.

The result of the module's self test. A zero indicates that the module passed all tests. Bits set in the result indicate error conditions.

The number of ports supported by the module.

A series of bytes containing status information about the module and each of the ports in the module. The first byte contains the status of the module (same value as moduleStatus), and subsequent bytes contain statuses for the first through last ports on the module (same value as ifOperStatus).

The manufacturer's model part number for the module.

The manufacturer's serial number for the module.

The manufacturer's equipment identifier.

The hardware version of the module.

The software version of the module.

Protection mode of a module.

The value of sysUpTime at the last switchover of the switch cards. The value is zero if there has been no switchover since agent initialization.

The reason for the last switch card switchover. The value is none(1) if there has been no switchover since agent initialization. Enumeration: 'none': 1, 'unknown': 2, 'moduleRecovered': 5, 'moduleInserted': 7, 'moduleFailed': 4, 'moduleRemoved': 6, 'userInitiated': 3.

Led OCTET String A series of bytes containing status information about each of leds in the module. For every led two bytes are allocated. The first byte indicates the led type, the second byte indicates the led state (on/off). Therefore byte string size is different depending of the module types. The leds of modules as follows: SYSCON: 1 CR(0) 2 MJ(1) 3 MN(2) 4 MNTC(3) 5 Fault(4) 6 ACO(5) SWITCH/SWPROC - 1 FAULT(1) 2 ACTIVE(2) WAN/MOC12 1 FAULT(0) 2 ACTIVE(1) 3 LOS(2) AU-1 1 FAULT(0) 2 ACTIVE(1) 3 LOS(2)

A descriptive string used by vendor to name the module.

This object tests the module LEDs. If the object is read, it should return ready. Setting the value test will initiate the LED test for this card. Enumeration: 'ready': 1, 'test': 2.

Indicates whether APS alarms should be generated for this interface. Enumeration: 'disabled': 2, 'enabled': 1.

This tables lists OAS's modules. The number of entries is equals the number of cards in an OAS chassis.

Entry contains module APS information.

This object is used to set the protection mode for a given slot. Note: Only main-a, main-b, au-1, au-2, au-3, au-4, au-5 au-6, au-7 or au-8 may be selected for. this object. Only slots containing SONET interfaces are valid.

This object indicates a protection mode of a given slot within an SPG group. Enumeration: 'active': 3, 'standby': 4, 'unprotected': 2, 'unavailable': 1.

This object is used to allow a user execution APS switch commands for a given slot.

The object indicates the current highest priority switching state of the slot. noop - this value should be returned by a read request when no switch command has been written to a given slot since initialization. sf - signal failure on the slot sd - signal degrade on the slot fail - equipment fail or removed Enumeration: 'force': 4, 'clear': 2, 'manual': 5, 'lockout': 3, 'fail': 8, 'noop': 1, 'sf': 6, 'sd': 7.

The value of sysUpTime at the time of the last switchover of the a given card. The value is zero if there has not been a switchover since agent initialization.

A list of port entries. The number of entries is determined by the number of modules in the chassis and the number of ports in each module.

Entry containing information for a particular port in a module.

A port number that uniquely identifies this port within a card. The value is determined by the location of the port in the module. Valid entries are 1 to the value of moduleNumPorts for this module.

A descriptive string used by the network administrator to name the port. This string has the same value as the ifName object

The physical layer port type. Enumeration: 'unknown': 1, 'main': 3, 'dws': 4, 'atmOc3': 5, 'e10100BaseT': 2.

The current operational status of the port. Enumeration: 'minorFault': 3, 'other': 1, 'ok': 2, 'majorFault': 4.

The value of the instance of the ifIndex object, defined in MIB-II, for the interface corresponding to this port.

The current loopback state of the port. The values mean: unLoop Not in the loopback state. A device that is not capable of performing a loopback on this interface will always return this value. facility The received signal at this interface is looped back out through the corresponding transmitter in the return direction.This test can be performed only on main card interfaces. terminalLoop The signal that is about to be transmitted is connected to the associated incoming receiver. This test can be performed on main and dws interfaces. Enumeration: 'terminal': 3, 'unloop': 1, 'facility': 2.

A table of IOT devices in the system.

Information about a single IOT device in the system.

The IOT serial number.

The IOT's DWS interface index. Indicates the interface index of the IOAS DWS interface to which this IOT is attached.

A Quantum Bridge identifier for the IOT device. This value can be changed if the IOAS is reset.

A textual description of the IOT. This value includes the full name and version identification of the system's hardware type, software operating-system, and networking software.

An administratively-assigned name for this IOT.

The physical location of the IOT. Note that, currently, this object readonly

When in the same set pdu as qbSysIotAdminStatus, this object indicates the version of software that the IOT will boot from if qbSysIotAdminStatus indicates a reset. If this object is not set, the default image will be used. When read, this value returns a null string. Note that the running IOT software version can be retrieved from the qbSysIotFileTable entry described below.

The hardware version of the module.

This object, when read, returns one of the following results: enable(5): IOT is currently operational disable(6): IOT is currently disabled( range, reset, standby, maintenance, or resetToDefault mode). Setting this object to one of the acceptable values gives the following results: reset(1): resets the IOT. This is the 'software reset button' of the agent. When set to 'reset(1)', the system will reset and reload its configuration from FLASH/NVRAM. resetToDefault(2): When set to resetDefault(2), the system will delete all provisioned data for this IOT and use default setings at initialization time. For both 'reset(1)' and 'resetToDefault(2)', the default IOT software version will be used unless the set PDU contains a value for qbSysIotSwVersion, in which case it will be used. range(3): When set to 'range', the IOAS will initiate or re-initiate the ranging process for the IOT. standby(4): When set to 'standby', the IOAS will halt communication with IOT, while retaining the associated connection parameters at both the IOAS and IOT. Setting this object to any other value results in an error. Enumeration: 'reset': 1, 'standby': 4, 'range': 3, 'enable': 5, 'disable': 6.

This is the operational IOT status. Enumeration: 'standBy': 4, 'fault': 6, 'down': 3, 'running': 2, 'other': 1, 'maintenance': 7, 'inService': 8, 'rangingInProgress': 5.

This variable mirrors the dsx1LineCoding object defined in the RFC2495. When the object is set to a new value it effects all 4 DS1 ports of the IOT. NOte: The dsx1LineCoding value effects only one DS1 port. Enumeration: 'dsx1B8ZS': 2, 'dsx1HDB3': 3, 'dsx1ZBTSI': 4, 'other': 6, 'dsx1AMI': 5, 'dsx1B6ZS': 7, 'dsx1JBZS': 1.

This string has the following format for old IOTs(YYWK-PC-XXXXXX) where yy - year, wk - week of the year, and xxxxxx - serial number. For new IOT models the FSAN serial string has the following format (QMBGXXXXXXXX) where XXXXXXXX - a unique hexedecimal serial number(e.g.1F338BE3).

The status of this conceptual row. This OBJECT can be set to: createAndGo(4) destroy(6) Setting this object to active(1) when its value is already active(1) is a no-op. Setting this object to createAndGo(4) causes the agent to attempt to create and commit the row based on the contents of the objects in the row. If all necessary information is present in the row and the values are acceptable to the agent, the agent will change the status to active(1). If any of the necessary objects are not available, the agent will reject the creation request. Setting this object to destroy(6) will remove the corresponding entry in this table. The following values may be read: active(1).

The IOT manufecturing serial number string.

The IOT type.

An product name for this IOT.

The IOT signal format type. Enumeration: 'e1': 2, 'ds1': 1.

This object when reads, returns the serial number of the selected IOT(the same as qbSysIotSerialNumber). When the object is set (the serial number must be be different) the agent ralls all existing configuration from the old serial number to the serial number. As a result of this, this row is deleted and a new row is created in the table.

The number of slots in the IOT chassis available for plug-in modules. QB616 contains 3 slots, all other IOT return 0

.

Information about files on a single IOT.

The IOT serial number that these files should be associated with.

The name of a version currently available on this IOT in the first FLASH region.

The name of a version currently running on this IOT in the second FLASH region.

The name of the version currently running on this IOT.

The name of a version currently accepted as the default image on this IOT. If no image is currently accepted, this entry will be null.

The name of a version of a file that the agent should attempt to download the next time qbSysIotFileAction is set to download.

The value of time since this IOT was initialized.

The value of sysUpTime entry was last modified.

This command allow a remote initiation of a file based command. Currently, by convention, if this object's value is set to 'accept', the SNMP response determines its success. If this object's value is succesfully set to 'downLoad' the application can monitor the action's progress by polling the qbSysIotFileDownLoadStatus and qbSysIotFileErrorMsg objects. DownLoadAbort ends the current download. Enumeration: 'downLoad': 3, 'downLoadAbort': 4, 'accept': 2, 'noAction': 1.

The Status of the current download. Enumeration: 'failed': 3, 'idle': 1, 'busy': 2.

The error message, if any, pertaining to the current download.

The Quantum Bridge Interface location table. This table contains physical mapping information for the device interfaces.

An entry in the Quantum Bridge Interface Location Table. Every row in the ifTable has a corresponding entry in this table which contains location information in iotaddr.slot.port format.

The slot number of the interface. If this is an IOT's interface the object is set to 0.

The IOT address of the interface. If this is an IOAS's card interface, the object is set to 0.

The port number of the interface.

Indicates the entity to which this interface belongs: 1 - IOT, 2-IOAS. Enumeration: 'ioas': 1, 'iot': 2.

If the qbIfLocationType indicates that this is an IOT, this object contains the IOT SerialNumber (as defined by qbSysIotSerialNumber) of the IOT to which this entry refers.

An SNMP trap definition for carrying Quantum Bridge system events. Some events have specific SNMP traps, such as linkUp or linkDown traps. (These are generally events with levels of info(3), warning(4), or fatal(5).) The events which do not have specific SNMP traps defined for them will be sent using this NOTIFICATION-TYPE if qbSysAlarmAsTrap is set to 'true(1)'.

An SNMP trap definition for carrying Quantum Bridge system events. Some events have specific SNMP traps, such as linkUp or linkDown traps. (These are generally events with levels of info(3), warning(4), or fatal(5).) The events which do not have specific SNMP traps defined for them will be sent using this NOTIFICATION-TYPE if qbSysEventAsTrap is set to 'true(1)'.

A qbSysModuleDown trap signifies that the agent entity has detected that the qbSysModuleStatus object in this MIB has transitioned from the ok(2) state to one of another state.

A qbSysModuleInserted trap signifies that the agent entity has detected that a board has been inserted into a particular slot in the IOAS.

A qbSysModuleRemoved trap signifies that the agent entity has detected that a board has been removed from a particular slot in the IOAS.

A qbSysIotDiscovered trap signifies that the agent entity has detected that a new IOT has been discovered/provisioned in the DWS network.

A qbSysIotRemoved trap signifies that the agent entity has detected that an IOT has been removed from the DWS network.

A qbSysIotOutOfService trap signifies that the agent entity has detected that an IOT has LOS condition.

This notification is generated when the value of qbSysModuleStandbyStatus changes from active(1) to either standby(2) or notProtected(3) or notPresent(4). The notification is also generated when the value of qbSysModuleStandbyStatus changes from standby(2) to active(1). The varbind indicates the current mode of the affected card.

A qbSysFlashInserted trap signifies that the agent entity has detected that a flash has been inserted into the syscon module in the IOAS.

A qbSysFlashRemoved trap signifies that the agent entity has detected that a flash card has been removed from a syscon module in the IOAS.

A qbSysConfigChanges trap that the agent entity has detected that provisoning changes were detected. The varbind indicates that type of changes occured for a given system. Note: Release 2

A qbDwsRxLos trap indicates Loss of Signal by the WAN/Sonet card receiver. The trap is generated by a WAN card when a WAN card receiver problem is detected. The trap contains the WAN port interface index.

The qbSysUnsolicited Event. Unsolicited Events typeically are fault or discovery events such as resource added or removed or alarm information.

the qbSysConfigurationEvent typically represents some sort of configuration or provisioning action on the system.

The compliance statement for all agents that support this MIB. A compliant agent implements all objects defined in this MIB.

The set of all accessible objects in the General group of this MIB.

The set of all accessible objects in the Configuration Parmaeters Group in this MIB.

The set of all accessible objects in the system events group in this MIB.

The set of all accessible objects in the Module Group of this MIB.

The set of all accessible objects in the Port Group of this MIB.

The set of all accessible objects in the Intelligent Terminal Group of this MIB.

The set of all accessible objects in the Interfaces Group of this MIB.