OID Repository
OID Repository
https://oid-base.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 itemclabProjCableHome(4) Action itemcabhCdpMib(4) Action itemcabhCdpObjects(1) Action itemcabhCdpAddr(2) Action itemcabhCdpWanDnsServerTable(3) Action itemcabhCdpWanDnsServerEntry(1)

cabhCdpWanDnsServerOrder(1)


Navigating the OID tree
Separation line
OID description

 
Action itemFormat of this page
Action itemModify this OID
Action itemCreate child OID
Action itemCreate sibling OID
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

cabhCdpWanDnsServerOrder OBJECT-TYPE
SYNTAX INTEGER {
primary(1),
secondary(2),
tertiary(3)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The order of preference for cable network and Internet DNS
servers, as listed in DHCP option 6 (Domain Server). Any
time the CDC receives valid IP address information within
DHCP option 6, as part of lease acquisition or renewal of
a WAN-Man or WAN-Data IP, it must update this information
into this table. As entries in DHCP option 6 are listed in
order of preference, the highest priority entry in DHCP
option 6 must correspond to the row with a
cabhCdpWanDnsServerOrder with a value of 1. If DHCP
option 6 contains 1 valid IP address, the PS MUST update
the row with a cabhCdpWanDnsServerOrder value of 1 and
MUST NOT modify rows with
cabhCdpWanDnsServerOrder values of 2 & 3
(if they exist). If DHCP option 6 contains 2 valid
IP addresses, the PS MUST update the rows with
cabhCdpWanDnsServerOrder values of 1 and 2
and MUST NOT modify the row with cabhCdpWanDnsServerOrder
value of 3 (if it exists). If DHCP option 6 contains 3
valid IP addresses, the PS MUST update rows with
cabhCdpWanDnsServerOrder values of 1, 2, and 3.
Any DNS server information included in DHCP option 6
beyond primary, secondary and tertiary will not be
represented in this table."



Classification:

MIB object for network management

See classes of OIDs

Information:

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

Rec. ITU-T J.192 represents an enhancement to Rec. ITU-T J.191, retaining a majority of J.191 functionality as a foundation and building upon this base to provide additional advanced features. A key design goal for equipment conforming to this Recommendation is interoperability with equipment conforming to Rec. ITU-T J.191. For example, common Management Information Bases (MIBs) are used for the foundational functionality. As a result, a J.192 based head-end may manage a mixed J.191 and J.192 deployment.

Separation line
Short URL for this page:
Separation line

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 © 2007-2025
Parent OID: cabhCdpWanDnsServerEntry(1) Next sibling OID: cabhCdpWanDnsServerIpType(2) Last sibling OID: cabhCdpWanDnsServerIp(3) Separation line
Chatbot helper Webmaster Bullet 7 Feb 2020 Bullet Page top