OID reference

fsEvcType

1.3.6.1.4.1.29601.2.71.3.1.1.4

Description

There are three type of EVC. Point-to-Point : In a Point-to-Point EVC (E-Line), exactly two UNIs must be associated with one another. Multipoint-to-Multipoint : In a Multipoint-to-Multipoint EVC (E-LAN), two or more UNIs must be associated with one another and all should be root node. Rooted-Multipoint : In a Rooted-M…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2.71.3.1.1 (fsEvcEntry)
Node code
4
Node name
fsEvcType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.29601.2.71.3.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.29601.2.71.3.1.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsmef(71) fsEvc(3) fsEvcTable(1) fsEvcEntry(1) fsEvcType(4)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/71/3/1/1/4
  • /ISO/Identified-Organization/6/1/4/1/29601/2/71/3/1/1/4
  • /ISO/3/6/1/4/1/29601/2/71/3/1/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/org/dod/internet/private/enterprise/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/org/dod/internet/private/enterprises/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/org/dod/internet/private/vendor-objects/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsmef/fsEvc/fsEvcTable/fsEvcEntry/fsEvcType

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
multipointtoMultipoint

Enumerated values

ValueName
1pointtoPoint
2multipointtoMultipoint
3rootedMultipoint

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: fsEvcContextId, fsEvcIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.29601.2.71.3.1.1.4

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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.

fsEvcType OBJECT-TYPE
      SYNTAX      INTEGER {
                           pointtoPoint(1),
                           multipointtoMultipoint(2),
                           rootedMultipoint(3)
                           }
      MAX-ACCESS   read-write
      STATUS       current
      DESCRIPTION
        "There are three type of EVC.

         Point-to-Point :
         In a Point-to-Point EVC (E-Line), exactly two UNIs must be associated
         with one another.

         Multipoint-to-Multipoint :
         In a Multipoint-to-Multipoint EVC (E-LAN), two or more UNIs must be 
         associated with one another and all should be root node.

         Rooted-Multipoint :
         In a Rooted-Multipoint EVC (E-Tree), one or more of the UNIs must be 
         designated as a Root and each of the other UNIs must be 
         designated as a Leaf.A root can send packet to all other root 
         and leaf node but leaf node can send packet to only root node."

      DEFVAL {multipointtoMultipoint}
      ::= { fsEvcEntry 4 }

Meaning

Descriptions

1 unique

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

There are three type of EVC. Point-to-Point : In a Point-to-Point EVC (E-Line), exactly two UNIs must be associated with one another. Multipoint-to-Multipoint : In a Multipoint-to-Multipoint EVC (E-LAN), two or more UNIs must be associated with one another and all should be root node. Rooted-Multipoint : In a Rooted-Multipoint EVC (E-Tree), one or more of the UNIs must be designated as a Root and each of the other UNIs must be designated as a Leaf.A root can send packet to all other root and leaf node but leaf node can send packet to only root node.

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

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

Status in source: current.

Names: fsEvcType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsEvcType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "pointtoPoint",
    "(",
    "1",
    ")",
    ",",
    "multipointtoMultipoint",
    "(",
    "2",
    ")",
    ",",
    "rootedMultipoint",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"There are three type of EVC. Point-to-Point : In a Point-to-Point EVC (E-Line), exactly two UNIs must be associated with one another. Multipoint-to-Multipoint : In a Multipoint-to-Multipoint EVC (E-LAN), two or more UNIs must be associated with one another and all should be root node. Rooted-Multipoint : In a Rooted-Multipoint EVC (E-Tree), one or more of the UNIs must be designated as a Root and each of the other UNIs must be designated as a Leaf.A root can send packet to all other root and leaf node but leaf node can send packet to only root node.\"",
    "DEFVAL",
    "{",
    "multipointtoMultipoint",
    "}",
    "::=",
    "{",
    "fsEvcEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "pointtoPoint",
            1
          ],
          [
            "multipointtoMultipoint",
            2
          ],
          [
            "rootedMultipoint",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "There are three type of EVC. Point-to-Point : In a Point-to-Point EVC (E-Line), exactly two UNIs must be associated with one another. Multipoint-to-Multipoint : In a Multipoint-to-Multipoint EVC (E-LAN), two or more UNIs must be associated with one another and all should be root node. Rooted-Multipoint : In a Rooted-Multipoint EVC (E-Tree), one or more of the UNIs must be designated as a Root and each of the other UNIs must be designated as a Leaf.A root can send packet to all other root and leaf node but leaf node can send packet to only root node."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "multipointtoMultipoint"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Siblings (12)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.71.3.1.1.1 fsEvcContextId00
1.3.6.1.4.1.29601.2.71.3.1.1.2 fsEvcIndex00
1.3.6.1.4.1.29601.2.71.3.1.1.3 fsEvcId00
1.3.6.1.4.1.29601.2.71.3.1.1.5 fsEvcMaxUni00
1.3.6.1.4.1.29601.2.71.3.1.1.6 fsEvcCVlanIdPreservation00
1.3.6.1.4.1.29601.2.71.3.1.1.7 fsEvcCVlanCoSPreservation00
1.3.6.1.4.1.29601.2.71.3.1.1.8 fsEvcRowStatus00
1.3.6.1.4.1.29601.2.71.3.1.1.9 fsEvcMtu00
1.3.6.1.4.1.29601.2.71.3.1.1.10 fsEvcL2CPTunnel00
1.3.6.1.4.1.29601.2.71.3.1.1.11 fsEvcL2CPPeer00
1.3.6.1.4.1.29601.2.71.3.1.1.12 fsEvcL2CPDiscard00
1.3.6.1.4.1.29601.2.71.3.1.1.13 fsEvcLoopbackStatus00