Reference record for OID 1.3.6.1.2.1.10.44.1.3


parent
1.3.6.1.2.1.10.44.1 (frnetservObjects)
node code
3
node name
frPVCEndptTable
dot oid
1.3.6.1.2.1.10.44.1.3
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) frnetservMIB(44) frnetservObjects(1) frPVCEndptTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) frnetservMIB(44) frnetservObjects(1) frPVCEndptTable(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) frnetservMIB(44) frnetservObjects(1) frPVCEndptTable(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) frnetservMIB(44) frnetservObjects(1) frPVCEndptTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) frnetservMIB(44) frnetservObjects(1) frPVCEndptTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) frnetservMIB(44) frnetservObjects(1) frPVCEndptTable(3)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/transmission/frnetservMIB/frnetservObjects/frPVCEndptTable
  • /iso/identified-organization/dod/internet/mgmt/mib/transmission/frnetservMIB/frnetservObjects/frPVCEndptTable
  • /iso/org/dod/internet/mgmt/mib-2/transmission/frnetservMIB/frnetservObjects/frPVCEndptTable
  • /iso/org/dod/internet/mgmt/mib/transmission/frnetservMIB/frnetservObjects/frPVCEndptTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/transmission/frnetservMIB/frnetservObjects/frPVCEndptTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/transmission/frnetservMIB/frnetservObjects/frPVCEndptTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/10/44/1/3

    Description by oid_info

    frPVCEndptTable OBJECT-TYPE SYNTAX SEQUENCE OF FrPVCEndptEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
    "The Frame Relay PVC End-Point table. This table
    is used to model a PVC end-point. This table
    contains the traffic parameters and statistics for
    a PVC end-point.
    This table is used to identify the traffic
    parameters for a bi-directional PVC segment end-point, and it also provides statistics for a PVC
    segment end-point.
    A PVC segment end-point is identified by a UNI/NNI
    logical port index value and DLCI index value.
    If the frame relay service provider allows the
    frame relay CNM subscriber to create, modify or
    delete PVCs using SNMP, then this table is used to
    identify and reserve the requested traffic
    parameters of each PVC segment end-point. The
    Connection table is used to connect the end-
    points together. Not all implementations will
    support the capability of
    creating/modifying/deleting PVCs using SNMP as a
    feature of frame relay CNM service.
    Uni-directional PVCs are modeled with zero valued
    traffic parameters in one of the directions (In or
    Out direction) in this table.
    To create a PVC, the following procedures shall be
    followed:
    1) Create the entries for the PVC segment
    endpoints in the frPVCEndptTable by specifying
    the traffic parameters for the bi-directional
    PVC segment endpoints. As shown in figure 2, a
    point-to-point PVC has two endpoints, thus two
    entries in this table. Uni-directional PVCs
    are modeled with zero valued traffic
    parameters in one direction; all the `In
    direction parameters for one frame relay PVC
    End-point or all the `Out direction
    parameters for the other frame relay PVC
    Endpoint.
    2) Go to the Frame Relay Connection Group."

    View at oid-info.com

    Description by mibdepot

    The Frame Relay PVC End-Point table. This table
    is used to model a PVC end-point. This table
    contains the traffic parameters and statistics for
    a PVC end-point.

    Parsed from file rfc1604.mib.txt
    Company: None
    Module: FRNETSERV-MIB

    Description by circitor

    The Frame Relay PVC End-Point table. This table
    is used to model a PVC end-point. This table
    contains the traffic parameters and statistics for
    a PVC end-point.

    This table is used to identify the traffic
    parameters for a bi-directional PVC segment end-

    point, and it also provides statistics for a PVC
    segment end-point.

    A PVC segment end-point is identified by a UNI/NNI
    logical port index value and DLCI index value.

    If the frame relay service provider allows the
    frame relay CNM subscriber to create, modify or
    delete PVCs using SNMP, then this table is used to
    identify and reserve the requested traffic
    parameters of each PVC segment end-point. The
    Connection table is used to 'connect' the end-
    points together. Not all implementations will
    support the capability of
    creating/modifying/deleting PVCs using SNMP as a
    feature of frame relay CNM service.

    Uni-directional PVCs are modeled with zero valued
    traffic parameters in one of the directions (In or
    Out direction) in this table.

    To create a PVC, the following procedures shall be
    followed:

    1) Create the entries for the PVC segment
    endpoints in the frPVCEndptTable by specifying
    the traffic parameters for the bi-directional
    PVC segment endpoints. As shown in figure 2, a
    point-to-point PVC has two endpoints, thus two
    entries in this table. Uni-directional PVCs
    are modeled with zero valued traffic
    parameters in one direction; all the `In'
    direction parameters for one frame relay PVC
    End-point or all the `Out' direction
    parameters for the other frame relay PVC
    Endpoint.

    In _____________________________ Out
    >>>>>>| |>>>>>>>>
    ______| Frame Relay Network |________
    Out | | In
    <<<<<<|_____________________________|<<<<<<<<
    Frame Relay Frame Relay
    PVC PVC
    Endpoint Endpoint

    Figure 2, PVC Terminology


    2) Go to the Frame Relay Connection Group.

    Parsed from file FRNETSERV-MIB.mib
    Module: FRNETSERV-MIB

    Information by oid_info

    Automatically extracted from RFC2954

    Information by mibdepot

    frPVCEndptTable OBJECT-TYPE SYNTAX SEQUENCE OF FrPVCEndptEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay PVC End-Point table. This table is used to model a PVC end-point. This table contains the traffic parameters and statistics for a PVC end-point." ::= { frnetservObjects 3 }

    Information by circitor

    frPVCEndptTable OBJECT-TYPE SYNTAX SEQUENCE OF FrPVCEndptEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay PVC End-Point table. This table is used to model a PVC end-point. This table contains the traffic parameters and statistics for a PVC end-point. This table is used to identify the traffic parameters for a bi-directional PVC segment end- point, and it also provides statistics for a PVC segment end-point. A PVC segment end-point is identified by a UNI/NNI logical port index value and DLCI index value. If the frame relay service provider allows the frame relay CNM subscriber to create, modify or delete PVCs using SNMP, then this table is used to identify and reserve the requested traffic parameters of each PVC segment end-point. The Connection table is used to 'connect' the end- points together. Not all implementations will support the capability of creating/modifying/deleting PVCs using SNMP as a feature of frame relay CNM service. Uni-directional PVCs are modeled with zero valued traffic parameters in one of the directions (In or Out direction) in this table. To create a PVC, the following procedures shall be followed: 1) Create the entries for the PVC segment endpoints in the frPVCEndptTable by specifying the traffic parameters for the bi-directional PVC segment endpoints. As shown in figure 2, a point-to-point PVC has two endpoints, thus two entries in this table. Uni-directional PVCs are modeled with zero valued traffic parameters in one direction; all the `In' direction parameters for one frame relay PVC End-point or all the `Out' direction parameters for the other frame relay PVC Endpoint. In _____________________________ Out >>>>>>| |>>>>>>>> ______| Frame Relay Network |________ Out | | In <<<<<<|_____________________________|<<<<<<<< Frame Relay Frame Relay PVC PVC Endpoint Endpoint Figure 2, PVC Terminology 2) Go to the Frame Relay Connection Group." ::= { frnetservObjects 3 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.10.44.1.3.1 frPVCEndptEntry 31 31 An entry in the Frame Relay PVC Endpoint table.

    Brothers (6)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.10.44.1.1 frLportTable 1 13 The Frame Relay Logical Port Information table.
    1.3.6.1.2.1.10.44.1.2 frMgtVCSigTable 1 26 The Frame Relay Management VC Signaling
    Parameters and Errors table.
    1.3.6.1.2.1.10.44.1.4 frPVCConnectIndexValue 1 1 This object contains an appropriate value to be
    used for frPVCConnectIndex when creating entries
    in the frPVCConnectTable. The v…
    1.3.6.1.2.1.10.44.1.5 frPVCConnectTable 1 14 The Frame Relay PVC Connect table. A bi-
    directional PVC segment is modeled as one entry in
    this table.
    1.3.6.1.2.1.10.44.1.6 frAccountPVCTable 1 5 The Frame Relay Accounting PVC table. This table
    is used to perform accounting on a PVC segment
    end-point basis.
    1.3.6.1.2.1.10.44.1.7 frAccountLportTable 1 4 The Frame Relay Accounting Logical Port table.
    This table is used to perform accounting on a
    UNI/NNI Logical Port basis.