Q-Logic SANBOX Manuel D’Utilisation
4 – MIB-II Objects
59047-03 B
4-13
A
ifSpecific (1.3.6.1.2.1.2.2.1.22)
A reference to MIB definitions specific to the particular media being used to realize
the interface. For example, if the interface is realized by an Ethernet, then the
value of this object refers to a document that defines objects specific to Ethernet.
If this information is not present, its value should be set to the OBJECT IDENTI-
FIER { 0 0 }, which is a syntactically valid object identifier, and any conformant
implementation of ASN.1 (Abstract Syntax Notation) and BER must be able to
generate and recognize this value.
the interface. For example, if the interface is realized by an Ethernet, then the
value of this object refers to a document that defines objects specific to Ethernet.
If this information is not present, its value should be set to the OBJECT IDENTI-
FIER { 0 0 }, which is a syntactically valid object identifier, and any conformant
implementation of ASN.1 (Abstract Syntax Notation) and BER must be able to
generate and recognize this value.
Syntax
OBJECT IDENTIFIER
Access
read-only
Status
mandatory
4.5
The Address Translation Group
Implementation of the Address Translation group is mandatory for all systems.
However, this group is deprecated by MIB-II. That is, it is being included solely for
compatibility with MIB-I Nodes, and will most likely be excluded from MIB-III
Nodes. From MIB-II and onwards, each network protocol group contains its own
address translation tables.
However, this group is deprecated by MIB-II. That is, it is being included solely for
compatibility with MIB-I Nodes, and will most likely be excluded from MIB-III
Nodes. From MIB-II and onwards, each network protocol group contains its own
address translation tables.
The Address Translation group contains one table which is the union across all
interfaces of the translation tables for converting a NetworkAddress (for example,
an IP address) into a subnetwork-specific address. For lack of a better term, this
document refers to such a subnetwork-specific address as a `physical' address.
interfaces of the translation tables for converting a NetworkAddress (for example,
an IP address) into a subnetwork-specific address. For lack of a better term, this
document refers to such a subnetwork-specific address as a `physical' address.
Examples of such translation tables are for: broadcast media where ARP is in use,
the translation table is equivalent to the ARP cache, or on an X.25 network where
non-algorithmic translation to X.121 addresses is required. The translation table
contains the NetworkAddress to X.121 address equivalences.
the translation table is equivalent to the ARP cache, or on an X.25 network where
non-algorithmic translation to X.121 addresses is required. The translation table
contains the NetworkAddress to X.121 address equivalences.