|
|
This chapter describes those individual MIB objects that comprise the PXM45-specific MIB files. These objects are taken from the following MIBs, each of which constitutes a section of this chapter:
The supported objects in ENTITY MIB are the Physical Table, Physical Contains Table, and Last Change Time. Other tables will not be described here. This MIB module represents multiple logical entities supported by a single SNMP agent.
Integer (1..2147483647)
current
This object is an arbitrary value which uniquely identifies the physical entity. The value should be a small positive integer; index values for different physical entities are not necessarily contiguous.
Integer {other(1), unknown(2), chassis(3), backplane(4), container(5), (for example, a chassis slot or daughter-card holder) powerSupply(6), fan(7), sensor(8), module(9), (for example, a plug-in card or daughter-card) port(10), stack(11) (for example, a stack of multiple chassis entities)}
current
This object is an enumerated value which provides an indication of the general hardware type of a particular physical entity. There are no restrictions as to the number of entPhysicalEntries of each entPhysicalClass, which must be instantiated by an agent. The enumeration other is applicable if the physical entity class is known, but does not match any of the supported values.
The enumeration unknown is applicable if the physical entity class is unknown to the agent. The enumeration chassis is applicable if the physical entity class is an overall container for networking equipment. Any class of physical entity except a stack may be contained within a chassis, and a chassis may only be contained within a stack.
The enumeration backplane is applicable if the physical entity class is a device for aggregating and forwarding networking traffic, such as a shared backplane in a modular ethernet switch. Note that an agent may model a backplane as a single physical entity, which is actually implemented as multiple discrete physical components (within a chassis or stack).
The enumeration container is applicable if the physical entity class is capable of containing one or more removable physical entities, possibly of different types. For example, each (empty or full) slot in a chassis will be modeled as a container. Note that all removable physical entities should be modeled within a container entity, such as field-replaceable modules, fans, or power supplies. Note that all known containers should be modeled by the agent, including empty containers. The enumeration powerSupply is applicable if the physical entity class is a power-supplying component.
The enumeration fan is applicable if the physical entity class is a fan or other heat-reduction component.The enumeration sensor is applicable if the physical entity class is a sensor, such as a temperature sensor within a router chassis.
The enumeration module is applicable if the physical entity class is a self-contained sub-system. If it is removable, then it should be modeled within a container entity, otherwise it should be modeled directly within another physical entity (for example, a chassis or another module).
The enumeration port is applicable if the physical entity class is a networking port, capable of receiving and/or transmitting networking traffic. The enumeration stack is applicable if the physical entity class is a super-container (possibly virtual), intended to group together multiple chassis entities. A stack may be realized by a virtual cable, a real interconnect cable, attached to multiple chassis, or may in fact be comprised of multiple interconnect cables. A stack should not be modeled within any other physical entities, but a stack may be contained within another stack. Only chassis entities should be contained within a stack.
Octet String (SIZE(0..32))---empty string or SnmpEngineID
current
This object is a specially formatted SnmpEngineID string for use with the ENTITY MIB.
If an instance of an object of syntax SnmpEngineIdOrNone has a non-zero length, then the object encoding and semantics are defined by the SnmpEngineID textual convention (refer to RFC2571).
If an instance of an object of syntax SnmpEngineIdOrNone contains a zero-length string, then no appropriate SnmpEngineID is associated with the logical entity (that is SNMPv3 is not supported).
Sequence of EntPhysicalEntry
not-accessible
current
This table contains one row per physical entity. There is always at least one row for an 'overall' physical entity.
::= { entityPhysical 1 }
entPhysicalEntry
not-accessible
current
This object provides information about a particular physical entity. Each entry provides objects (entPhysicalDescr, entPhysicalVendorType, and entPhysicalClass) to help a NMS identify and characterize the entry, and the objects entPhysicalContainedIn and entPhysicalParentRelPos, to relate this entry to other entries in this table.
{ entPhysicalIndex }
::= { entPhysicalTable 1 }
The entPhysicalEntry Sequence is shown in Table 2-1.
| Object | Syntax |
|---|---|
PhysicalIndex | |
SnmpAdminString | |
AutonomousType | |
Integer | |
PhysicalClass | |
Integer | |
SnmpAdminString | |
SnmpAdminString | |
SnmpAdminString | |
SnmpAdminString | |
SnmpAdminString | |
SnmpAdminString | |
SnmpAdminString | |
SnmpAdminString | |
SnmpAdminString | |
TruthValue |
PhysicalIndex
not-accessible
current
The object is the index for this entry.
::= { entPhysicalEntry 1 }
SnmpAdminString
read-only
current
This object provides a textual description of a physical entity. This object should contain a string which identifies the manufacturer's name for the physical entity, and should be set to a different value for each version or model of the physical entity.
::= { entPhysicalEntry 2 }
AutonomousType
read-only
current
This object indicates the vendor-specific hardware type of the physical entity. Note that this is different from the definition of MIB-II's sysObjectID.
An agent should set this object to a enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device.
If no vendor-specific registration identifier exists for this physical entity, or the value is unknown by this agent, then the value { 0 0 } is returned.
For possible values of this object, see Table 1-5.
::= { entPhysicalEntry 3 }
Integer (0..2147483647)
read-only
current
This object is the value of entPhysicalIndex for the physical entity containing this object. A value of zero indicates this physical entity is not contained in any other physical entity. Note that the set of containment relationships define a strict hierarchy; that is, recursion is not allowed.
In the event a physical entity is contained by more than one physical entity (for example, double-wide modules), this object should identify the containing entity with the lowest value of entPhysicalIndex.
::= { entPhysicalEntry 4 }
PhysicalClass
read-only
current
This object indicates the general hardware type of the physical entity.
An agent should set this object to the standard enumeration value which most accurately indicates the general class of the physical entity, or the primary class if there is more than one.
If no appropriate standard registration identifier exists for this physical entity, then the value other(1) is returned. If the value is unknown by this agent, then the value unknown(2) is returned.
::= { entPhysicalEntry 5 }
Integer (-1..2147483647)
read-only
current
This object indicates the relative position of this child component among all its sibling components. Sibling components are defined as entPhysicalEntries which share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects.
An NMS can use this object to identify the relative ordering for all sibling components of a particular parent (identified by the entPhysicalContainedIn instance in each sibling entry).
This value should match any external labeling of the physical component if possible. For example, for a container (for example, card slot) labeled as slot #3, entPhysicalParentRelPos should have the value 3. Note that the entPhysicalEntry for the module plugged in slot 3 should have an entPhysicalParentRelPos value of 1.
If the physical position of this component does not match any external numbering or clearly visible ordering, then user documentation or other external reference material should be used to determine the parent-relative position. If this is not possible, then the agent should assign a consistent (but possibly arbitrary) ordering to a given set of sibling components, perhaps based on internal representation of the components.
If the agent cannot determine the parent-relative position for some reason, or if the associated value of entPhysicalContainedIn is 0, then the value -1 is returned. Otherwise a non-negative integer is returned, indicating the parent-relative position of this physical entity.
Parent-relative ordering normally starts from 1 and continues to N, where N represents the highest positioned child entity. However, if the physical entities (for example, slots) are labeled from a starting position of zero, then the first sibling should be associated with a entPhysicalParentRelPos value of 0. Note that this ordering may be sparse or dense, depending on agent implementation.
The actual values returned are not globally meaningful, as each parent component may use different numbering algorithms. The ordering is only meaningful among siblings of the same parent component.
The agent should retain parent-relative position values across reboots, either through algorithmic assignment or use of non-volatile storage.
::= { entPhysicalEntry 6 }
SnmpAdminString
read-only
current
This object is the textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's console. This might be a text name, such as console, or a simple component number (for example, port or module number), such as 1, depending on the physical component naming syntax of the device. If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string.
Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, for example, slot-1 and the card in slot-1.
::= { entPhysicalEntry 7 }
SnmpAdminString
read-only
current
This object is the vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present).
Note that if revision information is stored internally in a non-printable format, (for example, binary) , then the agent must convert such information to a printable format, in an implementation-specific manner.
If no specific hardware revision string is associated with the physical component, or this information is unknown to the agent, then this object will contain a zero-length string.
::= { entPhysicalEntry 8 }
SnmpAdminString
read-only
current
This object is the vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable format, (for example, binary), then the agent must convert such information to a printable format, in an implementation-specific manner.
If no specific firmware programs are associated with the physical component, or this information is unknown to the agent, then this object will contain a zero-length string.
::= { entPhysicalEntry 9 }
SnmpAdminString
read-only
current
This object is the vendor-specific software revision string for the physical entity. Note that if revision information is stored internally in a non-printable format, (for example, binary), then the agent must convert such information to a printable format, in an implementation-specific manner.
If no specific software programs are associated with the physical component, or this information is unknown to the agent, then this object will contain a zero-length string.
::= { entPhysicalEntry 10 }
SnmpAdminString (SIZE (0..32))
read-write
current
This object is the vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present).
On the first instantiation of an physical entity, the value of entPhysicalSerialNum associated with that entity is set to the correct vendor-assigned serial number, if this information is available to the agent. If a serial number is unknown or non-existent, the entPhysicalSerialNum will be set to a zero-length string instead.
Note that implementations which can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the entPhysicalSerialNum object. Agents which cannot provide non-volatile storage for the entPhysicalSerialNum strings are not required to implement write access for this object.
Not every physical component will have a serial number, or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to false(2) (for example, the repeater ports within a repeater module), do not need their own unique serial number. An agent does not have to provide write access for such entities, and may return a zero-length string.
If write access is implemented for an instance of entPhysicalSerialNum, and a value is written into the instance, the agent must retain the supplied value in the entPhysicalSerialNum instance associated with the same physical entity for as long as that entity remains instantiated. This includes instantiations across all re- initializations/reboots of the network management system, including those which result in a change of the physical entity's entPhysicalIndex value.
::= { entPhysicalEntry 11 }
SnmpAdminString
read-only
current
This object is the manufacturer's name of the of this physical component. The preferred value is the manufacturer name string actually printed on the component itself (if present).
Note that comparisons between instances of the entPhysicalModelName, entPhysicalFirmwareRev, entPhysicalSoftwareRev, and the entPhysicalSerialNum objects, are only meaningful among entPhysicalEntries with the same value of entPhysicalMfgName.
If the manufacturer name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string.
::= { entPhysicalEntry 12 }
SnmpAdminString
read-only
current
This object is the model name identifier string associated with this physical component. It is different for each vendor. The preferred value is the customer-visible part number, which may be printed on the component itself.
If the model name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string.
::= { entPhysicalEntry 13 }
SnmpAdminString (SIZE (0..32))
read-write
current
This object is an alias name for the physical entity as specified by a network manager, and provides a non-volatile handle for the physical entity.
On the first instantiation of a physical entity, the value of entPhysicalAlias is set to the zero-length string. However, the agent may set the value to a locally unique default value, instead of a zero-length string.
If write access is implemented for an instance of entPhysicalAlias, and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAlias instance associated with the same physical entity for as long as that entity remains instantiated. This includes instantiations across all re-initializations and reboots of the network management system, including those which result in a change of the physical entity's entPhysicalIndex value.
::= { entPhysicalEntry 14 }
SnmpAdminString (SIZE (0..32))
read-write
current
This object is a user-assigned asset tracking identifier for the physical entity as specified by a network manager, and provides non-volatile storage of this information. On the first instantiation of an physical entity, the value of entPhysicalAssetID is set to the zero-length string.
Not every physical component will have an asset tracking identifier, or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to false(2) (that is, the repeater ports within a repeater module), do not need their own unique asset tracking identifier. An agent does not have to provide write access for such entities, and may instead return a zero-length string.
If write access is implemented for an instance of entPhysicalAssetID, and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAssetID instance associated with the same physical entity for as long as that entity remains instantiated. This includes instantiations across all re-initializations and reboots of the network management system, including those which result in a change of the physical entity's entPhysicalIndex value.
If no asset tracking information is associated with the physical component, then this object will contain a zero-length string.
::= { entPhysicalEntry 15 }
TruthValue
read-only
current
This object indicates whether or not this physical entity is considered a field replaceable unit by the vendor. If this object contains the value true (1) then this entPhysicalEntry identifies a field replaceable unit. For all entPhysicalEntries which represent components that are permanently contained within a field replaceable unit, the value false (2) should be returned for this object.
::= { entPhysicalEntry 16 }
Sequence of entPhysicalContainsEntry
not-accessible
current
This table exposes the container and or containee relationships between physical entities. This table provides all the information found by constructing the virtual containment tree for a given entPhysicalTable, but in a more direct format.
In the event a physical entity is contained by more than one other physical entity (for example, double-wide modules), this table should include these additional mappings, which cannot be represented in the entPhysicalTable virtual containment tree.
::= { entityMapping 3 }
entPhysicalContainsEntry
not-accessible
current
This object indicates a single container and or containee relationship.
{ entPhysicalIndex, entPhysicalChildIndex }
::= { entPhysicalContainsTable 1 }
PhysicalIndex
read-only
current
This object is the value of entPhysicalIndex for the contained physical entity.
::= { entPhysicalContainsEntry 1 }
TimeStamp
read-only
current
This object is the value of sysUpTime when a conceptual row is created, modified, or deleted in any of these tables:
::= { entityGeneral 1 }
This MIB was extracted from RFC 2233. This MIB module describes generic network interface sub-layers. This MIB is an updated version of MIB-II's ifTable, and incorporates the extensions defined in RFC 1229.
OCTET STRING (SIZE(0..255))
InterfaceIndex contains the semantics of ifIndex and should be used for any syntax defined on other MIB modules that need these semantics.
255a
current
This data type is used to model an administratively-assigned name of the resource-owner. This information is taken from the NVT ASCII character set. It is suggested that this name contain one or more of the following:
In some cases the agent itself will be the owner of an entry. In these cases, start of the string shall be the agent substring.
Integer32 (1..2147483647)
d
current
A unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
Integer32 (0..2147483647)
d
current
This textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. The value zero is specific and must therefore be defined as part of the description of any object using this syntax. Examples of the usage of zero might include situations when the interface was unknown, or when none or all interfaces need to be referenced.
Integer32
read-only
current
The number of network interfaces (regardless of their current state) present on this system.
::= { interfaces 1 }
TimeTicks
read-only
current
This object is the value of sysUpTime at the last creation or deletion of an entry in the ifTable. If the number of entries has been unchanged since the last re-initialization of the local network management subsystem, then this contains a zero value.
The Interfaces Table contains information on the entity's interfaces. Each sub-layer below the internetwork layer of a network interface is considered to be an interface.
Sequence of IfEntry
not-accessible
current
This table is a list of interface entries. The number of entries is given by the value of ifNumber.
::= { interfaces 2 }
IfEntry
not-accessible
current
This object is an entry containing management information applicable to a particular interface.
{ ifIndex }
::= { ifTable 1 }
The IfEntry Sequence table is shown in Table 2-2.
| Object | Syntax |
|---|---|
InterfaceIndex | |
DisplayString | |
IANAifType | |
Integer32 | |
Gauge32 | |
PhysAddress | |
Integer | |
Integer | |
TimeTicks | |
Counter32 | |
Counter32 | |
Counter32 (deprecated) | |
Counter32 | |
Counter32 | |
Counter32 | |
Counter32 | |
Counter32 | |
Counter32 (deprecated) | |
Counter32 | |
Counter32 | |
Gauge32 (deprecated) | |
IDENTIFIER (deprecated) |
InterfaceIndex
read-only
current
This object is a unique value, greater than zero, for each interface. It is recommended that values be assigned contiguously starting from 1. The value for each interface sub-layer must remain constant from one re-initialization of the entity's network management system to the next re-initialization.
::= { ifEntry 1 }
 |
Note For the Cisco MGX 8850, the values may not be contiguous and will not start from 1. The ifIndex association with a physical interface or a logical interface is found in ifName object. |
DisplayString (SIZE (0..255))
read-only
current
This object is a textual string containing information about the interface. This string should include the name of the manufacturer, the product name, and the version of the interface hardware/software.
An example might be the association of the interface with a physical or logical interface.
::= { ifEntry 2 }
IANAifType
read-only
current
This object indicates the type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA), by updating the syntax of the IANAifType textual convention.
::= { ifEntry 3 }
Integer32
read-only
current
This object indicates the size of the largest packet which can be sent and received on the interface, specified in octets. For interfaces that are used for transmitting network datagrams, this is the largest network datagram that can be sent on the interface.
::= { ifEntry 4 }
Gauge32
read-only
current
This object is an estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or no accurate estimation can be made, ifSpeed should indicate the nominal bandwidth. If the bandwidth of the interface is greater than the maximum value reportable, then ifSpeed should report its maximum value (4,294,967,295) and ifHighSpeed must be used to report the interface's speed. For a sub-layer which has no concept of bandwidth, ifSpeed should be zero.
::= { ifEntry 5 }
PhysAddress
read-only
current
This object indicates the interface's address at its protocol sub-layer. For example, for an interface normally contains a MAC address. The interface's media-specific MIB must define the bit and byte ordering and the format of the value of this address. For interfaces which do not have such an address (for example, a serial line), ifPhysAddress should contain an octet string of zero length.
::= { ifEntry 6 }
Integer {up (1), ready to pass packets down; (2), testing; (3) in some test mode}
read-write
current
This object indicates the desired state of the interface. The testing (3) state indicates no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down (2) state. As a result of either explicit management action or through configuration information retained by the managed system, ifAdminStatus is then changed to either the up (1), testing (3), or remains in the down (2) state.
::= { ifEntry 7 }
Integer {up (1), ready to pass packets; down (2); testing (3), in some test mode; unknown (4), status can not be determined; dormant (5); notPresent (6), some component is missing; lowerLayerDown (7), down due to state of lower-layer interface(s)}
read-only
current
This object indicates current operational state of the interface. The testing (3) state indicates that no operational packets can be passed. If ifAdminStatus is down (2) then ifOperStatus should be down (2). If ifAdminStatus is changed to up (1) then ifOperStatus should change to up (1). If the interface is ready to transmit and receive network traffic, it should change to dormant (5) when the interface is waiting for external actions (such as a serial line waiting for an incoming connection). It should remain in the down (2) state if and only if there is a fault that prevents it from going to the up (1) state. It should remain in the notPresent (6) state if the interface has missing hardware components.
::= { ifEntry 8 }
TimeTicks
read-only
current
This object indicates the value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this contains a zero value.
::= { ifEntry 9 }
Counter32
read-only
current
This object indicates the total number of octets received on the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 10 }
Counter32
read-only
current
This object indicates the number of packets delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 11 }
Counter32
read-only
deprecated
This object indicates the number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast or broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. This is deprecated in favour of ifInMulticastPkts and ifInBroadcastPkts.
::= { ifEntry 12 }
Counter32
read-only
current
This object indicates the number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 13 }
Counter32
read-only
current
For packet-oriented interfaces, the is object indicates the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 14 }
Counter32
read-only
current
For packet-oriented interfaces, this object indicates the number of packets received through the interface which were discarded because of an unknown or unsupported protocol. For character-oriented or fixed-length interfaces that support protocol multiplexing, this object indicates the number of transmission units received through the interface which were discarded because of an unknown or unsupported protocol. For an interface that does not support protocol multiplexing, this counter will always be 0. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 15 }
Counter32
read-only
current
This object indicates the number of octets transmitted out of the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 16 }
Counter32
read-only
current
This object indicates the number of packets that were requested for transmission by higher-level protocols, which were not addressed to a multicast or broadcast address at this sub-layer. The number includes those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times, as indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 17 }
Counter32
read-only
deprecated
This object indicates the number of packets that were requested for transmission by higher-level protocols, which were addressed to a multicast or broadcast address at this sub-layer. The number includes those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. This is deprecated in favour of ifOutMulticastPkts and ifOutBroadcastPkts.
::= { ifEntry 18 }
Counter32
read-only
current
This object indicates the number of outbound packets chosen to be discarded, even though no errors have been detected to prevent their transmission. One possible reason for discarding such a packet could be to free up buffer space. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 19 }
Counter32
read-only
current
For packet-oriented interfaces, this object indicates the number of outbound packets that could not be transmitted because of errors. For character-oriented or fixed-length interfaces, this object indicates the number of outbound transmission units that can not be transmitted because of errors. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifEntry 20 }
Gauge32
read-only
deprecated
This object indicates the length of the output packet queue (in packets).
::= { ifEntry 21 }
IDENTIFIER
read-only
deprecated
This object refers to MIB definitions specific to the particular media being used to realize the interface. It is recommended that this value point to an instance of a MIB in the media-specific MIB. The pointer should have the semantics associated with the Instance Pointer textual convention defined in RFC 1903. In fact, it is recommended that the media-specific MIB specify what value ifSpecific should take for values of ifType. If no MIB definitions specific to the particular media are available, the value should be set to the IDENTIFIER { 0 0 }.
::= { ifEntry 22 }
This table replaces the ifExtnsTable table.
SEQUENCE OF IfXEntry
not-accessible
current
This table is a list of interface entries. The number of entries is given by the value of ifNumber. This table contains additional entries for the interface table.
::= { ifMIBobjects 1 }
IfXEntry
not-accessible
current
This is an entry containing additional management information applicable to a particular interface.
{ ifEntry }
::= { ifXTable 1 }
The IfX Entry Sequence table is shown in Table 2-3.
| Object | Syntax |
|---|---|
DisplayString | |
Counter32 | |
Counter32 | |
Counter32 | |
Counter32 | |
Counter64 | |
Counter64 | |
Counter64 | |
Counter64 | |
Counter64 | |
Counter64 | |
Counter64 | |
Counter64 | |
Integer | |
Gauge32 | |
TruthValue | |
DisplayString | |
TimeStamp |
DisplayString
read-only
current
This object is the textual name of the interface. The value of ifName should be the name of the interface as assigned by the local device and should be suitable for use in commands entered at the device's console. This might be a text name, such as le0 or a simple port number, such as 1, depending on the interface naming syntax of the device. If several entries in the ifTable together represent a single interface as named by the device, then each will have the same value of ifName. Note that for an agent which responds to SNMP queries concerning an interface on some other (proxy) device, then the value of ifName for such an interface is the proxy device's local name for it. If there is no local name, or if ifName is not applicable, then this object contains a zero length string.
For the Cisco MGX 8850, ifName contains the physical or logical association of a name. shows three examples that illustrate the value(s) for ifName object. The actual values depend on the implementation.
| ifDescr | ifName | Remarks |
|---|---|---|
<string> | rs232MP.7.1.1 | Association of RS232 Maintenance Port Logical Slot 7, Bay 1, Port 1 |
<string> | ethernet.7.1.1 | Association of Ethernet Port Logical Slot 1, Bay 1, Port 1 |
<string> | slip.7.1.2.1 | Association of slip Logical Slot 7, Bay 1 rs232port 2, Interface 1 |
There are three conventions that are used for the value of ifName objects. These apply to physical lines, ATM physical lines, and ATM virtual interfaces.
This format is used for Physical Lines such as SONET, DS3, DS1, and so on
<lineType>.<logical-slot>.<bay>.<lineNumber>
where
Examples:
This format is used for ATM Physical Interfaces.
atm.<logical-slot>.<bay>.<lineNumber>
where
Examples:
This format is used for ATM Virtual Interfaces (atmVirtual)
atmVirtual.<logical-slot>.<bay>.<lineNumber>.<vi-number>.[<vpi-number>]
where
Examples
::= { ifXEntry 1 }
Counter32
read-only
current
This object indicates the number of packets delivered by this sub-layer to a higher sub-layer, addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both groups and functional addresses. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 2 }
Counter32
read-only
current
This object indicates the number of packets, delivered by this sub-layer to a higher sub-layer, which was addressed to a broadcast address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 3 }
Counter32
read-only
current
This object indicates the number of packets that higher-level protocols requested be transmitted, which were addressed to a multicast address, including those that were discarded or not sent. Both group and functional addresses are included if requested by a MAC layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 4 }
Counter32
read-only
current
This object indicates the number of packets that higher-level protocols requested be transmitted, which were addressed to a broadcast address at this sub-layer. The object includes those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 5 }
These counters are all 64 bit versions of the basic ifTable counters. They all have the same basic semantics as their 32-bit counterparts; their syntax has been extended to 64 bits.
Counter64
read-only
current
This object indicates the number of octets received on the interface, including framing characters. ifHCInOctets is a 64-bit version of ifInOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
Counter64
read-only
current
This object indicates the number of packets, delivered by this sub-layer to a higher sub-layer, which were not addressed to a multicast or broadcast address at this sub-layer. This is a 64-bit version of ifInUcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 7 }
Counter64
read-only
current
This object indicates the number of packets delivered by a sub-layer to a higher sub-layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both group and functional addresses. This is a 64-bit version of ifInMulticastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 8 }
Counter64
read-only
current
This object indicates the number of packets, delivered by a lower sub-layer to a higher sub-layer, which were addressed to a broadcast address at the lower sub-layer. This is a 64-bit version of ifInBroadcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 9 }
Counter64
read-only
current
This object indicates the number of octets transmitted out of the interface, including framing characters. This is a 64-bit version of ifOutOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 10 }
Counter64
read-only
current
This object indicates the number of packets that higher-level protocols requested be transmitted, which were not addressed to a multicast or broadcast address at this sub-layer. This includes those packets that were discarded or not sent. This is a 64-bit version of ifOutUcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 11 }
Counter64
read-only
current
This object indicates the total number of packets that higher-level protocols requested be transmitted, which were addressed to a multicast address at this sub-layer. This includes those packets that were discarded or not sent. For a MAC layer protocol, this includes both group and functional addresses. This is a 64-bit version of ifOutMulticastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
::= { ifXEntry 12 }
Counter64
read-only
current
This object indicates the number of packets that higher-level protocols requested be transmitted, which were addressed to a broadcast address at this sub-layer. This includes those packets that were discarded or not sent. This is a 64-bit version of ifOutBroadcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
Integer { enabled (1), disabled (2) }
read-write
current
This object indicates whether linkUp or linkDown traps should be generated for this interface. By default, this should have the value enabled (1) for interfaces which do not operate on top of any other interface (as defined in the ifStackTable), and disabled (2) otherwise.
::= { ifXEntry 14 }
Gauge32
read-only
current
This object provides an estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this reports a value of n then the speed of the interface is from n-500,000 to n+499,999. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, ifHighSpeed should contain the nominal bandwidth. For a sub-layer having a defined bandwidth, the value should be zero.
::= { ifXEntry 15 }
TruthValue
read-write
current
This object has a value of false (2) if the interface only accepts packets or frames that are addressed to this station. It has a value of true (1) when the station accepts all packets/frames transmitted on the media. The value true (1) is only valid on certain types of media. If valid, setting ifPromiscuousMode to a value of true (1) may require the interface to be reset before becoming effective. The value of ifPromiscuousMode does not effect the reception of broadcast and multicast packets or frames by the interface.
::= { ifXEntry 16 }
TruthValue
read-only
current
This object has the value true (1) if the interface sublayer has a physical connector and the value false (2) otherwise.
::= { ifXEntry 17 }
DisplayString (SIZE(0..64))
read-write
current
This object is an alias for the interface as specified by a network manager. It provides a non-volatile handle for the interface. On the first instance of an interface, the value of ifAlias associated with that interface is the zero-length string. When a value is written into ifAlias through a network management set operation, then the agent must retain the supplied value in the ifAlias instance associated with the same interface. The agent must retain this supplied value for as long as that interface remains instantiated. The duration that the interface remains instantiated includes all re- initializations and reboots of the network management system, including those which result in a change of the interface's ifIndex value.
An example of the value which a network manager might store in ifAlias for a WAN interface is the Telco's circuit number/identifier of the interface.
Some agents may support write-access only for interfaces having particular values of ifType. An agent which supports write access to this is required to keep the value in non-volatile storage, but it may limit the length of new values depending on how much storage is occupied by the current values for other interfaces.
::= { ifXEntry 18 }
TimeStamp
read-only
current
This object indicates the sysUpTime value on the most recent occasion one or more of this interface's counters suffered a discontinuity. The relevant counters are the specific instances associated with this interface of any Counter32 or Counter64 contained in the ifTable or ifXTable. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
::= { ifXEntry 19 }
{ifIndex, ifAdminStatus, ifOperStatus}
current
A linkDown trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifOperStatus for one of its communication links is about to enter the down state. This may be from any other state except the notPresent state. This previous state is indicated by the included value of ifOperStatus.
::= { snmpTraps 3 }
{ifIndex, ifAdminStatus, ifOperStatus}
current
A linkUp trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifOperStatus for one of its communication links left the down state and transitioned into some other state. This includes any previous state except the notPresent state. This previous state is indicated by the included value of ifOperStatus.
::= { snmpTraps 4 }
current
The compliance statement for SNMPv2 entities which have network interfaces.
PXM45
{ifGeneralInformationGroup, ifStackGroup2, ifCounterDiscontinuityGroup}
The description of each group is shown in Table 2-5.
| Group | Description |
|---|---|
This group is mandatory for all network interfaces which are character-oriented or transmit data in fixed-length transmission Units. | |
This group is mandatory only for those network interfaces which are character-oriented or transmit data in fixed-length transmission Units, and for which the value of the corresponding instance of ifSpeed is greater than 20 million bits/second. | |
This group is mandatory for all network interfaces which are packet-oriented. | |
This group is mandatory only for those network interfaces which are packet-oriented and for which the value of the corresponding instance of ifSpeed is greater than 650 million bits/second. | |
The applicability of this group must be defined by the media-specific MIBs. Media-specific MIBs must define the exact meaning, use, and semantics of the addresses in this group. |
read-only
Write access is not required for this object.
read-only
Write access is not required for this object.
Integer {active(1)} (a subset of RowStatus)
read-only
Write access is not required for this object. Only one of the six enumerated values for the RowStatus textual convention need be supported, specifically: active (1).
Integer {up(1), down(2)}
read-only
Write access is not required for this object, nor is support for the value testing(3).
read-only
Write access is not required for this object.
::= { ifCompliances 2 }
{ifIndex, ifDescr, ifType, ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange, ifLinkUpDownTrapEnable, ifConnectorPresent, ifHighSpeed, ifName, ifNumber, ifAlias, ifTableLastChange}
current
This group is a collection of objects that provides information applicable to all network interfaces.
::= { ifGroups 10 }
|
Note The following five groups ifFixedLengthGroup, ifPacketGroup, ifHCPacketGroup, ifVHCPacketGroup, and ifRcvAddressGroup are mutually exclusive; only one of these groups is implemented for any interface. |
{ifInOctets, ifOutOctets, ifInUnknownProtos, ifInErrors, ifOutErrors}
current
This group is a collection of objects that provides information specific to non-high speed character-oriented or fixed-length-transmission network interfaces.
|
Note Non-high speed interfaces are defined as those that transmit and receive at speeds less than or equal to 20 million bits/second. |
::= { ifGroups 2 }
{ifHCInOctets, ifHCOutOctets, ifInOctets, ifOutOctets, ifInUnknownProtos, ifInErrors, ifOutErrors }
current
This group is collection of objects that provides information specific to high speed (greater than
20 million bits/second) that are either character-oriented or fixed-length-transmission network interfaces.
::= { ifGroups 3 }
{ifInOctets, ifOutOctets, ifInUnknownProtos, ifInErrors, ifOutErrors, ifMtu, ifInUcastPkts, ifInMulticastPkts, ifInBroadcastPkts, ifInDiscards, ifOutUcastPkts, ifOutMulticastPkts, ifOutBroadcastPkts, ifOutDiscards, ifPromiscuousMode}
current
This group is a collection of objects that provides information specific to non-high speed (non-high speed interfaces transmit and receive at speeds less than or equal to 20 millionbits/second) packet-oriented network interfaces.
::= { ifGroups 4 }
{ifHCInOctets, ifHCOutOctets, ifInOctets, ifOutOctets, ifInUnknownProtos, ifInErrors, ifOutErrors, ifMtu, ifInUcastPkts, ifInMulticastPkts, ifInBroadcastPkts, ifInDiscards, ifOutUcastPkts, ifOutMulticastPkts, ifOutBroadcastPkts, ifOutDiscards, ifPromiscuousMode}
current
This group is a collection of objects that provides information specific to high speed (greater than
20 million bits/second but less than or equal to 650 million bits/second) packet-oriented network interfaces.
::= { ifGroups 5 }
{ifHCInUcastPkts, ifHCInMulticastPkts, ifHCInBroadcastPkts, ifHCOutUcastPkts, ifHCOutMulticastPkts, ifHCOutBroadcastPkts, ifHCInOctets, ifHCOutOctets, ifInOctets, ifOutOctets, ifInUnknownProtos, ifInErrors, ifOutErrors, ifMtu, ifInUcastPkts, ifInMulticastPkts, ifInBroadcastPkts, ifInDiscards, ifOutUcastPkts, ifOutMulticastPkts, ifOutBroadcastPkts, ifOutDiscards, ifPromiscuousMode}
current
This group is a collection of objects that provides information specific to higher speed (greater than
650 million bits/second) packet-oriented network interfaces.
::= { ifGroups 6 }
{ifRcvAddressStatus, ifRcvAddressType}
current
This group is a collection of objects that provides information on the multiple addresses which an interface receives.
::= { ifGroups 7 }
{ifStackStatus, ifStackLastChange}
current
This group is a collection of objects that provides information on the layering of MIB-II interfaces.
::= { ifGroups 11 }
{ifCounterDiscontinuityTime}
current
This group is a collection of objects that provides information specific to interface counter discontinuities.
::= { ifGroups 13 }
deprecated
This object is the deprecated compliance statement for SNMPv2 entities which have network interfaces.
PXM45
{ifGeneralGroup, ifStackGroup}
Table 2-6 shows the description of each group.
| Group | Description |
|---|---|
This group is mandatory for all network interfaces which are character-oriented or transmit data in fixed-length transmission units. | |
This group is mandatory only for those network interfaces which are character-oriented or transmit data in fixed-length transmission units, and for which the value of the corresponding instance of | |
This group is mandatory for all network interfaces which are packet-oriented. | |
This group is mandatory only for those network interfaces which are packet-oriented and for which the value of the corresponding instance of ifSpeed is greater than 650 million bits/second. | |
The applicability of this group must be defined by the media-specific MIBs. Media-specific MIBs must define the exact meaning, use, and semantics of the addresses in this group. |
read-only
Write access is not required for this object.
read-only
Write access is not required for this object.
Integer {active(1)} (subset of RowStatus)
read-only
Write access is not required for this object. Only one of the six enumerated values for the RowStatus textual convention need support, specifically: active (1).
Integer {up(1), down(2)}
read-only
Write access is not required for this object, nor is support for the value testing (3).
::= { ifCompliances 1 }
The CISCO ENTITY FRU CONTROL MIB is used to monitor and configure operational Status of Field Replaceable Units (FRUs) of the system listed in the ENTITY MIB (RFC 2037) entPhysicalTable.
FRUs include assemblies such as power supplies, fans, processor modules, interface modules, and so forth.
Integer {notsupported (1), redundant (2), combined (3)}
current
Valid values of power supply redundancy modes are shown in Table 2-7
| Value | Meaning |
|---|---|
notsupported(1) | Operational state , indicates only that the requested administrative state [redundant (2) or combined (3)] is not supported by the system. |
redundant(2) | A single power supply output can power the entire system, although there may be more than one supply in the system. For example, a system with one 1000-watt supply and one 1300-watt supply would be rated to power 1000-watts of FRUs. |
combined(3) | The combined output of the power supplies are available to operate the system. For example, two 1000-watt supplies in combined-mode supply 2000 watts to the system. |
Integer {on(1), off(2)}
current
This object sets the administratively desired FRU power state types. Valid values are on (1), Turn FRU on; and off (2), Turn FRU off.
Integer {offEnvOther(1), on(2), offAdmin(3), offDenied(4), offEnvPower(5), offEnvTemp(6), offEnvFan(7)}
current
This object sets the operational FRU Status types. Valid values are shown in Table 2-8
| Value | Meaning |
|---|---|
offEnvOther(1) | FRU is powered off because of a problem not listed below. |
on(2) | FRU is powered on. |
offAdmin(3) | Administratively off. |
offDenied(4) | FRU is powered off because available system power is insufficient. |
offEnvPower(5) | FRU is powered off because of a power problem. For example, the FRU's power translation (DC-DC converter) or distribution failed. |
offEnvTemp(6) | FRU is powered off because of a temperature problem. |
offEnvFan(7) | FRU is powered off because of fan problems. |
Integer ( -1000000000..1000000000 )
current
This object shows a current measurement, on the system power supply primary output, n cefcPowerUnits. Range is from negative 1 million to positive one million amperes.
A negative value expresses the current used by the FRU. A positive value expresses the current supplied by the FRU.
Integer {enabled (1), disabled (2), reset (3), outOfServiceAdmin (4)}
current
This object sets the administratively desired module states. Valid values are shown in Table 2-9.
| Value | Meaning |
|---|---|
enabled (1) | Module is operational. |
disabled (2) | Module is not operational. |
reset (3) | Module is reset. |
outOfServiceAdmin (4) | Module is powered on but out of service, set by CLI. |
Integer {unknown(1), ok(2), disabled(3), okButDiagFailed(4), boot(5), selfTest(6), failed(7), missing(8), mismatchWithParent(9), mismatchConfig(10), diagFailed(11), dormant(12), outOfServiceAdmin(13), outOfServiceEnvTemp(14)}
current
This object displays the operational module states. Valid values are shown in Table 2-10.
| Value | Meaning |
|---|---|
unknown(1) | Module is not in one of the other recognized operational states. |
ok(2) | Module is operational. |
disabled(3) | Module is disabled administratively. |
okButDiagFailed(4) | Module is operational but there is some diagnostic information available. This is a transitional state. |
boot(5) | Module is in the process of bringing up the image. After boot, it starts its operational software and transitions to the appropriate state. This is a transitional state. |
selfTest(6) | Module is performing a self test. This is a transitional state. |
failed(7) | Module has failed due to some condition not stated above. This is a failure state. |
missing(8) | Module has been provisioned, but it is missing. This is a failure state. |
mismatchWithParent(9) | Module is not compatible with parent entity. Module has not been provisioned; the wrong type of module is plugged in. This state can be cleared by plugging in the appropriate module. This is a failure state. |
mismatchConfig(10) | Module is not compatible with the current configuration. Module was provisioned correctly earlier, however the module was replaced by an incompatible module. This state can be resolved by clearing the configuration or by replacing the appropriate module. This is a failure state |
diagFailed(11) | Module diagnostic test failed due to a hardware failure. This is a failure state. |
dormant(12) | Module is waiting for an external or internal event to become operational. |
outOfServiceAdmin(13) | Module is set administratively to be powered on but out of service. |
outOfServiceEnvTemp(14) | Module is powered on but out of service, due to environmental temperature problem. An out-of-service module consumes less power and will consequently cool down. |
Integer {unknown(1), powerUp(2), parityError(3), clearConfigReset(4), manualReset(5)}
current
This object describes the reason for the last module reset operation. Valid values are shown in Table 2-11.
| Value | Meaning |
|---|---|
unknown(1) | Source of the reset is not identified. |
powerUp(2) | Indicates a system powerup operation. |
parityError(3) | Parity error occurred during system bringup operation. |
clearConfigReset(4) | Reset due to clear configuration operation. |
manualReset(5) | Reset due to administrative request. |
Sequence of cefcModuleEntry
not-accessible
current
A cefcModuleTable entry lists the operation and administrative status information for ENTITY MIB entPhysicalTable entries for FRUs of type PhysicalClass module(9).
::= { cefcModule 1 }
cefcModuleEntry
not-accessible
current
A cefcModuleStatusTable entry lists the operation and administrative status information for ENTITY MIB entPhysicalTable entries for FRUs of type PhysicalClass module (9).
Entries are created by the agent at the system power-up or module insertion.
Entries are deleted by the agent upon module removal.
{entPhysicalIndex}
::= { cefcModuleTable 1 }
The cefcModuleEntry sequence is shown in Table 2-12.
| Object | Syntax |
|---|---|
ModuleAdminType | |
ModuleOperType | |
ModuleResetReasonType | |
TimeStamp |
ModuleAdminType
read-write
current
This object provides administrative control of the module.
::= { cefcModuleEntry 1 }
ModuleOperType
read-only
current
This object shows the module's operational state.
::= { cefcModuleEntry 2 }
ModuleResetReasonType
read-only
current
This object identifies the reason for the last reset performed on the module.
::= { cefcModuleEntry 3 }
TimeStamp
read-only
current
This object displays the value of sysUpTime when the cefcModuleOperStatus is changed.
::= { cefcModuleEntry 4 }
{cefcModuleOperStatus, cefcModuleStatusLastChangeTime}
current
This notification is generated when the value of cefcModuleOperStatus changes. It is utilized by a NMS to update the status of the module it is managing.
::= { cefcMIBNotifications 1 }
{cefcModuleAdminStatus, cefcModuleOperStatus, cefcModuleResetReason, cefcModuleStatusLastChangeTime}
current
This collection of objects is used to get the operational state and redundancy state of the modules.
::= { cefcMIBGroups 3 }
The SENSOR MIB is used to monitor the values of sensors in the ENTITY MIB (refer to RFC 2037) entPhysicalTable.
Integer {other (1), unknown (2), voltsAC (3), voltsDC (4), amperes (5), watts (6), hertz (7), celsius (8), percentRH (9), rpm (10), cmm (11), truthvalue (12), specialEnum (13)}
current
The valid values of SensorDataType are shown in Table 2-13.
| Sensor Measurement | Valid Value(s) |
|---|---|
other(1) | measure other than those listed below |
unknown(2) | unknown measurement, or arbitrary, relative numbers |
voltsAC(3) | electric potential |
voltsDC(4) | electric potential |
amperes(5) | electric current |
watts(6) | power |
hertz(7) | frequency |
celsius(8) | temperature |
percentRH(9) | percent relative humidity |
rpm(10) | shaft revolutions per minute |
cmm(11) | cubic meters per minute (airflow) |
truthvalue(12) | value takes {true(1), false(2)} |
specialEnum(13) | value takes user defined enumerated values |
Integer {yocto (1), zepto (2), atto (3), femto (4), pico (5), nano (6), micro (7), milli (8), Units (9), kilo (10), mega (11), giga (12), tera (13), exa (14), peta (15), zetta (16), yotta (17)}
current
This object displays the International System of Units (SI) prefixes. Table 2-14 shows the prefix and its value.
| Prefix | Value |
|---|---|
yocto (1) | 10-24 |
zepto (2) | 10-21 |
atto (3) | 10-18 |
femto (4) | 10-15 |
pico (5) | 10-12 |
nano (6) | 10-9 |
micro (7) | 10-6 |
milli (8) | 10-3 |
Units (9) | 100 |
kilo (10) | 103 |
mega (11) | 106 |
giga (12) | 109 |
tera (13) | 1012 |
exa (14) | 1015 |
peta (15) | 1018 |
zetta (16) | 1021 |
yotta (17) | 1024 |
Integer (-8..9)
current
SensorPrecision is the number of decimal places in the fractional part of a SensorValue fixed-point number. When the range is from -8 to -1, SensorPrecision is the number of accurate digits in a SensorValue fixed-point number. SensorPrecision is 0 for non-fixed-point numbers.
Agent implementors must choose a value for SensorPrecision so that the precision and accuracy of a SensorValue is correctly indicated.
For example, a temperature sensor that measures from 0° to 100° C in 0.1° increments, ±0.05°, would have a SensorPrecision of 1, a SensorDataScale of Units (0), and a SensorValue ranging from 0 to 1000. The SensorValue would be interpreted as (°C * 10). If that temperature sensor's precision were 0.1° but its accuracy were only ±0.5°, then the SensorPrecision would be 0. The SensorValue would be interpreted as degrees C.
Another example, a fan rotation speed sensor that measures RPM from 0 to 10,000 in 100 RPM increments, with an accuracy of +50/-37 RPM, would have a SensorPrecision of -2, a SensorDataScale of Units(9), and a SensorValue ranging from 0 to 10000. The 10s and 1s digits of SensorValue would always be 0.
Integer (-1000000000..1000000000)
current
For sensors that measure AC volts, DC volts, amperes, watts, hertz, celsius, and cmm this item is a fixed point number ranging from -999,999,999 to +999,999,999. Use the value -1000000000 to indicate underflow. Use the value +1000000000 to indicate overflow. Use SensorPrecision to indicate how many fractional digits the SensorValue has.
For sensors that measure percent RH, this item is a number ranging from 0 to 100.
For sensors that measure rpm, this item can take only nonnegative values, 0..999999999.
For sensors of type truthvalue, this item can take only two values: true(1), false(2).
For sensors of type specialEnum, this item can take any value in the range (-1000000000..1000000000), but the meaning of each value is specific to the sensor.
For sensors of type other and unknown, this item can take any value in the range (-1000000000..1000000000), but the meaning of the values are specific to the sensor.
Use ENTITY MIB entPhysicalTable.entPhysicalVendorType to learn about the sensor type.
Integer {ok (1), unavailable (2), nonoperational (3)}
current
This object indicates the operational status of the sensor. Valid values are shown in Table 2-15.
| Sensor Measurement | Valid Value(s) |
|---|---|
ok (1) | The agent can read the sensor value. |
unavailable (2) | The agent presently can not report the sensor value. |
nonoperational (3) | The sensor could have a hard failure (disconnected wire), or a soft failure such as out-of-range, jittery, or wildly fluctuating readings. |
Integer (0..999999999)
current
This object indicates the interval in seconds between updates to the sensor's value.
A value of zero indicates one or more of the following:
Integer {other (1), minor (10), major (20)}
current
This object indicates sensor threshold severity. Valid values are shown in Table 2-16.
| Sensor Measurement | Valid Value(s) |
|---|---|
other (1) | Indicates a severity other than those listed below. |
minor (10) | Minor problem threshold. |
major (20) | Major problem threshold. |
Integer {lessThan (1), lessOrEqual (2), greaterThan (3), greaterOrEqual (4), equalTo (5),
notEqualTo (6)}
current
This object displays sensor threshold relational operator types. Valid values are shown in Table 2-17.
| Sensor Threshold | Valid Value(s) |
|---|---|
lessThan(1) | Sensor value is less than the threshold value |
lessOrEqual(2) | Sensor value is less than or equal to the threshold value |
greaterThan(3) | Sensor value is greater than the threshold value |
greaterOrEqual(4) | Sensor value is greater than or equal to the threshold value |
equalTo(5) | Sensor value is equal to the threshold value |
notEqualTo(6) | Sensor value is not equal to the threshold value |
Sequence of entSensorValueEntry
not-accessible
current
This table lists the type, scale, and present value of a sensor listed in the ENTITY MIB entPhysicalTable.
::= { entSensorValues 1 }
entSensorValueEntry
not-accessible
current
An entSensorValueTable entry describes the present reading of a sensor, the measurement units and scale, and the sensor operational status.
{ entPhysicalIndex }
::= { entSensorValueTable 1 }
The entSensorValueEntry Sequence is shown in Table 2-18.
| Object | Syntax |
|---|---|
SensorDataType | |
SensorDataScale | |
SensorPrecision | |
SensorValue | |
SensorStatus | |
TimeStamp | |
SensorValueUpdateRate |
SensorDataType
read-only
current
This object indicates the type of data reported by the entSensorValue.
This object is set by the agent at start-up and the value does not change during operation.
::= { entSensorValueEntry 1 }
SensorDataScale
read-only
current
This object indicates the exponent to apply to sensor values reported by entSensorValue.
This object is set by the agent at start-up and the value does not change during operation.
::= { entSensorValueEntry 2 }
SensorPrecision
read-only
current
This object indicates the number of decimal places of precision in fixed-point sensor values reported by entSensorValue.
This object is set to 0 when entSensorType is not a fixed-point type voltsAC (1), voltsDC (2),
amperes (3), watts (4), hertz (5), celsius (6), or cmm (9).
This object is set by the agent at start-up and the value does not change during operation.
::= { entSensorValueEntry 3 }
SensorValue
read-only
current
This object reports the most recent measurement seen by the sensor.
To correctly display or interpret this object's value, you must also know entSensorType, entSensorScale, and entSensorPrecision.
However, you can compare entSensorValue with the threshold values given in entSensorThresholdTable without any semantic knowledge.
::= { entSensorValueEntry 4 }
SensorStatus
read-only
current
This object indicates the present operational status of the sensor.
::= { entSensorValueEntry 5 }
TimeStamp
read-only
current
This object indicates the age of the value reported by entSensorValue.
::= { entSensorValueEntry 6 }
SensorValueUpdateRate
seconds
read-only
current
This object indicates the rate that the agent updates entSensorValue.
::= { entSensorValueEntry 7 }
Sequence of entSensorThresholdEntry
not-accessible
current
This table lists the threshold severity, relation, and comparison value for a sensor listed in the ENTITY MIB entPhysicalTable.
::= { entSensorThresholds 1 }
entSensorThresholdEntry
not-accessible
current
An entSensorThresholdTable entry describes the thresholds for a sensor, the threshold severity, the threshold value, the relation, and the evaluation of the threshold.
Only entities of type sensor (8) are listed in this table. Only pre-configured thresholds are listed in this table.
Users can create sensor-value monitoring instruments in different ways, such as RMON alarms, or Expression-MIB.
Entries are created by the agent at system startup and FRU insertion. Entries are deleted by the agent at FRU removal.
{ entPhysicalIndex, entSensorThresholdIndex }
::= { entSensorThresholdTable 1 }
The entSensorThresholdEntry Sequence is shown in Table 2-19.
| Object | Syntax |
|---|---|
Integer32 | |
SensorThresholdSeverity | |
SensorThresholdRelation | |
SensorValue | |
TruthValue | |
TruthValue |
Integer32 (1..99999999)
not-accessible
current
An index that uniquely identifies an entry in the entSensorThreshold table. This index permits the same sensor to have several different thresholds.
::= { entSensorThresholdEntry 1 }
SensorThresholdSeverity
read-only
current
This object indicates the severity of the sensor threshold.
::= { entSensorThresholdEntry 2 }
SensorThresholdRelation
read-only
current
This object indicates the relation between sensor value (entSensorValue) and threshold value (entSensorThresholdValue), required to trigger the alarm when evaluating the relation, entSensorValue is on the left of entSensorThresholdRelation, entSensorThresholdValue is on the right.
In pseudo-code, the evaluation-alarm mechanism is
... if (entSensorStatus == ok) thenif (evaluate(entSensorValue, entSensorThresholdRelation, entSensorThresholdValue)) then
if (entSensorThresholdNotificationEnable == true)) then raise_alarm(entSensorThresholdAlarmOID);
endifendif
endif
...
::= { entSensorThresholdEntry 3 }
SensorValue
read-only
current
This object indicates the value of the threshold.
To correctly display or interpret this object's value, you must also know entSensorType, entSensorScale, and entSensorPrecision.
However, you can directly compare entSensorValue with the threshold values given in entSensorThresholdTable without any semantic knowledge.
::= { entSensorThresholdEntry 4 }
TruthValue
read-only
current
This object indicates the result of the most recent evaluation of the threshold. If the threshold condition is true, entSensorThresholdEvaluation is true(1). If the threshold condition is false, entSensorThresholdEvaluation is false(2).
Thresholds are evaluated at the rate indicated by entSensorValueUpdateRate.
::= { entSensorThresholdEntry 5 }
TruthValue
read-write
current
This object controls the generation of entSensorThresholdNotification for this threshold.
When this object is true (1), the generation of entSensorThresholdNotification is enabled. When this object is false (2), generation of entSensorThresholdNotification is disabled.
This object controls only the generation of entSensorThresholdNotification.
::= { entSensorThresholdEntry 6 }
{ entSensorThresholdValue, entSensorValue }
current
This object generates a notification each time the sensor value crosses the threshold listed in entSensorThresholdTable. The agent implementation facilitates prompt, timely evaluation of threshold and generation of this notification.
::= { entitySensorMIBNotifications 1 }
current
An ENTITY MIB implementation that lists sensors in its entPhysicalTable must implement this group.
PXM45
{entitySensorValueGroup, entitySensorThresholdGroup, entitySensorThresholdNotificationGroup}
::= { entitySensorMIBCompliances 1 }
{entSensorType, entSensorScale, entSensorPrecision, entSensorValue, entSensorStatus, entSensorValueTimeStamp, entSensorValueUpdateRate}
current
This collection of objects is used to describe and monitor values of ENTITY MIB entPhysicalTable entries of sensors.
::= { entitySensorMIBGroups 1 }
{entSensorThresholdSeverity, entSensorThresholdRelation, entSensorThresholdValue, entSensorThresholdEvaluation, entSensorThresholdNotificationEnable}
current
This collection of objects is used to describe and monitor thresholds for sensors.
::= { entitySensorMIBGroups 2 }
|
Note The following was commented out because SMIC doesn't know about Notification Group. |
{ entSensorThresholdNotification }
current
This collection of notifications is used for monitoring sensor threshold activity.
::= { entitySensorMIBGroups 3 }
This MIB is part of AXIPOP-MIB released in MGX 8850 Release 1.x.x. It contains the MIB objects from Release 1.x.x that are supported in MGX 8850 Release 2.
Sequence of shelfEntry
not-accessible
mandatory
This table has the physical slot number and state of the cards.
::= { basisShelf 1 }
shelfEntry
not-Accessible
mandatory
This object is an entry for the slot.
{ shelfNum, shelfSlotNum }
::= { shelfTable 1}
The shelfEntry Table Sequence is shown in Table 2-20.
| Object | Syntax |
|---|---|
Integer | |
Integer | |
Integer | |
Integer | |
Integer | |
Integer |
Integer (1..4)
read-only
mandatory
This object represents a unique value for each shelf. Its value ranges between 1 and the maximum value of shelfNumber.
::= { shelfEntry 1 }
Integer (1..33)
read-only
mandatory
This object displays the slot number of a card. BASIS can have a maximum of 16 slots in one shelf. A value of 17 is used to reset the whole shelf. The Cisco MGX 8850 can have a maximum of 32 slots in one shelf. A value of 33 is used to reset the whole shelf.
::= { shelfEntry 2 }
Integer (1..4)
read-only
mandatory
This object has been deprecated. It is available as the 9th entry in basisShelf. It is included here to prevent a hole in the shelfEntry table.
::= { shelfEntry 3 }
Integer {nocard (1), standby (2), active (3), failed (4), selfTest (5), heldInReset (6), boot (7), mismatch (8), unknown (9), coreCardMismatch (10), blocked (11), reserved (12), (hold state applies to PXM during Graceful Upgrade) hold (13)}
read-only
mandatory
This object holds the Status of a card in a particular shelf-slot. The hold state is applicable only to the Cisco MGX 8800 platform and does not apply to the Cisco MGX 8850. The Slave PXM assumes the hold state during PXM upgrades. In this state the Slave PXM will be running a different firmware but will be receiving all standby updates (BRAM and Database).
::= { shelfEntry 4 }
Integer {other (1), asc (2), bnm-T3 (10), bnm-E3 (11), bnm-155 (12), srm-4T1E1 (20), srm-3T3 (21), frsm-4T1 (30), frsm-4E1 (31), frsm-4T1-C(32), frsm-4E1-C(33), HSSI: frsm-hs1 (34), HSSI frsm-8T1 (35), frsm-8E1 (36), frsm-hs1b (37), ausm-4T1 (40), ausm-4E1 (41), ausm-8T1 (50), ausm-8E1 (51), AUSM Model B: ausmB-8T1 (52), ausmB-8E1 (53), cesm-4T1 (60), cesm-4E1 (61), imatm-T3T1 (70), imatm-E3E1 (71), imatmB-T1 (72), imatmB-E1 (73), frasm-8T1 (80), cesm-8T1 (90), cesm-8E1 (91),SM from Netro: bscsm-2 (100), bscsm-4 (101), Testers: atmt-8T1 (110), atmt-8E1 (111), frt-8T1 (120), frt-8E1 (121), frsm_vhs cards frsm-2ct3 (130), frsm-2t3 (131), frsm-2e3 (132), frsm-hs2 (133), cesm-T3 (140), cesm-E3 (141), VISM: vism-8T1 (150), vism-8E1 (151), Reserved for MGX 8850 after 1000: pxm1 (1000), pxm1-2t3e3 (1001), pxm1-4oc3 (1002), pxm1-oc12 (1003), rpm (2000)}
read-only
mandatory
This object indicates the type of a card in a particular shelf-slot.
{ other }
::= { shelfEntry 5 }
Integer {doNotHold (1), holdInReset(2)}
read-write
mandatory
This object retains the card in a particular shelf-slot during reset, provided the object is set to holdInReset. If the object is set to doNotHold, then it only resets the card in the specified slot; if the slot number is 17 then it will reset the whole shelf.
::= { shelfEntry 6 }
IpAddress
read-only
mandatory
This object displays the IP address of the statsMaster.
::= { basisShelf 10 }
Integer (0..65535)
read-only
mandatory
This object displays the statistics collection interval in minutes.
{ 0 }
::= { basisShelf 11 }
Integer (0..65535)
read-only
mandatory
This object displays the statistics bucket interval in minutes.
{ 0 }
::= { basisShelf 12 }
DisplayString {SIZE (1..20)}
read-only
mandatory
This object displays the Username of the person logging in or logging out. It is used only in traps, and is currently limited to 12 characters.
::= { basisShelf 13 }
Integer {clear (1), minor (2), major (3), critical (4)}
read-only
mandatory
This object displays the alarm Status of the shelf. An implementation may not support all the values. Possible values are shown in Table 2-21.
| Value | Alarm Status |
|---|---|
clear (1) | Indicates that the shelf is not in alarm. |
minor (2) | Indicates that a non-service effecting condition has occurred and that corrective action should be taken in order to prevent a more serious fault. |
major (3) | Indicates that a service effecting condition has occurred and urgent corrective action is required. |
critical (4) | Indicates that a service effecting condition has occurred and immediate corrective action is required. |
The definitions for minor (2), major (3), and critical (4) are taken from Bellcore document GR-1248-CORE.
{ clear }
::= { basisShelf 14 }
This group contains information about the redundancy mapping. The Core Card Set in the Cisco MGX 8850 includes the Processor Switch Module (PXM) and the Service Redundancy/Resource Module (System Resource Manager).
The slot numbers where the Core Card Set can be plugged in may be different in different products.
A redundant pair is a set of cards/modules that may operate in a redundant manner. At any time one or more cards/modules of the pair are active, while other is standby. If an active member fails, one of the standby members becomes active.
Sequence OF SmRedMapEntry
not-accessible
mandatory
The table has the redundancy map for a service module. This table is for configuring redundancy for service modules. This table might contain entries for the Core Card Set in some implementations.
::= { axisRedundancy 1 }
smRedMapEntry
not-accessible
mandatory
This object provides an entry for module (Service Module, Core Card Set) redundancy. Some implementations might have entries for the core-card set. The entries for core-card set may not be added, modified or deleted. An entry has to be created in this table to configure service modules in redundant configuration.
For a 1:1 (Y cable ) redundancy configuration, an entry exists for each redundant pair with redPrimarySlotNum as the index.
For 1:N redundancy configuration, an entry exists with different primary slot numbers (redPrimarySlot value) with the same secondary slot numbers (redSecondarySlot value).
{ redPrimarySlotNum }
::= { smRedMapTable 1}
The smRedMapEntry sequence is shown in Table 2-22.
| Object | Syntax |
|---|---|
Integer | |
Integer | |
Integer | |
Integer | |
Integer | |
Integer | |
Integer | |
Integer | |
Integer | |
Integer | |
Integer |
Integer (1..32)
read-write
mandatory
This object describes the index to the table. This is the slot number of the primary module in the redundant configuration.
For systems where the entries are created by the agent for the Core Card Set, the implied slot numbers are used for this object. The implied slot number values are dependent on the system.
::= { smRedMapEntry 1 }
Integer {add(1), del(2), mod(3)}
read-write
mandatory
This object will add, delete, or modify the redundancy. Note that modify is not used but it is there for consistency. This object is for creating and deleting an entry in smRedMapTable. This object is set to add (1), to create an entry in the table. The values of redPrimarySlot and redSecondarySlot objects constitute the redundant pairs. The slot numbers specified for redPrimarySlot and redSecondarySlot should be in the same half of the shelf for half-height service modules. This object is set to del (2), to delete an entry from the table.
{ del }
::= { smRedMapEntry 2 }
Integer {other (1), bsc (2), aum-T3 (10), tim (20), frsm-4T1 (30), frsm-4E1 (31), frsm-hs1 (34), frsm-8T1 (35), frsm-8E1 (36), frsm-hs1b (37), ausm-4T1 (40), ausm-4E1 (41), ausm-8T1 (50), ausm-8E1 (51), AUSM Model B ausmB-8T1 (52), ausmB-8E1 (53), cesm-4T1 (60), cesm-4E1 (61), imatm-T3T1 (70), imatm-E3E1 (71), imatmB-T1 (72), imatmB-E1 (73), frasm-8T1 (80), cesm-8T1 (90), cesm-8E1 (91), SM from Netro bscsm-2 (100), bscsm-4 (101), frsm_vhs cards frsm-2ct3 (130), frsm-2t3 (131), frsm-2e3 (132), frsm-hs2 (133), cesm-t3e3 cards cesm-T3 (140), cesm-E3 (141), testers atmt-8T1 (110), atmt-8E1 (111), frt-8T1 (120), frt-8E1 (121), VISM vism-8T1 (150), vism-8E1 (151), reserved for MGX8850 after 1000 pxm1 (1000), pxm1-2t3e3 (1001), pxm1-4oc3 (1002), pxm1-oc12 (1003), rpm (2000)}
read-only
mandatory
This object holds the type of the primary card. Some of the card types are not supported in the table but they are defined for consistency. The bsc, ausm-T3, and tim modules are not supported.
::= { smRedMapEntry 3 }
Integer{nocard (1), standby (2), active (3), failed (4), selfTest (5), heldInReset (6), boot (7), mismatch (8), unknown (9), unusedCoreCardMisMatch (10), blocked (11), reserved (12), Hold state applies to PXM during Graceful Upgrade, unusedHold (13)}
read-only
mandatory
This object holds the state of the primary card. Some of the states are not supported in the table but are defined here for consistency with the card States. The values heldInReset, boot, and unknown are not supported.
Supported values are shown in Table 2-23.
| Value | Module Status |
|---|---|
nocard (1) | Module not present in the slot. |
standby (2) | Module is in standby state. |
active (3) | Module is in active state. |
failed (4) | Module is in failed state due to some condition. |
selfTest (5) | Module is performing selftest |
mismatch(8) | Wrong module is plugged in. |
::= { smRedMapEntry 4 }
Integer (0..32)
read-write
mandatory
This is the slot number of the redundant card for the primary card. The value of SecondarySlotNum will be 0 when no secondary card covers the primary card. The value of SecondarySlotNum should be from the same half of the shelf. If the primary card is in the top half then the secondary card should be in the same half and will be covered by the top SRM.
::= { smRedMapEntry 5 }
Integer {other (1), bsc (2), aum-T3 (10), tim (20), frsm-4T1 (30), frsm-4E1 (31), frsm-hs1 (34), frsm-8T1 (35), frsm-8E1 (36), frsm-hs1b (37), ausm-4T1 (40), ausm-4E1 (41), ausm-8T1 (50), ausm-8E1 (51), ausmB-8T1 (52), ausmB-8E1 (53), cesm-4T1 (60), cesm-4E1 (61), imatm-T3T1 (70), imatm-E3E1 (71), imatmB-T1 (72), imatmB-E1 (73), frasm-8T1 (80), cesm-8T1 (90), cesm-8E1 (91), SM from Netro bscsm-2 (100), bscsm-4 (101), frsm_vhs cards frsm-2ct3 (130), frsm-2t3 (131), frsm-2e3 (132), frsm-hs2 (133), cesm-t3e3 cards cesm-T3 (140), cesm-E3 (141), testers atmt-8T1 (110), atmt-8E1 (111), frt-8T1 (120), frt-8E1 (121), VISM vism-8T1 (150), vism-8E1 (151), reserved for MGX8850 after 1000 pxm1 (1000), pxm1-2t3e3 (1001), pxm1-4oc3 (1002), pxm1-oc12 (1003), rpm (2000)}
read-only
mandatory
This object holds the type of the redundant card. Note that redSecondaryType is the same as redPrimaryType unless it is changed for a new service module. Some of the card types are not supported in the table but they are defined here for consistency with the shelf card types. The bsc, ausm-T3, and tim modules are not supported.
::= { smRedMapEntry 6 }
Integer {nocard (1), standby (2), active (3), failed (4), selfTest (5), heldInReset (6), boot (7), mismatch (8), unknown (9), unusedCoreCardMisMatch (10), blocked (11), reserved (12), Hold state applies to PXM during Graceful Upgrade unusedHold (13)}
read-only
mandatory
This object holds the state of the secondary card. Supported values are shown in Table 2-24.
| Value | Module Status |
|---|---|
nocard (1) | Module not present in the slot. |
standby (2) | Module is in standby state. |
active (3) | Module is in active state. |
failed (4) | Module is in failed state. |
selfTest (5) | Module is performing selftest. |
mismatch (8) | Module is not compatible with the current configuration, or a wrong type of back-card or line module is inserted. |
::= { smRedMapEntry 7 }
Integer {yCable (1), oneToN (2) }
read-write
mandatory
This object describes the type of redundancy. The supported values are either yCable (1) or oneToN (2). yCable is a 1:1 (y cable) redundancy configuration. In this configuration, there is only one module which acts as the backup for the other. oneToN (2) is a 1:N redundancy configuration. In this configuration, there is one module (secondary) which acts as the backup for other primary modules. There are multiple primary modules and one secondary module in this configuration. At any point of time, the secondary module is backup for only one failed primary module. If more than one primary module fails, then the failed primary modules are not covered by the secondary module.
::= { smRedMapEntry 8 }
Integer (0..32)
read-only
mandatory
This object indicates the slot number of the primary card. The secondary card is covering this slot number. Note that redCoveringSlot is set to 0 when the primary is not being protected. If this primary card is being protected by its redundant card, then this object would be the primary slot number.
::= { smRedMapEntry 9 }
Integer
read-only
mandatory
This object indicates the feature of the primary card.
::= { smRedMapEntry 10 }
Integer {lm-DB15-4T1 (16), lm-DB15-4E1 (17), lm-BNC-4E1 (18), lm-DB15-4T1-R(19), lm-DB15-4E1-R(20), lm-BNC-4E1-R (21), lm-RJ48-8T1 (22), lm-RJ48-8E1 (23), lm-SMB-8E1 (24), lm-RJ48-T3T1 (25), lm-RJ48-E3E1 (26), lm-RJ48-T3E1 (27), lm-SMB-E3E1 (28), lm-RJ48-E3T1 (29), lm-SMB-T3E1 (30), lm-T3E3-D (32), lm-T3E3-B (33), lm-RJ48-8T1-R(48), lm-RJ48-8E1-R(49), lm-SMB-8E1-R (50), HSSI/X.21 lm-HS1-4X21 (60), lm-HS1-3HSSI(61), HSSI/X.21 lm-HS1-4V35 (62)}
read-only
mandatory
This object indicates the line module type for the primary card. This object is not configurable and it only has the type of the current line module that is present in the slot. Note that the types that end with a -R are of redundant back card type which do not have a connector on the faceplate. They are used for the redundant card but they can be plugged into the primary by mistake. This object would show its type.
::= { smRedMapEntry 11 }
Posted: Fri Apr 14 19:50:21 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.