OID reference

ipBaseAddress

1.3.6.1.4.1.6368.2.4.5

Description

Base address for the computation of the IP addresses for the management interfaces of the cards. When the PEMServer wants to connect to a card in the rack, it computes the card IP address from ipBaseAddress, the slot number of the card, and the systemNumber of the rack (also in pegasusSystem), as follows: the slot num…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6368.2.4 (pegasusSystem)
Node code
5
Node name
ipBaseAddress
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6368.2.4.5
URN notation
urn:oid:1.3.6.1.4.1.6368.2.4.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) pegasusSystem(4) ipBaseAddress(5)}
OID-IRI notation
  • /1/3/6/1/4/1/6368/2/4/5
  • /ISO/Identified-Organization/6/1/4/1/6368/2/4/5
  • /ISO/3/6/1/4/1/6368/2/4/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/6368/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/identified-organization/dod/internet/private/enterprise/schmidtelecom/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/identified-organization/dod/internet/private/enterprises/6368/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/identified-organization/dod/internet/private/enterprises/schmidtelecom/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/6368/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/schmidtelecom/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/identified-organization/dod/internet/private/vendor-objects/6368/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/identified-organization/dod/internet/private/vendor-objects/schmidtelecom/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/org/dod/internet/private/enterprise/6368/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/org/dod/internet/private/enterprise/schmidtelecom/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/org/dod/internet/private/enterprises/6368/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/org/dod/internet/private/enterprises/schmidtelecom/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/org/dod/internet/private/ldap-enterprise/6368/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/org/dod/internet/private/ldap-enterprise/schmidtelecom/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/org/dod/internet/private/vendor-objects/6368/pegasusMibModule/pegasusSystem/ipBaseAddress
  • /iso/org/dod/internet/private/vendor-objects/schmidtelecom/pegasusMibModule/pegasusSystem/ipBaseAddress
  • Additional combinations skipped.

SNMP properties

Value type
IpAddress
Maximum access defined by MIB
read-write
Status in MIB
current

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.6368.2.4.5.0

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.

ipBaseAddress OBJECT-TYPE
  SYNTAX      IpAddress
  MAX-ACCESS  read-write
  STATUS      current
  DESCRIPTION
      "Base address for the computation of the IP addresses for the management
      interfaces of the cards. When the PEMServer wants to connect to a card
      in the rack, it computes the card IP address from ipBaseAddress, the slot
      number of the card, and the systemNumber of the rack (also in
      pegasusSystem), as follows: the slot number is added to the last byte
      of ipBaseAddress, modulo 256, and the systemNumber is added to the next
      to last byte of ipBaseAddress, again modulo 256.

      Example                      1               2               3
      iPBaseAddress        |192.168.  0.  0|192.168.244.231|192.168.  0.  0
      systemNumber         |         +4    |         +4    |         +4
      slot number          |             +1|             +3|             +5
      sum                  |          4   1|          4 234|          4   5
      sum modulo 256       |          4   1|          4 234|          4   5
      Resulting mgmt IP-#  |192.168.  4.  1|192.168.248.234|192.168.  4.  5

      The slot cards compute their own management interface IP addresses in
      a similar way, using their own ip base addresses.  These base addresses
      are not visible through the PEM Client or SNMP. To read or change them
      on a card, the CLI must be used.

      All slot cards within a PEGASUS system must have the management IP
      addresses in the same network in order to communicate with each other.
      They must then have the same base address (with the exception
      of biasing, as explained below).
      The base addresses of all cards are usually chosen such that the
      management IP addresses end up in a non-routable (private) networks.

      Biasing: cards read slot and rack numbers through dedicated pins on
      their backplane plugs.  If such a pin is damaged, cards read bad
      numbers and compute bad (possibly conflicting) IP addresses.
      In this case, the CLI can be used to set the base address such that the
      resulting address is still correct."
  REFERENCE
          "RFC 1597, Section 3, Private Address Space"
   ::= { pegasusSystem 5 }

Meaning

Descriptions

1 unique

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

Base address for the computation of the IP addresses for the management interfaces of the cards. When the PEMServer wants to connect to a card in the rack, it computes the card IP address from ipBaseAddress, the slot number of the card, and the systemNumber of the rack (also in pegasusSystem), as follows: the slot number is added to the last byte of ipBaseAddress, modulo 256, and the systemNumber is added to the next to last byte of ipBaseAddress, again modulo 256. Example 1 2 3 iPBaseAddress |192.168. 0. 0|192.168.244.231|192.168. 0. 0 systemNumber | +4 | +4 | +4 slot number | +1| +3| +5 sum | 4 1| 4 234| 4 5 sum modulo 256 | 4 1| 4 234| 4 5 Resulting mgmt IP-# |192.168. 4. 1|192.168.248.234|192.168. 4. 5 The slot cards compute their own management interface IP addresses in a similar way, using their own ip base addresses. These base addresses are not visible through the PEM Client or SNMP. To read or change them on a card, the CLI must be used. All slot cards within a PEGASUS system must have the management IP addresses in the same network in order to communicate with each other. They must then have the same base address (with the exception of biasing, as explained below). The base addresses of all cards are usually chosen such that the management IP addresses end up in a non-routable (private) networks. Biasing: cards read slot and rack numbers through dedicated pins on their backplane plugs. If such a pin is damaged, cards read bad numbers and compute bad (possibly conflicting) IP addresses. In this case, the CLI can be used to set the base address such that the resulting address is still correct.

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

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

Status in source: current.

Names: ipBaseAddress

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ipBaseAddress",
    "OBJECT-TYPE",
    "SYNTAX",
    "IpAddress",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Base address for the computation of the IP addresses for the management interfaces of the cards. When the PEMServer wants to connect to a card in the rack, it computes the card IP address from ipBaseAddress, the slot number of the card, and the systemNumber of the rack (also in pegasusSystem), as follows: the slot number is added to the last byte of ipBaseAddress, modulo 256, and the systemNumber is added to the next to last byte of ipBaseAddress, again modulo 256. Example 1 2 3 iPBaseAddress |192.168. 0. 0|192.168.244.231|192.168. 0. 0 systemNumber | +4 | +4 | +4 slot number | +1| +3| +5 sum | 4 1| 4 234| 4 5 sum modulo 256 | 4 1| 4 234| 4 5 Resulting mgmt IP-# |192.168. 4. 1|192.168.248.234|192.168. 4. 5 The slot cards compute their own management interface IP addresses in a similar way, using their own ip base addresses. These base addresses are not visible through the PEM Client or SNMP. To read or change them on a card, the CLI must be used. All slot cards within a PEGASUS system must have the management IP addresses in the same network in order to communicate with each other. They must then have the same base address (with the exception of biasing, as explained below). The base addresses of all cards are usually chosen such that the management IP addresses end up in a non-routable (private) networks. Biasing: cards read slot and rack numbers through dedicated pins on their backplane plugs. If such a pin is damaged, cards read bad numbers and compute bad (possibly conflicting) IP addresses. In this case, the CLI can be used to set the base address such that the resulting address is still correct.\"",
    "REFERENCE",
    "\"RFC 1597, Section 3, Private Address Space\"",
    "::=",
    "{",
    "pegasusSystem",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "IpAddress",
      null
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Base address for the computation of the IP addresses for the management interfaces of the cards. When the PEMServer wants to connect to a card in the rack, it computes the card IP address from ipBaseAddress, the slot number of the card, and the systemNumber of the rack (also in pegasusSystem), as follows: the slot number is added to the last byte of ipBaseAddress, modulo 256, and the systemNumber is added to the next to last byte of ipBaseAddress, again modulo 256. Example 1 2 3 iPBaseAddress |192.168. 0. 0|192.168.244.231|192.168. 0. 0 systemNumber | +4 | +4 | +4 slot number | +1| +3| +5 sum | 4 1| 4 234| 4 5 sum modulo 256 | 4 1| 4 234| 4 5 Resulting mgmt IP-# |192.168. 4. 1|192.168.248.234|192.168. 4. 5 The slot cards compute their own management interface IP addresses in a similar way, using their own ip base addresses. These base addresses are not visible through the PEM Client or SNMP. To read or change them on a card, the CLI must be used. All slot cards within a PEGASUS system must have the management IP addresses in the same network in order to communicate with each other. They must then have the same base address (with the exception of biasing, as explained below). The base addresses of all cards are usually chosen such that the management IP addresses end up in a non-routable (private) networks. Biasing: cards read slot and rack numbers through dedicated pins on their backplane plugs. If such a pin is damaged, cards read bad numbers and compute bad (possibly conflicting) IP addresses. In this case, the CLI can be used to set the base address such that the resulting address is still correct."
    ],
    [
      "REFERENCE",
      "RFC 1597, Section 3, Private Address Space"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6368)

Poltera Gian Lucas

Siblings (21)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6368.2.4.1 autoPersistDelay00
1.3.6.1.4.1.6368.2.4.2 autoPersistEnabled00
1.3.6.1.4.1.6368.2.4.3 configPriority00
1.3.6.1.4.1.6368.2.4.4 hwAdaptionPolicy00
1.3.6.1.4.1.6368.2.4.6 javaRuntimeVersion00
1.3.6.1.4.1.6368.2.4.7 javaVMName00
1.3.6.1.4.1.6368.2.4.8 javaVMVersion00
1.3.6.1.4.1.6368.2.4.9 mgmtIPAddress00
1.3.6.1.4.1.6368.2.4.11 osArchitecture00
1.3.6.1.4.1.6368.2.4.12 osNameAndVersion00
1.3.6.1.4.1.6368.2.4.13 pemVersion00
1.3.6.1.4.1.6368.2.4.14 startedBy00
1.3.6.1.4.1.6368.2.4.15 systemNumber00
1.3.6.1.4.1.6368.2.4.16 mibRevision00
1.3.6.1.4.1.6368.2.4.17 readCommunity00
1.3.6.1.4.1.6368.2.4.18 writeCommunity00
1.3.6.1.4.1.6368.2.4.19 trapCommunity00
1.3.6.1.4.1.6368.2.4.20 trapDestination00
1.3.6.1.4.1.6368.2.4.21 agentPort00
1.3.6.1.4.1.6368.2.4.22 authRespEnabled00
1.3.6.1.4.1.6368.2.4.23 rackAlarmStatus00