BCS-IDENT-MIB: View SNMP OID List / Download MIB

The SMIv2 MIB module for the MOTOROLA BCS common ident objects. The MIB Tree for this is shown below.

This contains the serial number of the unit. There is no specification of the internal format of the serial number. The serial number is entered into either permanent or non- volatile memory of the unit at the time of manufacture. Note - the unit itself supplies the serial number.

This contains the chassis number of the unit. This is applicable only to a limited number of products, currently, only the ITEM-1000. For products for which this is not applicable, this will be a null object. There is no specification of the internal format of the chassis number. The means by which any product determines its chassis number is to be determined by each individual product.

This contains the IfIndex of the OAM&P port.

This contains a display string that defines the hardware version of this particular unit. There is no specification of the internal format of the hardware version. The hardware version is entered into the either permanent or non-volatile memory of the unit at the time of manufacture.

This contains a display string that defines the features of this particular unit. There is no specification of the internal format of the hardware features. The hardware features is entered into the either permanent or non-volatile memory of the unit at the time of manufacture.

This contains a display string that defines the inventory code for this unit. Once an inventory code has been set, it should be kept in non-volatile memory. The unit should only allow this object to be set when it is in the 'configuration' mode. There is no specification of the internal format of the inventory Code.

This contains a display string that defines the current version of the software for this unit. The format of the software version is a fully qualified directory name. This value is received by a unit as within a BOOTP response from the BOOTP server. It is available to the network manager for applications that track the installed software. Once the software version has been set, it should be kept in non-volatile memory.

This is different from the MIB II sysLocation variable as it contains only the location area and does not describe the precise location. This contains a display string that defines the area in which the unit is installed. Location is defined by a set of three objects: 'Area', 'Rack', and 'Shelf'. These location objects cannot be determined by the unit itself, but can only be determined by the network manager. It is available to the unit for display on a front panel. Display of the location on the front panel is useful in validating the configuration established by the network manager. The unit should only allow this object to be set when it is in the 'configuration' mode. Once the Location Area has been set, it should be kept in non-volatile memory.

This contains a display string that defines the rack in which the unit is installed. Location is defined by a set of three objects: 'Area', 'Rack', and 'Shelf'. These location objects cannot be determined by the unit itself, but can only be determined by the network manager. It is available to the unit for display on a front panel. Display of the location on the front panel is useful in validating the configuration established by the network manager. The unit should only allow this object to be set when it is in the 'configuration' mode. Once the Location Area has been set, it should be kept in non-volatile memory.

This contains a display string that defines the shelf in which the unit is installed. Location is defined by a set of three objects: 'Area', 'Rack', and 'Shelf'. These location objects cannot be determined by the unit itself, but can only be determined by the network manager. It is available to the unit for display on a front panel. Display of the location on the front panel is useful in validating the configuration established by the network manager. The unit should only allow this object to be set when it is in the 'configuration' mode. Once the Location Area has been set, it should be kept in non-volatile memory.

The version number of this MIB.

The version number of the Agent.

This is the command to be executed by the resource managed by the agent. The value unspecified is always returned on SNMP Get/GetNext while the resource is running. If the restart(1) command is given, currentlyRestarting(2) is returned while the resource is preparing to restart (reboot). Enumeration: 'currentlyRestarting': 2, 'purgeAndRestart': 4, 'purgeNvramAndRestart': 6, 'unspecified': 3, 'currentlyPurgingAndRestarting': 5, 'currentlyPurgingNvramAndRestarting': 7, 'restart': 1.

This table contains extensions to the MIB II ifTable which contains the definitions of all interfaces. An ifTable entry may be a board or just a port on a board. Any ifTable entry can have an extension in the identIfExtensionTable. The corrsponding entry in that table will have the identIfIndex = ifIndex. Within the ifTable the presence of such an entry is indicated by setting the variable ifSpecific to the OBJECT IDENTIFIER value of identIfExtensionTable. Otherwise iFSpecific is set to {0 0}. The ifType - other - is used for all board types not envisoned by MIB II.

An entry (conceptual row) in the Board Table.

Same value as ifIndex of MIB II for the same board.

This contains the serial number of the board. There is no specification of the internal format of the serial number. The serial number is entered into either permanent or non-volatile memory of the unit at the time of manufacture. Note - the unit itself supplies the serial number.

This contains a display string that defines the version of this particular board. There is no specification of the internal format of the hardware version. The hardware version is entered into the either permanent or non-volatile memory of the unit at the time of manufacture.

This contains a display string that defines the features of this particular board. There is no specification of the internal format of the hardware features. The hardware features is entered into the either permanent or non-volatile memory of the unit at the time of manufacture.

This contains a display string that defines the inventory code for this board. This is an optional value; if there is no inventory code, The unit will respond with a null string. Once an inventory code has been set, it should be kept in non-volatile memory. The unit should only allow this object to be set when it is in the 'configuration' mode. There is no specification of the internal format of the inventory Code.

Within a product, there may be several identifiers of such firmware, boot proms, kernel versions, flash versions, etc. This field (and the 3 that follow) are used to hold the identification of these items. These values must be entered into the board at the time of manufacturing. Unused fields are reported as null values. These fields are available to the network manager for applications that keep track of the firmware related identification. There is no specification of the internal format of firmware version identifiers.

Firmware related identification field # 2.

Firmware related identification field # 3.

Firmware related identification field # 4

This variable identifies the board slot.

This is the command to be executed by the resource managed by the agent. The value unspecified(10 is always returned on SNMP Get/GetNext while the other values are set by the manager and executed by the resource. Enumeration: 'reset': 2, 'restart': 3, 'unspecified': 1, 'halt': 4.

The current Adminsitrative state of the interface as defined in ISO/IEC 10164-2. Enumeration: 'locked': 1, 'shuttingDown': 3, 'unlocked': 2.

The current Operational state of the interface as defined in ISO/IEC 10164-2 Enumeration: 'disabled': 2, 'enabled': 1.

This object defines the Alarm status of the interface as defined in ISO/IEC 10164-2 and state-machine Enumeration: 'underRepair': 1, 'major': 3, 'idle': 6, 'critical': 2, 'alarmOutstanding': 5, 'minor': 4.

This object controls the Availability status of the interface as defined in ISO/IEC 10164-2 and state-machine Enumeration: 'available': 10, 'dependency': 6, 'notInstalled': 8, 'offDuty': 5, 'logFull': 9, 'inTest': 1, 'failed': 2, 'powerOff': 3, 'offLine': 4, 'degraded': 7.

The object identifier of a board type specific extension to the ifTable if necessary. Otherwise, identIfSpecific is set to {0 0}.

This object is used to create, delete or modify a row in this table. To create a a new network element, this object is initially set to 'createRequest'. After completion of the configuration of the new entry, the manager must set the appropriate instance of this object to the value valid(1) or aborts, setting this object to invalid(4). This object must not be set to 'active' unless the following columnar objects exist in this row: identIfExtensionIndex identIfSerialNumber identIfHardwareVersion identIfInventoryCode identIfFirmwareVersion1 identIfSpecific To delete an existing entry in this table, the manager must set the appropriate instance of this object to the value invalid(4). Creation of an instance of this object has the effect of creating the supplemental object instances to complete the conceptual row. An existing instance of this entry cannot be created. If circumstances occur which cause an entry to become invalid, the agent modifies the value of the appropriate instance of this object to invalid(4). Whenever, the value of this object for a particular entry becomes invalid(4), the conceptual row for that instance may be removed from the table at any time, either immediately or subsequently.

This contains the model of the product. For example, the ITEM-1000 would contain 'ITEM1000'.