Reference record for OID 1.3.6.1.4.1.193.72.300.30.1.21.4

Parent
1.3.6.1.4.1.193.72.300.30.1.21 (accessControlList)
Node code
4
Node name
vlanIdAclTable
Numeric OID
1.3.6.1.4.1.193.72.300.30.1.21.4
URN notation
urn:oid:1.3.6.1.4.1.193.72.300.30.1.21.4
ASN.1 notation

{1 3 6 1 4 1 193 72 300 30 1 21 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ericsson(193) diaxMIB(72) peaIpDslam(300) peaBridgeIpDslam(30) bridgeControl(1) accessControlList(21) vlanIdAclTable(4)}
OID-IRI notation
  • /1/3/6/1/4/1/193/72/300/30/1/21/4
  • /ISO/Identified-Organization/6/1/4/1/193/72/300/30/1/21/4
  • /ISO/3/6/1/4/1/193/72/300/30/1/21/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/identified-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/org/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/org/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/org/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/org/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/iso-organization/dod/internet/private/enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/iso-organization/dod/internet/private/enterprises/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable
  • /iso/iso-organization/dod/internet/private/vendor-objects/ericsson/diaxMIB/peaIpDslam/peaBridgeIpDslam/bridgeControl/accessControlList/vlanIdAclTable

Descriptions

vlanIdAclTable — Ericsson MIB copies (MibBrowser.online)

This table maintains a list of VLAN ID Access Control Lists in the IPDSLAM. Each Access Control List is made up of a group of access rules. The access rules are stored in the vlanIdAclRuleTable. This table is used to add/delete VLAN ID Access Control Lists. ACL's are statements which are called rules of ACL that are grouped together by a number. Within this group of statements, when a packet is processed by an ACL on the IPDSLAM, the IPDSLAM will go through certain steps in finding a match against the ACL statements. ACL's are processed top-down by the IPDSLAM. Using a top-down approach, a packet is compared to the first statement in the ACL, and if the IPDSLAM finds a match between the packet and the statement, the IPDSLAM will execute one of two actions included with the statement: - Permit - Deny If the IPDSLAM doesn't find a match of packet contents to the first ACL statement, the IPDSLAM will proceed to the next statement in the list, again going through the same matching process If there isn't a match on this statement, the IPDSLAM will keep on going through the list until it finds a match. If the IPDSLAM goes through the entire list and doesn't find a match, the IPDSLAM will drop the packet. If there is a match on a statement, no further statements are processed. Therefore, the order of the statements is very important in an ACL. Valid from: EDA 2.2 R3A

Source records

vlanIdAclTable

Status in source: current.

Names: vlanIdAclTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "vlanIdAclTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "VlanIdAclEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table maintains a list of VLAN ID Access Control Lists in the IPDSLAM. Each Access Control List is made up of a group of access rules. The access rules are stored in the vlanIdAclRuleTable. This table is used to add/delete VLAN ID Access Control Lists. ACL's are statements which are called rules of ACL that are grouped together by a number. Within this group of statements, when a packet is processed by an ACL on the IPDSLAM, the IPDSLAM will go through certain steps in finding a match against the ACL statements. ACL's are processed top-down by the IPDSLAM. Using a top-down approach, a packet is compared to the first statement in the ACL, and if the IPDSLAM finds a match between the packet and the statement, the IPDSLAM will execute one of two actions included with the statement: - Permit - Deny If the IPDSLAM doesn't find a match of packet contents to the first ACL statement, the IPDSLAM will proceed to the next statement in the list, again going through the same matching process If there isn't a match on this statement, the IPDSLAM will keep on going through the list until it finds a match. If the IPDSLAM goes through the entire list and doesn't find a match, the IPDSLAM will drop the packet. If there is a match on a statement, no further statements are processed. Therefore, the order of the statements is very important in an ACL. Valid from: EDA 2.2 R3A \"",
    "::=",
    "{",
    "accessControlList",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "VlanIdAclEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table maintains a list of VLAN ID Access Control Lists in the IPDSLAM. Each Access Control List is made up of a group of access rules. The access rules are stored in the vlanIdAclRuleTable. This table is used to add/delete VLAN ID Access Control Lists. ACL's are statements which are called rules of ACL that are grouped together by a number. Within this group of statements, when a packet is processed by an ACL on the IPDSLAM, the IPDSLAM will go through certain steps in finding a match against the ACL statements. ACL's are processed top-down by the IPDSLAM. Using a top-down approach, a packet is compared to the first statement in the ACL, and if the IPDSLAM finds a match between the packet and the statement, the IPDSLAM will execute one of two actions included with the statement: - Permit - Deny If the IPDSLAM doesn't find a match of packet contents to the first ACL statement, the IPDSLAM will proceed to the next statement in the list, again going through the same matching process If there isn't a match on this statement, the IPDSLAM will keep on going through the list until it finds a match. If the IPDSLAM goes through the entire list and doesn't find a match, the IPDSLAM will drop the packet. If there is a match on a statement, no further statements are processed. Therefore, the order of the statements is very important in an ACL. Valid from: EDA 2.2 R3A"
    ],
    null,
    null,
    null,
    null
  ]
}
  • Ericsson MIB copies (MibBrowser.online) · Publisher's source file: PEA-BRIDGE-IPDSLAM — archive MIB indexed for Ericsson

    Vendor MIB copy from the MibBrowser.online archive. Ericsson support.

    Module: PEA-BRIDGE-IPDSLAM

    Published definition
    vlanIdAclTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF VlanIdAclEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
        "This table maintains a list of VLAN ID Access Control Lists in the IPDSLAM.
         Each Access Control List is made up of a group of access rules. The
         access rules are stored in the vlanIdAclRuleTable. This table is used
         to add/delete VLAN ID Access Control Lists.
    
         ACL's are statements which are called rules of ACL that are grouped
         together by a number. Within this group of statements, when a packet
         is processed by an ACL on the IPDSLAM, the IPDSLAM will go through
         certain steps in finding a match against the ACL statements. ACL's are
         processed top-down by the IPDSLAM. Using a top-down approach, a packet
         is compared to the first statement in the ACL, and if the IPDSLAM finds
         a match between the packet and the statement, the IPDSLAM will execute
         one of two actions included with the statement:
    
         - Permit
         - Deny
    
         If the IPDSLAM doesn't find a match of packet contents to the first
         ACL statement, the IPDSLAM will proceed to the next statement in the list,
         again going through the same matching process If there isn't a match on
         this statement, the IPDSLAM will keep on going through the list until it
         finds a match. If the IPDSLAM goes through the entire list and doesn't
         find a match, the IPDSLAM will drop the packet.
    
         If there is a match on a statement, no further statements are processed.
         Therefore, the order of the statements is very important in an ACL.
    
         Valid from:                EDA 2.2 R3A
        "
        ::= { accessControlList 4 }
    Module imports
    {'SNMPv2-TC': ['TruthValue', 'TEXTUAL-CONVENTION', 'MacAddress', 'RowStatus', 'DateAndTime'], 'DIESEL-SMI': ['peaIpDslam'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'Unsigned32', 'IpAddress', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Counter32', 'Counter64', 'TimeTicks'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetPortNumber']}
    · Download PEA-BRIDGE-IPDSLAM — archive MIB indexed for Ericsson

    Related source files and packages:

    • DIESEL-SMI — archive MIB indexed for EricssonNative third-party archive copy; vendor association comes from the archive catalog and does not establish a current manufacturer release; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:11 GMT; 380 bytes
    • INET-ADDRESS-MIB — dependency MIB (MibBrowser.online)Native third-party archive dependency for Ericsson MIB imports; authorship is not attributed to that manufacturer; Native LAST-UPDATED: 200502040000Z; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:05 GMT; 17,177 bytes
    • SNMPv2-SMI — dependency MIB (MibBrowser.online)Native third-party archive dependency for Ericsson MIB imports; authorship is not attributed to that manufacturer; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:04 GMT; 10,283 bytes
    Show all 4 related files and packages
    • SNMPv2-TC — dependency MIB (MibBrowser.online)Native third-party archive dependency for Ericsson MIB imports; authorship is not attributed to that manufacturer; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:11 GMT; 38,034 bytes

    Source location: PEA-BRIDGE-IPDSLAM::vlanIdAclTable.
    Source version and references

    Published package: Ericsson archived MIB 200604251200Z; file: PEA-BRIDGE-IPDSLAM.mib.

    Native third-party archive copy; vendor association comes from the archive catalog and does not establish a current manufacturer release; Native LAST-UPDATED: 200604251200Z; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:13 GMT; 256,722 bytes

    Downloaded: 2026-10-27T05:19:20.410930+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.193)

David Partain

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.193)

Daniel Farias

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.193.72.300.30.1.21.4.5 vlanIdAclEntry33

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.193.72.300.30.1.21.6 vlanIdAclRuleTable16
1.3.6.1.4.1.193.72.300.30.1.21.10 etherTypeAclTable14
1.3.6.1.4.1.193.72.300.30.1.21.15 etherTypeAclRuleTable15
1.3.6.1.4.1.193.72.300.30.1.21.30 ipAclTable14
1.3.6.1.4.1.193.72.300.30.1.21.35 ipAclRuleTable122