esafeDevServiceIntImpact OBJECT-TYPE
SYNTAX INTEGER {
significant(1),
none(2),
unsupported(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this MIB object indicates the service
interruption impact assessment of the corresponding eSAFE
device as determined by the current status of the eSAFE
device, in accordance with the directives provided in the
eSAFE specification.
If esafeDevServiceIntImpact is set to significant (1), it
indicates that the corresponding eSAFE device (as per the
eSAFE specification) identifies a significant impact on the
active services at the given point in time. This impact
level is highly recommended for critical or real-time
services, though the impact assesment is left to the
directives provided by the associated eSAFE specification.
If esafeDevServiceIntImpact is set to none (2), it
indicates that the corresponding eSAFE device (as per the
eSAFE specification) identifies no significant impact on
the services offered at the given point in time.
If esafeDevServiceIntImpact is unsupported(3), it indicates
that the corresponding eSAFE device has no known interfaces
to support this feature or the eSAFE specification does not
recommend this feature.
If the eSAFE specification specifies the use of this
mechanism then it MUST define definitive states for the
impacts (significant or none) and the value of
unsupported(3) MUST not be used by the eDOCSIS device
for that eSAFE interface.
However, if the corresponding eSAFE specification does not
provide any directives then the value MUST be set to
unsupported(3).
If there exists multiple services being offered by an eSAFE
device (Either multiple services or multiple instances of
the same service), this MIB MUST indicate the highest
possible impact and other impact information SHOULD be
populated in the associated esafeDevServiceIntImpactInfo
table."
View at oid-info.com
The value of this MIB object indicates the service
interruption impact assessment of the corresponding eSAFE
device as determined by the current status of the eSAFE
device, in accordance with the directives provided in the
eSAFE specification.
If esafeDevServiceIntImpact is set to significant (1), it
indicates that the corresponding eSAFE device (as per the
eSAFE specification) identifies a significant impact on the
active services at the given point in time. This impact
level is highly recommended for critical or real-time
services, though the impact assessment is left to the
directives provided by the associated eSAFE specification.
If esafeDevServiceIntImpact is set to none (2), it
indicates that the corresponding eSAFE device (as per the
eSAFE specification) identifies no significant impact on
the services offered at the given point in time.
If esafeDevServiceIntImpact is unsupported(3), it indicates
that the corresponding eSAFE device has no known interfaces
to support this feature or the eSAFE specification does not
recommend this feature.
If the eSAFE specification specifies the use of this
mechanism then it MUST define definitive states for the
impacts (significant or none) and the value of
unsupported(3) MUST not be used by the eDOCSIS device
for that eSAFE interface.
However, if the corresponding eSAFE specification does not
provide any directives then the value MUST be set to
unsupported(3).
If there exists multiple services being offered by an eSAFE
device (Either multiple services or multiple instances of
the same service), this MIB MUST indicate the highest
possible impact and other impact information SHOULD be
populated in the associated esafeDevServiceIntImpactInfo
table.
Parsed from file ESAFE-MIB.mib
Module: ESAFE-MIB
Automatically extracted from Implementor\'s Guide for Recommendation ITU-T J.126 (01/05)
esafeDevServiceIntImpact OBJECT-TYPE SYNTAX INTEGER { significant(1), none(2), unsupported(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this MIB object indicates the service interruption impact assessment of the corresponding eSAFE device as determined by the current status of the eSAFE device, in accordance with the directives provided in the eSAFE specification. If esafeDevServiceIntImpact is set to significant (1), it indicates that the corresponding eSAFE device (as per the eSAFE specification) identifies a significant impact on the active services at the given point in time. This impact level is highly recommended for critical or real-time services, though the impact assessment is left to the directives provided by the associated eSAFE specification. If esafeDevServiceIntImpact is set to none (2), it indicates that the corresponding eSAFE device (as per the eSAFE specification) identifies no significant impact on the services offered at the given point in time. If esafeDevServiceIntImpact is unsupported(3), it indicates that the corresponding eSAFE device has no known interfaces to support this feature or the eSAFE specification does not recommend this feature. If the eSAFE specification specifies the use of this mechanism then it MUST define definitive states for the impacts (significant or none) and the value of unsupported(3) MUST not be used by the eDOCSIS device for that eSAFE interface. However, if the corresponding eSAFE specification does not provide any directives then the value MUST be set to unsupported(3). If there exists multiple services being offered by an eSAFE device (Either multiple services or multiple instances of the same service), this MIB MUST indicate the highest possible impact and other impact information SHOULD be populated in the associated esafeDevServiceIntImpactInfo table." ::={ esafeDevStatusEntry 1 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.4491.2.1.14.1.1.2.1.2 | esafeDevServiceIntImpactInfo | 0 | 0 | This object provides more information to the SNMP Managers regarding the condition reported in esafeDevServiceIntImpact. The eSAF… |