CPQNUNIF-MIB: View SNMP OID List / Download MIB

This table contains a list of all the MIB modules actively supported by a unit's agent. This includes any standard RFC and Compaq enterprise MIBs.

There is one entry defined for each separate MIB module the agent supports.

The index for this entry.

This is a short textual description of the MIB module for this entry. Examples could be RFC 1213 MIB-II or Compaq Unified MIB.

This is the OID representing the base node of the MIB for this entry. The base node of a MIB is defined here as the first MIB node that is not defined in another MIB. For example, the base node OID for RMON is MIB-II.RMON or 1.3.6.1.2.1.16.

Setting this object to reset(2) causes the unit to reset in the most complete manner possible. Any hardware units that can be reset, will be. If possible, this will be done using a hardware reset; if not, then the unit will perform a software re-initialization. All non-durable information, including counter values, will be lost. All durable information is retained. The value returned for this object will ALWAYS be running(1). After receiving a request to set this variable to reset(2), the unit may delay the reset for a short period. This is done to respond to the SNMP set request. The warm-start(3) setting has the same behavior. Note that not all units support warm-start(3). If not supported, a unit will return a BAD VALUE error. For more information on the meaning and semantics of 'reset' and 'warm-start', see the User's Guide for the unit. Setting this object to reset-to-factory-values(4) will cause all configurable parameters to be reset to the factory settings. Note that all user-configured information will be lost: this includes the system description, passwords, community names, the contents of the access control table (cpqnCommunityAccessTable), and default routes. See the unit's documentation for information on factory settings. Enumeration: 'reset': 2, 'running': 1, 'reset-to-factory-values': 4, 'warm-start': 3.

This object indicates which entry in the cpqnSerialPortTable is the primary serial port. For a list of the functions and features provided on a unit's primary serial port, see the unit's documentation.

There is one entry in this table for each serial port on the unit.

This entry provides information and objects to control a serial port.

The index of this row.

This object indicates which entry in the MIB-II interface table this serial port corresponds to. If this value is zero (0), then this serial port DOES NOT have an associated MIB-II interface. This object will only be non-zero for serial ports which support SLIP, PPP or a similar protocol.

DURABLE: If this object is enabled(1) then after a power up or reset the unit will transmit the modem init string out the primary serial port in order to initialize the modem. This will occur at the baud rate value of cpqnSPortBaudRate. Note that some units have more sophisticated modem support features. For more information on how a unit supports modems, see the unit's documentation. Enumeration: 'disabled': 2, 'enabled': 1.

DURABLE: This object contains a Modem Initialization String which is used to configure a modem on this port to the desired mode. Refer to the unit-specific documentation for information on the factory setting for this object and for other information on how the unit supports modems.

DURABLE: If enabled(1), the unit automatically detects the baud rate of incoming calls and will adjust the baud rate on this port to match. This is accomplished by watching for the connect indication strings from a modem attached to the port. For more information on how a unit supports modems, see the unit's documentation. Enumeration: 'disabled': 2, 'enabled': 1.

DURABLE: This is the current baud rate for the port. Its value must match a cpqnBaudRate entry in cpqnSupportBaudRateTable. Note that this value can automatically change if cpqnSPortModemAutoNegotiateState is set to enabled(1).

A table of supported baud rates for this unit.

There is one entry defined for each supported baud rate for each serial port.

The index into the cpqnSerialPortTable table identifying the port this entry applies to.

The index of this row.

The supported baud rate for the port indexed by cpqnBaudRatePortIndex.

This table contains a list of hardware and/or software components resident in the unit.

There is one entry defined for each hardware and/or software component.

The index into the version table.

The component's type.

A brief description of the component. This object may be empty.

The MAJOR version number of the component. This is always a value between 0 and 255 and should be interpreted as a decimal number. An example is version 2.14 where 2 is the major version number.

The MINOR version number of the component. This is always a value between 0 and 99 and should be interpreted as a two-digit decimal number. An example is version 2.01 where 1 is the minor version number. Another example is version 2.1 where 10 is the minor version number.

The STEP identifier for the associated component. This value indicates the level or class of the component, such as prototype, production, or beta.

The REVISION of the step for the associated component. An example is version 1.00B3 where 3 is the revision number.

The serial number of this component. The format of this object is dependent on the unit type. Refer to the unit-specific documentation for more information. This object is empty for components which do not have a serial number.

This is a number that uniquely identifies which unit in a collection of one or more units that this entry applies to. For example, this unit may be part of a stack, or a plug-in card in a chassis. For units that are not part of a collection (standalone) this value is always a 1.

A component represented by an entry in this table may be a sub-component of another entity or unit. In this case, the value of this object indicates this entry's parent entry in this table. For example, a plug-in uplink card may be plugged into unit #3 of a stack of repeaters. In this case, this value would contain the index into this table which has a cpqnVersionUnitId of 3. If this entry has no parent, then this object contains the value zero.

DURABLE: This object controls the Telnet feature of the unit. If this object is set to disabled(2), then Telnet is disabled and no Telnet session can be initiated, regardless of the settings of other access control mechanisms. If this object is enabled(1), then Telnet sessions can be initiated and are subject to the other access control mechanisms. Enumeration: 'disabled': 2, 'enabled': 1.

This table contains objects which control access to the agent over IP. Access is restricted to only the hosts listed in this table. If a station does not have read-write-allow-telnet(4) access to a unit, then this table is not accessible, e.g. GET or SET messages accessing this table from stations will have an authentication error returned. GET NEXTs on this MIB from such stations will simply skip over this table. Care must be taken when modifying this table. A network management station can inadvertently modify this table so that it no longer has read-write-allow-telnet(4) access. If this occurs, then this table can only be modified from another network management station with write access, via telnet, or via a direct connection to the unit's primary serial port. Access to this unit via SNMP and Telnet can also be blocked if all the entries in this table and the cpqnCommunityAccessIPXTable are deleted. In this case, this table can only be modified via a direct connection via the primary serial port using the unit's user interface. This table can be set to factory values using the user interface accessed by Telnet or a direct connection to the unit's primary serial port. This table will also be set to factory values when cpqnUnitReset is set to reset-to-factory-values(4).

There is one entry defined for each host-community pair.

The index to this entry.

DURABLE: The status of this row entry. Rows are added to this table using 'row sets'. When a row is added, this object must be set to row-valid(1). To delete a row from this table, set this object for the row to row-invalid(2). Row sets for new rows with a row status set to row-invalid(2) return a BAD VALUE error. This object will always read as row-valid(1). If no more rows can be added to the end of the table, then a row set to create a new row will return BAD VALUE. When rows are deleted from this table, the indexes of the other rows do not change. In other words, this table can be 'sparse' or have 'holes'. Deleted entries can be re-created using a row set with a row status of row-valid(1).

DURABLE: This mask is applied to the source address of received SNMP/IP messages. If the masked address matches cpqnAclIPAddrMatch and the community in the SNMP packet matches the community name in cpqnAclIPCommunity for the row, then the SNMP request will be serviced by the unit's agent. The transmitting node's access to this unit's MIB tables is determined by the cpqnAclIPRights. For example, assuming cpqnAclIPAddrMask = 255.255.255.000, cpqnAclIPAddrMatch = 198.085.034.000, and cpqnAclCommunity = compaq, then a SNMP request coming from 198.85.34.72 with community compaq will pass whereas a request from 120.1.2.4 with community compaq will fail.

DURABLE: The Masked address must match this value.

DURABLE: The community string that is required for any requests coming from this host. The default value for this object is 'public'.

DURABLE: This object controls the access granted to SNMP requests which match a mask/match and community name string. no-access(1) means that that address/community name pair has neither SNMP/IP nor Telnet access. read-only-prevent-telnet(2) allows only read access to MIB objects and disallows Telnet access. read-only-allow-telnet(3) also allows only read access, but the station can initiate a Telnet session. read-write-allow-telnet(4) allows full access to the device's MIB and allows the station to initiate a Telnet session. NOTE: Telnet access is either allowed or disallowed. Generally, devices do not have read-only telnet sessions. This mechanism does not preclude the use of a password for Telnet access. Enumeration: 'no-access': 1, 'read-only-allow-telnet': 3, 'read-write-allow-telnet': 4, 'read-only-prevent-telnet': 2.

This table contains objects which control SNMP/IPX access to the agent. Access is restricted to only the hosts listed in this table. If a station does not have read-write(3) access to a unit, then this table is not accessible,e.g. GET or SET messages accessing this table from stations will have an authentication error returned. GET NEXTs on this MIB from such stations will simply skip over this table. Care must be taken when modifying this table. A network management station can inadvertently modify this table so that it no longer has read-write(3) access. If this occurs, then this table can only be modified from another network management station with write access, via telnet, or via a direct connection to the unit's primary serial port. Access to this unit via SNMP and Telnet can also be blocked if all the entries in this table and the cpqnCommunityAccessIPTable are deleted. In this case, this table can only be modified via a direct connection via the primary serial port using the unit's user interface. This table can be set to factory values using the user interface accessed by Telnet or a direct connection to the unit's primary serial port. This table will also be set to factory values when cpqnUnitReset is set to reset-to-factory-values(4).

There is one entry defined for each host-community pair.

The index to this entry.

DURABLE: The status of this row entry. Rows are added to this table using 'row sets'. When a row is added, this object must be set to row-valid(1). To delete a row from this table, set this object for the row to row-invalid(2). Row sets for new rows with a row status set to row-invalid(2) return a BAD VALUE error. This object will always read as row-valid(1). If no more rows can be added to the end of the table, then a row set to create a new row will return BAD VALUE. When rows are deleted from this table, the indexes of the other rows do not change. In other words, this table can be 'sparse' or have 'holes'. Deleted entries can be re-created using a row set with a row status of row-valid(1).

DURABLE: This mask is applied to the source address of received SNMP messages. If the masked address matches cpqnAclIPXAddrMask and the community in the SNMP packet matches the community name in cpqnAclIPXCommunity for the row, then the SNMP request will be serviced by the unit's agent. The transmitting node's access to this unit's MIB tables is determined by the cpqnAclIPXRights. For example, 0081CCAB:00805FEAE01D is an IPX address which could be matched with a mask of 00FFFFFF:000000000000. Due to the nature of IPX address, the node address of an IPX address mask are simply 0's. This controls SNMP access by IPX network number only.

DURABLE: The Masked address must match this value.

DURABLE: The community string that is required for any requests coming from this host. The default value for this object is 'public'.

DURABLE: This object controls the access granted to SNMP/IPX requests which match a mask/match and community name string. no-access(1) means that that address/community name pair has no SNMP/IPX access. read-only(2) allows only read access to MIB objects. read-write(3) allows full access to the device's MIB. Enumeration: 'no-access': 1, 'read-write-access': 3, 'read-only-access': 2.

A list of IP trap destination entries.

A destination entry which defines the IP address to which traps are sent for a community.

A value that uniquely identifies this IPTrapDestEntry.

DURABLE: The status of this row entry. Rows are added to this table using 'row sets'. When a row is added, this object must be set to row-valid(1). To delete a row from this table, set this object for the row to row-invalid(2). Row sets for new rows with a row status set to row-invalid(2) return a BAD VALUE error. This object will always read as row-valid(1). If no more rows can be added to the end of the table, then a row set to create a new row will return BAD VALUE. When rows are deleted from this table, the indexes of the other rows do not change. In other words, this table can be 'sparse' or have 'holes'. Deleted entries can be re-created using a row set with a row status of row-valid(1).

DURABLE: A community name to which this destination IP address belongs.

DURABLE: The IP address to send traps to on behalf of this entry.

A list of IPX trap destination entries.

A destination entry which defines the IPX address to which traps are sent for a community.

A value that uniquely identifies this IPXTrapDestEntry.

DURABLE: The status of this row entry. Rows are added to this table using 'row sets'. When a row is added, this object must be set to row-valid(1). To delete a row from this table, set this object for the row to row-invalid(2). Row sets for new rows with a row status set to row-invalid(2) return a BAD VALUE error. This object will always read as row-valid(1). If no more rows can be added to the end of the table, then a row set to create a new row will return BAD VALUE. When rows are deleted from this table, the indexes of the other rows do not change. In other words, this table can be 'sparse' or have 'holes'. Deleted entries can be re-created using a row set with a row status of row-valid(1).

DURABLE: A community name to which this destination IPX address belongs.

DURABLE: The IPX address to send traps to on behalf of this entry. IPX traps are sent to the standard IPX SNMP socket number.

This table describes IP network information for each management agent interface. This could include all possible bridge groups and the SLIP interface

There is one entry for each agent interface which describes the IP protocol information on that interface.

This is the ifIndex value of an interface in the MIB-II interface table for which this table entry applies.

The physical address of the management agent interface. This is usually an interfaces IEEE MAC Address. For IEEE MAC address, the value will be 6 bytes in network byte order. For interfaces which do not have such physical address (e.g., SLIP interfaces), this object will one zero byte.

DURABLE: The IP Address of this Agent interface.

DURABLE: The IP Subnet Mask of this Agent interface.

DURABLE: The IP Address of the next hop Router (default Gateway) used by this interface.

DURABLE: Except when booting up, an agent communicates over IP using a single frame type defining the type of network that the IP traffic is running on: Ethernet_II or IEEE 802.2_SNAP. When the agent is performing BOOTP, it may not assume any frame type and can attempt to BOOTP over both types. (see cpqnBootpEnable) It will use the frame type that the first BOOTP response uses for the rest of its communication. The frame type of the BOOTP response will be stored by this object. For interfaces that do not have an Ethernet frame type, e.g., the serial port, the frame type is always not-applicable(1). Enumeration: 'ethernet-ii': 2, 'not-applicable': 1, 'ieee-802-2-snap': 3.

DURABLE: This object allows a user to enable the unit to send out periodic ICMP Pings to ensure that the unit's IP Address is contained in the ARP cache of its default gateway (cpqnIpRouter, if any!). If the user sets the state to discover(1), then the unit will issue ICMP Pings at a rate defined by cpqnIpPingPacketRate. If the user selects do-not-discover(2) then the unit does not send any ICMP Pings and may not be autodiscovered by IP based management applications. Enumeration: 'do-not-discover': 2, 'discover': 1.

DURABLE: This object determines the rate (in seconds) at which ICMP Pings are sent out by the unit to ensure that its IP Address remains in the ARP cache of the unit's default gateway (cpqnIpRouter). This object is useful only if cpqnIPAutoDiscoveryStatus is set to discover(1).

Setting this object allows the changes made to any of the settable objects in this table to be written into non-volatile memory. The changes will not take effect nor be written into non-volatile memory until this object is set; therefore, until that time, the changes are stored but not used. This object will return values-valid(4) unless some object has been changed but the changes were not written to non-volatile memory. In this case it will return values-changed(3) until the changes are written to non-volatile memory. Enumeration: 'ignore-changes': 1, 'write-changes-to-nvram': 2, 'values-valid': 4, 'values-changed': 3.

This table describes IPX network information for each agent interface.

There is one entry for each agent interface which describes the IPX protocol information on that interface.

This is the ifIndex value of an interface in the MIB-II interface table for which this table entry applies.

The physical address of the management agent interface. This is usually an interfaces IEEE MAC Address. For IEEE MAC address, the value will be 6 bytes in network byte order. For interfaces which do not have such physical address (e.g., SLIP interfaces), this object will one zero byte.

DURABLE: The frame type with which IPX communication originating from the unit will take place. The unit will respond to a packet using the same frame type as was used in the request. This frame type comes into effect on any packet that is generated by the unit not in response to another external packet. An example is a SNMP Trap. Enumeration: 'ieee-802-2-snap': 5, 'ethernet-802-3-raw': 3, 'ethernet-ii': 2, 'not-applicable': 1, 'ieee-802-2': 4.

DURABLE: The IPX Network number for this interface. If this object is 00000000, then the unit has not yet determined the network number.

DURABLE: The unit may generate IPX SAP broadcasts. This allows the unit to be auto-discovered. By setting this object to do-ipx-SAPs(1), the unit will generate SAP broadcasts at a rate of one every 60 seconds. By setting this object to no-ipx-SAPs(2), the hub will not generate SAP broadcasts. Enumeration: 'no-ipx-SAPs': 2, 'do-ipx-SAPs': 1.

A table of BOOTP configuration information for each management agent interface. This table controls the BOOTP behavior of the basic booting system. Other software components installed in a unit may also do BOOTP. This table does not control those components.

A list of BOOTP configuration information for each management agent interface.

This is the ifIndex value of an interface in the MIB-II interface table for which this table entry applies.

DURABLE: This object allows the user to enable/disable generation of BOOTP requests on the interface specified by cpqnBootpIfIndex. BOOTP requests can be generated over the SNAP frame type, Ethernet-II frame type, or both. Enumeration: 'enable-bootp-ieee-802-2-snap': 3, 'disable-bootp': 1, 'enable-bootp-both': 4, 'enable-bootp-ethernet-ii': 2.

DURABLE: This determines the number of BOOTP requests that will be transmitted from the interface indicated by cpqnBootpIfIndex. This object is used in conjunction with the cpqnBootpRetryInterval object. If both frame types are enabled, then for each try, two BOOTP frames will be generated, one for each frame type. WARNING: Remember that while the unit is booting up, management may not be available, so be careful in selecting the number of retries and the interval for BOOTP. If these values are large, then the SNMP agent could be delayed in starting up by a significant time.

DURABLE: This object allows the user to set the time period (in seconds) between the transmission of BOOTP requests on the interface specified by cpqnBootpIfIndex. This object is used in conjunction with the cpqnBootpRetries object. WARNING: Remember that while the unit is booting up, management may not be available, so be careful in selecting the number of retries and the interval for BOOTP. If these values are large, then the SNMP agent could be delayed in starting up by a significant time.

The IP address of the BOOTP Server that last responded on the interface indicated by cpqnBootpIfIndex. If no BOOTP server has responded, then this object will be '0.0.0.0'.