OID reference

smdsAddressCodes

1.3.6.1.4.1.148.1.1.2.1.1.15

Description

This object provides hints on how an SMDS Address is divided into three fields. These three fields are used as indices into tables that need to be indexed by an SMDS address. These three fields provide for a user-friendly/readable format in order to do SETs and GETs. The three fields are country code, destination code…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.148.1.1.2.1.1 (smdsSubscrEntry)
Node code
15
Node name
smdsAddressCodes
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.148.1.1.2.1.1.15
URN notation
urn:oid:1.3.6.1.4.1.148.1.1.2.1.1.15
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-only
Status in MIB
mandatory
Allowed size (octets)
0–255

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 smdsSubscrIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.148.1.1.2.1.1.15.<smdsSubscrIndex>. Use an index value actually 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.1.1.15

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.

smdsAddressCodes OBJECT-TYPE







              SYNTAX  DisplayString (SIZE(0..255))
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "This object provides hints on how an SMDS Address
                      is divided into three fields.  These three fields
                      are used as indices into tables that need to be
                      indexed by an SMDS address.  These three fields
                      provide for a user-friendly/readable format in
                      order to do SETs and GETs.  The three fields are
                      country code, destination code, and subscriber
                      number.  Each field MUST only contain 1 to 9
                      digits and must NOT start with a zero.  All SMDS
                      addresses will have a country code.  Most SMDS
                      addresses will have a destination code (e.g., in
                      the US this number is the area code).  The
                      subscriber number is the rest of the SMDS address,
                      which is less than or equal to the remaining 9
                      digits.  For those SMDS addresses that do not have
                      a destination code or whose subscriber number is
                      more than 9 digits long, the destination code and
                      the subscriber number must be divided in a logical
                      way. Also, if a field starts with zero(s), then
                      these zero(s) must be the trailing zero(s) of the
                      previous field.  It is up to the service provider
                      to determine this logic.  This object describes
                      the way that the SMDS addresses are divided for
                      this SNI (ifIndex).  For example, in the US, this
                      object will contain the following text:  'Country
                      code = 1. Destination code = area code (e.g.,
                      908). Subscriber number = the remaining 7 digits
                      (e.g., 7582107). The OID looks like
                      objectName.1.908.7582107 and the SMDSAddress =
                      C19087582107FFFF in Hex'."
              ::= { smdsSubscrEntry 15 }

Meaning

Descriptions

1 unique

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

This object provides hints on how an SMDS Address is divided into three fields. These three fields are used as indices into tables that need to be indexed by an SMDS address. These three fields provide for a user-friendly/readable format in order to do SETs and GETs. The three fields are country code, destination code, and subscriber number. Each field MUST only contain 1 to 9 digits and must NOT start with a zero. All SMDS addresses will have a country code. Most SMDS addresses will have a destination code (e.g., in the US this number is the area code). The subscriber number is the rest of the SMDS address, which is less than or equal to the remaining 9 digits. For those SMDS addresses that do not have a destination code or whose subscriber number is more than 9 digits long, the destination code and the subscriber number must be divided in a logical way. Also, if a field starts with zero(s), then these zero(s) must be the trailing zero(s) of the previous field. It is up to the service provider to determine this logic. This object describes the way that the SMDS addresses are divided for this SNI (ifIndex). For example, in the US, this object will contain the following text: 'Country code = 1. Destination code = area code (e.g., 908). Subscriber number = the remaining 7 digits (e.g., 7582107). The OID looks like objectName.1.908.7582107 and the SMDSAddress = C19087582107FFFF in Hex'.

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

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

Status in source: mandatory.

Names: smdsAddressCodes

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "smdsAddressCodes",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"This object provides hints on how an SMDS Address is divided into three fields. These three fields are used as indices into tables that need to be indexed by an SMDS address. These three fields provide for a user-friendly/readable format in order to do SETs and GETs. The three fields are country code, destination code, and subscriber number. Each field MUST only contain 1 to 9 digits and must NOT start with a zero. All SMDS addresses will have a country code. Most SMDS addresses will have a destination code (e.g., in the US this number is the area code). The subscriber number is the rest of the SMDS address, which is less than or equal to the remaining 9 digits. For those SMDS addresses that do not have a destination code or whose subscriber number is more than 9 digits long, the destination code and the subscriber number must be divided in a logical way. Also, if a field starts with zero(s), then these zero(s) must be the trailing zero(s) of the previous field. It is up to the service provider to determine this logic. This object describes the way that the SMDS addresses are divided for this SNI (ifIndex). For example, in the US, this object will contain the following text: 'Country code = 1. Destination code = area code (e.g., 908). Subscriber number = the remaining 7 digits (e.g., 7582107). The OID looks like objectName.1.908.7582107 and the SMDSAddress = C19087582107FFFF in Hex'.\"",
    "::=",
    "{",
    "smdsSubscrEntry",
    "15",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "DisplayString",
      [
        "octetStringSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This object provides hints on how an SMDS Address is divided into three fields. These three fields are used as indices into tables that need to be indexed by an SMDS address. These three fields provide for a user-friendly/readable format in order to do SETs and GETs. The three fields are country code, destination code, and subscriber number. Each field MUST only contain 1 to 9 digits and must NOT start with a zero. All SMDS addresses will have a country code. Most SMDS addresses will have a destination code (e.g., in the US this number is the area code). The subscriber number is the rest of the SMDS address, which is less than or equal to the remaining 9 digits. For those SMDS addresses that do not have a destination code or whose subscriber number is more than 9 digits long, the destination code and the subscriber number must be divided in a logical way. Also, if a field starts with zero(s), then these zero(s) must be the trailing zero(s) of the previous field. It is up to the service provider to determine this logic. This object describes the way that the SMDS addresses are divided for this SNI (ifIndex). For example, in the US, this object will contain the following text: 'Country code = 1. Destination code = area code (e.g., 908). Subscriber number = the remaining 7 digits (e.g., 7582107). The OID looks like objectName.1.908.7582107 and the SMDSAddress = C19087582107FFFF in Hex'."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.148)

Tesink Kaj

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.148.1.1.2.1.1.1 smdsSubscrIndex00
1.3.6.1.4.1.148.1.1.2.1.1.2 smdsContact00
1.3.6.1.4.1.148.1.1.2.1.1.3 smdsSNILocation00
1.3.6.1.4.1.148.1.1.2.1.1.4 smdsAccessClass00
1.3.6.1.4.1.148.1.1.2.1.1.5 smdsMCDUsIn00
1.3.6.1.4.1.148.1.1.2.1.1.6 smdsMCDUsInChange00
1.3.6.1.4.1.148.1.1.2.1.1.7 smdsMCDUsOut00
1.3.6.1.4.1.148.1.1.2.1.1.8 smdsMCDUsOutChange00
1.3.6.1.4.1.148.1.1.2.1.1.9 smdsUnassignedSAs00
1.3.6.1.4.1.148.1.1.2.1.1.10 smdsAccessClassExceededCounts00
1.3.6.1.4.1.148.1.1.2.1.1.11 smdsSAScreenViolations00
1.3.6.1.4.1.148.1.1.2.1.1.12 smdsDAScreenViolations00
1.3.6.1.4.1.148.1.1.2.1.1.13 smdsMCDUsExceededAtIngressCounts00
1.3.6.1.4.1.148.1.1.2.1.1.14 smdsMCDUsExceededAtEgressCounts00