This object returns a hint to be used for frPVCConnectIndex when creating entries in the frPVCConnectTable.
The value 0 indicates that no unassigned entries are available.
To obtain the frPVCConnectIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent must modify the value to the next unassigned index to prevent assignment of the same value to multiple management systems.
A management system should repeat the read to obtain a new value should an attempt to create the new row using the previously returned hint fail.
Table details
frLportTable
1.3.6.1.2.1.10.44.1.1
Index: ifIndex
The Frame Relay Logical Port Information table is an interface-specific addendum to the generic ifTable of the Interface MIB.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
The value of this object identifies the network address numbering plan for this UNI/NNI logical port. The network address is the object ifPhysAddress. The value none(4) implies that there is no ifPhysAddress. The FRS agent will return an octet string of zero length for ifPhysAddress. The value other(1) means that an address has been assigned to this interface, but the numbering plan is not enumerated here. Reference: E.164 [29] X.121 [30]
frLportContact
1.3.6.1.2.1.10.44.1.1.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The value of this object identifies the network contact for this UNI/NNI logical port.
frLportLocation
1.3.6.1.2.1.10.44.1.1.1.3
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The value of this object identifies the frame relay network location for this UNI/NNI logical port.
frLportType
1.3.6.1.2.1.10.44.1.1.1.4
INTEGER1 = uni2 = nni · Integer32
The value of this object identifies the type of network interface for this logical port.
The value of this object identifies the Local In-Channel Signaling Protocol that is used for this frame relay UNI/NNI logical port.
none(1): Interface does not use a PVC
signaling protocol
lmi(2): Interface operates the Stratacom/
Nortel/DEC Local Management Interface Specification protocol
ansiT1617D(3): Interface operates the ANSI T1.617
Annex D PVC status protocol
ansiT1617B(4): Interface operates the ANSI
T1.617 Annex B procedures
ccittQ933A(5): Interface operates the ITU Q.933
Annex A PVC status protocol Reference: LMI [24] T1.617 Annex D [17], Q.933 Annex A [22]
frLportVCSigPointer
1.3.6.1.2.1.10.44.1.1.1.7
OBJECT IDENTIFIER
The value of this object is used as a pointer to the table that contains the Local In-Channel Signaling Protocol parameters and errors for this UNI/NNI logical port.
This object has been deprecated to reflect the fact that the local in-channel signaling parameters are accessed from a single table (frMgtVCSigTable) that includes parameters for all possible signaling protocols. Early design anticipated multiple tables, one for each signaling protocol.
frLportDLCIIndexValue
1.3.6.1.2.1.10.44.1.1.1.8
Integer32 (16..4194303)
This object contains a hint to be used for frPVCEndptDLCIIndex when creating entries in the frPVCEndptTable. The SYNTAX of this object matches the SYNTAX of the frPVCEndptDLCIIndex - an object that is restricted to legal Q.922 DLCI values for the size of the address field.
The value 0 indicates that no unassigned entries are available.
To obtain the frPVCEndptDLCIIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent must modify the value to the next unassigned index to prevent assignment of the same value to multiple management systems.
A management system should repeat the read to obtain a new value should an attempt to create the new row using the previously returned hint fail. Reference: Q.922 [25]
frLportTypeAdmin
1.3.6.1.2.1.10.44.1.1.1.9
INTEGER1 = uni2 = nni · Integer32
The value of this object desired identifies the type of network interface for this logical port.
The value of this object identifies the desired Local In-Channel Signaling Protocol that is used for this frame relay UNI/NNI logical port. This value must be made the active protocol as soon as possible on the device.
Refer to frLportVCSigProtocol for a description of each signaling protocol choices. Reference: LMI [24] T1.617 Annex D [17], Q.933 Annex A [22]
frLportFragControl
1.3.6.1.2.1.10.44.1.1.1.11
INTEGER1 = on2 = off · Integer32
This object controls the transmission and reception of fragmentation frames for this UNI or NNI interface.
on(1) Frames are fragmented using the interface
fragmentation format
Note: The customer side of the interface
must also be configured to fragment frames.
off(2) Frames are not fragmented using the
interface fragmentation format. Reference: FRF.12 [21]
frLportFragSize
1.3.6.1.2.1.10.44.1.1.1.12
Integer32 (0..4096) · Octets
The value of this object is the size in octets of the maximum size of each fragment to be sent when fragmenting. This object is only used by the fragmentation transmitter, and the two sides of the interface may differ. The fragment size includes the octets for the frame relay header, the UI octet, the NLPID, the fragmentation header, and the fragment payload. If frLportFragControl is set to off, this value should be zero. Reference: FRF.12 [21]
frMgtVCSigTable
1.3.6.1.2.1.10.44.1.2
Index: ifIndex
The Frame Relay Management VC Signaling Parameters and Errors table.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
The value of this object identifies the local in-channel signaling procedural role that is used for this UNI/NNI logical port. Bidirectional procedures implies that both user-side and network-side procedural roles are used.
u2nnet(1) Logical port operates user to network
procedure in the role of the network side
bidirect(2) Logical port operates the bidirectional procedure (both user and network side roles)
u2nuser(3) Logical port operates user to network
procedure in the role of the user side Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigUserN391
1.3.6.1.2.1.10.44.1.2.1.2
INTEGER (1..255) · Integer32 · Polls
The value of this object identifies the User-side N391 full status polling cycle value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated and an attempt to read will result in the noSuchInstance exception response. Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigUserN392
1.3.6.1.2.1.10.44.1.2.1.3
INTEGER (1..10) · Integer32 · Events
The value of this object identifies the User-side N392 error threshold value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigUserN393
1.3.6.1.2.1.10.44.1.2.1.4
INTEGER (1..10) · Integer32 · Events
The value of this object identifies the User-side N393 monitored events count value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigUserT391
1.3.6.1.2.1.10.44.1.2.1.5
INTEGER (5..30) · Integer32 · Seconds
The value of this object identifies the User-side T391 link integrity verification polling timer value for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigNetN392
1.3.6.1.2.1.10.44.1.2.1.6
INTEGER (1..10) · Integer32 · Events
The value of this object identifies the Network- side N392 error threshold value (nN2 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17], LMI [24]
frMgtVCSigNetN393
1.3.6.1.2.1.10.44.1.2.1.7
INTEGER (1..10) · Integer32 · Events
The value of this object identifies the Network- side N393 monitored events count value (nN3 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17], LMI [24]
frMgtVCSigNetT392
1.3.6.1.2.1.10.44.1.2.1.8
INTEGER (5..30) · Integer32 · Seconds
The value of this object identifies the Network- side T392 polling verification timer value (nT2
for LMI) for this UNI/NNI logical port. If the
logical port is not performing network-side procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17], LMI [24]
frMgtVCSigNetnN4
1.3.6.1.2.1.10.44.1.2.1.9
INTEGER (5) · Integer32 · Events
The value of this object identifies the Network- side nN4 maximum status enquires received value for this UNI/NNI logical port. If the logical port is not performing network-side procedures or is not performing LMI procedures, then this object is not instantiated.
This object applies only to LMI and always has a value of 5. Reference: LMI [24]
The value of this object identifies the Network- side nT3 timer (for nN4 status enquires received) value for this UNI/NNI logical port. If the logical port is not performing network-side procedures or is not performing LMI procedures, then this object is not instantiated.
This object applies only to LMI. Reference: LMI [24]
frMgtVCSigUserLinkRelErrors
1.3.6.1.2.1.10.44.1.2.1.11
Counter32 · Errors
The number of user-side local in-channel signaling link reliability errors (i.e., non- receipt of Status/Status Enquiry messages or invalid sequence numbers in a Link Integrity Verification Information Element) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated.
frMgtVCSigUserProtErrors
1.3.6.1.2.1.10.44.1.2.1.12
Counter32 · Errors
The number of user-side local in-channel signaling protocol errors (i.e., protocol discriminator, unnumbered information, message type, call reference, and mandatory information element errors) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated.
frMgtVCSigUserChanInactive
1.3.6.1.2.1.10.44.1.2.1.13
Counter32 · Events
The number of times the user-side channel was declared inactive (i.e., N392 errors in N393 events) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated.
frMgtVCSigNetLinkRelErrors
1.3.6.1.2.1.10.44.1.2.1.14
Counter32 · Errors
The number of network-side local in-channel signaling link reliability errors (i.e., non- receipt of Status/Status Enquiry messages or invalid sequence numbers in a Link Integrity Verification Information Element) for this UNI/NNI logical port.
frMgtVCSigNetProtErrors
1.3.6.1.2.1.10.44.1.2.1.15
Counter32 · Errors
The number of network-side local in-channel signaling protocol errors (i.e., protocol discriminator, message type, call reference, and mandatory information element errors) for this UNI/NNI logical port.
frMgtVCSigNetChanInactive
1.3.6.1.2.1.10.44.1.2.1.16
Counter32 · Events
The number of times the network-side channel was declared inactive (i.e., N392 errors in N393 events) for this UNI/NNI logical port.
The value of this object identifies the local in-channel signaling procedural role that is used for this UNI/NNI logical port. Bidirectional procedures implies that both user-side and network-side procedural roles are used.
u2nnet(1) Logical port operates user to network
procedure in the role of the network side
bidirect(2) Logical port operates the bidirectional procedure (both user and network side roles)
u2nuser(3) Logical port operates user to network
procedure in the role of the user side Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigUserN391Admin
1.3.6.1.2.1.10.44.1.2.1.18
INTEGER (1..255) · Integer32 · Polls
The value of this object identifies the desired User-side N391 full status polling cycle value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigUserN392Admin
1.3.6.1.2.1.10.44.1.2.1.19
INTEGER (1..10) · Integer32 · Events
The value of this object identifies the desired User-side N392 error threshold value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigUserN393Admin
1.3.6.1.2.1.10.44.1.2.1.20
INTEGER (1..10) · Integer32 · Events
The value of this object identifies the desired User-side N393 monitored events count value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigUserT391Admin
1.3.6.1.2.1.10.44.1.2.1.21
INTEGER (5..30) · Integer32 · Seconds
The value of this object identifies the desired User-side T391 link integrity verification polling timer value for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17]
frMgtVCSigNetN392Admin
1.3.6.1.2.1.10.44.1.2.1.22
INTEGER (1..10) · Integer32 · Events
The value of this object identifies the desired Network-side N392 error threshold value (nN2 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17], LMI [24]
frMgtVCSigNetN393Admin
1.3.6.1.2.1.10.44.1.2.1.23
INTEGER (1..10) · Integer32 · Events
The value of this object identifies the desired Network-side N393 monitored events count value (nN3 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17], LMI [24]
frMgtVCSigNetT392Admin
1.3.6.1.2.1.10.44.1.2.1.24
INTEGER (5..30) · Integer32 · Seconds
The value of this object identifies the desired Network-side T392 polling verification timer value
(nT2 for LMI) for this UNI/NNI logical port. If
the logical port is not performing network-side procedures, then this object is not instantiated. Reference: Q.933 Annex A [22], T1.617 Annex D [17], LMI [24]
The value of this object identifies the desired Network-side nT3 timer (for nN4 status enquires received) value for this UNI/NNI logical port. If the logical port is not performing network-side procedures or is not performing LMI procedures, then this object is not instantiated. This object applies only to LMI. Reference: LMI [24]
frPVCEndptTable
1.3.6.1.2.1.10.44.1.3
Index: ifIndex · frPVCEndptDLCIIndex
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.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
frPVCEndptDLCIIndex
1.3.6.1.2.1.10.44.1.3.1.1
Integer32 (16..4194303)
The value of this object is equal to the DLCI value for this PVC end-point.
The values are restricted to the legal range for the size of address field supported by the logical port (frLportAddrDLCILen). Reference: Q.922 [25]
frPVCEndptInMaxFrameSize
1.3.6.1.2.1.10.44.1.3.1.2
Integer32 (1..4096) · Octets
The value of this object is the size in octets of the largest frame relay information field for this PVC end-point in the ingress direction (into the frame relay network). The value of frPVCEndptInMaxFrameSize must be less than or equal to the corresponding ifMtu for this frame relay UNI/NNI logical port. Reference: FRF.1 [31] Q.922 [25] Q.933 [22]
frPVCEndptInBc
1.3.6.1.2.1.10.44.1.3.1.3
Integer32 (1..2147483647) · Bits
The value of this object is equal to the committed burst size (Bc) parameter (measured in bits) for this PVC end-point in the ingress direction (into the frame relay network).
Note that the max value of this range is lower than the max value allowed by Q.933 (16383 * 10**6). Note that the value is encoded in bits whilst the Q.933 Link layer core parameters information element encodes this information using octet units. Reference: Q.933 [22]
frPVCEndptInBe
1.3.6.1.2.1.10.44.1.3.1.4
Integer32 (1..2147483647) · Bits
The value of this object is equal to the excess burst size (Be) parameter (measured in bits) for this PVC end-point in the ingress direction (into the frame relay network).
Note that the max value of this range is lower than the max value allowed by Q.933 (16383 * 10**6).
Note that the value is encoded in bits whilst the Q.933 Link layer core parameters information element encodes this information using octet units. Reference: Q.933 [22]
frPVCEndptInCIR
1.3.6.1.2.1.10.44.1.3.1.5
Integer32 (1..2147483647) · Bits per Second
The value of this object is equal to the committed information rate (CIR) parameter (measured in bits per second) for this PVC end- point in the ingress direction (into the frame relay network).
Note that the max value of this range is lower than the max value allowed by Q.933 (2047 * 10**6). Reference: Q.933 [22]
frPVCEndptOutMaxFrameSize
1.3.6.1.2.1.10.44.1.3.1.6
Integer32 (1..4096) · Octets
The value of this object is the size in octets of the largest frame relay information field for this PVC end-point in the egress direction (out of the frame relay network). The value of frPVCEndptOutMaxFrameSize must be less than or equal to the corresponding ifMtu for this frame relay UNI/NNI logical port. Reference: FRF.1 [31] Q.922 [25] Q.933 [22]
frPVCEndptOutBc
1.3.6.1.2.1.10.44.1.3.1.7
Integer32 (1..2147483647) · Bits
The value of this object is equal to the committed burst size (Bc) parameter (measured in bits) for this PVC end-point in the egress direction (out of the frame relay network).
Note that the max value of this range is lower than the max value allowed by Q.933 (16383 * 10**6).
Note that the value is encoded in bits whilst the Q.933 Link layer core parameters information element encodes this information using octet units. Reference: Q.933 [22]
frPVCEndptOutBe
1.3.6.1.2.1.10.44.1.3.1.8
Integer32 (1..2147483647) · Bits
The value of this object is equal to the excess burst size (Be) parameter (measured in bits) for this PVC end-point in the egress direction (out of the frame relay network).
Note that the max value of this range is lower than the max value allowed by Q.933 (16383 * 10**6).
Note that the value is encoded in bits whilst the Q.933 Link layer core parameters information element encodes this information using octet units. Reference: Q.933 [22]
frPVCEndptOutCIR
1.3.6.1.2.1.10.44.1.3.1.9
Integer32 (1..2147483647) · Bits per Second
The value of this object is equal to the committed information rate (CIR) parameter (measured in bits per second) for this PVC end- point in the egress direction (out of the frame relay network).
Note that the max value of this range is lower than the max value allowed by Q.933 (2047 * 10**6). Reference: Q.933 [22]
frPVCEndptConnectIdentifier
1.3.6.1.2.1.10.44.1.3.1.10
Integer32 (0..2147483647)
This object is used to associate PVC end-points as being part of one PVC segment connection. This value of this object is equal to the value of frPVCConnectIndex, which is used as one of the indices into the frPVCConnectTable.
A connection that has been cross-connected via the FR/ATM PVC Service IWF cross-connect table will return the value zero when this object is read. In case of these interworked connections, the frPVCEndptAtmIwfConnIndex object must be accessed to select the entry in the FR/ATM PVC Service IWF cross-connect table.
The value of this object is provided by the agent, after the associated entries in the frPVCConnectTable or frAtmIwfConnectionTable have been created.
frPVCEndptRowStatus
1.3.6.1.2.1.10.44.1.3.1.11
RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].)
The status column has six defined values:
- `active', which indicates that the conceptual row is available for use by the managed device;
- `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device;
- `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated);
- `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device;
- `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.
Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management
protocol retrieval operation: `notReady', `notInService' or
`active'. That is, when queried, an existing conceptual row
has only three states: it is either available for use by
the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady').
NOTE WELL
This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'.
Also note that whenever any elements of a row exist, the RowStatus column must also exist.
To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram:
STATE +--------------+-----------+-------------+-------------
| A | B | C | D
| |status col.|status column|
|status column | is | is |status column
ACTION |does not exist| notReady | notInService| is active
--------------+--------------+-----------+-------------+-------------
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndGo |inconsistent- | | |
| Value| | |
--------------+--------------+-----------+-------------+-------------
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndWait |wrongValue | | |
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError
column to | Value| entValue| |
active | | | |
| | or | |
| | | |
| |see 2 ->D|see 8 ->D| ->D
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError ->C
column to | Value| entValue| |
notInService | | | |
| | or | | or
| | | |
| |see 3 ->C| ->C|see 6
--------------+--------------+-----------+-------------+-------------
set status |noError |noError |noError |noError ->A
column to | | | | or
destroy | ->A| ->A| ->A|see 7
--------------+--------------+-----------+-------------+-------------
set any other |see 4 |noError |noError |see 5
column to some| | | |
value | | see 1| ->C| ->D
--------------+--------------+-----------+-------------+-------------
(1) goto B or C, depending on information available to the agent.
(2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D.
(3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C.
(4) at the discretion of the agent, the return value may be either:
inconsistentName: because the agent does not choose to
create such an instance when the corresponding RowStatus instance does not exist, or
inconsistentValue: if the supplied value is
inconsistent with the state of some other MIB object's value, or
noError: because the agent chooses to create the instance.
If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A.
(5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned.
(6) the return value can indicate one of the following errors:
wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or
inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated.
(7) the return value can indicate the following error:
inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated.
(8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue.
NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc.
Conceptual Row Creation
There are four potential interactions when creating a
conceptual row: selecting an instance-identifier which is
not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device.
Interaction 1: Selecting an Instance-Identifier
The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics.
In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.)
Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different.
Finally, the management station could select a pseudo-random number to use as the index. In the event that this index
was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation.
A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used.
Interaction 2: Creating the Conceptual Row
Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions.
Interaction 2a: Creating and Activating the Conceptual Row
The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes:
- a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'.
When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information
available to the agent is provided by two sources: the
management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row.
NOTE WELL
Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm.
Interaction 2b: Negotiating the Creation of the Conceptual Row
The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the
columns indicated by its column requirements.) Otherwise,
the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3.
Interaction 3: Initializing non-defaulted Objects
The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes:
- a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4.
Interaction 4: Making the Conceptual Row Available
Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'.
NOTE WELL
A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device.
If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row.
Conceptual Row Suspension
When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified).
Conceptual Row Deletion
For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady',
`notInService' or `active'.) If the operation succeeds,
then all instances associated with the conceptual row are immediately removed. · Integer32
This object is used to create new rows in this table, modify existing rows, and to delete existing rows. To create a new PVC, the entries for the PVC segment end-points in the frPVCEndptTable must first be created. Next, the frPVCConnectTable is used to associate the frame relay PVC segment end-points. In order for the manager to have the necessary error diagnostics, the frPVCEndptRowStatus object must initially be set to `createAndWait(5)'. While the frPVCEndptRowStatus object is in the `createAndWait(5)' state, the manager can set each columnar object and get the necessary error diagnostics. The frPVCEndptRowStatus object may not be set to `active(1)' unless the following columnar objects exist in this row: frPVCEndptInMaxFrameSize, frPVCEndptInBc, frPVCEndptInBe, frPVCEndptInCIR, frPVCEndptOutMaxFrameSize, frPVCEndptOutBc, frPVCEndptOutBe, and frPVCEndptOutCIR.
The value of this object identifies the PVC status received via the local in-channel signaling procedures for this PVC end-point. This object is only pertinent for interfaces that perform the bidirectional procedures.
Each value has the following meaning:
deleted(1): This PVC is not listed in the full
status reports received from the user device. The object retains this value for as long as the PVC is not listed in the full status reports
active(2): This PVC is reported as active, or
operational, by the user device.
inactive(3): This PVC is reported as inactive, or non-operational, by the user device.
none(4): This interface is only using the
network-side in-channel signaling procedures, so this object does not apply.
frPVCEndptInFrames
1.3.6.1.2.1.10.44.1.3.1.13
Counter32 · Frames
The number of frames received by the network (ingress) for this PVC end-point. This includes any frames discarded by the network due to submitting more than Bc + Be data or due to any network congestion recovery procedures.
frPVCEndptOutFrames
1.3.6.1.2.1.10.44.1.3.1.14
Counter32 · Frames
The number of frames sent by the network (egress) regardless of whether they are Bc or Be frames for this PVC end-point.
frPVCEndptInDEFrames
1.3.6.1.2.1.10.44.1.3.1.15
Counter32 · Frames
The number of frames received by the network (ingress) with the DE bit set to (1) for this PVC end-point.
frPVCEndptInExcessFrames
1.3.6.1.2.1.10.44.1.3.1.16
Counter32 · Frames
The number of frames received by the network (ingress) for this PVC end-point which were treated as excess traffic. Frames which are sent to the network with DE set to zero are treated as excess when more than Bc bits are submitted to the network during the Committed Information Rate Measurement Interval (Tc). Excess traffic may or may not be discarded at the ingress if more than Bc + Be bits are submitted to the network during Tc. Traffic discarded at the ingress is not recorded in frPVCEndptInExcessFrames. Frames which are sent to the network with DE set to one are also treated as excess traffic.
frPVCEndptOutExcessFrames
1.3.6.1.2.1.10.44.1.3.1.17
Counter32 · Frames
The number of frames sent by the network (egress) for this PVC end-point which were treated as excess traffic. (The DE bit may be set to one.)
frPVCEndptInDiscards
1.3.6.1.2.1.10.44.1.3.1.18
Counter32 · Frames
The number of frames received by the network (ingress) that were discarded due to traffic enforcement for this PVC end-point. Congestion discards are not counted in this object.
frPVCEndptInOctets
1.3.6.1.2.1.10.44.1.3.1.19
Counter32 · Octets
The number of octets received by the network (ingress) for this PVC end-point. This counter should only count octets from the beginning of the frame relay header field to the end of user data. If the network supporting frame relay can not count octets, then this count should be an approximation.
frPVCEndptOutOctets
1.3.6.1.2.1.10.44.1.3.1.20
Counter32 · Octets
The number of octets sent by the network (egress) for this PVC end-point. This counter should only count octets from the beginning of the frame relay header field to the end of user data. If the network supporting frame relay can not count octets, then this count should be an approximation.
frPVCEndptInDiscardsDESet
1.3.6.1.2.1.10.44.1.3.1.21
Counter32 · Frames
The number of frames received by the network (ingress) that were discarded with the DE bit set due to traffic enforcement for this PVC end-point. Congestion discards are not counted in this object.
frPVCEndptInFramesFECNSet
1.3.6.1.2.1.10.44.1.3.1.22
Counter32 · Frames
The number of frames received by the network (ingress) that have the FECN bit set for this PVC end-point.
frPVCEndptOutFramesFECNSet
1.3.6.1.2.1.10.44.1.3.1.23
Counter32 · Frames
The number of frames sent by the network (egress) that have the FECN bit set for this PVC end- point.
frPVCEndptInFramesBECNSet
1.3.6.1.2.1.10.44.1.3.1.24
Counter32 · Frames
The number of frames received by the network (ingress) that have the BECN bit set for this PVC end-point.
frPVCEndptOutFramesBECNSet
1.3.6.1.2.1.10.44.1.3.1.25
Counter32 · Frames
The number of frames sent by the network (egress) that have the BECN bit set for this PVC end- point.
frPVCEndptInCongDiscards
1.3.6.1.2.1.10.44.1.3.1.26
Counter32 · Frames
The number of frames received by the network (ingress) that were discarded due to input buffer congestion, rather than traffic enforcement, for this PVC end-point.
frPVCEndptInDECongDiscards
1.3.6.1.2.1.10.44.1.3.1.27
Counter32 · Frames
The number of frames counted by frPVCEndptInCongDiscards with the DE bit set to (1).
frPVCEndptOutCongDiscards
1.3.6.1.2.1.10.44.1.3.1.28
Counter32 · Frames
The number of frames sent by the network (egress) that were discarded due to output buffer congestion for this PVC end-point.
frPVCEndptOutDECongDiscards
1.3.6.1.2.1.10.44.1.3.1.29
Counter32 · Frames
The number of frames counted by frPVCEndptOutCongDiscards with the DE bit set to (1).
frPVCEndptOutDEFrames
1.3.6.1.2.1.10.44.1.3.1.30
Counter32 · Frames
The number of frames sent by the network (egress) with the DE bit set to (1) for this PVC end- point.
frPVCEndptAtmIwfConnIndex
1.3.6.1.2.1.10.44.1.3.1.31
Integer32 (0..2147483647)
This object contains the index value of the FR/ATM cross-connect table entry used to link the frame relay PVC with an ATM PVC.
Each row of the frPVCEndptTable that is not cross-connected with an ATM PVC must return the value zero when this object is read.
The value of this object is initialized by the agent after the associated entries in the frAtmIwfConnectionTable have been created.
The value of this object is reset to zero following destruction of the associated entry in the frAtmIwfConnectionTable
The Frame Relay PVC Connect Table is used to model the bi-directional PVC segment flows
including: point-to-point PVCs, point-to-
multipoint PVCs, and multipoint-to-multipoint PVCs.
This table has read-create access and is used to associate PVC end-points together as belonging to one connection. The frPVCConnectIndex is used to associate all the bi-directional flows. Not all implementations will support the capability of creating/modifying/deleting PVCs using SNMP as a feature of frame relay CNM service.
Once the entries in the frPVCEndptTable are created, the following step are used to associate the PVC end-points as belonging to one PVC connection:
1) Obtain a unique frPVCConnectIndex
using the frPVCConnectIndexValue object.
2) Connect the PVC segment endpoints together
with the applicable frPVCConnectIndex value
obtained via frPVCConnectIndexValue. The
entries in this table are created by using the frPVCConnectRowStatus object.
3) The agent will provide the value of the
corresponding instances of frPVCEndptConnectIdentifier with the frPVCConnectIndex value.
4) Set frPVCConnectAdminStatus to `active(1)' in
all rows for this PVC segment to turn the PVC on.
For example, the Frame Relay PVC Connection Group models a bi-directional, point-to-point PVC segment as one entry in this table.
Frame Relay Frame Relay
Network Network
Low Port High Port
__________________________________
| |
_____| >> from low to high PVC flow >> |_____
| << from high to low PVC flow << |
|__________________________________|
The terms low and high are chosen to represent numerical ordering of a PVC segment's endpoints for representation in this table. That is, the endpoint with the lower value of ifIndex is termed 'low', while the opposite endpoint of the segment is termed 'high'. This terminology is to provide directional information; for example the frPVCConnectL2hOperStatus and frPVCConnectH2lOperStatus as illustrated above.
If the Frame Relay Connection table is used to model a unidirectional PVC, then one direction (either from low to high or from high to low) has its Operational Status equal to down.
A PVC segment is a portion of a PVC that traverses one Frame Relay Network, and a PVC segment is identified by its two end-points (UNI/NNI logical port index value and DLCI index value) through one Frame Relay Network.
frPVCConnectIndex
1.3.6.1.2.1.10.44.1.5.1.1
Integer32 (0..2147483647)
The value of this object is equal to the frPVCConnectIndexValue obtained to uniquely identify this PVC segment connection.
frPVCConnectLowIfIndex
1.3.6.1.2.1.10.44.1.5.1.2
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object is equal to IF-MIB ifIndex value of the UNI/NNI logical port for this PVC segment. The term low implies that this PVC segment end-point has the numerically lower ifIndex value than the connected/associated PVC segment end-point.
RFC 1604 permitted a zero value for this object to identify termination at a non-frame relay interface. However, this cross-connect table is limited to frame relay connections. See the frame relay/ATM IWF MIB [28] for the cross-connect table used for those types of connections.
frPVCConnectLowDLCIIndex
1.3.6.1.2.1.10.44.1.5.1.3
Integer32 (16..4194303)
The value of this object is equal to the DLCI value for this end-point of the PVC segment. Reference: Q.922 [25]
frPVCConnectHighIfIndex
1.3.6.1.2.1.10.44.1.5.1.4
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object is equal to IF-MIB ifIndex value for the UNI/NNI logical port for this PVC segment. The term high implies that this PVC segment end-point has the numerically higher ifIndex value than the connected/associated PVC segment end-point.
frPVCConnectHighDLCIIndex
1.3.6.1.2.1.10.44.1.5.1.5
Integer32 (16..4194303)
The value of this object is equal to the egress DLCI value for this end-point of the PVC segment. Reference: Q.922 [25]
The value of this object identifies the desired administrative status of this bi-directional PVC segment. The active(1) state means the PVC segment is currently operational; the inactive(2) state means the PVC segment is currently not operational; the testing(3) state means the PVC segment is currently undergoing a test. This state is set by an administrative entity. This value affects the PVC status indicated across the ingress NNI/UNI of both end-points of the bi- directional PVC segment. When a PVC segment connection is created using this table, this object is initially set to `inactive(2)'. After the frPVCConnectRowStatus object is set to `active(1)' (and the corresponding/associated entries in the frPVCEndptTable have their frPVCEndptRowStatus object set to `active(1)'), the frPVCConnectAdminStatus object may be set to `active(1)' to turn on the PVC segment connection.
The value of this object identifies the current operational status of the PVC segment connection in one direction; (i.e., in the low to high direction). This value affects the PVC status indicated across the ingress NNI/UNI (low side) of the PVC segment.
The values mean:
active(1) - PVC is currently operational
inactive(2) - PVC is currently not operational. This may be because of an underlying LMI or DS1 failure.
testing(3) - PVC is currently undergoing a test.
This may be because of an underlying frLport or DS1 undergoing a test.
unknown(4) - the status of the PVC currently can
not be determined.
The value of this object identifies the current operational status of the PVC segment connection in one direction; (i.e., in the high to low direction).. This value affects the PVC status indicated across the ingress NNI/UNI (high side) of the PVC segment.
The values mean:
active(1) - PVC is currently operational
inactive(2) - PVC is currently not operational. This may be because of an underlying LMI or DS1 failure.
testing(3) - PVC is currently undergoing a test.
This may be because of an underlying frLport or DS1 undergoing a test.
unknown(4) - the status of the PVC currently can
not be determined.
frPVCConnectL2hLastChange
1.3.6.1.2.1.10.44.1.5.1.9
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be
defined in the description of any object defined using this type.
If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of the Interface MIB's sysUpTime object at the time this PVC segment entered its current operational state in the low to high direction. If the current state was entered prior to the last re-initialization of the FRS agent, then this object contains a zero value.
frPVCConnectH2lLastChange
1.3.6.1.2.1.10.44.1.5.1.10
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be
defined in the description of any object defined using this type.
If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of the Interface MIB's sysUpTime object at the time this PVC segment entered its current operational state in the high to low direction. If the current state was entered prior to the last re-initialization of the FRS agent, then this object contains a zero value.
frPVCConnectRowStatus
1.3.6.1.2.1.10.44.1.5.1.11
RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].)
The status column has six defined values:
- `active', which indicates that the conceptual row is available for use by the managed device;
- `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device;
- `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated);
- `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device;
- `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.
Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management
protocol retrieval operation: `notReady', `notInService' or
`active'. That is, when queried, an existing conceptual row
has only three states: it is either available for use by
the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady').
NOTE WELL
This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'.
Also note that whenever any elements of a row exist, the RowStatus column must also exist.
To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram:
STATE +--------------+-----------+-------------+-------------
| A | B | C | D
| |status col.|status column|
|status column | is | is |status column
ACTION |does not exist| notReady | notInService| is active
--------------+--------------+-----------+-------------+-------------
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndGo |inconsistent- | | |
| Value| | |
--------------+--------------+-----------+-------------+-------------
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndWait |wrongValue | | |
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError
column to | Value| entValue| |
active | | | |
| | or | |
| | | |
| |see 2 ->D|see 8 ->D| ->D
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError ->C
column to | Value| entValue| |
notInService | | | |
| | or | | or
| | | |
| |see 3 ->C| ->C|see 6
--------------+--------------+-----------+-------------+-------------
set status |noError |noError |noError |noError ->A
column to | | | | or
destroy | ->A| ->A| ->A|see 7
--------------+--------------+-----------+-------------+-------------
set any other |see 4 |noError |noError |see 5
column to some| | | |
value | | see 1| ->C| ->D
--------------+--------------+-----------+-------------+-------------
(1) goto B or C, depending on information available to the agent.
(2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D.
(3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C.
(4) at the discretion of the agent, the return value may be either:
inconsistentName: because the agent does not choose to
create such an instance when the corresponding RowStatus instance does not exist, or
inconsistentValue: if the supplied value is
inconsistent with the state of some other MIB object's value, or
noError: because the agent chooses to create the instance.
If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A.
(5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned.
(6) the return value can indicate one of the following errors:
wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or
inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated.
(7) the return value can indicate the following error:
inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated.
(8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue.
NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc.
Conceptual Row Creation
There are four potential interactions when creating a
conceptual row: selecting an instance-identifier which is
not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device.
Interaction 1: Selecting an Instance-Identifier
The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics.
In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.)
Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different.
Finally, the management station could select a pseudo-random number to use as the index. In the event that this index
was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation.
A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used.
Interaction 2: Creating the Conceptual Row
Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions.
Interaction 2a: Creating and Activating the Conceptual Row
The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes:
- a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'.
When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information
available to the agent is provided by two sources: the
management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row.
NOTE WELL
Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm.
Interaction 2b: Negotiating the Creation of the Conceptual Row
The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the
columns indicated by its column requirements.) Otherwise,
the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3.
Interaction 3: Initializing non-defaulted Objects
The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes:
- a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column.
- the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column.
- the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column.
If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4.
Interaction 4: Making the Conceptual Row Available
Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'.
NOTE WELL
A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device.
If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row.
Conceptual Row Suspension
When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified).
Conceptual Row Deletion
For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady',
`notInService' or `active'.) If the operation succeeds,
then all instances associated with the conceptual row are immediately removed. · Integer32
The status of this entry in the frPVCConnectTable. This variable is used to create new connections for the PVC end-points and to change existing connections of the PVC end- points. This object must be initially set to `createAndWait(5)'. In this state, the agent checks the parameters in the associated entries in the frPVCEndptTable to verify that the PVC end- points can be connected (i.e., the In parameters for one PVC end-point are equal to the Out parameters for the other PVC end-point). This object can not be set to `active(1)' unless the following columnar object exists in this row: frPVCConnectAdminStatus. The agent also supplies the associated value of frPVCConnectIndex for the frPVCEndptConnectIdentifier instances. To turn on a PVC segment connection, the frPVCConnectAdminStatus is set to `active(1)'.
frPVCConnectUserName
1.3.6.1.2.1.10.44.1.5.1.12
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
This is a service user assigned textual representation of a PVC.
frPVCConnectProviderName
1.3.6.1.2.1.10.44.1.5.1.13
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
This is a system supplied textual representation of PVC. It is assigned by the service provider.
frAccountPVCTable
1.3.6.1.2.1.10.44.1.6
Index: ifIndex · frAccountPVCDLCIIndex
The Frame Relay Accounting PVC table. This table is used to perform accounting on a PVC segment end-point basis.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
frAccountPVCDLCIIndex
1.3.6.1.2.1.10.44.1.6.1.1
Integer32 (16..4194303)
The value of this object is equal to the DLCI value for this PVC segment end-point. Reference: Q.922 [25]
frAccountPVCSegmentSize
1.3.6.1.2.1.10.44.1.6.1.2
Integer32 · Octets
The value of this object is equal to the Segment Size for this PVC segment end-point.
frAccountPVCInSegments
1.3.6.1.2.1.10.44.1.6.1.3
Counter32 · Segments
The value of this object is equal to the number of segments received by this PVC segment end- point.
frAccountPVCOutSegments
1.3.6.1.2.1.10.44.1.6.1.4
Counter32 · Segments
The value of this object is equal to the number of segments sent by this PVC segment end-point.
frAccountLportTable
1.3.6.1.2.1.10.44.1.7
Index: ifIndex
The Frame Relay Accounting Logical Port table. This table is used to perform accounting on a UNI/NNI Logical Port basis.
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
frAccountLportSegmentSize
1.3.6.1.2.1.10.44.1.7.1.1
Integer32 · Octets
The value of this object is equal to the Segment Size for this UNI/NNI logical port.
frAccountLportInSegments
1.3.6.1.2.1.10.44.1.7.1.2
Counter32 · Segments
The value of this object is equal to the number of segments received by this UNI/NNI logical port.
frAccountLportOutSegments
1.3.6.1.2.1.10.44.1.7.1.3
Counter32 · Segments
The value of this object is equal to the number of segments sent by this UNI/NNI logical port.
Trap details
frPVCConnectStatusNotif
1.3.6.1.2.1.10.44.2.0.2
This notification indicates that the indicated PVC has changed state.
This notification is not sent if an FR-UNI changes state; a linkDown or linkUp notification should be sent instead. The first instance of frPVCEndptRcvdSigStatus is for the endpoint with LowIfIndex, LowDLCIIndex. The second instance of frPVCEndptRcvdSigStatus is for the endpoint with HighIfIndex, HighDLCIIndex
The value of this object identifies the current operational status of the PVC segment connection in one direction; (i.e., in the low to high direction). This value affects the PVC status indicated across the ingress NNI/UNI (low side) of the PVC segment.
The values mean:
active(1) - PVC is currently operational
inactive(2) - PVC is currently not operational. This may be because of an underlying LMI or DS1 failure.
testing(3) - PVC is currently undergoing a test.
This may be because of an underlying frLport or DS1 undergoing a test.
unknown(4) - the status of the PVC currently can
not be determined.
The value of this object identifies the current operational status of the PVC segment connection in one direction; (i.e., in the high to low direction).. This value affects the PVC status indicated across the ingress NNI/UNI (high side) of the PVC segment.
The values mean:
active(1) - PVC is currently operational
inactive(2) - PVC is currently not operational. This may be because of an underlying LMI or DS1 failure.
testing(3) - PVC is currently undergoing a test.
This may be because of an underlying frLport or DS1 undergoing a test.
unknown(4) - the status of the PVC currently can
not be determined.
The value of this object identifies the PVC status received via the local in-channel signaling procedures for this PVC end-point. This object is only pertinent for interfaces that perform the bidirectional procedures.
Each value has the following meaning:
deleted(1): This PVC is not listed in the full
status reports received from the user device. The object retains this value for as long as the PVC is not listed in the full status reports
active(2): This PVC is reported as active, or
operational, by the user device.
inactive(3): This PVC is reported as inactive, or non-operational, by the user device.
none(4): This interface is only using the
network-side in-channel signaling procedures, so this object does not apply.
frPVCConnectStatusChange
1.3.6.1.2.1.10.44.2.1
Refer to the description of the frPVCConnectStatusNotif notification that has replaced this notification. The notification is deprecated due to the incorrect inclusion of index values and to take advantage of the trap prefix for automatic conversion from SMIv2 to SMIv1 by making the one but last sub-ID a zero (i.e. the so-called trap prefix).
frPVCConnectIndex
1.3.6.1.2.1.10.44.1.5.1.1
Integer32 (0..2147483647)
The value of this object is equal to the frPVCConnectIndexValue obtained to uniquely identify this PVC segment connection.
frPVCConnectLowIfIndex
1.3.6.1.2.1.10.44.1.5.1.2
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object is equal to IF-MIB ifIndex value of the UNI/NNI logical port for this PVC segment. The term low implies that this PVC segment end-point has the numerically lower ifIndex value than the connected/associated PVC segment end-point.
RFC 1604 permitted a zero value for this object to identify termination at a non-frame relay interface. However, this cross-connect table is limited to frame relay connections. See the frame relay/ATM IWF MIB [28] for the cross-connect table used for those types of connections.
frPVCConnectLowDLCIIndex
1.3.6.1.2.1.10.44.1.5.1.3
Integer32 (16..4194303)
The value of this object is equal to the DLCI value for this end-point of the PVC segment. Reference: Q.922 [25]
frPVCConnectHighIfIndex
1.3.6.1.2.1.10.44.1.5.1.4
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object is equal to IF-MIB ifIndex value for the UNI/NNI logical port for this PVC segment. The term high implies that this PVC segment end-point has the numerically higher ifIndex value than the connected/associated PVC segment end-point.
frPVCConnectHighDLCIIndex
1.3.6.1.2.1.10.44.1.5.1.5
Integer32 (16..4194303)
The value of this object is equal to the egress DLCI value for this end-point of the PVC segment. Reference: Q.922 [25]
The value of this object identifies the current operational status of the PVC segment connection in one direction; (i.e., in the low to high direction). This value affects the PVC status indicated across the ingress NNI/UNI (low side) of the PVC segment.
The values mean:
active(1) - PVC is currently operational
inactive(2) - PVC is currently not operational. This may be because of an underlying LMI or DS1 failure.
testing(3) - PVC is currently undergoing a test.
This may be because of an underlying frLport or DS1 undergoing a test.
unknown(4) - the status of the PVC currently can
not be determined.
The value of this object identifies the current operational status of the PVC segment connection in one direction; (i.e., in the high to low direction).. This value affects the PVC status indicated across the ingress NNI/UNI (high side) of the PVC segment.
The values mean:
active(1) - PVC is currently operational
inactive(2) - PVC is currently not operational. This may be because of an underlying LMI or DS1 failure.
testing(3) - PVC is currently undergoing a test.
This may be because of an underlying frLport or DS1 undergoing a test.
unknown(4) - the status of the PVC currently can
not be determined.
The value of this object identifies the PVC status received via the local in-channel signaling procedures for this PVC end-point. This object is only pertinent for interfaces that perform the bidirectional procedures.
Each value has the following meaning:
deleted(1): This PVC is not listed in the full
status reports received from the user device. The object retains this value for as long as the PVC is not listed in the full status reports
active(2): This PVC is reported as active, or
operational, by the user device.
inactive(3): This PVC is reported as inactive, or non-operational, by the user device.
none(4): This interface is only using the
network-side in-channel signaling procedures, so this object does not apply.