OID reference

iccpNodeCreateIccpRg

1.3.6.1.4.1.8708.2.61.2.2.1.1.4

Description

Create an Inter-Chassis Communication Protocol (ICCP) Redundancy Group (RG). Group ID - The two PE:s that protect the same LAG must have the same Group ID. MEP - Select the remote UP MEP that has been configured to be used as communication channel for the ICCP and mLACP protocol. NOTE! Only UP MEPs can be used for thi…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.8708.2.61.2.2.1.1 (iccpNodeEntry)
Node code
4
Node name
iccpNodeCreateIccpRg
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.8708.2.61.2.2.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.8708.2.61.2.2.1.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 8708 2 61 2 2 1 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lumentis(8708) lumGeneric(2) lumIccpMIB(61) lumIccpMIBObjects(2) iccpNodeList(2) iccpNodeTable(1) iccpNodeEntry(1) iccpNodeCreateIccpRg(4)}
OID-IRI notation
  • /1/3/6/1/4/1/8708/2/61/2/2/1/1/4
  • /ISO/Identified-Organization/6/1/4/1/8708/2/61/2/2/1/1/4
  • /ISO/3/6/1/4/1/8708/2/61/2/2/1/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/8708/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/identified-organization/dod/internet/private/enterprise/lumentis/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/identified-organization/dod/internet/private/enterprises/8708/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/identified-organization/dod/internet/private/enterprises/lumentis/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/8708/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lumentis/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/identified-organization/dod/internet/private/vendor-objects/8708/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/identified-organization/dod/internet/private/vendor-objects/lumentis/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/org/dod/internet/private/enterprise/8708/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/org/dod/internet/private/enterprise/lumentis/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/org/dod/internet/private/enterprises/8708/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/org/dod/internet/private/enterprises/lumentis/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/org/dod/internet/private/ldap-enterprise/8708/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/org/dod/internet/private/ldap-enterprise/lumentis/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/org/dod/internet/private/vendor-objects/8708/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • /iso/org/dod/internet/private/vendor-objects/lumentis/lumGeneric/lumIccpMIB/lumIccpMIBObjects/iccpNodeList/iccpNodeTable/iccpNodeEntry/iccpNodeCreateIccpRg
  • Additional combinations skipped.

SNMP properties

Value type
CommandString
Maximum access defined by MIB
read-only
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.

The displayed source records contain one distinct definition. Compare its source records.

iccpNodeCreateIccpRg OBJECT-TYPE
    SYNTAX      CommandString
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Create an Inter-Chassis Communication Protocol (ICCP) Redundancy Group (RG).

        Group ID -              The two PE:s that protect the same LAG must have the same Group ID.

        MEP -                   Select the remote UP MEP that has been configured to be used as communication channel for the ICCP and mLACP protocol.
                                NOTE! Only UP MEPs can be used for this purpose.

        Create MC-LAG -         Whether the MC-LAG should be created is optional in this dialogue. It can be added or removed from the ICCP RG later.

        Node ID -               This MUST be unique in a RG. Be sure to use different values for both PE:s in the RG. The node ID is used in mLACP to ensure
                                uniqueness of LACP port numbers.

        LAG -                   Select the LAG that should be protected. NOTE! LACP must be enabled on the LAG.

        Administrative
        system priority -       This is the administrative system priority for this MC-LAG. This will be used in the negotiation with the other PE in the
                                RG which system parameters to use in LACPDU:s. Both PE:s will automatically agree on the same system priority, system id and key.

        Administrative
        port priority -         This port priority is used on all ports in the LAG.

"
    ::= { iccpNodeEntry 4 }

Meaning

Descriptions

1 unique

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

Create an Inter-Chassis Communication Protocol (ICCP) Redundancy Group (RG). Group ID - The two PE:s that protect the same LAG must have the same Group ID. MEP - Select the remote UP MEP that has been configured to be used as communication channel for the ICCP and mLACP protocol. NOTE! Only UP MEPs can be used for this purpose. Create MC-LAG - Whether the MC-LAG should be created is optional in this dialogue. It can be added or removed from the ICCP RG later. Node ID - This MUST be unique in a RG. Be sure to use different values for both PE:s in the RG. The node ID is used in mLACP to ensure uniqueness of LACP port numbers. LAG - Select the LAG that should be protected. NOTE! LACP must be enabled on the LAG. Administrative system priority - This is the administrative system priority for this MC-LAG. This will be used in the negotiation with the other PE in the RG which system parameters to use in LACPDU:s. Both PE:s will automatically agree on the same system priority, system id and key. Administrative port priority - This port priority is used on all ports in the LAG.

Sources for this description

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

See 1 matching source record

Evidence

Source records

1 records

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

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

Description 1

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

Status in source: current.

Names: iccpNodeCreateIccpRg

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "iccpNodeCreateIccpRg",
    "OBJECT-TYPE",
    "SYNTAX",
    "CommandString",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Create an Inter-Chassis Communication Protocol (ICCP) Redundancy Group (RG). Group ID - The two PE:s that protect the same LAG must have the same Group ID. MEP - Select the remote UP MEP that has been configured to be used as communication channel for the ICCP and mLACP protocol. NOTE! Only UP MEPs can be used for this purpose. Create MC-LAG - Whether the MC-LAG should be created is optional in this dialogue. It can be added or removed from the ICCP RG later. Node ID - This MUST be unique in a RG. Be sure to use different values for both PE:s in the RG. The node ID is used in mLACP to ensure uniqueness of LACP port numbers. LAG - Select the LAG that should be protected. NOTE! LACP must be enabled on the LAG. Administrative system priority - This is the administrative system priority for this MC-LAG. This will be used in the negotiation with the other PE in the RG which system parameters to use in LACPDU:s. Both PE:s will automatically agree on the same system priority, system id and key. Administrative port priority - This port priority is used on all ports in the LAG. \"",
    "::=",
    "{",
    "iccpNodeEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "CommandString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Create an Inter-Chassis Communication Protocol (ICCP) Redundancy Group (RG). Group ID - The two PE:s that protect the same LAG must have the same Group ID. MEP - Select the remote UP MEP that has been configured to be used as communication channel for the ICCP and mLACP protocol. NOTE! Only UP MEPs can be used for this purpose. Create MC-LAG - Whether the MC-LAG should be created is optional in this dialogue. It can be added or removed from the ICCP RG later. Node ID - This MUST be unique in a RG. Be sure to use different values for both PE:s in the RG. The node ID is used in mLACP to ensure uniqueness of LACP port numbers. LAG - Select the LAG that should be protected. NOTE! LACP must be enabled on the LAG. Administrative system priority - This is the administrative system priority for this MC-LAG. This will be used in the negotiation with the other PE in the RG which system parameters to use in LACPDU:s. Both PE:s will automatically agree on the same system priority, system id and key. Administrative port priority - This port priority is used on all ports in the LAG."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.8708)

Carlsson Martin

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.8708.2.61.2.2.1.1.1 iccpNodeIndex00
1.3.6.1.4.1.8708.2.61.2.2.1.1.2 iccpNodeName00
1.3.6.1.4.1.8708.2.61.2.2.1.1.3 iccpNodeSystemMacAddress00
1.3.6.1.4.1.8708.2.61.2.2.1.1.5 iccpNodeInternalReference00