Nortel-Magellan-Passport-FrameRelayNniMIB: View SNMP OID List / Download MIB

This entry controls the addition and deletion of frNni components.

A single entry in the table represents a single frNni component.

This variable is used as the basis for SNMP naming of frNni components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNni tables.

This variable represents the index for the frNni tables.

This entry controls the addition and deletion of frNniDna components.

A single entry in the table represents a single frNniDna component.

This variable is used as the basis for SNMP naming of frNniDna components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDna tables.

This variable represents the index for the frNniDna tables.

This entry controls the addition and deletion of frNniDnaCug components.

A single entry in the table represents a single frNniDnaCug component.

This variable is used as the basis for SNMP naming of frNniDnaCug components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDnaCug tables.

This variable represents the index for the frNniDnaCug tables.

Attributes in this group define ClosedUserGroup options associated with interlockCode. DNA's with the same CUG (interlockCode) can make calls within this group. Various combinations which permit or prevent calls in the same CUG group are defined here.

An entry in the frNniDnaCugCugOptionsTable.

This attribute specifies the CUG type - the CUG is either a national CUG, or an international CUG. International closed user groups are usually established between DTEs for which there is an X.75 Gateway between; whereas national closed user groups are usually established between DTEs for which there is no X.75 Gateway between. (National CUGs cannot normally traverse an X.75 Gateway). If this attribute is set to national, then the CUG is a national CUG, in which case, the dnic should be left at its default value since it is not part of a national CUG. If this attribute is set to international, then the CUG is an international CUG, in which case, the dnic should be set appropriately as part of the CUG interlockCode. Enumeration: 'international': 1, 'national': 0.

This attribute specifies the dnic (Data Network ID Code) of the CUG by which packet networks are identified. This attribute is not applicable if the CUG is a national CUG, as specified by the CUG type attribute. There are usually 1 or 2 dnics assigned per country, for public networks. The U.S. is an exception where each BOC has a dnic. Also, a group of private networks can have its own dnic. dnic value is not an arbitrary number. It is assigned by international agreement and controlled by CCITT.

This attribute specifies the CUG identifier of a national or international CUG call. It is an arbitrary number and it also can be called CUG in some descriptions. Interfaces (DNA's) defined with this number can make calls to DNA's with the same interlockCode.

The attribute 'preferential', if set to yes indicates that this CUG is the SIMPLE CUG (as defined in ITU X.36 [10/96]), in which case it will be used during the call establishment phase if the DTE has not explicitly specified a CUG index in the call request packet. If set to no, then this CUG is not the SIMPLE CUG, but an instance of the SELECTABLE CUG. The attribute 'preferential' is set to no by CAS when a CUG instance is created. If only one CUG instance exists under a DNA, and if this CUG's attributes 'incCalls' and 'outCall' are both set to allowed, then this CUG instance can be changed to a SIMPLE CUG by setting the attribute 'preferential' to yes. If more than one CUG instances exist under a DNA, none of the CUGs can be set by the user as 'preferential'. Essentially, the attribute 'preferential' distinguishes a SIMPLE CUG from a SELECTABLE CUG. In the case of a FRUNI DNA with a single CUG instance, the CUG can be a SIMPLE CUG (preferential = yes) or the only instance of a SELECTABLE CUG (preferential = no). Enumeration: 'yes': 1, 'no': 0.

This attribute, if set to allowed indicates that outgoing calls (from the DTE into the network) can be made using this particular CUG. If set to a value of disallowed, then outgoing calls cannot be made using this CUG - such calls will be cleared by the local DCE. This attribute corresponds to the CCITT 'Outgoing Calls Barred' feature for CUGs in that outgoing calls are barred if this attribute is set to a value of disallowed. Enumeration: 'disallowed': 0, 'allowed': 1.

This attribute, if set to allowed indicates that incoming calls (from the network to the DTE) can be made using this particular CUG. If set to disallowed, then incoming calls cannot be made using this CUG - such calls will be cleared by the local DCE. This attribute corresponds to the CCITT 'Incoming Calls Barred' feature for CUGs in that incoming calls are barred if this attribute is set to a value of disallowed. Enumeration: 'disallowed': 0, 'allowed': 1.

This entry controls the addition and deletion of frNniDnaHgM components.

A single entry in the table represents a single frNniDnaHgM component.

This variable is used as the basis for SNMP naming of frNniDnaHgM components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDnaHgM tables.

This variable represents the index for the frNniDnaHgM tables.

This entry controls the addition and deletion of frNniDnaHgMHgAddr components.

A single entry in the table represents a single frNniDnaHgMHgAddr component.

This variable is used as the basis for SNMP naming of frNniDnaHgMHgAddr components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDnaHgMHgAddr tables.

This variable represents the index for the frNniDnaHgMHgAddr tables.

This group contains attributes common to all DNAs. Every DNA used in the network is defined with this group of 2 attributes.

An entry in the frNniDnaHgMHgAddrAddrTable.

This attribute indicates the Numbering Plan Indicator (NPI) of the DNA. The address may belong to X.121 or E.164 plans. Enumeration: 'e164': 1, 'x121': 0.

This attribute contains digits which form the unique identifier of the customer interface. It can be compared (approximation only) to a telephone number where the phone number identifies a unique telephone set. DNA digits are selected and assigned by network operators.

This group contains the interface parameters between the HuntGroupMember and the hunt group server.

An entry in the frNniDnaHgMIfTable.

This attribute specifies how much availableAggregateCIR can change before an Availability Message Packet (AMP) is sent to the hunt group server informing it of the change. If the value specified is not a multiple of 2048, the value actually used as the threshold will be the next higher multiple of 2048.

This group contains the operational attributes of the HuntGroupMember component.

An entry in the frNniDnaHgMOpTable.

This attribute indicates the maximum aggregate CIR availability for this hunt group member. It is the sum of the maximum CIRs provisioned for SVCs in the FrUni Signaling component.

This attribute indicates the current available aggregate CIR reported to the hunt group in the Availability Message Packet (AMP). It is incremented by the application when a DLCI is freed. It is decremented when a DLCI is allocated. The value is the sum of the currently available aggregate CIRs for SVCs. Both this attribute and the availableDlcis attribute must be non zero for this DNA to receive calls on the hunt group.

This attribute indicates the net change in the available aggregate CIR since the last Availability Message Packet (AMP) was sent to the Hunt Group. Once the absolute value of this attribute reaches the availabilityUpdateThreshold an AMP is sent to the hunt group server(s) and the availabilityDelta is re-computed.

This attribute indicates the number of DLCIs available for SVCs on the interface associated with this DNA. If this value reaches 0, an AMP with zero availability is sent to the hunt group server(s). Both this attribute and the availableAggregateCir attribute must be non zero for this DNA to receive calls on the hunt group.

This group contains attributes common to all DNAs. Every DNA used in the network is defined with this group of 2 attributes.

An entry in the frNniDnaAddressTable.

This attribute indicates the Numbering Plan Indicator (NPI) of the DNA that is entered. Address may belong to X.121 or E.164 plans. X.121 is used in packet switched data networks. Enumeration: 'e164': 1, 'x121': 0.

This attribute indicates the customer's unique identifier. It is the equivalent of the telephone number in the telephone network.

This group defines DNA call options for calls made from the interface. These options are not used for calls arriving to the interface represented by this DNA.

An entry in the frNniDnaOutgoingOptionsTable.

This attribute indicates the default priority of outgoing calls from the DTE to the network. It can be overridden by the discardPriority under DLCI Direct Call subcomponent. This option can be also included in X.25 signalling, in such case it will be overruled. Enumeration: 'high': 1, 'normal': 0.

This attribute specifies the default class of path sensitivity to network for all outgoing calls that use this DNA. The chosen default class of path sensitivity applies to all outgoing calls established using this DNA. This attribute, if set to throughput, indicates that the default class is throughput sensitive. If set to delay, then the default class is delay sensitive. The default of outDefaultPathSensitivity is throughput. Enumeration: 'delay': 1, 'throughput': 0.

If this attribute is set to yes in the call request, the called end will use the calling end provisioning data on path sensitivity to override its own provisioning data. The default of outPathSensitivityOverRide is yes. Enumeration: 'yes': 1, 'no': 0.

This attribute specifies the default class of routing for reliability routing for all outgoing calls (from the DTE to the network) using this particular DNA. The chosen default class of routing applies to all outgoing calls established using this DNA, and applies to the packets travelling in both directions on all outgoing calls (local to remote, and remote to local). For incoming calls, the default class of routing is chosen by the calling party (as opposed to DPN, where either end of the call can choose the default routing class). This attribute, if set to a value of normal, indicates that the default class of routing is normal reliability routing. If set to a value of high, then the default class of routing is high reliability routing. High reliability is the standard choice for most DPN and Passport services. It usually indicates that packets are overflowed or retransmitted at various routing levels. Typically high reliability results in duplication and disordering of packets in the network when errors are detected or during link congestion. However, the VC handles the duplication and disordering to ensure that packets are delivered to the DTE properly. For the Frame Relay service, duplication of packets is not desired, in which case, normal reliability may be chosen as the preferred class of routing. Enumeration: 'high': 0, 'normal': 1.

This attribute is an extension of the Closed User Group (CUG) facility, as follows: This attribute, if set to a value of allowed indicates that outgoing calls (from the DTE to the network) to the open (non-CUG) part of the network are permitted. It also permits outgoing calls to DTEs that have Incoming Access capabilities. If set to a value of disallowed, then such calls cannot be made using this DNA. Such calls will be cleared by the local DCE. This attribute corresponds to the CCITT 'Closed User Group with Outgoing Access' feature for DNAs in that outgoing access is granted if this attribute is set to a value of allowed. Enumeration: 'disallowed': 0, 'allowed': 1.

This attribute specifies the default transfer priority for all outgoing calls using this particular DNA. It can be overridden by the transferPriority provisioned in the Dlci DirectCall sub-component. The transfer priority is a preference configured for an application according to its delay-sensitivity requirement. Frames with higher transfer priority are served by the network before the frames with lower priority. The transfer priority standard is defined to have 16 levels from 0 to 15. Each transfer priority n, where n indicates the transfer priority index, contains a default setting for routing class of service (multimedia, delay or throughput) and frame relay egress queue (depending on the number of supported egress queues on the remote end interface) specified by the routingClassOfService and emissionPriority attributes provisioned in the Mod Frs DprsNet Tpm/n component. The default mapping can be altered by a user if required. The default defaultTransferPriority is 0. Enumeration: 'n12': 12, 'n13': 13, 'n10': 10, 'n11': 11, 'n14': 14, 'n15': 15, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

When this attribute is set to yes in the call request, the called end will use the calling end provisioning data on transfer priority to override its own provisioning data. If it is set no, the called end will use its own provisioning data on transfer priority. This attribute is not applicable for Frame Relay SVCs. For more information about transfer priority, please refer to the previous attribute defaultTransferPriority. The default of transferPriorityOverRide is yes. Enumeration: 'yes': 1, 'no': 0.

This group defines options for incoming calls. These options are used for calls arriving to the interface represented by this DNA. For calls originated from the interface, IncomingOptions attributes are not used.

An entry in the frNniDnaIncomingOptionsTable.

This attribute, if set to a value of allowed specifies that incoming calls (from the network to the DTE) from the open (non-CUG) part of the network are permitted. It also permits incoming calls from DTEs that have outgoing access capabilities. If set to a value of disallowed, such calls cannot be made to this DNA. They will be cleared by the local DCE. This attribute corresponds to the CCITT 'Closed User Group with Incoming Access' feature for DNAs in that incoming access is granted if this attribute is set to a value of allowed. Enumeration: 'disallowed': 0, 'allowed': 1.

This group defines additional all options for not related to direction of the call.

An entry in the frNniDnaCallOptionsTable.

This attribute specifies the accounting class which is reserved for network operations usage. Its value is returned in the accounting record in the local and remote service type attributes. Use of this attribute is decided by network operator. This attribute is returned by the local VC in the accounting record for all calls that are set up using this particular DNA.

This attribute indicates that accounting records are to be collected by the network for the various reasons: billing, test, study, auditing. The last of the parameters, force, indicates that accounting records are to be collected irrespective of other collection reasons. The force option is available for X.75 Gateways only. If none of these reasons are set, then accounting will be suppressed. To set a specific accounting collection reason, the reason is entered and the corresponding bit in the structure is set to a value of 1. To turn off a specific accounting collection reason, the reason is entered preceded with the '~' character, and the corresponding bit in the structure is set to a value of 0. The bit placement for the accounting collection reasons is as follows: Bit 0 - Bill Bit 1 - Test Bit 2 - Study Bit 3 - Audit Bit 4 - Force Description of bits: bill(0) test(1) study(2) audit(3) force(4)

This attribute is an arbitrary number, Data Service Exchange, as entered by the network operator and reported in accounting record. It is converted into an internal 8-bit integer value for use in the accounting record as well as in various X.25 and X.75 Tariff utilities.

This attribute specifies if egress accounting is enabled by the frame relay service. If egress accounting is disabled, only segment counts are collected by the VC. No frame relay counts appear in the accounting records for the frame relay service. If egress accounting is enabled, the accounting records for the frame relay service will contain frame relay specific counts. Enumeration: 'yes': 1, 'no': 0.

This attribute specifies the data path to be used by Virtual Circuits on this interface. If the connection has a DirectCall component then the value can be overridden by the dataPath attribute of the DirectCall component. This value applies to the connection after data transfer state is reached. All the data and control trafic will be sent using this data path. If the provisioned dataPath is not available the connection is not established. The value of the dataPath is signalled by both ends of the connection. If this value is not the same at both ends dprsOnly is used for the duration of the connection. A virtual circuit connection is always established using dprsOnly even if this attribute is provisioned as some other value. dprsOnly - dynamic packet routing system is used dprsMcsOnly - dprs Multi-Service Cut-Through Switching path is used. dprsMcsFirst - dprs Multi-Service Cut-Through Switching path is used if it is available. If it is not avaliable dprsOnly is used. Enumeration: 'dprsMcsOnly': 1, 'dprsMcsFirst': 2, 'dprsOnly': 0.

This entry controls the addition and deletion of frNniFramer components.

A single entry in the table represents a single frNniFramer component.

This variable is used as the basis for SNMP naming of frNniFramer components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniFramer tables.

This variable represents the index for the frNniFramer tables.

This group contains the base provisioning data for the Framer component. Application or hardware interface specific provisioning data is contained in other provisionable Framer groups.

An entry in the frNniFramerProvTable.

This attribute contains a hardware component name. The attribute associates the application with a specific link. This defines the module processor on which Framer's parent component (as well as Framer itself) will run.

This group contains attributes defining the framing of data on the link interface.

An entry in the frNniFramerLinkTable.

This attribute defines the number of flags that are inserted between frames sent to the link interface.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the frNniFramerStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains the operational statistics data for a Framer component.

An entry in the frNniFramerStatsTable.

The number of frames transmitted to the link interface by Framer. Note: This does not include the number of frames transmitted directly to the hardware queue, thus bypassing the Framer component.

The number of frames received from the link interface by Framer.

The number of bytes received from the link interface by Framer.

This attribute is the total number of aborts received.

This attribute is the total number of frames with CRC errors, occurring in the receive direction from the link.

This attribute is the total number of frames with LRC errors, occurring in the Tx link prior to transmission onto the link.

This attribute is the total number of frames that were non octet aligned.

This attribute is the total number of frames received from the link for which overruns occurred.

This attribute is the total number of frames transmitted to the link for which underruns occurred.

This attribute is the total number of frames received which were too large. The frame execeeded the maximumFrameLengthLimit provisioned attribute or it contained more than the 255 block hardware limit.

This attribute is the total number of frames detected with framing mode errors. A framingModeError is flagged when frames are inconsistent with the specified framingType, that is when interrupting frames are used while running in hdlc mode.

This group contains the link utilizaiton operational data for a Framer component.

An entry in the frNniFramerUtilTable.

This attribute is the utilization of the normal and high priority data traffic (interruptable traffic) sent to the link as a percentage of the available bandwidth on the link. Note that this includes traffic with Transfer Priorities (TP) of 0, 6 and 9 and/or Emission Priority of 2 and 3. The utilization is the average for the last minute.

This attribute is the utilization of the normal and high priority data traffic (interruptable traffic) received from the link as a percentage of the available bandwidth on the link. Note that this includes traffic with Transfer Priorities (TP) of 0, 6 and 9 and/or Emission Priority of 2 and 3. The utilization is the average for the last minute.

This entry controls the addition and deletion of frNniLmi components.

A single entry in the table represents a single frNniLmi component.

This variable is used as the basis for SNMP naming of frNniLmi components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniLmi tables.

This variable represents the index for the frNniLmi tables.

This group contains the provisionable attributes of the Local Management Interface component.

An entry in the frNniLmiParmsTable.

This attribute selects the procedures to be used for the Local Management Interface. The following are the supported procedures: none: Local Management Interface procedures are not running on this interface. This accommodates Frame Relay user equipment which didn't implement any LMI procedures. In this case, the remaining attributes of this group are ignored. ansi: Local Management Interface procedures from the ANSI specification are supported. DLCI 0 is used for the LMI protocol. itu: Local Management Interface procedures from the ITU-T specification are supported. DLCI 0 is used for the LMI protocol. Was previously ccitt. autoConfigure: The interface determines automatically which Local Management Interface procedures to use. The procedures currently being used can be seen in the operational attribute opProcedures. Enumeration: 'ansi': 2, 'none': 0, 'it': 3, 'autoConfigure': 4.

This attribute selects the use of asynchronous PVC status report procedures as specified in ANSI and CCITT specification. Enumeration: 'on': 1, 'off': 0.

For the network-side-procedure, an event is defined as follows: (1) receipt of a STATUS ENQUIRY message, or (2) expiration of timer T392. An error event is (1) nonreceipt of STATUS ENQUIRY in T392 seconds; (2) invalid format of a LMI message; (3) invalid receive sequence number. For the user-side-procedure, an event is defined as a polling cycle or a status enquiry and status report exchange. An error event is (1) non-receipt of a STATUS within the polling cycle, or (2) invalid format of a LMI message, or (3) invalid sequence number This attribute specifies the number of error events which, if they occur within eventCount events, will cause a protocol error condition. The condition is cleared after eventCount sequential correct events occur. It must be less than or equal to eventCount (n393)

This attribute specifies the number of contiguous events within which no more than eventErrorThreshold error events are allowed. It must be greater than or equal to errorEventThreshold (n392).

This attribute selects the time (in seconds) within which a STATUS ENQUIRY message is expected. It must be greater than linkVerificationTimer (t391).

This attribute specifies whether the Frame Relay LMI Active Bit (A-bit) has a bearing on the transfer of user data across this Frame Relay interface for both directions of traffic flow. When this attribute is set to yes, the A-bit status of a user DLCI connection does not affect data transfer. When this attribute is set to no, data received from the local interface is discarded if an A-bit =0 condition exists towards the local user. Data being sent to the local interface is discarded if an A- bit = 0 condition exists towards the local user. Enumeration: 'yes': 1, 'no': 0.

This group contains the provisionable attributes of the Local Management Interface component which are unique to NNI.

An entry in the frNniLmiNniParmsTable.

This attribute specifies how frequently the Frame Relay NNI service should initiate a Status Enquiry for a full PVC status report. A polling cycle is a Status Enquiry and Status Report exchange.

This attribute specifies how frequently the Frame Relay NNI service should initiate a Status Enquiry for link integrity verification. It must be less than checkPointTimer (t392).

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the frNniLmiStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group provides the protocol status of the Local Management Interface.

An entry in the frNniLmiPsiTable.

This attribute indicates whether the LMI is in an error condition or whether the LMI procedures are behaving normally. When operating with no LMI protocol, this attribute is always set to normalCondition. When operating with LMI procedures, this attribute is set to errorCondition after n392 of the last n393 events are in error. The consequence of an errorCondition is that all DLCIs on this interface will become inactive in both directions. The errorCondition is lifted and a normalCondition is indicated when a sufficient number of events have occurred without error. In ANSI, this occurs when n393 consecutive good events take place. If the procedures attribute is set to autoConfigure, this attribute is se to configuring while adaptive LMI determines which LMI procedures are running on the link. A single LMI error event during auto configuration causes the attribute value to change to errorCondition. If during configuring no LMI message is received, an LMI errorCondition is raised after n392 x t392 seconds. Enumeration: 'normalCondition': 1, 'configuring': 2, 'errorCondition': 0.

This attribute indicates the procedures being used for the Local Management Interface. This attribute should be ignored if protocolStatus is not normalCondition. The following procedures are supported: none: Local Management Interface procedures are not running on this interface. This accommodates Frame Relay user equipment that has not implemented any LMI procedures. ansi: Local Management Interface procedures from the ANSI specification are running. DLCI 0 is used for the LMI protocol. itu: Local Management Interface procedures from the ITU-T specification are running. DLCI 0 is used for the LMI protocol. Was previously ccitt. unknown: Local Management Interface procedures have yet to be determined by Adaptive LMI. Enumeration: 'ansi': 2, 'none': 0, 'it': 3, 'unknown': 4.

This group contains the operational statistics for the Frame Relay NNI Local Management Interface.

An entry in the frNniLmiStatsTable.

This attribute counts the number of Local Management Interface keep alive status messages sent to the external network in response to a status enquiry for keep alive status. When the maximum count is exceeded it wraps to zero.

This attribute counts the number of Local Management Interface full status messages sent to the external network in response to a status enquiry for keep alive or full status. When the maximum count is exceeded it wraps to zero.

This attribute counts the number of Local Management Interface valid keep alive status enquiry messages received from the external network. When the maximum count is exceeded it wraps to zero.

This attribute counts the number of Local Management Interface valid full status enquiry messages received from the external network. When the maximum count is exceeded it wraps to zero.

This attribute displays the Local Management Interface network side procedure event history in order of occurrence. An event is represented by a single symbol. A '+' symbol indicates a good event. An 'X' symbol indicates a protocol error event. The leftmost event is the most recent to occur. The provisioned eventCount (nN3/ N393) dictates the maximum number of events displayed. A good event is triggered by receipt of a valid status enquiry message. An error event is either a nT2/T392 timer expiry or receipt of a status enquiry with bad sequence numbers.

This attribute displays the Local Management Interface user side procedure event history in order of occurrence. An event is represented by a single symbol. A '+' symbol indicates a good event. An 'X' symbol indicates a protocol error event. The leftmost event is the most recent to occur. The provisioned eventCount (nN3/ N393) dictates the maximum number of events displayed. A good event is triggered by receipt of a valid status message. An error event is either a nT1/T391 timer expiry or receipt of a status message with bad sequence numbers.

This attribute counts the number of Local Management Interface protocol errors. It is the sum of the sequence (sequenceErrors and statusSequenceErrors) and timeout (pollingVerifTimeouts and noStatusReportCount) errors. When the maximum count is exceeded it wraps to zero.

This attribute counts the number of Local Management Interface frames received with an Information Element identifier that is unknown or unexpected. An unexpected Information Element is not a protocol error. When the maximum count is exceeded, this counter wraps to zero.

This attribute counts the number of Local Management Interface Status Enquiry message sequence errors. A sequence error is receipt of a Status Enquiry message with a receive sequence number not equal to the last send sequence number. When the maximum count is exceeded the counter wraps to zero.

This attribute counts the number of Local Management Interface Status message sequence errors. A sequence error is receipt of a Status message with a receive sequence number not equal to the last send sequence number. When the maximum count is exceeded the counter wraps to zero.

This attribute counts the number of Local Management Interface frames received with an unknown or unexpected report type. An unexpected report type is not a protocol error. When the maximum count is exceeded the counter wraps to zero.

This attribute counts the number of checkPointTImer (t392) timer expiries occurring on the Local Management Interface. When the maximum count is exceeded the counter wraps to zero.

This attribute counts the number of times when no status report or an invalid status report comes from the external network. This attribute is incremented in two cases: i) after a status enquiry is sent out and T391 timer expires without having a status report received. ii) an invalid status report is received. When the maximum count is exceeded it wraps to zero.

This entry controls the addition and deletion of frNniDlci components.

A single entry in the table represents a single frNniDlci component.

This variable is used as the basis for SNMP naming of frNniDlci components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDlci tables.

This variable represents the index for the frNniDlci tables.

This entry controls the addition and deletion of frNniDlciDc components.

A single entry in the table represents a single frNniDlciDc component.

This variable is used as the basis for SNMP naming of frNniDlciDc components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDlciDc tables.

This variable represents the index for the frNniDlciDc tables.

Options group defines attributes associated with direct call. It defines complete connection in terms of path and call options. This connection can be permanent (pvc) or switched (svc). It can have facilities. The total number of bytes of facilities including the facility codes, and all of the facility data from all of the four classes of facilities: CCITT_Facilities DTE_Facilities National_Facilities International_Facilities must not exceed 512 bytes.

An entry in the frNniDlciDcOptionsTable.

Destination Numbering Plan Indicator (Npi) indicates the numbering plan used in the remoteDna. Enumeration: 'e164': 1, 'x121': 0.

This attribute specifies the Data Network Address (DNA) of the remote. This is the called (destination) DTE address (DNA) to which this direct call will be sent. Initially, the called DTE address attribute must be present, that is, there must be a valid destination address. However, it may be possible in the future to configure the direct call with a mnemonic address, in which case, this attribute will contain a zero-length DNA, and the mnemonic address will be carried as one of the facilities.

L(LCN) of the destination. This attribute provides the remote LCN (Logical Channel Number) - it is used only for PVCs, where the parameter Type is set to a value of PVC.

This attribute specifies the type of Vc call: permanentMaster, permanentSlave, permanentSlaveWithBackup, permanentBackupSlave. If the value is set to permanentMaster, then a permanent connection will be established between 2 ends. The remote end must be defined as a permanentSlave, permanentBackupSlave or permanentSlaveWithBackup. The Connection cannot be established if the remote end is defined as anything else. The end defined as permanentMaster always initiates the calls. It will attempt to call once per minute. If the value is set to permanentSlave then a permanent connection will be established between 2 ends. The remote end must be defined as a permanentMaster. The Connection cannot be established if the remote end is defined as anything else. The permanentSlave end will attempt to call once per minute. If the value is set to permanentSlaveWithBackup then a permanent connection will be established between the two ends. The remote end must be defined as a permanentMaster. The connection cannot be established if the remote interface end is defined as anything else. The permanentSlaveWithBackup end will attempt to call once per minute. When type is set to permanentSlaveWithBackup connection will be cleared if interface becomes unavailable. This enables a retry of the connection which can be redirected to permanentBackupSlave. If the value is set to permanentBackupSlave then a permanent connection will be established between the 2 ends only if the permanentMaster end is disconnected from the permanentSlaveWithBackup end and a backup call is established by the redirection system. If the permanentSlaveWithBackup interface becomes visible again, the permanentBackupSlave end is disconnected and the permanentSlaveWithBackup end is reconnected to the permanentMaster end. The permanentBackupSlave end does not try to establish pvc call. Enumeration: 'permanentSlave': 2, 'permanentMaster': 1, 'permanentBackupSlave': 3, 'permanentSlaveWithBackup': 4.

This attribute specifies the transfer priority to network for the outgoing calls using this particular DLCI. It overRides the defaultTransferPriority provisioned in its associated Dna component. The transfer priority is a preference configured for an application according to its delay-sensitivity requirement. Frames with higher transfer priority are served by the network before the frames with lower priority. The transfer priority standard is defined to have 16 levels from 0 to 15. Each transfer priority n, where n is the transfer priority index, contains a default setting for routing class of service (multimedia, delay or throughput) and frame relay egress queue (depending on the number of supported egress queues on the remote end interface) specified by the routingClassOfService and emissionPriority attributes provisioned under the Mod Frs DprsNet Tpm/n component. The default mapping can be altered by a user if required. The default of transferPriority is useDnaDefTP. It means using the provisioning value under defaultTransferPriority of its associated Dna for this DLCI. Enumeration: 'n12': 12, 'n13': 13, 'n10': 10, 'n11': 11, 'n14': 14, 'n15': 15, 'useDnaDefTP': 255, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the discard priority for outgoing call using this DLCI. The discard priority has three provisioning values: normal, high, and useDnaDefPriority. Traffic with normal priority are discarded first than the traffic with high priority. The Dna default value (provisioned by outDefaultPriority) is taken if this attribute is set to the value useDnaDefPriority. The default of discardPriority is useDnaDefPriority. Enumeration: 'high': 1, 'useDnaDefPriority': 3, 'normal': 0.

This attribute specifies whether the discardPriority applies to DE frames for this DLCI. If deDiscardPriority is set to determinedByDiscardPriority, traffic with DE bit set will be discarded according to the setting of the discardPriority. If deDiscardPriority is set to lowest, all traffic with DE bit set will be treated the same and be sent to the subnet at the lowest discard priority. Enumeration: 'lowest': 0, 'determinedByDiscardPriority': 1.

This attribute specifies the data path to be used by Virtual Circuits on this interface. The value of the dataPath attribute in the Dna component is overridden by this attribute if the value is not useDnaValue. This value applies to the connection after data transfer state is reached. All the data and control trafic will be sent using this data path. If the provisioned dataPath is not available the connection is not established. The value of the dataPath is signalled by both ends of the connection. If this value is not the same at both ends dprsOnly is used for the duration of the connection. A virtual circuit connection is always established using dprsOnly even if this attribute is provisioned as some other value. dprsOnly - dynamic packet routing system is used dprsMcsOnly - dprs Multi-Service Cut-Through Switching path is used. dprsMcsFirst - dprs Multi-Service Cut-Through Switching path is used if it is available. If it is not avaliable dprsOnly is used. useDnaValue - use the value provisioned in Dna component. Enumeration: 'useDnaValue': 3, 'dprsMcsOnly': 1, 'dprsMcsFirst': 2, 'dprsOnly': 0.

This attribute specifies the CUG index which is to be signalled in PVC call requests to the remote end. The type of CUG signalling is defined in attribute cugType in this component.

This attribute specifies the type of CUG signalling to be used in PVC call request. Index of CUG to be used is defined in attribute cugIndex in this component. Possible values are: cug - signal cug cugOa - signal cug with outgoing access doNotSignal - no CUG in call request Enumeration: 'cug': 3, 'doNotSignal': 0, 'cugOa': 9.

This is the i'th National facility required for this direct call. Within the provisioning system, the user specifies the facility code along with the facility parameters. The facility is represented internally as a hexadecimal string following the X.25 CCITT representation for facility data. Two explicit attributes discardPriority and pathSensitivity are created to replace H.01 and H.30 in the group VcsDirectCallOptionsProv of this file. The migrate escape here (DcComponent::migrateFaxEscape) propagates the old provisioning data under H.01 and H.30 into discardPriority and transferPriority. The rule of the above propagation are: 0 in H.01 is equivalent to discardPriority 0; 1 in H.01 is equivalent to discardPriority 1. And 0 in H.30 is equivalent to transferPriority throughput; 1 in H.30 is equivalent to pathSensitivity delay. Please refer to discardPriority and pathSensitivity for more information on how to use them.

An entry in the frNniDlciDcNfaTable.

This variable represents the index for the frNniDlciDcNfaTable.

This variable represents an individual value for the frNniDlciDcNfaTable.

This variable is used to control the addition and deletion of individual values of the frNniDlciDcNfaTable.

This entry controls the addition and deletion of frNniDlciVc components.

A single entry in the table represents a single frNniDlciVc component.

This variable is used as the basis for SNMP naming of frNniDlciVc components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDlciVc tables.

This variable represents the index for the frNniDlciVc tables.

This group represents operational call data related to Frame Relay Vc. It can be displayed only for Frame Relay Vc which is created by application.

An entry in the frNniDlciVcCadTable.

This attribute displays the type of call, pvc,svc or spvc. Enumeration: 'spvc': 2, 'pvc': 1, 'svc': 0.

This attribute displays the state of call control. P5 state is not supported but is listed for completness. Transitions from one state to another take very short time. state most often displayed is dataTransferP4. Enumeration: 'readyP1': 1, 'creating': 0, 'dteWaitingP2': 2, 'dceWaitingP3': 3, 'termination': 8, 'dataTransferP4': 4, 'dteClearRequestP6': 6, 'dceClearIndicationP7': 7, 'unsupportedP5': 5.

This attribute displays the previous state of call control. This is a valuable field to determine how the processing is progressing. Enumeration: 'readyP1': 1, 'creating': 0, 'dteWaitingP2': 2, 'dceWaitingP3': 3, 'termination': 8, 'dataTransferP4': 4, 'dteClearRequestP6': 6, 'dceClearIndicationP7': 7, 'unsupportedP5': 5.

This attribute displays the internal substate of call control. It is used to further refine state of call processing.

This attribute displays the internal substate of call control. It is used to further refine state of call processing.

This attribute displays the Numbering Plan Indicator (NPI) of the called end. Enumeration: 'e164': 1, 'x121': 0.

This attribute displays the Data Network Address (Dna) of the called (destination) DTE to which this call is sent. This address if defined at recieving end will complete Vc connection.

This attribute displays the Logical Channel Number of the called end. It is valid only after both ends of Vc exchanged relevant information.

This attribute displays the Numbering Plan Indicator (NPI) of the calling end. Enumeration: 'e164': 1, 'x121': 0.

This attribute displays the Data Network Address (Dna) of the calling end.

This attribute displays the Logical Channel Number of the calling end.

This attribute indicates that this optional section of accounting record is suppressed or permitted. If accountingEnabled is yes, conditions for generation of accounting record were met. These conditions include billing options, vc recovery conditions and Module wide accounting data options. Enumeration: 'yes': 0, 'no': 1.

This attribute displays that this is a fast select call. Enumeration: 'yes': 1, 'no': 0.

This attribute displays the path reliability. Enumeration: 'high': 0, 'normal': 1.

This attribute indicates if this end should generate an accounting record. Normally, callingEnd is the end to generate an accounting record. Enumeration: 'calledEnd': 1, 'callingEnd': 0.

This attribute displays whether the call is a normal or a high priority call. Enumeration: 'high': 1, 'normal': 0.

This attribute displays the segment size (in bytes) used on the call. It is used to calculate the number of segments transmitted and received.

This attribute indicates the maximum packet size allowed on the Vc.

This attribute indicates the routing metric routing class of service to the network. Enumeration: 'delay': 1, 'multimedia': 2, 'throughput': 0.

This attribute displays the routing metric Routing Class of Service from the Network. Enumeration: 'delay': 1, 'multimedia': 2, 'throughput': 0.

This attribute displays the network internal emission priotity to the network. Enumeration: 'high': 1, 'interrupting': 2, 'normal': 0.

This attribute displays the network internal emission priotity from the network. Enumeration: 'high': 1, 'interrupting': 2, 'normal': 0.

This attribute indicates the data path used by the connection. The data path is provisioned in Dna and DirectCall components. The displayed value of this attribute can be different from the provisioned value. If the connection is using dprsOnly data path, the string dprsOnly is displayed. (dynamic packet routing system) If the connection is using dprsMcsOnly data path, the string dprsMcsOnly is displayed. If the connection is using dprsMcsFirst data path, the string dprsMcsFirst is displayed.

This group defines display of interval data collected by Vc. Data in this group is variable and may depend on time when this display command is issued.

An entry in the frNniDlciVcIntdTable.

This attribute displays the call reference number which is a unique number generated by the switch.The same Call Reference Number is stored in the interval data (accounting record) at both ends of the call. It can be used as one of the attributes in matching duplicate records generated at each end of the call.

This attribute displays the elapsed time representing the period of this interval data. It is elapsed time in 0.1 second increments since Vc started.

This attribute displays the number of segments received at the time command was issued. This is the segment received count maintained by accounting at each end of the Vc. This counter is updated only when the packet cannot be successfully delivered out of the sink Vc and to the sink AP Conditions in which packets may be discarded by the sink Vc include: missing packets due to subnet discards, segmentation protocol violations due to subnet discard, duplicated and out-of-ranged packets and packets that arrive while Vc is in path recovery state.

This attribute displays the number of segments sent at the time command was issued. This is the segment sent count maintained by accounting at the source Vc. Vc only counts packets that Vc thinks can be delivered successfully into the subnet. In reality, these packets may be dropped by trunking, for instance. This counter is not updated when splitting fails, when Vc is in a path recovery state, when packet forwarding fails to forward this packet and when subsequent packets have to be discarded as we want to minimize the chance of out-of-sequence and do not intentionally send out-of- sequenced packets into the subnet.

This attribute displays the start time of this interval period. If Vc spans 12 hour time or time of day change startTime reflects new time as recorded at 12 hour periods or time of day changes.

This group defines Frame Relay attributes collected by Frame Relay Vc. The purpose of Vc attributes is to aid end users and verification people to understand the Vc internal behavior. This is particularly useful when the network has experienced abnormality and we want to isolate problems and pinpoint trouble spots. Attributes are collected on a per Vc basis. Until a need is identified, statistics are not collected at a processor level. Each attribute is stored in a 32 bit field and is initialized to zero when a Vc enters into the data transfer state. When a PVC is disconnected and then connected again, the attributes will be reset. Attributes cannot be reset through other methods. Frame Relay Vc uses a best effort data packet delivery protocol and a different packet segmentation and combination methods from the General Vc. The Frame Relay Vc uses the same call setup and control mechanism (e.g. the support of non-flow control data packets) as in a General Vc. Most General Vc statistics and internal variables are used in a Frame Relay Vc and are displayed by software developers

An entry in the frNniDlciVcFrdTable.

This attribute displays the number of frames from link discarded due to lack of resources. It keeps track of the number of frames from link that have to be discarded. The discard reasons include insufficient memory for splitting the frame into smaller subnet packet size.

This attribute displays the number of discarded packets that can not be forwarded into the subnet because of subnet congestion. Number of frames from link discarded due to failure in forwarding a packet from Vc into the subnet.- This attribute is increased when packet forwarding fails to forward a packet into the subnet. If a frame is split into multiple subnet packets and a partial packet has to be discarded, all subsequent partial packets that have not yet been delivered to the subnet will be discarded as well.

This attribute records the number of frames from link discarded when the Vc tries to recover from internal path failure.

This attribute displays the number of frames from subnet discarded due to out of sequence range for arriving too late.

This attribute records the number of subnet packets discarded at the sink Vc due to the Vc segmentation and combination protocol error. Usually, this occurs when the subnet discards packets and thus this statistics can be used to guest the number of subnet packets that are not delivered to the Vc. It cannot be used as an actual measure because some subnet packets may have been delivered to Vc but have to be discarded because these are partial packets to a frame in which some other partial packets have not been properly delivered to Vc

This attribute displays the number of subnet packets discarded due to duplication. Although packets are not retransmitted by the Frame Relay Vc, it is possible for the subnet to retransmit packets. When packets are out-of-sequenced and copies of the same packets arrive, then this attribute is increased.

This attribute displays the number of subnet packets discarded when data transfer is suspended in Vc recovery.

This attribute displays the number of lost frame timer expiries. When this count is excessive, the network is very congested and packets have been discarded in the subnet.

This attribute displays the number times that the out of sequence byte threshold is exceeded. When the threshold is exceeded, this condition is treated as if the loss frame timer has expired and all frames queued at the sink Vc are delivered to the AP. We need to keep this count to examine if the threshold is engineered properly. This should be used in conjunction with the peak value of out-of- sequenced queue and the number of times the loss frame timer has expired. This count should be relatively small when compared with loss frame timer expiry count.

This attribute displays the frame relay peak packet count of the out of sequence queue. This attribute records the maximum queue length of the out-of-sequenced queue. The counter can be used to deduce the message buffer requirement on a Vc.

This attribute displays the frame relay peak size of the sequence packet queue. The subnet may deliver packets out-of- sequenced. These packets are then queued in an out-of-sequenced queue, waiting for a packet with the expected sequence number to come. When that packet arrives, this attribute records the maximum number of packets that were out-of-sequenced, but now have become in-sequenced. The statistics is used to measure expected queue size due to normal subnet packet disorder (not due to subnet packet discard). Current implementation also uses this statistics to set a maximum size for the out-of-sequenced queue.

This attribute displays the Vc internal packet's send sequence number. Note that a 'packet' in this context, may be either a user data packet, or an OAM frame.

This attribute displays the number of packets which have retransmission time-outs. When this count is excessive, the network is very congested and packets have been discarded in the subnet.

This attribute displays the peak size of retransmission queue. This attribute is used as an indicator of the acknowledgment behavior across the subnet. Records the largest body of unacknowledged packets.

This attribute displays the number of successful Vc recovery attempts.

This attribute displays the number times that the out of sequence packet threshold is exceeded. When the threshold is exceeded, this condition is treated as if the loss frame timer has expired and all frames queued at the sink Vc are delivered to the AP. We need to keep this count to examine if the threshold is engineered properly. This should be used in conjunction with the peak value of out-of- sequenced queue and the number of times the loss frame timer has expired. This count should be relatively small when compared with loss frame timer expiry count.

This attribute displays the frame relay peak byte count of the out of sequence queue. This attribute records the maximum queue length of the out-of-sequenced queue. The counter can be used to deduce the message buffer requirement on a Vc.

This attribute displays the data path used by the connection. Data path is provisioned in Dna and DirectCall components. If the connection is using dprsOnly data path, this attribute is empty. If the connection is using dprsMcsOnly or dprsMcsFirst data path, this attribute displays component name of the dprsMcsEndPoint.

An entry in the frNniDlciVcDmepTable.

This variable represents both the value and the index for the frNniDlciVcDmepTable.

This entry controls the addition and deletion of frNniDlciSp components.

A single entry in the table represents a single frNniDlciSp component.

This variable is used as the basis for SNMP naming of frNniDlciSp components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDlciSp tables.

This variable represents the index for the frNniDlciSp tables.

This group contains the provisionable attributes for the Data Link Connection Identifier. These attributes reflect the service parameters specific to this instance of DLCI . The congestion control attributes in this group are defined in T1.606 Addendum 1.

An entry in the frNniDlciSpParmsTable.

This attribute specifies the maximum number of octets which may be included in the information field. The frame relay header and CRC octets are not included in this definition. This attribute corresponds to the dN1 parameter described in the Vendor Forum Specification.

This attribute specifies whether rate enforcement is in effect for this user Data Link Connection on this Frame Relay interface. Turning on rate enforcement means that CIR and DE=1 traffic will be measured and enforced. Turning off rate enforcement means that all frames from the user will be accepted and no modifications to the frame with respect to the DE bit will be made. Enumeration: 'on': 1, 'off': 0.

This attribute specifies the committed information rate (CIR) in bits per second (bit/s). When rateEnforcement is set to on, cir is the rate at which the network agrees to transfer information under normal conditions. This rate is measured over a measurement interval (t) that is determined internally based on CIR and the committed burst size (Bc). An exception to this occurs when CIR is provisioned to be zero, in which case the measurement interval (t) must be provisioned explicitly. This attribute is ignored when rateEnforcement is off. If rateEnforcement is on and this attribute is 0, Bc must also be 0.

This attribute specifies the committed burst size (Bc) in bits. bc is the amount of data that a network agrees to transfer under normal conditions over a measurement interval (t). Data marked DE=1 is not accounted for in Bc. This attribute is ignored when rateEnforcement is off. If rateEnforcement is on and this attribute is 0, cir must also be 0.

This attribute specifies the excess burst size (Be) in bits. Be is the amount of uncommitted data that the network will attempt to deliver over measurement interval T. Data marked DE=1 by the user or by the network is accounted for here. CIR, Bc, and Be cannot all be zero when rateEnforcement is on.

When cir and bc are zero and rateEnforcement is on, this attribute must be provisioned to specify the time interval (in milliseconds) over which rates and burst sizes are measured. When cir and bc are non-zero, the time interval is internally calculated and is not shown. In that situation, this field is ignored, and is not representative of the time interval. This attribute is ignored when rateEnforcement is off, or when cir and bc are non-zero. If rateEnforcement is on and both cir and bc are zero, this field must be non-zero.

This attribute specifies whether rate adaptation is in effect for this user Data Link Connection on this Frame Relay interface. Rate adaptation is a feature that, in periods of congestion, adapts the rate at which the user is allowed to send data into the network to that which the network is able to handle at that time. This pro-active measure of handling congestion optimizes network resources by causing the ingress to discard frames that would otherwise be discarded in the network. If this attribute is set to on, then, at the onset of congestion, the excess information rate (EIR) is reduced to a very low rate. If congestion persists, then the allowed CIR is reduced geometrically by 25% of the current value at that time. The minimum to which CIR can be reduced is 1/16th (6.25%) of the provisioned value. As congestion alleviates, CIR is increased linearly by 6.25% of the provisioned value specified in committedInformationRate. If set to eirOnly, then rate adaptation will only apply to the excess information rate (EIR). At the onset of congestion, the allowed EIR is reduced by 25% of its provisioned value. If congestion persists, EIR is reduced geometrically by 25% of the current value at that time. As congestion alleviates, EIR is gradually increased linearly by 6.25% of the provisioned EIR. If set to cirProportionate, then rate adaptation will also only apply to the excess information rate (EIR). At the onset of congestion the initial allowed EIR is set to a multiple of the provisioned CIR. If congestion persists, the allowed EIR is reduced geometrically by 25% of the current value at that time. As congestion alleviates, EIR is gradually increased linearly by 6.25% of the provisioned EIR. Note that the allowed EIR may be set higher than the provisioned EIR, since it is calculated initially using another parameter, the provisioned CIR. If the allowed EIR at the moment is higher than the provisioned EIR, then the provisioned EIR is used instead. This attribute can only be set to on eirOnly or cirProportionate if rateEnforcement is turned on. Enumeration: 'cirProportionate': 3, 'on': 1, 'off': 0, 'eirOnly': 2.

This attribute specifies whether accounting data collection and record generation is turned on at this DLCI. For accounting data collection and record generation to be turned on, the accountingOn bit and at least one of the accountCollection bits in the DataNetworkAddress component must be set to on. Enumeration: 'on': 1, 'off': 0.

This attribute specifies the sensitivity of the rate adaptation system. A higher number indicates a higher sensitivity and therefore a quicker reaction time to network conditions. A quicker reaction time allows the network to discard frames at the access and protect network resources, but can lead to false alarms and a greater fluctuation of the allowed rate. A higher setting therefore tends to favour the protection of the network over the allowed throughput of the user. A lower number indicates a lower sensitivity and therefore a slower reaction to network conditions. A slower reaction time results in a greater amount of user traffic allowed into the network, but can lead to a waste of network bandwidth since the traffic may be discarded at the congested resource. A lower setting therefore tends to favour the allowed throughput of the user over the protection of the network. This attribute is applicable for adapting EIR when rateAdaptation is eirOnly or cirProportionate, or CIR when rateAdaptation is on. This attribute is ignored if rateAdaptation is turned off.

This attribute specifies whether internal Backward Congestion Indication (BCI) bits will report congestion external to the Passport network, as communicated through incoming BECN bits. If updateBCI is set to on, then BCI bits for incoming frames will be set if the BECN on the frame is set. If updatBCI is set to off, then incoming BECN bits will have no effect. Setting updateBCI on for a DLCI means that the remote end of the DLCI, which is specified by the remotedna and remotedlci attributes of the dc component of the dlci, may perform Rate Adaptation using the flow of incoming BECN bits, in addition to internal Passport congestion management systems. If the rateAdaptation attribute of the remote dlci is provisioned as eirOnly, cirProportionate, or on, then congestion from another network connected to a Passport network may trigger dynamic congestion management. If the rateAdaptation attribute of the remote dlci is provisioned to off, then the setting of updateBCI attribute here will have no effect.. Enumeration: 'on': 1, 'off': 0.

This entry controls the addition and deletion of frNniDlciLb components.

A single entry in the table represents a single frNniDlciLb component.

This variable is used as the basis for SNMP naming of frNniDlciLb components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniDlciLb tables.

This variable represents the index for the frNniDlciLb tables.

This group contains all the statistics for the data loopback tool.

An entry in the frNniDlciLbStatsTable.

This attribute records the number of frames looped back to the link since loopback was last started.

This attribute records the number of bytes looped back to the link since loopback mode was started.

This attribute records the number of frames with the Forward Explicit Congestion Notification (FECN) bit set, looped back to the link since the loopback mode was started.

This attribute records the number of frames with the Backward Explicit Congestion Notification (BECN) bit set, looped back to the link since the loopback mode was started.

This attribute records the number of frames with the Discard Eligibility (DE) bit set, looped back to the link since the loopback mode was started.

This attribute records the number of bytes in frames with the Discard Eligibility (DE) bit set, looped back to the link since the loopback mode was started.

This attribute records the number of frames looped back to the subnet since loopback was last started.

This attribute records the number of bytes looped back to the subnet since loopback was last started.

This attribute records the number of frames with the Forward Explicit Congestion Notification (FECN) bit set, looped back to the subnet since the loopback mode was started.

This attribute records the number of frames with the Backward Explicit Congestion Notification (BECN) bit set, looped back to the subnet since the loopback mode was started.

This attribute records the number of frames with the Discard Eligibility (DE) bit set, looped back to the subnet since the loopback mode was started.

This attribute records the number of bytes in frames with the Discard Eligibility (DE) bit set, looped back to the subnet since the loopback mode was started.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241- 7001-150, Passport Operations and Maintenance Guide.

An entry in the frNniDlciStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains the A-Bit status information for this Data Link Connection Identifier.

An entry in the frNniDlciAbitTable.

This attribute is the most recent A-bit status sent to the interface. The A-bit status is part of the LMI protocol, and indicates willingness to accept data from the local interface. When an inactive setting is sent out, the Frame Relay service will discard any data offered from the local interface. When an active setting is sent out, the Frame Relay service will try to process all data offered from the local interface. Enumeration: 'active': 1, 'inactive': 0.

This attribute provides the reason (if any) for an inactive status to be sent to the interface. This reason is not applicable for an active status. Enumeration: 'remoteLmiError': 3, 'notApplicable': 0, 'pvcDown': 6, 'localLmiError': 2, 'remoteUserSignaled': 1, 'localLinkDown': 4, 'remoteLinkDown': 5.

This attribute is the most recent A-Bit status received from the interface. Enumeration: 'active': 1, 'inactive': 0.

This attribute provides the reason (if any) for an inactive status to be sent to the subnet. This reason is not applicable for an active status. Enumeration: 'missingFromLmiReport': 7, 'notApplicable': 0, 'localLmiError': 2, 'remoteUserSignaled': 1, 'localLinkDown': 4.

This attribute has the value on when the DLCI is in loopback mode and off otherwise. This loopback command verbs start and stop are used to initiate and terminate the loopback mode for a DLCI. While loopbackState is on, the local LMI will report to the interface the A- bit status as active. Also an active A-bit signal will be reliably propagated across the subnet to the remote DLCI. Enumeration: 'on': 1, 'off': 0.

This group defines the service and traffic parameters specific to this instance of DLCI. For PVCs, the values of attributes with the exception of the measurementInterval should be identical to those in the group FrsDataLinkConnectionProv under the FrsNniServiceParametersProv component. For SVC's, the values of attributes may be different from the values provisioned under the Signaling subcomponent, if Q933 negotiations has ocurred to alter service parameters.

An entry in the frNniDlciSpOpTable.

This attribute specifies the maximum number of octets which may be included in the information field. The frame relay header and CRC octets are not included in this definition. This attribute corresponds to the dN1 parameter described in the Vendor Forum Specification.

This attribute is obsolete. It provided the same information as the provision attribute rateEnforcement in dlci/* sp. Enumeration: 'on': 1, 'off': 0.

This attribute specifies the committed information rate (CIR) in bits per second (bit/s). When rateEnforcement is set to on, cir is the rate at which the network agrees to transfer information under normal conditions. This rate is measured over a measurement interval (t) that is determined internally based on CIR and the committed burst size (Bc). An exception to this occurs when CIR is provisioned to be zero, in which case the measurement interval (t) must be provisioned explicitly. This attribute should be ignored when rateEnforcement is off.

This attribute specifies the committed burst size (Bc) in bits. bc is the amount of data that a network agrees to transfer under normal conditions over a measurement interval (t). Data marked DE=1 is not accounted for in Bc. This attribute should be ignored when rateEnforcement is off.

This attribute specifies the excess burst size (Be) in bits. Be is the amount of uncommitted data that the network will attempt to deliver over measurement interval T. Data marked DE=1 by the user or by the network is accounted for here. This attribute should be ignored when rateEnforcement is off.

This attribute specifies the time interval (in milliseconds) over which rates and burst sizes are measured. This attribute should be ignored when rateEnforcement is off.

This attribute is obsolete. It provided the information which is now in the provision attribute rateAdaptation in dlci/* sp. Enumeration: 'on': 1, 'off': 0, 'eirOnly': 2.

This attribute specifies whether accounting data collection and record generation is turned on at this DLCI. For accounting data collection and record generation to be turned on, the accountingOn bit and at least one of the accountCollection bits in the DataNetworkAddress component must be set to on. Enumeration: 'on': 1, 'off': 0.

This attribute indicates the emission priority of frames sent to the interface. A larger value denotes a higher priority.

This attribute indicates the priority at which data is transferred to the network. The transfer priority is a preference configured for an application according to its delay-sensitivity requirement. Frames with higher transfer priority are served by the network before the frames with lower priority. The transfer priority standard is defined to have 16 indices from 0 to 15. Each transfer priority n, where n specifies the transfer priority index, contains a default setting for routing class of service (multimedia, delay or throughput) and frame relay egress queue (depending on the number of supported egress queues on the remote end interface) specified by the routingClassOfService and emissionPriority attributes provisioned in the Mod Frs DprsNet Tpm/n component. The default mapping can be altered by a user if required.

This attribute indicates the priority at which data is transferred from the network. The transfer priority is a preference configured for an application according to its delay-sensitivity requirement. Frames with higher transfer priority are served by the network before the frames with lower priority. The transfer priority standard is defined to have 16 indices from 0 to 15. Each transfer priority n, where n specifies the transfer priority index, contains a default setting for routing class of service (multimedia, delay or throughput) and frame relay egress queue (depending on the number of supported egress queues on the remote end interface) specified by the routingClassOfService and emissionPriority attributes provisioned in the Mod Frs DprsNet Tpm/n component. The default mapping can be altered by a user if required.

This group contains the operational statistics for the Frame Relay Data Link Connection Identifier.

An entry in the frNniDlciStatsTable.

This attribute counts the frames sent out the interface. When the maximum count is reached the count wraps to zero.

This attribute counts the frames sent to the interface with the Forward Explicit Congestion Notification (FECN) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the frames sent to the interface with the Backward Explicit Congestion Notification (BECN) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the frames sent into the local network with the Backward Congestion Indication (BCI) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the frames sent to the interface with the Discard Eligibility (DE) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the number of frame discards at the Frame Relay service due to local congestion in the direction toward the interface. When this count reaches maximum, it wraps to zero.

This attribute counts the number of discarded frames, with the Discard Eligibility (DE) bit set, at the Frame Relay service, due to local congestion in the direction toward the interface. When this count reaches maximum, it wraps to zero.

This attribute counts the frames received from the interface. It includes the frames that are discarded due to error or excess. When the maximum count is reached the count wraps to zero.

This attribute counts the frames received from the interface with the Forward Explicit Congestion Notification (FECN) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the frames received from the interface with the Backward Explicit Congestion Notification (BECN) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the frames received from the network with the Forward Congestion Indication (FCI) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the frames received from the network with the Backward Congestion Indication (BCI) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the frames received from the interface with the Discard Eligibility (DE) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the frames received from the interface with the Discard Eligibility (DE) bit clear, but subsequently set by the network due to rate enforcement. When the count reaches maximum it wraps to zero.

This attribute counts the frames which were discarded due to rate enforcement. When the count reaches maximum it wraps to zero.

This attribute counts the number of frame discards at the Frame Relay Service, due to an inactive PVC status, in the direction toward the local network. When this count reaches maximum, it wraps to zero.

This attribute counts the number of frame discards at the Frame Relay service due to local congestion in the direction toward the network. When this count reaches maximum, it wraps to zero.

This attribute counts the number of discarded frames, with the Discard Eligibility (DE) bit set, at the Frame Relay service, due to local congestion, in the direction toward the local network. When this count reaches maximum, it wraps to zero.

This attribute counts the frames received with 0 octets in the information field. When the count reaches maximum it wraps to zero.

This attribute counts the frames received with number of octets in the information field greater than the subscribed maximum. When the count reaches maximum it wraps to zero. Frames whose lengths are greater than the hardware receive buffer are ignored by the hardware and are therefore not included in this count.

This attribute counts the number of frames with BECN set by the Frame Relay service. It is incremented whenever the Frame Relay service sets BECN on a frame upon detecting local congestion. This count is incremented regardless of whether the frame already bears a set BECN bit since its use is to determine the place of congestion. When the count reaches maximum, it wraps to zero.

This attribute counts the bytes sent out the interface. When the maximum count is reached the count wraps to zero.

This attribute counts the bytes sent to the interface with the Discard Eligibility (DE) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the number of byte discards at the Frame Relay service due to local congestion in the direction toward the link. When this count reaches maximum, it wraps to zero.

This attribute counts the number of discard eligible (DE=1) byte discards at the Frame Relay service due to local congestion in the direction toward the link. When the maximum count is reached the count wraps to zero.

This attribute counts the bytes received from the interface. Bytes that are discarded due to error or excess are not counted. When the maximum count is reached the count wraps to zero.

This attribute counts the bytes received from the interface with the Discard Eligibility (DE) bit set. When the count reaches maximum it wraps to zero.

This attribute counts the bytes received from the interface with the Discard Eligibility (DE) bit clear, but subsequently set by the network due to rate enforcement. When the count reaches maximum it wraps to zero.

This attribute counts the bytes which were discarded due to rate enforcement. When the count reaches maximum it wraps to zero.

This attribute counts the bytes which were discarded due to aBit turned off.

This attribute counts the number of byte discards at the Frame Relay service due to local congestion in the direction toward the network. When this count reaches maximum, it wraps to zero.

This attribute counts the number of discard eligible (DE=1) byte discards at the Frame Relay service due to local congestion in the direction toward the network. When the maximum count is reached the count wraps to zero.

This attribute counts the bytes received with 0 octets in the information field. When the count reaches maximum it wraps to zero.

This attribute counts the bytes received with number of octets in the information field greater than the subscribed maximum. When the count reaches maximum it wraps to zero. Bytes whose lengths are greater than the hardware receive buffer are ignored by the hardware and are therefore not included in this count.

This attribute counts the number of rate reductions due to rate adaptation. Rate adaptation causes the allowed rate to be reduced in steps. After each reduction, a period of time is awaited before further action is taken. At the end of this period, the allowed rate is further reduced if congestion is still prevalent. When this count reaches maximum, it wraps to zero.

This attribute provides a cumulative count of the amount of time that rate adaptation procedures have been in effect. When this count reaches maximum, it wraps to zero.

This attribute is obsolete. It is replaced by attribute transferPriorityToNetwork under group FrsNniDataLinkConnectionIdentifierServiceParametersOp. Enumeration: 'n12': 12, 'n13': 13, 'n10': 10, 'n11': 11, 'n14': 14, 'n15': 15, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute is obsolete. It is replaced by attribute transferPriorityFromNetwork under group FrsNniDataLinkConnectionIdentifierServiceParametersOp. Enumeration: 'n12': 12, 'n13': 13, 'n10': 10, 'n11': 11, 'n14': 14, 'n15': 15, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute provides the actual Committed Information Rate (CIR) enforced for this DLCI. This number is in units of 800 bits/ sec, since that is the internal resolution of Passport rate enforcement. If rateEnforcement is off, then this number does not have meaning. Normally, this attribute matches the provisioned CIR for the DLCI. But when Rate Adaptation is active, then this number will vary to represent the actual Allowed CIR at the moment that this attribute is collected.

This attribute provides the actual Excess Information Rate (EIR) enforced for this DLCI. This number is in units of 800 bits/sec, since that is the internal resolution of Passport rate enforcement. If rateEnforcement is off, then this number does not have meaning. Normally, this attribute matches the provisioned EIR for the DLCI. But when Rate Adaptation is active, then this number will vary to represent the actual Allowed EIR at the moment that this attribute is collected.

This group contains the operational statistics for the Frame Relay Data Link Connection Identifier interval data (accounting data).

An entry in the frNniDlciIntTable.

This attribute displays the start time of this interval period. If Vc spans 12 hour time or time of day change startTime reflects new time as recorded at 12 hour periods or time of day changes. A new interval period is started each time an accounting record is generated.

This attribute counts the total bytes received from the interface since the start of the interval period. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated.

This attribute counts the total bytes sent to the interface since the start of the interval period. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated.

This attribute counts the total bytes with the Discard Eligibility (DE) bit set sent to the subnet since the start of the interval period. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated.

This attribute counts the total bytes with the Discard Eligibility (DE) bit set sent to the interface since the start of the interval period. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated.

This attribute counts the total bytes in invalid frames received from the interface and discarded at the DLCI since the start of the interval period. This count is a sum of octets in frames discarded due to the number of octets in the information field greater than the subscribed maximum or equal to 0, due to aBit turned off, or due to rate enforcement. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated.

If the value of the unitsCounted attribute in moduleData component is segments, this attribute counts the total number of segments in frames received from the interface since the start of the interval period. If the value of the unitsCounted attribute in moduleData component is frames, this attribute counts the total number of frames received from the interface since the start of the interval period. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated

If the value of the unitsCounted attribute in moduleData component is segments, this attribute counts the total number of segments in frames sent to the interface since the start of the interval period. If the value of the unitsCounted attribute in moduleData component is frames, this attribute counts the total number of frames sent to the interface since the start of the interval period. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated

If the value of the unitsCounted attribute in moduleData component is segments, this attribute counts the number of segments in frames with the Discard Eligibility (DE) bit set sent to the subnet since the start of the interval period. If the value of the unitsCounted attribute in moduleData component is frames, this attribute counts the number of frames with the Discard Eligibility (DE) bit set sent to the subnet since the start of the interval period. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated

If the value of the unitsCounted attribute in moduleData component is segments, this attribute counts the number of segments in frames with the Discard Eligibility (DE) bit set sent to the interface since the start of the interval period. If the value of the unitsCounted attribute in moduleData component is frames, this attribute counts the number of frames with the Discard Eligibility (DE) bit set sent to the interface since the start of the interval period. The start of the interval period is captured in the startTime attribute. The count is reset to zero when an accounting record is generated

If the value of the unitsCounted attribute in moduleData component is segments, this attribute counts the number of segments in invalid frames received from the interface and discarded at the DLCI. If the value of the unitsCounted attribute in moduleData component is frames, this attribute counts the number of invalid frames received from the interface and discarded at the DLCI. Segments of frames are counted since the start of the interval period. The count is reset to zero when an accounting record is generated. The count is a sum of segments in frames or frames discarded due to the number of octets in the information field greater than the subscribed maximum or equal to 0, due to aBit turned off, or due to rate enforcement.

This attribute has moved to the statistics subgroup. See cirPresent..

This attribute has moved to the statistics subgroup. See eirPresent.

This attribute is obsolete. It is the same as the provisioned rateEnforcement attributed.. Enumeration: 'on': 1, 'off': 0.

This attribute is obsolete. See the provisioning attribute rateAdaptation for the data that it intended to provide. Enumeration: 'on': 1, 'off': 0.

This attribute specifies whether rate adaptation has occurred on this user Data Link Connection on this Frame Relay interface.The count is reset to no when an accounting record is generated. Enumeration: 'yes': 1, 'no': 0.

This attribute displays the call reference number which is a unique number generated by the switch.The same Call Reference Number is stored in the interval data (accounting record) at both ends of the call. It can be used as one of the attributes in matching duplicate records generated at each end of the call.

This attribute displays the elapsed time representing the period of this interval data. It is elapsed time in 0.1 second increments since the call started.

This entry controls the addition and deletion of frNniVFramer components.

A single entry in the table represents a single frNniVFramer component.

This variable is used as the basis for SNMP naming of frNniVFramer components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniVFramer tables.

This variable represents the index for the frNniVFramer tables.

This group contains provisionable attributes for the VirtualFramer component.

An entry in the frNniVFramerProvTable.

This attribute specifies the other VirtualFramer to which the service is linked, for example, FrUni/n VirtualFramer, FrDte/n VirtualFramer.

This attribute specifies the logical processor on which the service component will reside.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the frNniVFramerStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains the operational statistics data for a VirtualFramer component.

An entry in the frNniVFramerStatsTable.

This attribute counts the frames transmitted to the otherVirtualFramer.

This attribute counts the frames received from the otherVirtualFramer.

This attribute counts the octets received from the otherVirtualFramer.

This entry controls the addition and deletion of frNniLts components.

A single entry in the table represents a single frNniLts component.

This variable is used as the basis for SNMP naming of frNniLts components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniLts tables.

This variable represents the index for the frNniLts tables.

This entry controls the addition and deletion of frNniLtsPat components.

A single entry in the table represents a single frNniLtsPat component.

This variable is used as the basis for SNMP naming of frNniLtsPat components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the frNniLtsPat tables.

This variable represents the index for the frNniLtsPat tables.

This attribute group contains the specifications of the pattern.

An entry in the frNniLtsPatDefaultsTable.

This attribute specifies for which dlci (on the local end) the frames are destined.

This attribute specifies the number of frames in this pattern. This is the number of frames of this type which will be generated in one timeInterval.

This attribute specifies the payload size of each frame in bytes. This is in excess to the header.

This attribute specifies whether the following bits are on/off in the header of each frame. The following bits can be set: BeCn, C/R, De, FeCn Description of bits: becn(0) fecn(1) cr(2) de(3)

This attribute specifies the size of the frame relay header in bytes. Passport currently only supports a 2-byte header.

This attribute specifies how the address field extension bits are set in the frame header. Consider the value to be a four bit binary number. For example, 4 = 0100. Only the first headerLength bits are used. For instance, suppose headerLength is 3, then the appropriate EABits is 2, or 0010. This attribute can be used to create a header of length greater than two bytes or to specify incorrect EABits in the header.

This attribute specifies the payload of each frame. The value specified is in hexadecimal, where every two digits represent a byte. A maximum of 24 digits (12 bytes) may be set, after which the pattern will repeat in the payload (depending on repeatPattern attribute). NOTE: If a RFC 1490 header is specified, via the 1490Header attribute, the specified pattern will begin following the header (i.e. at the 9th byte in the payload).

This attribute specifies the appropriate RFC 1490 encapsulated header of the frame. A value of 0 indicates no 1490 header. NOTE: This header resides in the first 8 bytes of the payload. If the specified value is non-zero, then the payload pattern provisioned will begin at the 9th byte. Enumeration: 'n12': 12, 'n13': 13, 'n10': 10, 'n11': 11, 'n16': 16, 'n17': 17, 'n14': 14, 'n15': 15, 'none': 18, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies whether the frames from this pattern are to have a bad LRC prior to being sent to the framer. The LRC is checked while the frame is being put onto the link and the failure should cause an abort frame to be sent. Enumeration: 'yes': 1, 'no': 0.

This attribute group contains the specifications of the pattern.

An entry in the frNniLtsPatSetupTable.

This attribute specifies for which dlci (on the local end) the frames are destined.

This attribute specifies the number of frames in this pattern. This is the number of frames of this type which will be generated in one timeInterval.

This attribute specifies the payload size of each frame in bytes. This is in excess to the header.

This attribute specifies whether the following bits are on/off in the header of each frame. The following bits can be set: BeCn, C/R, De, FeCn Description of bits: becn(0) fecn(1) cr(2) de(3)

This attribute specifies the size of the frame relay header in bytes. Passport currently only supports a 2-byte header. Valid values are 0, 2, 3, 4. 0 indicates to use no header. That is, the frame will start with either the payload or rfc1490 header.

This attribute specifies how the address field extension bits are set in the frame header. Consider the value to be a four bit binary number. For example, 4 = 0100. Only the first headerLength bits are used. For instance, suppose headerLength is 3, then the appropriate eaBits is 2, or 0010. This attribute can be used to create a header of length greater than two bytes or to specify incorrect eaBits in the header.

This attribute specifies the payload of each frame. The value specified is in hexadecimal, where every two digits represent a byte. A maximum of 24 digits (12 bytes) may be set, after which the pattern will repeat in the payload (depending on repeatPattern attribute). NOTE: If a RFC 1490 header is specified, via the 1490Header attribute, the specified pattern will begin following the header (i.e. at the 9th byte in the payload).

This attribute specifies the appropriate RFC 1490 encapsulated header of the frame. A value of 0 indicates no 1490 header. NOTE: This header resides in the first 8 bytes of the payload. If the specified value is non-zero, then the payload pattern provisioned will begin at the 9th byte. Enumeration: 'n12': 12, 'n13': 13, 'n10': 10, 'n11': 11, 'n16': 16, 'n17': 17, 'n14': 14, 'n15': 15, 'none': 18, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies whether the frames from this pattern are to have a bad LRC prior to being sent to the framer. The LRC is checked while the frame is being put onto the link and the failure should cause an abort frame to be sent. Enumeration: 'yes': 1, 'no': 0.

This group contains the operational attributes which allow changing the pattern outside of provisioning mode.

An entry in the frNniLtsPatOpDataTable.

This attribute displays the first 20 to 24 bytes of the frame payload, depending on the frame relay header size selected. This attribute represents the frame if it were at least 20 to 24 bytes in size. That is, the actual frame may be smaller.

This attribute displays how many times a zero bit will be inserted after 5 consecutive 1 bits when a frame from this pattern is sent out.

This group contains the attributes containing the operational statistics of the pattern.

An entry in the frNniLtsPatOpStateTable.

This attribute indicates the load due to this particular pattern. The loads associated with all of the provisioned patterns are summed to arrive at the FrLts load.

This attributes specifies the administrative state of the pattern. A disabled pattern will not be generated, although it can still be triggered. Enumeration: 'disabled': 1, 'enabled': 0.

This attribute group contains the parameters used to configure the behavior of the Frame Relay Load Test System.

An entry in the frNniLtsSetupTable.

This attribute specifies the duration of the test in milliseconds. The test will run until the duration expires or the STOP command is issued. A value of 0 is used to indicate infinity.

This attribute specifies which algorithm is used to generate the frames. ContinuousBurst This mode of traffic generation creates traffic at the maximum rate possible until all of the frames have been sent. The generator then waits until the end of the timeInterval to begin again. IntervalBurst This algorithm attempts to generate 10 ms bursts of burstSize frames. It will generate as many of the burstSize frames as it can per sub-interval. DelayedBurst This algorithm generates bursts of burstSize frames separated by 10 ms delays. FixedBurst This aglorithm is similar to IntervalBurst, except a fixed burst size of 12 frames is used. delayMeasurement This algorithm is used to measure delay. The specified number of frames in the indicated pattern are generated, one at a time, with a maximum wait of maxDelay before sending the next frame. This algorithm is not implemented yet. Enumeration: 'continousBurst': 0, 'intervalBurst': 1, 'delayBurst': 2, 'fixedBurst': 3.

This attribute specifies the number of frames per burst under the delayedBurst and intervalBurst algorithms.

This attribute specifies the time interval to the specified number of seconds. Granuality is in centiseconds. Maximum is 1 minute.

This group contains the operation statistics of the load generator.

An entry in the frNniLtsStateTable.

This attribute indicates whether the Lts is generating traffic. Enumeration: 'running': 1, 'stopped': 0.

This attribute indicates whether the time required to generate all of the enabled patterns is more than timeInterval by a true value. Otherwise, this flag is set to false. Default is True. Enumeration: 'true': 1, 'false': 0.

This attribute indicates the actual time it took to generate all of the enabled patterns in the last cycle. If cycleIncomplete is true, this value should be zero.

This attribute indicates the load being generated. This value represents that calculated using the set number of ticks. The actual burstTimeInterval may differ. One entire cycle of the patterns is completed in activeInterval and thus most of the load may be concentrated early in the set interval.

This attribute indicates how many milliseconds have elapsed since the start of this test.

This group contains the frame counting attributes for the LTS component.

An entry in the frNniLtsResultsTable.

This attribute specifies the number of frames send to the network since the last time these statistics were cleared. This is similar to the framesToIf attribute of the FRAMER component.

This attribute indicates the number of bytes sent.

This attribute indicates the bit rate being sent to the link. It should only differ from the load if the burstTimeInterval would be >= the timeInterval or burstSize frames cannot be generated in 10ms (intervalBurst algorithm).

This attribute indicates the frame rate being sent to the link. It is calculated using the number of frames sent to the link in one cycle of the patterns.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the frNniCidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241- 7001-150, Passport Operations and Maintenance Guide.

An entry in the frNniStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

FrNni/n Statistics This group contains the statistics about the operational behavior of the service at the interface level.

An entry in the frNniStatsTable.

This attribute identifies the most recent DLCI which user frames were received on for which a DLCI has not been provisioned on the port.

This attribute contains a count of the number of frames received from the interface with an unknown DLCI (DLCI which is not provisioned). When the maximum is reached the count wraps to zero.

This attribute counts the number of frames received from the interface with an invalid header format. When the maximum is reached the count wraps to zero.

This group contains the provisionable attributes for the ifEntry.

An entry in the frNniIfEntryTable.

The desired state of the interface. The up state indicates the interface is operational. The down state indicates the interface is not operational. The testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This is the index for the IfEntry. Its value is automatically initialized during the provisioning process.

This group includes the Operational Status attribute. This attribute defines the current operational state of this component.

An entry in the frNniOperStatusTable.

The current state of the interface. The up state indicates the interface is operational and capable of forwarding packets. The down state indicates the interface is not operational, thus unable to forward packets. testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This group contains the provisionable attribute to specifie the number of Frame Relay egress emission priority queues to be used on that Frame Relay Interface

An entry in the frNniEmissionPriorityQsTable.

This attribute specifies the number of egress emission priority queues that will be used for that Frame Relay interface. The possible values of this attribute are 2 or 4: For V.35, V.11, HSSI, E1, DS1, E3, DS3 or 8pDS1 the possible values are: 2 (in which case they are hardware queues), or 4 (in which case they are software queues). For DS1C, E1C or DS3C the possible values are 2, 4 (in all cases they are software queues).

This attribute counts the total number of frames transmitted to the interface per egress emission priority queue since the component has been activated. There is potientially a maximum of 4 emission priority queues. The number of available egress queues varies according to the value of the provisionable attribute numberOfEmissionQs. Egress queue 0 has the lowest priority, while egress queue 3 has the highest priority. The queue values are only indicated when the numberOfEmissionQs is set to 4 queues.

An entry in the frNniFrmToIfByQueueTable.

This variable represents the index for the frNniFrmToIfByQueueTable.

This variable represents an individual value for the frNniFrmToIfByQueueTable.

This attribute counts the total number of octets transmitted from the service to the interface per emission priority queue since the component has been activated. There is potientially a maximum of 4 emission priority queues. The number of available egress queues varies according to the value of the provisionable attribute numberOfEmissionQs. Egress queue 0 has the lowest priority, while egress queue 3 has the highest priority.

An entry in the frNniOctetToIfByQueueTable.

This variable represents the index for the frNniOctetToIfByQueueTable.

This variable represents an individual value for the frNniOctetToIfByQueueTable.