OID reference

screenStatusChange

1.3.6.1.4.1.148.1.1.2.3.1.1.5

Description

This object is used to change the screenStatus. If this object is different from the screenStatus, then the screenStatus is undergoing change. When these objects are the same, then the screenStatus is stable. The agent may refuse the change to be made and thus return the value for screenStatusChange to its previous va…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.148.1.1.2.3.1.1 (addressScreeningMasterEntry)
Node code
5
Node name
screenStatusChange
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.148.1.1.2.3.1.1.5
URN notation
urn:oid:1.3.6.1.4.1.148.1.1.2.3.1.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Enumerated values

ValueName
1allowed
2disallowed
3empty
4notSupported

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.

In SMDS-Subscription-MIB, the row index consists of these components in order:

  1. sniScreenIndex (INTEGER): one numeric subidentifier for the non-negative value.
  2. screenIndex (INTEGER): one numeric subidentifier for the non-negative value.
  3. screenType (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.148.1.1.2.3.1.1.5.<sniScreenIndex>.<screenIndex>.<screenType>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.148.1.1.2.3.1.1.5

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.

screenStatusChange OBJECT-TYPE
              SYNTAX  INTEGER {
                   allowed (1),
                   disallowed (2),
                   empty (3),
                   notSupported (4)
              }
              ACCESS  read-write
              STATUS  mandatory
              DESCRIPTION
                      "This object is used to change the screenStatus.
                      If this object is different from the screenStatus,
                      then the screenStatus is undergoing change.  When
                      these objects are the same, then the screenStatus
                      is stable.  The agent may refuse the change to be
                      made and thus return the value for
                      screenStatusChange to its previous value which is
                      equal to the screenStatus value.  If the agent
                      accepts the change, the screenStatus value will be
                      set equal to the screenStatusChange value.  An NMS
                      may SET the screenStatus to empty to clean out all
                      the addresses in an individualAddressScreenTable
                      or a groupAddressScreenTable.  The addresses in
                      the associatedAddressesIndScreenTable and
                      associatedAddressesGrpScreenTable would need to be
                      moved to another screening list (otherwise,
                      screening would be turned off for these addresses
                      and all packets will be allowed through for these
                      associated SNI addresses).  An NMS may not SET the







                      status of screenStatusChange if the value of
                      screenStatus is equal to notSupported and the
                      value of screenStatusChange is equal to
                      notSupported.  If an NMS tries to SET the status
                      of screenStatusChange to notSupported or to move
                      it from the notSupported state, then the agent
                      will return badValue.  An SNI must have at least
                      one Individual Address Screen and one Group
                      Address Screen, in which case all their SNI
                      addresses are associated with that screen.  See
                      reference TR-TSV-000772 for the requirements and
                      objectives on address screening."
              ::= { addressScreeningMasterEntry 5 }

Meaning

Descriptions

1 unique

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

This object is used to change the screenStatus. If this object is different from the screenStatus, then the screenStatus is undergoing change. When these objects are the same, then the screenStatus is stable. The agent may refuse the change to be made and thus return the value for screenStatusChange to its previous value which is equal to the screenStatus value. If the agent accepts the change, the screenStatus value will be set equal to the screenStatusChange value. An NMS may SET the screenStatus to empty to clean out all the addresses in an individualAddressScreenTable or a groupAddressScreenTable. The addresses in the associatedAddressesIndScreenTable and associatedAddressesGrpScreenTable would need to be moved to another screening list (otherwise, screening would be turned off for these addresses and all packets will be allowed through for these associated SNI addresses). An NMS may not SET the status of screenStatusChange if the value of screenStatus is equal to notSupported and the value of screenStatusChange is equal to notSupported. If an NMS tries to SET the status of screenStatusChange to notSupported or to move it from the notSupported state, then the agent will return badValue. An SNI must have at least one Individual Address Screen and one Group Address Screen, in which case all their SNI addresses are associated with that screen. See reference TR-TSV-000772 for the requirements and objectives on address screening.

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

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

Status in source: mandatory.

Names: screenStatusChange

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "screenStatusChange",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "allowed",
    "(",
    "1",
    ")",
    ",",
    "disallowed",
    "(",
    "2",
    ")",
    ",",
    "empty",
    "(",
    "3",
    ")",
    ",",
    "notSupported",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"This object is used to change the screenStatus. If this object is different from the screenStatus, then the screenStatus is undergoing change. When these objects are the same, then the screenStatus is stable. The agent may refuse the change to be made and thus return the value for screenStatusChange to its previous value which is equal to the screenStatus value. If the agent accepts the change, the screenStatus value will be set equal to the screenStatusChange value. An NMS may SET the screenStatus to empty to clean out all the addresses in an individualAddressScreenTable or a groupAddressScreenTable. The addresses in the associatedAddressesIndScreenTable and associatedAddressesGrpScreenTable would need to be moved to another screening list (otherwise, screening would be turned off for these addresses and all packets will be allowed through for these associated SNI addresses). An NMS may not SET the status of screenStatusChange if the value of screenStatus is equal to notSupported and the value of screenStatusChange is equal to notSupported. If an NMS tries to SET the status of screenStatusChange to notSupported or to move it from the notSupported state, then the agent will return badValue. An SNI must have at least one Individual Address Screen and one Group Address Screen, in which case all their SNI addresses are associated with that screen. See reference TR-TSV-000772 for the requirements and objectives on address screening.\"",
    "::=",
    "{",
    "addressScreeningMasterEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "allowed",
            1
          ],
          [
            "disallowed",
            2
          ],
          [
            "empty",
            3
          ],
          [
            "notSupported",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This object is used to change the screenStatus. If this object is different from the screenStatus, then the screenStatus is undergoing change. When these objects are the same, then the screenStatus is stable. The agent may refuse the change to be made and thus return the value for screenStatusChange to its previous value which is equal to the screenStatus value. If the agent accepts the change, the screenStatus value will be set equal to the screenStatusChange value. An NMS may SET the screenStatus to empty to clean out all the addresses in an individualAddressScreenTable or a groupAddressScreenTable. The addresses in the associatedAddressesIndScreenTable and associatedAddressesGrpScreenTable would need to be moved to another screening list (otherwise, screening would be turned off for these addresses and all packets will be allowed through for these associated SNI addresses). An NMS may not SET the status of screenStatusChange if the value of screenStatus is equal to notSupported and the value of screenStatusChange is equal to notSupported. If an NMS tries to SET the status of screenStatusChange to notSupported or to move it from the notSupported state, then the agent will return badValue. An SNI must have at least one Individual Address Screen and one Group Address Screen, in which case all their SNI addresses are associated with that screen. See reference TR-TSV-000772 for the requirements and objectives on address screening."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.148)

Tesink Kaj

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.148.1.1.2.3.1.1.1 sniScreenIndex00
1.3.6.1.4.1.148.1.1.2.3.1.1.2 screenIndex00
1.3.6.1.4.1.148.1.1.2.3.1.1.3 screenType00
1.3.6.1.4.1.148.1.1.2.3.1.1.4 screenStatus00