Reference record for OID 1.3.6.1.4.1.562.36.2.1.100.3.9.10.1.5



parent
1.3.6.1.4.1.562.36.2.1.100.3.9.10.1 (mscVrPpSrtBpProvEntry)
node code
5
node name
mscVrPpSrtBpPortNum
dot oid
1.3.6.1.4.1.562.36.2.1.100.3.9.10.1.5
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nortel(562) msCarrier(36) mscPassport(2) mscComponents(1) mscVr(100) mscVrPp(3) mscVrPpSrtBp(9) mscVrPpSrtBpProvTable(10) mscVrPpSrtBpProvEntry(1) mscVrPpSrtBpPortNum(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) northernTelecom(562) msCarrier(36) mscPassport(2) mscComponents(1) mscVr(100) mscVrPp(3) mscVrPpSrtBp(9) mscVrPpSrtBpProvTable(10) mscVrPpSrtBpProvEntry(1) mscVrPpSrtBpPortNum(5)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) northernTelecom(562) msCarrier(36) mscPassport(2) mscComponents(1) mscVr(100) mscVrPp(3) mscVrPpSrtBp(9) mscVrPpSrtBpProvTable(10) mscVrPpSrtBpProvEntry(1) mscVrPpSrtBpPortNum(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nt(562) msCarrier(36) mscPassport(2) mscComponents(1) mscVr(100) mscVrPp(3) mscVrPpSrtBp(9) mscVrPpSrtBpProvTable(10) mscVrPpSrtBpProvEntry(1) mscVrPpSrtBpPortNum(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nortel(562) msCarrier(36) mscPassport(2) mscComponents(1) mscVr(100) mscVrPp(3) mscVrPpSrtBp(9) mscVrPpSrtBpProvTable(10) mscVrPpSrtBpProvEntry(1) mscVrPpSrtBpPortNum(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) northernTelecom(562) msCarrier(36) mscPassport(2) mscComponents(1) mscVr(100) mscVrPp(3) mscVrPpSrtBp(9) mscVrPpSrtBpProvTable(10) mscVrPpSrtBpProvEntry(1) mscVrPpSrtBpPortNum(5)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) northernTelecom(562) msCarrier(36) mscPassport(2) mscComponents(1) mscVr(100) mscVrPp(3) mscVrPpSrtBp(9) mscVrPpSrtBpProvTable(10) mscVrPpSrtBpProvEntry(1) mscVrPpSrtBpPortNum(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nt(562) msCarrier(36) mscPassport(2) mscComponents(1) mscVr(100) mscVrPp(3) mscVrPpSrtBp(9) mscVrPpSrtBpProvTable(10) mscVrPpSrtBpProvEntry(1) mscVrPpSrtBpPortNum(5)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/nortel/msCarrier/mscPassport/mscComponents/mscVr/mscVrPp/mscVrPpSrtBp/mscVrPpSrtBpProvTable/mscVrPpSrtBpProvEntry/mscVrPpSrtBpPortNum
  • /iso/identified-organization/dod/internet/private/enterprise/northernTelecom/msCarrier/mscPassport/mscComponents/mscVr/mscVrPp/mscVrPpSrtBp/mscVrPpSrtBpProvTable/mscVrPpSrtBpProvEntry/mscVrPpSrtBpPortNum
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/northernTelecom/msCarrier/mscPassport/mscComponents/mscVr/mscVrPp/mscVrPpSrtBp/mscVrPpSrtBpProvTable/mscVrPpSrtBpProvEntry/mscVrPpSrtBpPortNum
  • /iso/org/dod/internet/private/enterprise/nt/msCarrier/mscPassport/mscComponents/mscVr/mscVrPp/mscVrPpSrtBp/mscVrPpSrtBpProvTable/mscVrPpSrtBpProvEntry/mscVrPpSrtBpPortNum
  • /iso/org/dod/internet/private/enterprises/nortel/msCarrier/mscPassport/mscComponents/mscVr/mscVrPp/mscVrPpSrtBp/mscVrPpSrtBpProvTable/mscVrPpSrtBpProvEntry/mscVrPpSrtBpPortNum
  • /iso/org/dod/internet/private/enterprises/northernTelecom/msCarrier/mscPassport/mscComponents/mscVr/mscVrPp/mscVrPpSrtBp/mscVrPpSrtBpProvTable/mscVrPpSrtBpProvEntry/mscVrPpSrtBpPortNum
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/northernTelecom/msCarrier/mscPassport/mscComponents/mscVr/mscVrPp/mscVrPpSrtBp/mscVrPpSrtBpProvTable/mscVrPpSrtBpProvEntry/mscVrPpSrtBpPortNum
  • /iso/iso-identified-organization/dod/internet/private/enterprises/nt/msCarrier/mscPassport/mscComponents/mscVr/mscVrPp/mscVrPpSrtBp/mscVrPpSrtBpProvTable/mscVrPpSrtBpProvEntry/mscVrPpSrtBpPortNum
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/562/36/2/1/100/3/9/10/1/5

    Description by mibdepot

    This attribute is indicative of the unique number assigned to the bridge
    port. It is used for SNMP management of this bridge port and in
    spanning tree as an identifier this bridge port.
    Notes regarding portNum:

    Escape routines exist for initializing, copying, and deleting port
    numbers. This is necessary because SNMP requires a unique port
    instance identifier. The initPortNum escape routine sets the port number
    to a value in the range 1-255 for this purpose. The setCopiedPortNum
    escape routine exists to maintain the uniqueness of the port number in
    cases when one port is copied to another. When a bridge port is deleted,
    the releasePortNum escape routine places the port number being
    released into a pending deletion state. This is because the port number
    cannot be re-allocated until the port is truely deleted in the current view.
    This is necessary since there is no guarantee of order when processing
    changes to multiple protocol ports so without the pending deletion state,
    the same port number could be temporarily assigned to two ports for a
    short period of time.

    The portNum is set as component critical since bridging also uses the
    port number as a key for indexing into its data structures. If a port is
    deleted then re-added under the same protocol port, CAS treats the
    change as a SET to the portNum attribute.

    Parsed from file nortelPC-bridgeV1.mib.txt
    Company: None
    Module: Nortel-MsCarrier-MscPassport-BridgeMIB

    Description by circitor

    This attribute is indicative of the unique number assigned to the bridge
    port. It is used for SNMP management of this bridge port and in
    spanning tree as an identifier this bridge port.
    Notes regarding portNum:

    Escape routines exist for initializing, copying, and deleting port
    numbers. This is necessary because SNMP requires a unique port
    instance identifier. The initPortNum escape routine sets the port number
    to a value in the range 1-255 for this purpose. The setCopiedPortNum
    escape routine exists to maintain the uniqueness of the port number in
    cases when one port is copied to another. When a bridge port is deleted,
    the releasePortNum escape routine places the port number being
    released into a pending deletion state. This is because the port number
    cannot be re-allocated until the port is truely deleted in the current view.
    This is necessary since there is no guarantee of order when processing
    changes to multiple protocol ports so without the pending deletion state,
    the same port number could be temporarily assigned to two ports for a
    short period of time.

    The portNum is set as component critical since bridging also uses the
    port number as a key for indexing into its data structures. If a port is
    deleted then re-added under the same protocol port, CAS treats the
    change as a SET to the portNum attribute.

    Parsed from file Nortel-MsCarrier-MscPassport-BridgeMIB.mib
    Module: Nortel-MsCarrier-MscPassport-BridgeMIB

    Information by oid_info

    Vendor: Northern Telecom, Ltd.
    Module: Nortel-MsCarrier-MscPassport-BridgeMIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    mscVrPpSrtBpPortNum OBJECT-TYPE SYNTAX Unsigned32 (0..255) ACCESS read-only STATUS mandatory DESCRIPTION "This attribute is indicative of the unique number assigned to the bridge port. It is used for SNMP management of this bridge port and in spanning tree as an identifier this bridge port. Notes regarding portNum: Escape routines exist for initializing, copying, and deleting port numbers. This is necessary because SNMP requires a unique port instance identifier. The initPortNum escape routine sets the port number to a value in the range 1-255 for this purpose. The setCopiedPortNum escape routine exists to maintain the uniqueness of the port number in cases when one port is copied to another. When a bridge port is deleted, the releasePortNum escape routine places the port number being released into a pending deletion state. This is because the port number cannot be re-allocated until the port is truely deleted in the current view. This is necessary since there is no guarantee of order when processing changes to multiple protocol ports so without the pending deletion state, the same port number could be temporarily assigned to two ports for a short period of time. The portNum is set as component critical since bridging also uses the port number as a key for indexing into its data structures. If a port is deleted then re-added under the same protocol port, CAS treats the change as a SET to the portNum attribute." DEFVAL { 0 } ::= { mscVrPpSrtBpProvEntry 5 }

    Information by circitor

    mscVrPpSrtBpPortNum OBJECT-TYPE SYNTAX Unsigned32 (0..255) ACCESS read-only STATUS mandatory DESCRIPTION "This attribute is indicative of the unique number assigned to the bridge port. It is used for SNMP management of this bridge port and in spanning tree as an identifier this bridge port. Notes regarding portNum: Escape routines exist for initializing, copying, and deleting port numbers. This is necessary because SNMP requires a unique port instance identifier. The initPortNum escape routine sets the port number to a value in the range 1-255 for this purpose. The setCopiedPortNum escape routine exists to maintain the uniqueness of the port number in cases when one port is copied to another. When a bridge port is deleted, the releasePortNum escape routine places the port number being released into a pending deletion state. This is because the port number cannot be re-allocated until the port is truely deleted in the current view. This is necessary since there is no guarantee of order when processing changes to multiple protocol ports so without the pending deletion state, the same port number could be temporarily assigned to two ports for a short period of time. The portNum is set as component critical since bridging also uses the port number as a key for indexing into its data structures. If a port is deleted then re-added under the same protocol port, CAS treats the change as a SET to the portNum attribute." DEFVAL { 0 } ::= { mscVrPpSrtBpProvEntry 5 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.562)

    Sharon Chisholm

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.562)

    Mike Bobbitt

    Brothers (4)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.562.36.2.1.100.3.9.10.1.1 mscVrPpSrtBpTranslateIpx 0 0 This attribute specifies the type of translation to be performed on frames
    carrying IPX packets. Ethernet frames carrying IPX ...
    1.3.6.1.4.1.562.36.2.1.100.3.9.10.1.2 mscVrPpSrtBpFragmentIp 0 0 This attribute specifies if or not outbound frames carrying IP datagrams
    should be fragmented to conform to message transfer u...
    1.3.6.1.4.1.562.36.2.1.100.3.9.10.1.3 mscVrPpSrtBpServiceClass 0 0 This attribute specifies if the frames should be ordered or not before they
    are transmitted through a bridge port.
    If this attr...
    1.3.6.1.4.1.562.36.2.1.100.3.9.10.1.4 mscVrPpSrtBpConvertArpMacAddress 0 0 This attribute is indicative of the state of the MAC address format
    conversion process for ARP/RARP frames. The MAC addresses ...