OID repository
OID Repository
http://oid-info.com
Display OID:
 
Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemprivate(4) Action itementerprise(1) Action item4491 Action itemclabProject(2) Action itemclabProjDocsis(1) Action itemesafeMib(14) Action itemesafeMibObjects(1) Action itemesafeBase(1) Action itemesafeDevStatusTable(2) Action itemesafeDevStatusEntry(1)  

Navigating the OID tree

esafeDevServiceIntImpact(1)
 
Separation line
 
OID description

   
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

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."



Information:

Automatically extracted from Rec. ITU-T J.126.

 
Short URLs for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved, Orange © 2024
Parent OID: esafeDevStatusEntry(1) Next sibling OID: esafeDevServiceIntImpactInfo(2) Last sibling OID: esafeDevServiceIntImpactInfo(2)
Separation line
OID helper Webmaster Bullet 8 Jul 2022 Bullet Page top