| OID | 1.3.6.1.2.1.97.1.1.1.1 |
| Module | DIFFSERV-MIB (CISCO) |
| Nom | diffServDataPathEntry |
| Status | current |
| Description | An entry in the data path table indicates the start of a single
Differentiated Services Functional Data Path in this device.
These are associated with individual interfaces, logical or
physical, and therefore are instantiated by ifIndex. Therefore,
the interface index must have been assigned, according to the
procedures applicable to that, before it can be meaningfully
used. Generally, this means that the interface must exist.
When diffServDataPathStorage is of type nonVolatile, however,
this may reflect the configuration for an interface whose ifIndex
has been assigned but for which the supporting implementation is
not currently present. |
| Module | DIFFSERV-MIB (DELL) |
| Nom | diffServDataPathEntry |
| Status | current |
| Description | An entry in the data path table indicates the start of a single
Differentiated Services Functional Data Path in this device.
These are associated with individual interfaces, logical or
physical, and therefore are instantiated by ifIndex. Therefore,
the interface index must have been assigned, according to the
procedures applicable to that, before it can be meaningfully
used. Generally, this means that the interface must exist.
When diffServDataPathStorage is of type nonVolatile, however,
this may reflect the configuration for an interface whose ifIndex
has been assigned but for which the supporting implementation is
not currently present. |
| Module | DIFFSERV-MIB (ietf) |
| Nom | diffServDataPathEntry |
| Status | current |
| Description | An entry in the data path table indicates the start of a single
Differentiated Services Functional Data Path in this device.
These are associated with individual interfaces, logical or
physical, and therefore are instantiated by ifIndex. Therefore,
the interface index must have been assigned, according to the
procedures applicable to that, before it can be meaningfully
used. Generally, this means that the interface must exist.
When diffServDataPathStorage is of type nonVolatile, however,
this may reflect the configuration for an interface whose ifIndex
has been assigned but for which the supporting implementation is
not currently present. |
| Module | DIFFSERV-DSCP-TC (Force10-9.14.2.1) |
| Nom | diffServDataPathEntry |
| Status | current |
| Description | An entry in the data path table indicates the start of a single
Differentiated Services Functional Data Path in this device.
These are associated with individual interfaces, logical or
physical, and therefore are instantiated by ifIndex. Therefore,
the interface index must have been assigned, according to the
procedures applicable to that, before it can be meaningfully
used. Generally, this means that the interface must exist.
When diffServDataPathStorage is of type nonVolatile, however,
this may reflect the configuration for an interface whose ifIndex
has been assigned but for which the supporting implementation is
not currently present. |
| Module | DIFFSERV-MIB (FS) |
| Nom | diffServDataPathEntry |
| Status | current |
| Description | An entry in the data path table indicates the start of a single
Differentiated Services Functional Data Path in this device.
These are associated with individual interfaces, logical or
physical, and therefore are instantiated by ifIndex. Therefore,
the interface index must have been assigned, according to the
procedures applicable to that, before it can be meaningfully
used. Generally, this means that the interface must exist.
When diffServDataPathStorage is of type nonVolatile, however,
this may reflect the configuration for an interface whose ifIndex
has been assigned but for which the supporting implementation is
not currently present. |