OID reference

individualAddressScreenTable

1.3.6.1.4.1.148.1.1.2.3.5

Description

This list identifies the individual addresses that will be screened per individual address screen table. The are up to s (s is equal to 4) individual address screens per SNI and at least one individual address screen per SNI. The Individual Address Screens and the Group Address Screens together consist of up to n addr…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.148.1.1.2.3 (addressScreening)
Node code
5
Node name
individualAddressScreenTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.148.1.1.2.3.5
URN notation
urn:oid:1.3.6.1.4.1.148.1.1.2.3.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 148 1 1 2 3 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bellcore(148) requirements(1) taTsv001062(1) smdsSubscr(2) addressScreening(3) individualAddressScreenTable(5)}
OID-IRI notation
  • /1/3/6/1/4/1/148/1/1/2/3/5
  • /ISO/Identified-Organization/6/1/4/1/148/1/1/2/3/5
  • /ISO/3/6/1/4/1/148/1/1/2/3/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/148/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/identified-organization/dod/internet/private/enterprise/bellcore/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/identified-organization/dod/internet/private/enterprises/148/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/identified-organization/dod/internet/private/enterprises/bellcore/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/148/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bellcore/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/148/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/bellcore/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/org/dod/internet/private/enterprise/148/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/org/dod/internet/private/enterprise/bellcore/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/org/dod/internet/private/enterprises/148/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/org/dod/internet/private/enterprises/bellcore/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/org/dod/internet/private/ldap-enterprise/148/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/org/dod/internet/private/ldap-enterprise/bellcore/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/org/dod/internet/private/vendor-objects/148/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • /iso/org/dod/internet/private/vendor-objects/bellcore/requirements/taTsv001062/smdsSubscr/addressScreening/individualAddressScreenTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF IndividualAddressScreenEntry
Maximum access defined by MIB
not-accessible
Status in MIB
mandatory

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.

individualAddressScreenTable  OBJECT-TYPE
              SYNTAX  SEQUENCE OF IndividualAddressScreenEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This list identifies the individual addresses
                      that will be screened per individual address
                      screen table.  The are up to s (s is equal to 4)
                      individual address screens per SNI and at least
                      one individual address screen per SNI.  The
                      Individual Address Screens and the Group Address
                      Screens together consist of up to n addresses.
                      The initial value of n is defined as 128. In the
                      future a value of n up to 2048 may be supported.
                      The Individual Address Screen is used to perform
                      Destination Address Screening for individually
                      addressed data units and Source Address Screening
                      for all data units.  The Group Address Screen is
                      used to perform Destination Address Screening for
                      group addressed data units."
              ::= { addressScreening 5 }

Meaning

Descriptions

1 unique

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

This list identifies the individual addresses that will be screened per individual address screen table. The are up to s (s is equal to 4) individual address screens per SNI and at least one individual address screen per SNI. The Individual Address Screens and the Group Address Screens together consist of up to n addresses. The initial value of n is defined as 128. In the future a value of n up to 2048 may be supported. The Individual Address Screen is used to perform Destination Address Screening for individually addressed data units and Source Address Screening for all data units. The Group Address Screen is used to perform Destination Address Screening for group addressed data units.

Sources for this description

Bellcore MIB copies (IPNetwork Monitor archive)

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 1Bellcore MIB copies (IPNetwork Monitor archive)1 record · 1 source

Description 1

individualAddressScreenTable · mandatoryBellcore MIB copies (IPNetwork Monitor archive)1 source

Status in source: mandatory.

Names: individualAddressScreenTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "individualAddressScreenTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "IndividualAddressScreenEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"This list identifies the individual addresses that will be screened per individual address screen table. The are up to s (s is equal to 4) individual address screens per SNI and at least one individual address screen per SNI. The Individual Address Screens and the Group Address Screens together consist of up to n addresses. The initial value of n is defined as 128. In the future a value of n up to 2048 may be supported. The Individual Address Screen is used to perform Destination Address Screening for individually addressed data units and Source Address Screening for all data units. The Group Address Screen is used to perform Destination Address Screening for group addressed data units.\"",
    "::=",
    "{",
    "addressScreening",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "IndividualAddressScreenEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This list identifies the individual addresses that will be screened per individual address screen table. The are up to s (s is equal to 4) individual address screens per SNI and at least one individual address screen per SNI. The Individual Address Screens and the Group Address Screens together consist of up to n addresses. The initial value of n is defined as 128. In the future a value of n up to 2048 may be supported. The Individual Address Screen is used to perform Destination Address Screening for individually addressed data units and Source Address Screening for all data units. The Group Address Screen is used to perform Destination Address Screening for group addressed data units."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.148)

Tesink Kaj

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.148.1.1.2.3.5.1 individualAddressScreenEntry88

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.148.1.1.2.3.1 addressScreeningMasterTable16
1.3.6.1.4.1.148.1.1.2.3.2 numberAndDefaultScreeningTable19
1.3.6.1.4.1.148.1.1.2.3.3 associatedAddressesIndScreenTable110
1.3.6.1.4.1.148.1.1.2.3.4 associatedAddressesGrpScreenTable19
1.3.6.1.4.1.148.1.1.2.3.6 groupAddressScreenTable19