entPhysicalTable

1.3.6.1.2.1.47.1.1.1.1.1

entPhysicalIndex

Integer32{(1,2147483647)}

not-accessible

The index for this entry.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.2

entPhysicalDescr

OCTET STRING{(0,255)}

read-only

A textual description of physical entity. This object

should contain a string that identifies the manufacturer's

name for the physical entity, and should be set to a

distinct value for each version or model of the physical

entity.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.3

entPhysicalVendorType

OBJECT IDENTIFIER

read-only

An indication of 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 an 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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.4

entPhysicalContainedIn

Integer32{(0,2147483647)}

read-only

The actually supported access is read-only.

This object is used only as the VB bound variable of the alarm.

1.3.6.1.2.1.47.1.1.1.1.5

entPhysicalClass

INTEGER{other(1),unknown(2),chassis(3),backplane(4),container(5),powerSupply(6),fan(7),sensor(8),module(9),port(10),stack(11),cpu(12)}

read-only

The actually supported access is read-only.

This object is used only as the VB bound variable of the alarm.

1.3.6.1.2.1.47.1.1.1.1.6

entPhysicalParentRelPos

Integer32{(-1,2147483647)}

read-only

An indication of the relative position of this 'child'

component among all its 'sibling' components. Sibling

components are defined as entPhysicalEntries that 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).

If possible, this value should match any external labeling

of the physical component. For example, for a container

(e.g., 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

(e.g., slots) are labeled from a starting position of zero,

then the first sibling should be associated with an

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

OCTET STRING{(0,255)}

read-only

The actually supported access is read-only.

This object is used only as the VB bound variable of the alarm.

1.3.6.1.2.1.47.1.1.1.1.8

entPhysicalHardwareRev

OCTET STRING{(0,255)}

read-only

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 (e.g., binary) format, 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 if this information is unknown to

the agent, then this object will contain a zero-length

string.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.9

entPhysicalFirmwareRev

OCTET STRING{(0,255)}

read-only

The vendor-specific firmware revision string for the

physical entity.

Note that if revision information is stored internally in a

non-printable (e.g., binary) format, 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 if this information is unknown to the

agent, then this object will contain a zero-length string.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.10

entPhysicalSoftwareRev

OCTET STRING{(0,255)}

read-only

The vendor-specific software revision string for the

physical entity.

Note that if revision information is stored internally in a

non-printable (e.g., binary) format, 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 if this information is unknown to the

agent, then this object will contain a zero-length string.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.11

entPhysicalSerialNum

OCTET STRING{(0,32)}

read-write

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 that 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)'

(e.g., 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 resulting in a change of the physical

entity's entPhysicalIndex value.

The actually supported access is read-only.

1.3.6.1.2.1.47.1.1.1.1.12

entPhysicalMfgName

OCTET STRING{(0,255)}

read-only

The name of the manufacturer 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 amongst 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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.13

entPhysicalModelName

OCTET STRING{(0,255)}

read-only

The vendor-specific model name identifier string associated

with this physical component. 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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.47.1.1.1.1.14

entPhysicalAlias

OCTET STRING{(0,32)}

read-write

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 associated with that entity 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/reboots of the network management system,

including those resulting in a change of the physical

entity's entPhysicalIndex value.

The actually supported access is read-only.

1.3.6.1.2.1.47.1.1.1.1.15

entPhysicalAssetID

OCTET STRING{(0,32)}

read-write

This object is a user-assigned asset tracking identifier

(as specified by a network manager) for the physical entity,

and provides non-volatile storage of this information.

On the first instantiation of a physical entity, the value

of entPhysicalAssetID associated with that entity 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)' (e.g., 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/reboots of the network management system,

including those resulting 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.

The actually supported access is read-only.

1.3.6.1.2.1.47.1.1.1.1.16

entPhysicalIsFRU

INTEGER{true(1),false(2)}

read-only

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 that represent components

permanently contained within a field replaceable unit, the

value 'false(2)' should be returned for this object.

This object is implemented as defined in the corresponding MIB files.