OID reference

fsDhcp6SrvRealmTable

1.3.6.1.4.1.29601.2.42.2.6

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.29601.2.42.2 (fsDhcp6SrvConfig)
Node code: 6
Node name: fsDhcp6SrvRealmTable
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.29601.2.42.2.6
URN notation: urn:oid:1.3.6.1.4.1.29601.2.42.2.6

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 29601 2 42 2 6}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsdhcpv6srv(42) fsDhcp6SrvConfig(2) fsDhcp6SrvRealmTable(6)}

OID-IRI notation

/1/3/6/1/4/1/29601/2/42/2/6
/ISO/Identified-Organization/6/1/4/1/29601/2/42/2/6
/ISO/3/6/1/4/1/29601/2/42/2/6

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/identified-organization/dod/internet/private/enterprises/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/org/dod/internet/private/enterprise/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/org/dod/internet/private/enterprises/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/org/dod/internet/private/ldap-enterprise/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/org/dod/internet/private/vendor-objects/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/iso-organization/dod/internet/private/enterprise/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/iso-organization/dod/internet/private/enterprises/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable
/iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsdhcpv6srv/fsDhcp6SrvConfig/fsDhcp6SrvRealmTable

SNMP properties

Value type: SEQUENCE OF FsDhcp6SrvRealmEntry
Maximum access defined by MIB: not-accessible
Status in MIB: current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Published definitions

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

fsDhcp6SrvRealmTable · current

fsDhcp6SrvRealmTable OBJECT-TYPE  
    SYNTAX SEQUENCE OF FsDhcp6SrvRealmEntry
    MAX-ACCESS not-accessible  
    STATUS current  
    DESCRIPTION  
       "Server authenticate the received information request with 
        HMAC MD5 algorithm when received message contains the 
        Authentication option tlv .Realms are container for 
        authentication information. For the Authentication key id is required.
        Keys are assigned to clients. This table is used to create 
        the Realm Row and the fsDhcp6SrvRealmIndex index is also used
        by the fsDhcp6SrvAuthClntTable. Following is an example
        of a server authentication hierarchy:

        realm testrealm01.aricent.com 
        {
           key 1 TESTREALMKEY01
           key 2 TESTREALMKEY02
        }
        realm testrealm02.aricent.com 
        {
           key 1 TESTREALMKEY01
        }"
    ::=  { fsDhcp6SrvConfig 6 }

fsDhcp6SrvRealmTable · current

fsDhcp6SrvRealmTable OBJECT-TYPE  
    SYNTAX SEQUENCE OF FsDhcp6SrvRealmEntry
    MAX-ACCESS not-accessible  
    STATUS current  
    DESCRIPTION  
       "Server authenticate the received information request with 
        HMAC MD5 algorithm when received message contains the 
        Authentication option tlv .Realms are container for 
        authentication information. For the Authentication key id is required.
        Keys are assigned to clients. This table is used to create 
        the Realm Row and the fsDhcp6SrvRealmIndex index is also used
        by the fsDhcp6SrvAuthClntTable. Following is an example
        of a server authentication hierarchy:

        realm testrealm01.private.com 
        {
           key 1 TESTREALMKEY01
           key 2 TESTREALMKEY02
        }
        realm testrealm02.private.com 
        {
           key 1 TESTREALMKEY01
        }"
    ::=  { fsDhcp6SrvConfig 6 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

Server authenticate the received information request with HMAC MD5 algorithm when received message contains the Authentication option tlv .Realms are container for authentication information. For the Authentication key id is required. Keys are assigned to clients. This table is used to create the Realm Row and the fsDhcp6SrvRealmIndex index is also used by the fsDhcp6SrvAuthClntTable. Following is an example of a server authentication hierarchy: realm testrealm01.aricent.com { key 1 TESTREALMKEY01 key 2 TESTREALMKEY02 } realm testrealm02.aricent.com { key 1 TESTREALMKEY01 }

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Description 2

Server authenticate the received information request with HMAC MD5 algorithm when received message contains the Authentication option tlv .Realms are container for authentication information. For the Authentication key id is required. Keys are assigned to clients. This table is used to create the Realm Row and the fsDhcp6SrvRealmIndex index is also used by the fsDhcp6SrvAuthClntTable. Following is an example of a server authentication hierarchy: realm testrealm01.private.com { key 1 TESTREALMKEY01 key 2 TESTREALMKEY02 } realm testrealm02.private.com { key 1 TESTREALMKEY01 }

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 1

fsDhcp6SrvRealmTable · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: fsDhcp6SrvRealmTable

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsDhcp6SrvRealmTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsDhcp6SrvRealmEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Server authenticate the received information request with HMAC MD5 algorithm when received message contains the Authentication option tlv .Realms are container for authentication information. For the Authentication key id is required. Keys are assigned to clients. This table is used to create the Realm Row and the fsDhcp6SrvRealmIndex index is also used by the fsDhcp6SrvAuthClntTable. Following is an example of a server authentication hierarchy: realm testrealm01.aricent.com { key 1 TESTREALMKEY01 key 2 TESTREALMKEY02 } realm testrealm02.aricent.com { key 1 TESTREALMKEY01 }\"",
    "::=",
    "{",
    "fsDhcp6SrvConfig",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsDhcp6SrvRealmEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Server authenticate the received information request with HMAC MD5 algorithm when received message contains the Authentication option tlv .Realms are container for authentication information. For the Authentication key id is required. Keys are assigned to clients. This table is used to create the Realm Row and the fsDhcp6SrvRealmIndex index is also used by the fsDhcp6SrvAuthClntTable. Following is an example of a server authentication hierarchy: realm testrealm01.aricent.com { key 1 TESTREALMKEY01 key 2 TESTREALMKEY02 } realm testrealm02.aricent.com { key 1 TESTREALMKEY01 }"
    ],
    null,
    null,
    null,
    null
  ]
}

Belden, GarrettCom and Hirschmann IT official standalone MIBs · Publisher's source file: fsdh6s.mib
Module: ARICENT-DHCPv6-SERVER-MIB

See published definition above
Module imports
```
{'SNMPv2-TC': ['DisplayString', 'TruthValue', 'RowStatus', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Counter32', 'enterprises', 'Unsigned32', 'Integer32']}
```
· Download fsdh6s.mib
Related source files and packages:
- Firmware > Magnum 5RX_10RX > 5RX_10RX MIB — 10RX_mibs.zip

Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

fsDhcp6SrvRealmTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: fsDhcp6SrvRealmTable

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsDhcp6SrvRealmTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FsDhcp6SrvRealmEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Server authenticate the received information request with HMAC MD5 algorithm when received message contains the Authentication option tlv .Realms are container for authentication information. For the Authentication key id is required. Keys are assigned to clients. This table is used to create the Realm Row and the fsDhcp6SrvRealmIndex index is also used by the fsDhcp6SrvAuthClntTable. Following is an example of a server authentication hierarchy: realm testrealm01.private.com { key 1 TESTREALMKEY01 key 2 TESTREALMKEY02 } realm testrealm02.private.com { key 1 TESTREALMKEY01 }\"",
    "::=",
    "{",
    "fsDhcp6SrvConfig",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FsDhcp6SrvRealmEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Server authenticate the received information request with HMAC MD5 algorithm when received message contains the Authentication option tlv .Realms are container for authentication information. For the Authentication key id is required. Keys are assigned to clients. This table is used to create the Realm Row and the fsDhcp6SrvRealmIndex index is also used by the fsDhcp6SrvAuthClntTable. Following is an example of a server authentication hierarchy: realm testrealm01.private.com { key 1 TESTREALMKEY01 key 2 TESTREALMKEY02 } realm testrealm02.private.com { key 1 TESTREALMKEY01 }"
    ],
    null,
    null,
    null,
    null
  ]
}

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.

Module: ARICENT-DHCPv6-SERVER-MIB

See published definition above
Module imports
```
{'SNMPv2-TC': ['DisplayString', 'TruthValue', 'RowStatus', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Counter32', 'enterprises', 'Unsigned32', 'Integer32']}
```
· Download ARICENT-DHCPv6-SERVER-MIB
Related source files and packages:
- Observium Community original distribution archive

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Direct children (1)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.29601.2.42.2.6.1	fsDhcp6SrvRealmEntry	4	4

Siblings (7)

OID	Name	Direct children	Descendants
1.3.6.1.4.1.29601.2.42.2.1	fsDhcp6SrvPoolTable	1	9
1.3.6.1.4.1.29601.2.42.2.2	fsDhcp6SrvIncludePrefixTable	1	6
1.3.6.1.4.1.29601.2.42.2.3	fsDhcp6SrvOptionTable	1	7
1.3.6.1.4.1.29601.2.42.2.4	fsDhcp6SrvSubOptionTable	1	5
1.3.6.1.4.1.29601.2.42.2.5	fsDhcp6SrvIfTable	1	12
1.3.6.1.4.1.29601.2.42.2.7	fsDhcp6SrvClientTable	1	6
1.3.6.1.4.1.29601.2.42.2.8	fsDhcp6SrvKeyTable	1	4