DFRAP-MIB: View SNMP OID List / Download MIB

A textual description of the system model identifier. for example: SYNC-DFRAP

Displays the Software Revision installed in this node.

Displays the Hardware Revision of the node.

The number of T1 ports that are installed.

The number of DTE ports that are installed.

The number of Async Maintenance/Console ports that are installed.

The user supplied name of the node. This object does not affect operation, but may be useful for network management.

The serial number of the board.

Command to reset the node. NODE WILL BE OFF-LINE AND USER DATA WILL BE INTERRUPTED FOR APPROXIMATELY 15 SECONDS. Full network recovery may take longer. Enumeration: 'reset-node': 321.

The amount of memory (RAM) installed (in megabytes).

The number of DDS ports that are installed.

The user supplied location of the node. This object does not affect operation, but may be useful for network management.

The user supplied contact information for the node. This object does not affect operation, but may be useful for network management.

Configurable Command Line Interface (CLI) prompt. CLI is the User Interface protocol used for directly attached VT100 terminal access as well as Remote access via Telnet.

Displays the bootblock Software Revision installed in this node.

Shows whether the unit has SLIP (Serial Line IP) capability. SLIP is a method for out-of-band management that connects through the asynchronous terminal port.

Shows whether the unit has PPP (Point to Point protocol) capability. PPP is a method for out-of-band management that connects through the asynchronous terminal port.

Shows whether the unit has Remote Dial Out capability.

Shows whether the unit has direct Ethernet capability.

Shows whether the unit has direct Token Ring capability.

Shows whether the unit has External Timing capability. This is the ability to derive WAN timing from the DTE port.

Shows whether the unit has BRI (ISDN Basic Rate) capability.

Shows whether the unit has a Selectable DTE interface. This being the ability to select amongst various electrical interface formats (V.35, RS449, RS232, etc.) via software.

Shows whether the unit supports MLs (out-of-band management links). N/A to frame relay networks.

Shows how many DLCIs can be monitored for frame-based statistics. The unit will pass an unlimited number of DLCIs but will only collect statistics on this number (first come first served).

Shows how many DLCIs can be specified in the Long Term Statistics Filter.

Shows how many protocols can be specified in the Long Term Statistics Filter.

Shows how many protocols can be defined by the user. The user configures TCP/UDP ports which can be monitored as protocols. They are available for short term or long term statistics monitoring.

Shows how many SNMP managers can be programmed in the table dfrapCfgSnmpMngrTable. These managers are sent TRAPs.

Shows how many DLCI names can be defined by the user in the table dfrapCfgFrPerfDlciNamesTable.

The IP address for this node.

This parameter is not used internally by the unit. It is intended to identify either the device directly connected to the SLIP port or, in Frame Relay applications, the address of the primary network management station.

The IP Subnet Mask (eg 255.255.255.0). This parameter should be consisent with the IP subnet address setting of the external internetworking equipment (router/frad).

The Maximum Transmission Unit is the size of the largest IP packet supported (including header). This value should be set to the lowest value supported by any equipment in the transmission path. For Frame Relay management the typical value is 1500. For SLIP management the typical value is 1006.

This is the method by which IP traffic is being carried. Either via the SLIP port or a DLCI. This reflects how your Management scheme is configured (read only). Enumeration: 'none': 1, 'in-band-dlci': 3, 'slip-port': 2.

Enables/Disables the telnet feature. (1) enable-telnet (2) disable-telnet Enumeration: 'enable-telnet': 1, 'disable-telnet': 2.

If Telnet Auto logout is enabled the unit will automatically disconnect from a Telnet session after a period of inactivity (absence of key strokes from remote terminal). (2) disables this feature (1) auto logout after 15 minutes inactivity (3) auto logout after 3 minutes inactivity (5) auto logout after 5 minutes inactivity (10) auto logout after 10 minutes inactivity (30) auto logout after 30 minutes inactivity (60) auto logout after 60 minutes inactivity Enumeration: 'autologout-at-30-minutes': 30, 'disable-autologout': 2, 'autologout-at-10-minutes': 10, 'autologout-at-60-minutes': 60, 'autologout-at-5-minutes': 5, 'autologout-at-15-minutes': 1, 'autologout-at-3-minutes': 3.

Setting this object to a value that matches the TFTP Password will command the unit to attempt a TFTP file transfer. A TFTP profile including host ip address, dlci value, interface, and file name must first be configured.

The IP address of the TFTP host with which the unit will attempt to establish a TFTP session when initiated.

The name of the file located on the TFTP host that will be transferred to the unit. Typically this is a product-specific software image that will be programmed into unit FLASH. The unit provides several levels of checking to verify the validity and integrity of this file. Note - depending upon the host, this file name may be case sensitive.

The physical interface out which the TFTP host is located. This parameter is only required for Piggyback and Bi-directional in-band frame relay managed applications. With Local and Remote in-band and SLIP-based applications the interface is known and Sets to this will be ignored. Enumeration: 'dds-interface': 2, 'dte-interface': 1, 'slip-interface': 3.

The local DLCI value on which the TFTP host can be reached. This DLCI should be active prior to initiating the TFTP session. This parameter is only required for Piggyback in-band frame relay managed applications. With Private management (Local, Remote or Bi-directional in-band applications) the DLCI is known and will be reported here (Sets will be ignored). In SLIP-based applications the DLCI value is not applicable and a value of -1 is reported (Sets will be ignored).

The status of current or most recent TFTP operation. (1) TFTP inactive, sets to this value will abort the session (2) TFTP requested (3) TFTP transferring (4) TFTP programming FLASH - unit will reset (5) TFTP fail: session aborted by user or error condition (6) TFTP fail: host no reply - verify TFTP profile and host (7) TFTP fail: file not found - verify file name and location (8) TFTP fail: invalid file - file rejected by unit as inappropriate (9) TFTP fail: corrupt file - session terminated due to checksum error (10) TFTP transfer successful and file has been verified Enumeration: 'invalid-file': 8, 'requested': 2, 'host-no-reply': 6, 'transferring': 3, 'programming': 4, 'corrupt-file': 9, 'successful': 10, 'inactive': 1, 'file-not-found': 7, 'transfer-aborted': 5.

The number of Bytes from the ROM image that have been TFTP'd to the unit

Controls whether or not the Frame Relay DLCI status change traps are issued. These traps are dfrapDLCIActiveTrap and dfrapDLCIInactiveTrap. When dfrapCfgSnmpFrTrap is enabled (1), a trap will be sent each time an individual DLCI changes status between active and inactive. When dfrapCfgSnmpFrTrap is disabled (2), the traps are not sent. Enumeration: 'disabled': 2, 'enabled': 1.

The table of SNMP manager profiles to which traps are sent. In all managed modes an SNMP trap mangager's ip address is required as a minimum. Additionally for Piggyback managed units the DLCI and interface must also be configured appropriately. For Local, Remote and SLIP-based management, the DLCI and interface are implied and need not be configured as part of this profile.

The SNMP trap manager profiles to which the unit sends TRAPs.

The index to the list of SNMP managers receiving TRAPs.

The IP address of a SNMP manager to receive this node's TRAPs. Setting this value to 0.0.0.0 will disable the issuance of traps to the indexed manager.

The interface out which the indexed trap manager can be reached. This entry is required in Piggyback and Bi-directional in-band managed applications. In Local, Remote and SLIP-based applications, the interface is known and this parameter is ignored. When the node is configured for SLIP, a GET on this MIB object will return slip-interface(3) and a SET of this MIB object to slip-interface(3) is allowed but unnecessary. When the node is not configured for SLIP, this MIB object can be SET to dte-interface(1) or dds-interface(2); slip-interface(3) would be rejected. Enumeration: 'dds-interface': 2, 'dte-interface': 1, 'slip-interface': 3.

The DLCI out which the indexed trap manager can be reached. This entry is required in Piggyback in-band managed applications. In Private in-band applications the DLCI is known and Sets to this parameter will be ignored. In SLIP mode the DLCI is not applicable, Sets will be ignored and a -1 will be returned as the DLCI value.

Controls whether Traps are Sent or Muted. If traps are Muted then a single trap (#75) will be periodically issued by the unit at the programmed frequency. If Muting is Disabled then the full set of Trap events are reported accordingly. (0) Disable Trap Muting (30-10080) Trap Muting frequency in minutes.

Enables or disables the sending of per-DLCI utilization traps. (1) enable utilization traps (2) disable utilization traps Enumeration: 'enable': 1, 'disable': 2.

Deletes the number of entries in the dfrapCfgSnmpMgrTable indicated by the value. If the value is a positive number the entries will be deleted starting from the first entry. If the value is negative the entries will be deleted starting from the last entry.

The protocol running on the Maintenance/Comm port (console). Setting this to SLIP mode will automatically disable in-band management if it's enabled. (1) VT100 for directly attached async terminal (2) SLIP - Serial Line IP out-of-band management Enumeration: 'slip': 2, 'vt100': 1.

Asynchronous baud rate for the Maintenance/Comm port (Console). This must be configured to match either the VT100 compatible terminal or the SLIP Terminal Server depending upon the Comm port mode. (2) baud-2400 (4) baud-9600 (5) baud-19200 (6) baud-38400 Enumeration: 'baud-9600': 4, 'baud-19200': 5, 'baud-2400': 2, 'baud-38400': 6.

Asynchronous data format for the Maintenance/Comm port (Console). This must be configured to match either the VT100 compatible terminal or the SLIP Terminal Server depending upon the Comm port mode. (1) 7 databits per character (2) 8 databits per character Enumeration: 'databits-7': 1, 'databits-8': 2.

Asynchronous intercharacter protocol for the Maintenance/Comm port (Console). This must be configured to match either the VT100 compatible terminal or the SLIP Terminal Server depending upon the Comm port mode. (1) 1 stopbit (2) 1.5 stopbits (3) 3 stopbits Enumeration: 'stopbits-1-5': 2, 'stopbits-1': 1, 'stopbits-2': 3.

Asynchronous parity checking protocol for the Maintenance/Comm port (Console). This must be configured to match either the VT100 compatible terminal or the SLIP Terminal Server depending upon the Comm port mode. (1) no parity (2) odd-parity (3) even-parity Enumeration: 'even-parity': 3, 'no-parity': 1, 'odd-parity': 2.

Flow Control for the Maintenance/Comm port (Console). (1) no flow control supported. Enumeration: 'no-flow-control': 1.

In-band Frame Relay management mode. A variety of options exist which are differentiated by how PVCs can be provisioned to manage the unit and the resulting impact to the logical processing of Link Management Protocol messages (LMI spoofing and sourcing). The unit is designed to support these management modes even in non-provisioned or failed frame relay networks. This setting also has implications upon how networking protocols such as ARP and InARP are handled by the unit. (1) inactive: in-band management is not enabled (2) local DLCI mode: in-band managed using a private dedicated DLCI accessible via the DTE port only. A DLCI value is configured which, through LMI spoofing, will only be visible to the DTE equipment and need not be provisioned on the WAN. All traffic on this DLCI will be terminated by the unit. (3) remote DLCI mode: in-band managed using a private dedicated DLCI accessible via the WAN port only. A DLCI value is configured which, through LMI spoofing, will only be visible from the WAN side and will not be seen by any DTE equipment. All traffic on this DLCI will be terminated by the unit. (4) bidirectional mode: in-band managed using a private dedicated DLCI accessible through either port. A DLCI value is configured which is expected to be fully provisioned in the frame relay network but dedicated to the management function of this particular unit. All traffic on this DLCI will be terminated by the unit. (5) piggyback mode: in-band managed using any DLCI on any interface. A DLCI value is defined that becomes the default DLCI that will be maintained by the unit during network or LMI failure conditions. The unit will terminate and respond accordingly to management and networking data while transparently passing on user data. (6) fixed DCE mode: special mode of operation to support frame relay applications that do not include a switch (frame relay DCE). The unit will independently respond to LMI requests on each interface and will provision the configured DLCI to each Frame Relay DTE device. Except for this, the unit behaves like piggyback. Enumeration: 'remote': 3, 'fixed-dce': 6, 'piggyback': 5, 'inactive': 1, 'bidirectional': 4, 'local': 2.

If in-band management is being used this DLCI value should be defined. In all modes of in-band management with the LMI Sourcing feature enabled the unit may provision this DLCI during LMI failure to facilitate management access. In Private modes (Local, Remote, and Bidirectional) this is the dedicated DLCI for management data and address resolution protocols - all other traffic on this DLCI will be discarded. In Piggyback mode this DLCI is treated like all others except during LMI failure sourcing when it may be provisioned by the unit. In Piggyback mode if InARP is enabled on a single DLCI then this value defines that DLCI.

This is the protocol used for enacapsulating and formatting ip data for Frame Relay transmission. This setting is specific to management data to and from the unit. (1)RFC1490 - per IETF standard with Network Level Protocol ID (NLPID) set for IP encapsulation. (2)RFC1490 SNAP/IP - per IETF standard with NLPID set for Sub-Network Access Protocol (SNAP). (3)auto - adjusts to either of these encapsulation techniques as required. (4)Cisco - proprietary encapsulation (4-byte header). Enumeration: 'rfc1490': 1, 'auto': 3, 'cisco': 4, 'rfc1490snap': 2.

Provides user control over the state of the Frame Relay Discard Eligibility bit of all management frames generated by the unit. Frames marked DE=1 are more likely to be dropped in a congested Frame Relay network than those that are DE=0. Heavily congested circumstances can cause both to be dropped. Additionally, frames marked DE=0 may get re-marked to DE=1 by intervening equipment. (1) DE bit cleared to 0: frame is not discard eligible (2) DE bit set to 1: frame is discard eligible Enumeration: 'no-DE-bit-0': 1, 'yes-DE-bit-1': 2.

Timing source for transmission of data towards the WAN and for the generation of DTE clocking. There should be only one source per end-to-end WAN link. Unit is typically network timed in a point-to-network application. (1) internal: derive timing from a high-stability on-board crystal oscillator. (2) network: or Loop timing, derive timing from the signal received at the WAN interface (3) dte: derive timing from the clock presented by the DTE equipment on the Terminal Timing(TT)/Transmit Clock External (TCE) leads. This setting expects the DTE timing mode to be Loop 1 and the DTE device to be generating a clock at the DTE data rate. Enumeration: 'internal': 1, 'network': 2, 'dte': 3.

Alphanumeric circuit identifier may be provided by the service provider for reference or assigned arbitrarily per user requirements.

This unit provides many features specifically adapted to Frame Relay transmission links; this includes diagnostic utilities, statistical analysis, protocol trends, quality of service reporting, and in-band SNMP management. If the unit will be operating in a Frame Relay network the Application Type must be set to Frame Relay to enable these features. To operate in a non-Frame Relay network or to bypass this feature set the unit may be placed in Dedicated mode and will emulate a more familiar DSU/CSU. Note - changing this value will automatically change the Application Format setting and vice versa. (1) dedicated: protocol-independent transparent DSU/CSU (2) Frame Relay: Frame and protocol aware DSU/CSU Enumeration: 'frame-relay': 2, 'dedicated': 1.

Refer to Application Type. Frame Relay is based upon HDLC framing. To operate in a Frame Relay application the Format must be set for HDLC. To operate in a protocol-independent application the Format must be set for Constant Bit Operation (CBO). Note - changing this value will automatically change the Application Type setting and vice versa (1) CBO: protocol-independent transparent DSU/CSU (2) HDLC: Frame and protocol aware DSU/CSU Enumeration: 'cbo': 1, 'hdlc': 2.

The length of time a service-impacting loopback or diagnostic utility may run before automatically returning to normal operation. This setting will override any alternatively timed tests (such as VBERT). (0) Loopbak Timeout Disabled (1-1440) Loopback Timeout

This value controls the throttling mechanism used to determine the optimum level of statistical processing versus managability of the unit. The lower the value (1 - 128), the unit becomes more responsive to management commands during very heavy utilization at the possible expense of statistical accuracy. The larger the value (129 - 512), the more accurate the DFRAP performs statistical analysis of the frames but management may seem slow or unresponsive during periods of very heavy link utilization. NOTE: A value of 0 disables statistical processing entirely.

Provisioned DDS WAN data rate. This unit conforms to either 56K DDS service or 64K (72K with framing) DDS service. (1) 56Kbps DDS (2) 64Kbs DDS (72K loop rate) Enumeration: 'sixty-four': 2, 'fifty-six': 1.

The unit may be configured to issue traps in response to Bipolar Violations (BPVs) received from the WAN. If enabled the unit will issue a trap when more than 5 BPVs are detected in a one-second interval and a follow-up trap when the BPV threshold is no longer exceeded. BPVs that are part of network control codes do not contribute to this feature. (1) BPV Trap Threshold is 10e-4 (2) Disable BPV Traps Enumeration: 'thresholding-at-10E-4': 1, 'disable-thresholding': 2.

The electrical interface for the DTE port (3) V.35 interface (4) RS-449 interface Enumeration: 'intf-rs449': 4, 'intf-v35': 3.

This selection controls how the unit internally latches the transmit data from the DTE. Normal will sample data with the rising edge of the selected TX Clock, Invert will sample data with the falling edge of the selected TX Clock. The TX Clock is selected using CfgDteTiming. This clock invertion is most useful when loop-2 timing is used - particularly at higher rates and with long cable runs. Only in rare circumstances will clock-invert be used with loop-1 timing. If the DTE Interface TX statistics are indicating excessive crc errors or aborts then changing this setting may have some benefit. (1) normal (2) invert Enumeration: 'clock-invert': 2, 'clock-normal': 1.

Serial DTE Transmit Timing mode. Loop-1 (1) uses the clock returned from the DTE (TT/TCE) to sample tx data, Loop-2 (2) uses the clock (ST/TC) generated by the node to sample tx data. Loop-1 is the preferred mode. Loop-2 timing could experience data errors at high rates or due to long DTE cable runs - may need to Invert the clock (see CfgDteClockMode). (1) Loop 1: external clock returned from DTE with data (2) Loop 2: internal clock used to sample incoming data Enumeration: 'loop-2': 2, 'loop-1': 1.

Controls the reporting of the status of the DTE's Request to Send (RTS) control signal, specifically the generation of traps in response to control signal state changes. If Internally Held Active, the unit will ignore the actual status and always report this signal Active. If External, the unit will reflect the status as driven by the DTE; as such, Traps will be generated due to change of state (these may be useful fora network manager's assessment of interface status. (1) Internally Held Active (2) Externally Presented from DTE Enumeration: 'internal-held-active': 1, 'external-from-dte': 2.

Controls the reporting of the status of the DTE's Data Terminal Ready (DTR) control signal, specifically the generation of traps in response to control signal state changes. If Internally Held Active, the unit will ignore the actual status and always report this signal Active. If External, the unit will reflect the status as driven by the DTE; as such, Traps will be generated due to change of state (these may be useful fora network manager's assessment of interface status. (1) Internally Held Active (2) Externally Presented from DTE Enumeration: 'internal-held-active': 1, 'external-from-dte': 2.

Specifies the behavior of the Data Carrier Detect (DCD) control signal generated by the unit towards the DTE. (1) inactive always: signal is permanently INACTIVE. (2) active always: signal is permanently ACTIVE. (3) reflect WAN carrier: signal echoes the received signal status from the WAN. (4) inactive with test mode: signal is ACTIVE during normal data transfer and INACTIVE during diagnostic conditions that interfere with data transfer from the DTE to the WAN. (5) follow RTS: signal echoes the status of RTS as processed from the DTE. (6) reflect carrier and RTS: signal is a logical AND between RTS processed from the DTE and the received signal status from the WAN. No signal received from the WAN or RTS INACTIVE will cause this control signal to be asserted INACTIVE. (7) reflect sync and RTS: signal is a logical AND between RTS processed from the DTE and the frame synchronization with the WAN. Frame Synchronization is only applicable with 64K DDS service, otherwise this is equivalent to (6). (8) reflect LMI and carrier and RTS: signal is a logical AND between RTS processed from the DTE and the carrier signal status from the WAN and LMI. If the unit is in an LMI passthrough state then LMI is considered Active. LMI Inactivity timer must be non-zero for LMI to be declared Inactive. In non-Frame Relay applications (type = dedicated) LMI will be presumed ACTIVE so this will setting is equivalent to (6). Note that there is a separate parameter for how the unit processes RTS that is related to this function if options (4), (5), (6), or (7) is selected, see CfgDteRts. Enumeration: 'follow-sync-rts': 7, 'signal-off': 1, 'follow-test': 4, 'follow-carrier': 3, 'follow-lmi-carr-rts': 8, 'follow-rts': 5, 'follow-carrier-rts': 6, 'signal-on': 2.

Specifies the behavior of the Data Set Ready (DSR) control signal generated by the unit towards the DTE. (1) inactive always: signal is permanently INACTIVE. (2) active always: signal is permanently ACTIVE. (3) reflect WAN carrier: signal echoes the received signal status from the WAN. (4) inactive with test mode: signal is ACTIVE during normal data transfer and INACTIVE during diagnostic conditions that interfere with data transfer from the DTE to the WAN. (5) follow RTS: signal echoes the status of RTS as processed from the DTE. (6) reflect carrier and RTS: signal is a logical AND between RTS processed from the DTE and the received signal status from the WAN. No signal received from the WAN or RTS INACTIVE will cause this control signal to be asserted INACTIVE. (7) reflect sync and RTS: signal is a logical AND between RTS processed from the DTE and the frame synchronization with the WAN. Frame Synchronization is only applicable with 64K DDS service, otherwise this is equivalent to (6). (8) reflect LMI and carrier and RTS: signal is a logical AND between RTS processed from the DTE and the carrier signal status from the WAN and LMI. If the unit is in an LMI passthrough state then LMI is considered Active. LMI Inactivity timer must be non-zero for LMI to be declared Inactive. In non-Frame Relay applications (type = dedicated) LMI will be presumed ACTIVE so this will setting is equivalent to (6). Note that there is a separate parameter for how the unit processes RTS that is related to this function if options (4), (5), (6), or (7) is selected, see CfgDteRts. Enumeration: 'follow-sync-rts': 7, 'signal-off': 1, 'follow-test': 4, 'follow-carrier': 3, 'follow-lmi-carr-rts': 8, 'follow-rts': 5, 'follow-carrier-rts': 6, 'signal-on': 2.

Specifies the behavior of the Clear to Send (CTS) control signal generated by the unit towards the DTE. (1) inactive always: signal is permanently INACTIVE. (2) active always: signal is permanently ACTIVE. (3) reflect WAN carrier: signal echoes the received signal status from the WAN. (4) inactive with test mode: signal is ACTIVE during normal data transfer and INACTIVE during diagnostic conditions that interfere with data transfer from the DTE to the WAN. (5) follow RTS: signal echoes the status of RTS as processed from the DTE. (6) reflect carrier and RTS: signal is a logical AND between RTS processed from the DTE and the received signal status from the WAN. No signal received from the WAN or RTS INACTIVE will cause this control signal to be asserted INACTIVE. (7) reflect sync and RTS: signal is a logical AND between RTS processed from the DTE and the frame synchronization with the WAN. Frame Synchronization is only applicable with 64K DDS service, otherwise this is equivalent to (6). (8) reflect LMI and carrier and RTS: signal is a logical AND between RTS processed from the DTE and the carrier signal status from the WAN and LMI. If the unit is in an LMI passthrough state then LMI is considered Active. LMI Inactivity timer must be non-zero for LMI to be declared Inactive. In non-Frame Relay applications (type = dedicated) LMI will be presumed ACTIVE so this will setting is equivalent to (6). Note that there is a separate parameter for how the unit processes RTS that is related to this function if options (4), (5), (6), or (7) is selected, see CfgDteRts. Enumeration: 'follow-sync-rts': 7, 'signal-off': 1, 'follow-test': 4, 'follow-carrier': 3, 'follow-lmi-carr-rts': 8, 'follow-rts': 5, 'follow-carrier-rts': 6, 'signal-on': 2.

Shows the size that DLCI address field. This setting must correspond to the Frame Relay transmission format; typically Two bytes. (1) two byte DLCI address field (2) three byte DLCI address field (3) four byte DLCI address field Enumeration: 'threebytes': 2, 'twobytes': 1, 'fourbytes': 3.

This defines the manner in which the unit handles HDLC protocol errors (crc errors) in a Frame Relay application. If Discard is selected the unit will respond to an errored frame by aborting the frame if transmission has begun; or simply discarding it if transmission has not begun. If Passthru is selected the unit transmit the entire frame but will place an incorrect crc in it to preserve the error indication. (1) discard (2) pasthru Enumeration: 'passthr': 2, 'discard': 1.

The LMI type used in a Frame Relay application. This setting must match the attached Frame Relay device configuration. Annex-A and Annex-D use DLCI 0, and Type 1 uses DLCI 1023. Type 1 is alternatively referred to as Cisco, Group of four, or simply LMI. Annex-D may be referred to as ANSI T1.617. Annex-A may be referred to as ITU or CCITT Q.933. Auto-sense will either use the most recently detected LMI type or, in the absence of any LMI, will attempt to instigate LMI communications using each protocol. (1) Annex-A: conforms to ITU (CCITT) Q.933 annex A (2) Annex-D: conforms to ANSI T1.617 annex D (3) Type 1: conforms to the original LMI as developed by the Group of Four (4) Auto-sense: unit will attempt to detect and synchronize to the LMI type of the attached equipment. Enumeration: 'autosense': 4, 'annexa': 2, 'type1': 3, 'annexd': 1.

Timer used by the unit to determine that an attached device is not participating in the LMI protocol and that the unit should attempt to source LMI. This timer also controls the length of time that the LMI sourcing state machine remains in a particular state as it attempts to locate an LMI peer. (0) LMI Sourcing disabled (2-255) LMI Inactivity timeout

Timer used by the unit to determine the frequency at which Status Enquiries are issued during LMI sourcing states where the unit is emulating a Frame Relay DTE device. (2-255) length of time between sending enquiries (in seconds)

The ip-based Address Resolution protocol supported in the application. With ARP, requests are received and replies are generated accordingly. With InARP, requests are received and replies are generated; additionally, InARP requests are issued by the unit at the frequency defined by the InARP timer. Address Resolution will circumvent the need for static routes and automatically log an associated dynamic entry into the routing tables. (1) inactive: no address resolution support (2) ARP: only provide ARP responses. ARP is useful when the router knows the unit's ip address but doesn't know the DLCI. (3) InARP: provide both InARP responses and InARP requests. InARP is useful when the router knows the DLCI but not the ip address. (4) Both ARP and InARP. Enumeration: 'arp': 2, 'both': 4, 'inactive': 1, 'inarp': 3.

If the unit is configured to support the InARP address resolution protocol, this is the frequency of INARP requests that the unit will generate. (5-86400) - InARP Request Timer in seconds

Timer used by the unit to determine if an LMI Full Status Report is missing. In the absence of a Full Status report for the duration defined by this timer, the unit will declared all DLCI's status INACTIVE and begin logging down time. Data passage is not interfered with. (0) Full Status Timer is disabled (20-3600) Full Status Report Timeout in seconds.

Address Resolution Dlcis determines which dlcis will support address resolution. In Private management modes (Local, Remote, Bidirectional), address resolution runs on the single defined management DLCI only (regardless of this setting). In Piggyback management the user has options based upon two models: Single, where the address resolution protocols run only upon the defined managment DLCI and Multiple, where its supported on all active DLCIs recognized by the unit. (1) Single - address resolution on the defined default DLCI on both ports (2) Multiple - address resolution on all active DLCIs on both ports (3) DDSMulti - Single on DTE and Multiple on DDS (4) DTEMulti - Single on DDS and Multiple on DTE Enumeration: 'dtemulti': 4, 'single': 1, 'multiple': 2, 'ddsmulti': 3.

This setting configures the unit for VNIP topology support on a per-interface basis. Establishing a VNIP topology is a fundamental prerequisite to applying the VNIP feature set which includes PVC-based delay measurement, diagnostics, and congestion monitoring. With VNIP enabled on an interface the unit will attempt to locate VNIP peers out that port. As peers are discovered and logged the unit will report the topology it has learned on its opposite interface. If VNIP is inactive on one interface it will not engage in any VNIP dialog; however it will continue to listen for topology messages on the inactive interface and will reflect these messages out the opposite interface if VNIP is enabled. With VNIP inactive on both interfaces the unit will transparently pass all VNIP messages. The topology database includes ip addresses, DLCI values, and the number of VNIP hops in between. (1) Topology Inactive: VNIP messages pass through unit (2) Topology Enabled on DTE only: unit logs VNIP peers seen out the DTE interface. Unit listens for topology reports from the WAN but doesn't generate any towards the WAN. Will report learned WAN topology towards the DTE. (3) Topology Enabled on WAN only: unit logs VNIP peers seen out the WAN interface. Unit listens for topology reports from the DTE but doesn't generate any towards the DTE. Will report learned DTE topology towards the WAN. (4) Topolgy Enabled on Both DTE and WAN: Unit logs VNIP peers seen out both interfaces and generates DTE topolgy reports towards the WAN and vice versa. Enumeration: 'dds': 3, 'both': 4, 'inactive': 1, 'dte': 2.

VNIP peer to peer communications are initiated following the detection of a VNIP Hello message. The unit will periodically issue this message out interfaces that have VNIP enabled until a Hello response is received. Following the reception of the Hello response, the unit will stop issuing Hello messahges on that DLCI/interface and generate periodic topology reports at the VNIP Keep Alive frequency. The unit will generate periodic Hello messages, at the InitTimer frequency if no Hello responses are ever detected or a topology message not been detected within the time period defined by the VNIP Inactivity timer. (5-86400) VNIP Hello frequency (in seconds)

This is the frequency that topology reports are issued out any interface that has VNIP enabled. Once a Hello exchange occurs, the unit will periodically issue a VNIP message which reflects the topology it has learned on the opposite interface. This Keep Alive timer must be less than any peer unit's Inactivity timer. (5-86400) VNIP Topology Update frequency (in seconds)

The length of time to wait before dropping a VNIP peer from the database and attempting tp reestablish communications by issuing the VNIP Hello message. If this timer expires then the entire topology database is reset. The Inactivity timers of any unit participating in a VNIP topology must be greater than the highest Keep Alive timer in the topology. (5- 86400) VNIP Hello frequency (in seconds)

Transit Delay measurements may be enabled between any DLCI peers that have been logged through the topology protocol. Delay messages are issued at this frequency and results are recorded. Transit delay measures the round-trip network delay between two VNIP peers (internal unit latencies are not part of the measurement). Traps may be optionally generated if a delay threshold is exceeded. (15-86400): Transit Delay message frequency (in seconds)

The table defining the transit delay measurement profile for each of the learned VNIP peers. As peers are located and logged into the topology database, a default transit delay profile is assumed. The default is to enable transit delay to all hops located out the interface. A DLCI's transit delay profile cannot be modified unless the DLCI has been discovered through the VNIP topology protocol.

A VNIP Transit Delay configuration entry for a particular DLCI on a particular interface. A DLCI's transit delay profile cannot be modified unless the DLCI has been discovered through the VNIP topology protocol

This is the interface being configured for VNIP Transit Delay. If topology is enabled, each interface will contain a database of VNIP peers organized by DLCI value and Number of Hops. (1) DTE Interface (2) DDS Interface Enumeration: 'dds-interface': 2, 'dte-interface': 1.

This is the DLCI being configured for VNIP Transit Delay. If topology is enabled, each interface will contain a database of VNIP peers organized by DLCI value and Number of Hops.

VNIP topolgy may include multiple units on a given DLCI/interface. The topology logs the number of intermediate VNIP peers between units (Hops). This setting determines which peers on a DLCI are participating in delay measurements. (0) All hops (1-254) individually addressable delay measurement between any two peers. (255) Furthest hop only

Controls the Receive Summary Cancellation feature of VNIP Transit Delay on this interface/DLCI. Every Transit Delay measurement exchange includes a follow-up message from the initiator with the delay results. If RSC is enabled, a unit will log results based upon this summary message and will not issue its next scheduled delay measurement. With RSC disabled, the unit will not use the summary message and will always issue its regularly scheduled message based on the delay frequency timer. The purpose of this feature is to reduce traffic introduced by VNIP. In a typical peer-to-peer transit delay measurement where both ends are concurrently conducting transit delay measurements it's recommended that one end have RSC enabled and one end disabled. Enumeration: 'disable-rsc': 2, 'enable-rsc': 1.

Specifies a transit delay threshold for this DLCI/interface. When the transit delay exceeds the threshold, a TRAP is sent. The threshold may be set from one millisecond to 24 hours. A value of 0 will prevent a TRAP from being sent. (0): Transit delay threshold trap disabled for this DLCI/interface (1-86400000): delay threshhold. Any delay measurements exceeding this result will generate a trap.

The table allows the user to disable transit delay measurements for a specific DLCI on a particular interface.

Disables VNIP Transit Delay for a particular interface and DLCI.

Transit delay can be disabled for a given DLCI on either interface. This indexes the interface. Setting this index and the associated DLCI index will disable transit delay on that combination. Enumeration: 'dds-interface': 2, 'dte-interface': 1.

Transit delay can be disabled for a given DLCI on either interface. This indexes the DLCI. Setting this index and the associated interface index will disable transit delay on that combination.

The dfrapCfgTransitDelayTable is cleared. (1) clear the table Enumeration: 'clear-table': 1.

This table allows the user to configure DLCI specific parameters such as Names, CIR, and EIR. Additionally, any DLCIs configured with these parameters will be added into the Short Term statistics database next time its cleared.

A table entry indexed by DLCI, containing a DLCI, a DLCI name, a CIR, and how the CIR value was obtained.

A DLCI selected for customized configuration and to be added to short term statistics collection (if it wasn't already there).

A user-specifiable name for an individual DLCI.

The CIR value for an individual DLCI. This value is used in the calculation utilization as a percentage of CIR. If the CIR is reported in the LMI message then the reported value will override this configured entry. In the absence of LMI CIR and a configured CIR, the unit will assume that teh CIR is the DTE Line Rate.

The source of the CIR value for this DLCI. If CIR for a DLCI is part of the LMI message then this LMI supplied CIR will override any defined CIR. If CIR is not part of LMI and has not been explicitly defined by the user it will default to the DTE Line Rate. (1) CIR reported in LMI Full Status message (2) CIR configured by user (3) CIR defaulted to DTE Line Rate Enumeration: 'cir-configured-by-user': 2, 'cir-acquired-from-lmi': 1, 'cir-is-datarate': 3.

The threshold for generating a utilization threshold trap as a percentage of the CIR. If the utilization percentage is above this threshold for more than dfrapCfgFrPerfDlciUtilThreshold number of dfrapCfgFrPerfTimersSTInterval's a dfrapPvc(Rx/Tx)UtilizationExceeded trap will be issued. If the If the utilization percentage falls below this threshold for more than dfrapCfgFrPerfDlciUtilThreshold number of dfrapCfgFrPerfTimersSTInterval's a dfrapPvc(Rx/Tx)UtilizationExceeded trap will be issued.

The EIR value for an individual DLCI. In the absence of a configured EIR, the unit will assume that the EIR is the DTE Line Rate.

Setting this object with a specific DLCI value will remove the DLCI form the DLCI-specific parameters database.

Short term statistics maintain cumulative counts, and counts for the current and previous short term windows. This value is the window size for the short term statistics intervals. (3-60): short term statistics collection interval

Long term statistics maintain 96 contiguous intervals of configurable protocol per DLCI statistics. This value is the window size of each interval. Adjusting this value will change the overall length of time that the 96 intervals will span. (4-3600): long term statsistics collection interval

This table allows the user to select TCP/UDP ports for statistics collection. Tx and Rx byte counts will collected on the specified ports. These ports are selectable as protocols in the long term statistics filter and are displayed with the other protocols in the short term statistics.

An index and TCP/UDP port number pair.

An index. Beginning with index 1, the range is defined in SysNumUserProtocols

Tx and Rx byte counts will be collected on the user-specifiable TCP/UDP port number. (0) port not defined (1-65535): IP TCP/UDP protocol port number.

Long term statistics can only be collected on a limited number of DLCIs. The value of SysLTFNumDlcis defines the maximum number of DLCIs that can be included in the Long Term Statistics. Once one or more DLCIs are added to Long Term Stats, the user may assign a set of protocols that will be monitored across all of the Long Term DLCIs.

An index and DLCI number pair.

An index. Beginning with index 1, the maximum is defined by the value of SysLTFNumDlcis.

Setting a DLCI value here will add that DLCI into the Long term statistics database (associated with its index) and it will be monitored for the protocol activity defined in the Long Term Protocol filter.

Long term statistics can only be collected on a limited number of protocols. The maximum number of Long Term Protoocls are defined by SysLTFNumProtocols. This table allows the user to configure those protocols.

An index and protocol pair.

An index. Beginning with index 1, the maximum is defined by the value of SysLTFNumProtocols.

Long term statistics will be collected on the user-specifiable protocol. Setting a -1 remove the indexed protocol from the filter. Enumeration: 'snmptrap-tcp-ip-tx-bc': 19, 'gp-mem-report-icmp-ip-tx-bc': 69, 'addr-mask-req-icmp-ip-rx-bc': 62, 'tftp-tcp-ip-rx-bc': 12, 'lmi-full-enq-tx-bc': 159, 'gp-mem-query-icmp-ip-tx-bc': 67, 'thru-de-rx-c': 136, 'other-ip-tx-bc': 75, 'annex-g-rx-bc': 172, 'snmptrap-udp-ip-rx-bc': 38, 'user-defined-2-rx-bc': 122, 'snmp-tcp-ip-rx-bc': 18, 'icmp-ip-tx-bc': 41, 'ftp-udp-ip-rx-bc': 24, 'spx-ipx-rx-bc': 80, 'thru-byte-rx-bc': 128, 'icmp-ip-rx-bc': 42, 'cir-percent-range7-tx-bc': 149, 'netbios-ssn-tcp-ip-rx-bc': 16, 'netbios-ipx-rx-bc': 88, 'dest-unr-icmp-ip-rx-bc': 46, 'tftp-udp-ip-rx-bc': 30, 'snmp-udp-ip-rx-bc': 36, 'cir-percent-range4-rx-bc': 144, 'thru-de-tx-c': 135, 'cir-percent-range2-rx-bc': 140, 'echoreq-icmp-ip-tx-bc': 51, 'telnet-tcp-ip-tx-bc': 7, 'cir-percent-range1-tx-bc': 137, 'lmi-rx-bc': 154, 'user-defined-1-rx-bc': 120, 'param-prob-icmp-ip-rx-bc': 56, 'src-quench-icmp-ip-tx-bc': 47, 'udp-ip-rx-bc': 22, 'vnip-tx-bc': 169, 'user-defined-4-rx-bc': 126, 'addr-mask-req-icmp-ip-tx-bc': 61, 'ncp-ipx-rx-bc': 82, 'ftp-tcp-ip-rx-bc': 6, 'rarp-rep-rx-bc': 100, 'ftp-udp-ip-tx-bc': 23, 'cir-percent-range3-tx-bc': 141, 'sna-netbios-tx-bc': 113, 'smtp-tcp-ip-tx-bc': 9, 'netbios-ipx-tx-bc': 87, 'thru-fecn-tx-c': 131, 'snmp-udp-ip-tx-bc': 35, 'gp-mem-reduct-icmp-ip-rx-bc': 72, 'ip-rx-bc': 2, 'dest-unr-icmp-ip-tx-bc': 45, 'cir-percent-range2-tx-bc': 139, 'smtp-udp-ip-rx-bc': 28, 'inarp-req-tx-bc': 101, 'arp-req-tx-bc': 93, 'tftp-tcp-ip-tx-bc': 11, 'addr-mask-rep-icmp-ip-rx-bc': 64, 'cisco-rx-bc': 116, 'rarp-rep-tx-bc': 99, 'redirect-icmp-ip-tx-bc': 49, 'other-ipx-rx-bc': 90, 'spx-ipx-tx-bc': 79, 'echorep-icmp-ip-tx-bc': 43, 'param-prob-icmp-ip-tx-bc': 55, 'ospf-ip-tx-bc': 73, 'echorep-icmp-ip-rx-bc': 44, 'redirect-icmp-ip-rx-bc': 50, 'thru-fecn-rx-c': 132, 'snmptrap-tcp-ip-rx-bc': 20, 'lmi-tx-bc': 153, 'http-tcp-ip-tx-bc': 13, 'cir-percent-range8-tx-bc': 151, 'sap-ipx-rx-bc': 84, 'thru-becn-tx-c': 133, 'sna-tx-bc': 105, 'other-ipx-tx-bc': 89, 'lmi-livo-stat-rx-bc': 158, 'sna-rx-bc': 106, 'ipx-tx-bc': 77, 'echoreq-icmp-ip-rx-bc': 52, 'sna-appn-rx-bc': 112, 'other-rx-bc': 118, 'cir-percent-range1-rx-bc': 138, 'smtp-tcp-ip-rx-bc': 10, 'thru-frame-rx-c': 130, 'http-udp-ip-tx-bc': 31, 'total-downtime': 166, 'addr-mask-rep-icmp-ip-tx-bc': 63, 'vnip-rx-bc': 170, 'arp-rep-rx-bc': 96, 'user-defined-2-tx-bc': 121, 'annex-g-tx-bc': 171, 'rip-udp-ip-rx-bc': 40, 'arp-rx-bc': 92, 'src-quench-icmp-ip-rx-bc': 48, 'rip-ipx-tx-bc': 85, 'user-defined-3-tx-bc': 123, 'cir-percent-range3-rx-bc': 142, 'lmi-other-tx-bc': 163, 'lmi-full-enq-rx-bc': 160, 'user-defined-3-rx-bc': 124, 'igrp-rx-bc': 168, 'sna-periph-rx-bc': 110, 'arp-rep-tx-bc': 95, 'rip-udp-ip-tx-bc': 39, 'other-ip-rx-bc': 76, 'tftp-udp-ip-tx-bc': 29, 'netbios-dgm-udp-ip-tx-bc': 33, 'rarp-req-tx-bc': 97, 'lmi-other-rx-bc': 164, 'snmp-tcp-ip-tx-bc': 17, 'timestamp-rep-icmp-ip-rx-bc': 60, 'telnet-udp-ip-tx-bc': 25, 'snmptrap-udp-ip-tx-bc': 37, 'pkt-too-big-icmp-ip-tx-bc': 65, 'cir-percent-range6-tx-bc': 147, 'cir-percent-range7-rx-bc': 150, 'lmi-livo-stat-tx-bc': 157, 'sna-netbios-rx-bc': 114, 'ip-tx-bc': 1, 'pkt-too-big-icmp-ip-rx-bc': 66, 'ncp-ipx-tx-bc': 81, 'user-defined-4-tx-bc': 125, 'lmi-livo-enq-tx-bc': 155, 'gp-mem-query-icmp-ip-rx-bc': 68, 'gp-mem-report-icmp-ip-rx-bc': 70, 'user-defined-1-tx-bc': 119, 'telnet-udp-ip-rx-bc': 26, 'ospf-ip-rx-bc': 74, 'tcp-ip-rx-bc': 4, 'lmi-livo-enq-rx-bc': 156, 'udp-ip-tx-bc': 21, 'cisco-tx-bc': 115, 'rip-ipx-rx-bc': 86, 'arp-req-rx-bc': 94, 'thru-becn-rx-c': 134, 'smtp-udp-ip-tx-bc': 27, 'sna-appn-tx-bc': 111, 'http-tcp-ip-rx-bc': 14, 'gp-mem-reduct-icmp-ip-tx-bc': 71, 'other-tx-bc': 117, 'igrp-tx-bc': 167, 'timestamp-req-icmp-ip-rx-bc': 58, 'timestamp-rep-icmp-ip-tx-bc': 59, 'time-excd-icmp-ip-rx-bc': 54, 'lmi-full-stat-tx-bc': 161, 'timestamp-req-icmp-ip-tx-bc': 57, 'ftp-tcp-ip-tx-bc': 5, 'netbios-ssn-tcp-ip-tx-bc': 15, 'time-excd-icmp-ip-tx-bc': 53, 'cir-percent-range4-tx-bc': 143, 'sna-periph-tx-bc': 109, 'sna-subarea-rx-bc': 108, 'telnet-tcp-ip-rx-bc': 8, 'netbios-dgm-udp-ip-rx-bc': 34, 'thru-byte-tx-bc': 127, 'lmi-full-stat-rx-bc': 162, 'inarp-req-rx-bc': 102, 'delete-entry': -1, 'arp-tx-bc': 91, 'tcp-ip-tx-bc': 3, 'rarp-req-rx-bc': 98, 'thru-frame-tx-c': 129, 'inarp-rep-rx-bc': 104, 'cir-percent-range5-rx-bc': 146, 'ipx-rx-bc': 78, 'sna-subarea-tx-bc': 107, 'cir-percent-range5-tx-bc': 145, 'cir-percent-range6-rx-bc': 148, 'inarp-rep-tx-bc': 103, 'http-udp-ip-rx-bc': 32, 'total-uptime': 165, 'sap-ipx-tx-bc': 83, 'cir-percent-range8-rx-bc': 152.

The default threshold for generating a utilization threshold trap as a percentage of the CIR. This value is used for dfrapCfgFrPerfDlciNamesUtilThreshold when a DLCI is first discovered.

The number of Short Term Intervals that a DLCI's utilization as a percentage of CIR must be above or below the value of dfrapCfgFrPerfDlciUtilThreshold before a dfrapPvc(Rx/Tx)UtilizationExceededTrap or dfrapPvc(Rx/Tx)UtilizationClearedTrap is issued.

Clears the smperCfgFrPerfDlciNamesTable (1) clear the table or (2) clear the table but don't remove the dlcis from the short term statistics. Enumeration: 'clear-table-keep-stats': 2, 'clear-table': 1.

Clears the dfrapCfgFrPerfUserProtocolsTable (1) clear the table Enumeration: 'clear-table': 1.

Clears the dfrapCfgFrPerfLTDlciFilterTable (1) clear the table Enumeration: 'clear-table': 1.

Clears the dfrapCfgFrPerfLTProtocolFilterTable (1) clear the table Enumeration: 'clear-table': 1.

Delete all unprovisioned and Not-In-LMI dlcis (1) delete all unprovisioned Enumeration: 'delete-unprov': 1.

The password needed to start a CLI (Command Line Interface), Telnet or LCD session.

The password needed to initiate a TFTP download.

OBSOLETE: The Telnet, CLI and LCD passwords are one and the same. Use the above CfgTelnetCliLcdPassword to log into the CLI (Command Line Interface).

OBSOLETE: The Telnet, CLI and LCD passwords are one and the same. Use the above CfgTelnetCliLcdPassword to log into the LCD Interface.

The community string for doing SNMP GETs. The unit will respond to GETs that use either this string or the SET community string. All others will be rejected and a trap will be generated. String is case sensitive.

The community string for doing SNMP SETs. The unit will reject SETs with any other coimmunity string and will generate a trap. String is case sensitive.

Request to start configuration download and lock out any other means of configuring the unit. The integer passed in represents the time out period in seconds between sets. A set to this object will fail if the unit is already in a configuration locked state.

Returns the IP Address of the management station currently in control of configuration. A unit that is not in a configuration locked state will return 0.0.0.0

A read of this object returns the Current Configuration ID string. A write sets the Configuration ID string. The string contains a starting character to indicate the last configuration source C = Envisage N = CLI/TELNET L = LCD S= other SNMP management station and a unique 7 integer value to differentiate configurations between common sources. A value of *STARTUP indicates the configuration has been defaulted. A write will only be accepted from the management station that has successfully obtained the configuration lock

The status of a configuration install is reported here. On startup, a status of success will be reported. (1) The configuration has been locked and an update or unlock command has not been received. (2) An update command has been received and the configuration has been validated as consistent; . (3) An update command has been received but the DTE port datarate is not compatible with the density. (4) An update command has been received but the number of channels to be allocated will not fit in the available channels. (5) An update command has been received but there is an error in the configuration that is not a datarate-density-conflict or bandwidth-allocation-error. (6) The time between consecutive set requests exceeded the timeout sent with the dfrapCfgLock command. (7) The user sent a dfrapCfgUnlock command before a dfrapCfgUpdate command. This usually means that one of the sets in the configuration failed. Enumeration: 'aborted-by-user': 7, 'success': 2, 'in-progress': 1, 'datarate-density-conflict': 3, 'general-error': 5, 'timeout': 6, 'bandwidth-allocation-error': 4.

The management station sets this variable to complete the configuration install process. Un-lock (1) notifies the agent to remove the lock on configuring the unit without updating the configuration. Enumeration: 'un-lock': 1.

The management station sets this variable to complete the configuration install process. Update (1) notifies the agent to start the update process within the unit. Enumeration: 'update': 1.

Controls a bi-directional unit loopback. Data is received from either interface, processed, and transmitted back towards the same interface. When configured for Frame Relay operation the unit will preserve the LMI path during this loopback. In Frame Relay mode, only valid frames are looped back (pseudorandom test patterns will be dropped). (1) enable unit loopback Enumeration: 'enable-loopback-mode': 1, 'disable-loopback-mode': 2.

Enables the operator to remotely reset the unit. Using this command will cause the unit to terminate all its connections and drop data. (1): reset unit Enumeration: 'reset-unit': 1.

The remaining time on the active loopback before the loopback times out. The time is in hundredths of seconds (TimeTicks).

Controls local network loopback. All data received from the WAN, regardless of format or content, is transmitted back out (line interface loopback) while still being sent to the DTE. When configured for Frame Relay operation the unit will not preserve the LMI path during this loopback. (1) enable DDS line loopback (2) disable DDS line loopback Enumeration: 'enable-loopback-mode': 1, 'disable-loopback-mode': 2.

Enables the operator to examine (ONLY) the status of network loopbacks placed by external equipment, such as your local CO. Any of these conditions will result in a DDS line loopback. (1) no remote loop up command (2) simplex current reversal loopback command (3) non-latching loopback command (4) latching loopback comamnd Enumeration: 'simplex-current-loop': 2, 'non-latching-loop': 3, 'latching-loopback': 4, 'no-loop-from-remote': 1.

The remaining time on the active loopback before the loopback times out. The time is in hundredths of seconds (TimeTicks).

Controls a bi-directional DTE loopback. All data received at the DTE interface is looped back regardless of format or content (line loopback). All data received at the WAN interface is looped back regardless of format or content (line loopback). When configured for Frame Relay operation the unit will not preserve the LMI path during this loopback. (1) enable DTE loopback (2) disable DTE loopback Enumeration: 'enable-loopback-mode': 1, 'disable-loopback-mode': 2.

This selection displays the status of the DTE Channel V.54 Loopback for the channel. This loopback is initiated by the remote node, causing this unit to enter a Local DTE loopback condition. (1) V54 loopback pattern received from WAN (2) V54 loopback pattern not received from WAN Enumeration: 'v54-not-received': 2, 'v54-received': 1.

This selection controls the DTE Channel V.54 Remote Loopback. Transmit-code-enable (3) will cause the node to transmit a V.54 code to the remote node which will then enter a Local DTE Loopback state. transmit-code-disable (4) will transmit the loopdown code and cause the remote unit to remove the Local DTE Loopback path. (1) send remote V54 loop up command (2) send remote V54 loop down command Enumeration: 'transmit-code-disable': 4, 'transmit-code-enable': 3.

The remaining time on the active loopback before the loopback times out. The time is in hundredths of seconds (TimeTicks).

The unit is capable of sending a pseudorandom test pattern (511 or QRSS) out the WAN and monitoring the WAN received data for the same pattern. This test may be ineffective in certain frame relay applications as pseudorandom data lacks appropriate framing. Refer to VLOOP and VBERT for PVC-based error-rate testing in a live frame relay network. (1) Start a BERT test (2) Stop a BERT test (4) Inject a single bit error into the outgoing pattern (5) Clear current BERT results Enumeration: 'stop-test': 3, 'clear-error': 5, 'inject-error': 4, 'start-test': 1.

Displays the current BERT test sync status. (1) BERT is not running (2) BERT is running but is not in sync (3) BERT is running and has detected a received BERT Enumeration: 'bert-out-of-sync': 2, 'bert-off': 1, 'bert-in-sync': 3.

Displays the number of errors detected in Bert Test.

Displays the number of seconds containing 1 or more errors in BERT Test.

Elapsed time since BERT test was started or last cleared.

Displays the number of times BERT test has synched up on the pattern. The BERT will attempt to resynchronize in response to excessive errors. A running count here indicates that a clean BERT is not being received.

The type of pseudorandom BERT pattern used. (1) 511: 9-bit pseudorandom pattern (2) QRSS: 20-bit pseudorandom pattern with no more than 14 consecutive zeros Enumeration: 'five11-pattern': 1, 'qrss': 2.

Table of Diagnostics performed with the VNIP protocol

VNIP VLOOP and VBERT diagnostic profile. Initiating these tests require an established and stable VNIP topology on an interface. Once the topology is in place, the user can execute a PVC-based diagnostic between this unit and any indexed entry in the topology table. The index into the topology table for a particular interface is required.

The interface out which a PVC-based VNIP diagnostic will be run. This must be an interface with a valid and stable VNIP topology for a VNIP Diagnostic. Enumeration: 'dte-interface': 1, 't1-interface': 2.

The index to the external VNIP peer as presented by the VNIP topology database for the given interface. Refer to VnipTopologyTable to determine the index of the remote peer.

This is the DLCI value for the given interface/index combination. This comes from the VniptTopologyTable.

This is the ip address for the given interface/index combination. This comes from the VniptTopologyTable.

Controls execution of the Vnip Logical Loopback (VLOOP) test. VLOOP is designed as an intrusive test and customer data on the DLCI-under-test will be discarded. The VLOOP test includes a timed VBERT test and is run using the profile configured within this table. (1) start VLOOP test (2) stop VLOOP test (override VBERT test duration) Enumeration: 'stop-test': 2, 'start-test': 1.

Controls execution of the Vnip Virtual Bit Eror Rate (VBERT) test. VBERT is designed to be a non-intrusive test and will attempt to statistically multiplex VBERT test data and customer data on the DLCI-under-test. However, VBERT data is given priority over customer data when the selected VBERT volume causes internal congestion. The test is run using the profile configured within this table. (1) start test (2) stop test (override VBERT test duration) Enumeration: 'start': 1, 'stop': 2.

Specifies the throughput bit rate applied by VBERT or VLOOP to the DLCI-under-test. Any rate up to the DTE line rate may be selected. Note that selecting rates that approach line rate will impact neighboring DLCIs. (8000-64000): VBERT/VLOOP data rate (in bits per second).

Specifies the size of framed data that will be used during the VBERT test, measures in Bytes. (64) 64-byte frames (128) 128-byte frames (256) 256-byte frames (512) 512-byte frames (1024) 1024-byte frames (2048) 2048-byte frames Enumeration: 'thousand-twenty-four-byte': 1024, 'sixty-four-byte': 64, 'two-thous-forty-eight-byte': 2048, 'one-twenty-eight-byte': 128, 'two-fifty-six-byte': 256, 'five-hundred-twelve-byte': 512.

Specifies percentage of VBERT packets that will have the Frame Relay Discard Eligibility bit set. Frames with this bit set may be more likley to get dropped in a congested network. (1) 0% of the test frames are marked discard eligible (2) 25% of the test frames are marked discard eligible (3) 50% of the test frames are marked discard eligible (4) 75% of the test frames are marked discard eligible (5) 100% of the test frames are marked discard eligible Enumeration: 'twentyFive-percent': 2, 'zero-percent': 1, 'seventyFive-percent': 4, 'oneHundred-percent': 5, 'fifty-percent': 3.

Specifies the duration of a VBERT test. Note that VBERT is subjected to the unit's Loopback Timer and will be terminated by whichever timer expires first. (10-1440): VBERT time duration in seconds

VNIP topology is a feature that, for each interface, maps all compatible VNIP peers, their DLCI value, ip address and relative location. The topology is a fundamental prerequisite to applying the VNIP feature set which includes PVC-based delay measurement, diagnostics, and congestion monitoring. With VNIP enabled on an interface the unit will attempt to locate VNIP peers out that port. As peers are discovered and logged the unit will report the topology it has learned on its opposite interface. If VNIP is inactive on one interface it will not engage in any VNIP dialog; however it will continue to listen for topology messages on the inactive interface and will reflect these messages out the opposite interface if VNIP is enabled. With VNIP inactive on both interfaces the unit will transparently pass all VNIP messages. The topology database includes the interface, local DLCI value, remote peer DLCI value, remote peer ip address, and the number of VNIP hops in between. This table also reports the status of other VNIP features as well.

The DLCI, IP address, and number of hops for a particular node, discovered via VNIP off of an interface. The entry may also have transit delay measurements and VBERT diagnostic status to report as well.

The interface off of which the peer was discovered. Topology is discovered by sending VNIP messages out each interface. Units discovered via a particular interface are kept in a list associated with that interface. (1) VNIP peers and status out DTE interface (2) VNIP peers and status out WAN interface Enumeration: 'dds-interface': 2, 'dte-interface': 1.

The number of this discovered peer in the list of nodes for this interface. For each interface, the nodes are numbered 1 through n. This index is required when disabling or enabling VBERT/VLOOP to a particular peer.

The DLCI of the discovered neighboring peer. This may be different from the local DLCI.

The IP address for the discovered peer.

The discovered peer is this number of hops away. Each hop is a VNIP peer.

The DLCI from this unit over which the remote peer was discovered.

The number of transit delay samples collected.

The average transit delay between this unit and the remote peer (in milliseconds).

The maximum transit delay between this unit and the remote peer (in milliseconds).

The minimum transit delay between this node and the remote peer (in milliseconds).

The most recent transit delay measured between this node and the remote peer (in milliseconds).

This selection displays the status of the VNIP PVC Loopback for this entry. This loopback is initiated by the remote node through the VLOOP utility, causing this node to loop data back to the remote node. Enumeration: 'loopback-enable': 1, 'loopback-disable': 2.

Displays the current status of the VBERT/VLOOP test. (1) Off: no test has run or the entry has been cleared (2) Testing: the entry is generating VBERT test frames (3) Test Failed: the request for a test on this entry failed (4) Test Completed: a test has run and is finished results are complete (5) In Test: the entry is on the receiving end of VBERT packets Enumeration: 'test-failed': 3, 'test-completed': 4, 'testing': 2, 'off': 1, 'in-test': 5.

Displays the number of Frames transmitted during VBERT/VLOOP Test that had the Discard Eligibility indicator bit set.

Displays the number of Frames received during VBERT/VLOOP Test that had the Discard Eligibility indicator bit set.

Displays the number of Frames transmitted during VBERT/VLOOP Test that had the Discard Eligibility indicator bit cleared.

Displays the number of Frames received during VBERT/VLOOP Test that had the Discard Eligibility indicator bit cleared.

The maximum transit delay between this node and the remote peer during the VBERT/VLOOP test.

The average transit delay between this node and the remote peer during the VBERT/VLOOP test.

Elapsed time since VBERT/VLOOP test was started or cleared.

The calculated percent of CIR utilization during a VBERT test, this value is only valid after a test is complete not during.

The calculated percent of EIR utilization during a VBERT test, this value is only valid after a test is complete not during.

This is the method in which the unit is configured for SNMP management access. (1) None: SNMP management disabled (2) SLIP: out-of-band management via asynchronous Serial Line IP (3) Private DLCI: in-band management using a private DLCI that is dedicated solely to this unit's management. (4) Piggyback DLCI: in-band management using any DLCI optionally multiplexing both management and user data. Enumeration: 'none': 1, 'piggyback-dlci': 4, 'private-dlci': 3, 'slip': 2.

This is the port(s) on which the management traffic will appear. (1) Async Maintenance(Comm)/Console port - SLIP mode (2) Local DTE interface: unit is configured for Private Local DLCI mode (3) Remote WAN Interface: unit is confiogured for Private Remote DLCI mode (4) DTE and WAN Interfaces: unit is configured for either Piggyback Bidirectional mode. Enumeration: 'local-and-remote': 4, 'comm': 1, 'remote-wan': 3, 'local-dte': 2.

This is the status of the port(s) on which the management traffic will appear. (1) Active: port is configured and status is okay (2) Inactive: port is declared out of service (3) Alarm: port is experiencing an alarm condition that may interefere with management access Enumeration: 'active': 1, 'alarm': 3, 'inactive': 2.

This is the DLCI for the PVC that is defined for the Management port. All traffic using this DLCI in the Frame Replay packet will be destined for the InBand Management task.

This is the status of the default management DLCI. (1) not applicable: SLIP mode or management is disabled (2) DLCI Active: default DLCI is active in the LMI full status response. (3) DLCI Inactive: default DLCI is not active in the LMI full status response. Enumeration: 'dlci-active': 2, 'na': 1, 'dlci-inactive': 3.

Status of the DTE Mode LED. (1) DTE Mode LED off: Missing control signals (2) DTE Mode LED green: Normal (3) DTE Mode LED yellow: Test Mode Enumeration: 'offLED-DTE-inactive': 1, 'greenLED-normal': 2, 'yellowLED-test-mode': 3.

Status of the DTE Status LED. (1) DTE Status LED green: normal Enumeration: 'greenLED-active': 2.

Status of the DTE Tx Data LED. In Frame Relay mode, this LED is ON (green) when the DTE is not sending HDLC Flags and is OFF when HDLC flags are being transmit. In CBO mode, the LED is ON (green) for a SPACE and OFF for a MARK. (1) DTE Transmit LED OFF: inactive (HDLC flags or CBO marks) (2) DTE Transmit LED ON: active (HDLC frames or CBO spaces) Enumeration: 'greenLED-tx-data-transmitting': 2, 'offLED-inactive': 1.

Status of the DTE Rx Data LED. In Frame Relay mode, this LED is ON (green) when the WAN is receiving HDLC Flags and is OFF when HDLC flags are being received. In CBO mode, the LED is ON (green) for a SPACE and OFF for a MARK. (1) DTE Receive LED OFF: inactive (HDLC flags or CBO marks) (2) DTE Receive LED ON: active (HDLC frames or CBO spaces) Enumeration: 'greenLED-rx-data-receiving': 2, 'offLED-inactive': 1.

Status of the DDS Mode LED. (1) DDS Mode LED is green: normal data mode (2) DDS Mode LED is yellow: test mode Enumeration: 'greenLED-normal': 2, 'yellowLED-test-mode': 3.

Status of the DDS Status LED. (1) DDS Status LED is OFF: no signal received from WAN (2) DDS Status LED is green: normal (3) DDS Status LED is yellow: remote alarm Enumeration: 'greenLED-normal': 2, 'yellowLED-remote-alarm': 3, 'offLED-DDS-no-signal': 1.

Status of all six DFRAP LEDs, encoded in a string. 'F' off '5' green '0' yellow 'A' red '7' blinking green and off '3' blinking yellow and off 'B' blinking red and off '4' blinking green and yellow '6' blinking green and red '8' blinking yellow and red Positionally, the 6 letters are DTE Mode, DTE status, Dte Tx, Dte Rx, DDS Mode, and DDS Status. For example, '555550' would mean: DTE in normal mode, active status, transmitting and receiving and DDS normal with remote alarm.

Allows the user to clear all the VNIP Transit Delay data collected in the VNIP topology database. (1) Clear entire Transit Delay results database Enumeration: 'clear-transit-delay': 1.

If configured for Frame Relay with a non-zero LMI inactivity timer the unit will monitor the status of LMI and, if proper messaging is not detected, will attempt to emulate either Frame Relay DTE or DCE devices in attempt to restore LMI to any attached equipment and provide managed access for diagnostic purposes. Typically frads/routers are Frame Relay DTE while switches are Frame Relay DCE but this model may vary. In the absence of full-duplex LMI, the unit will cycle through various states in attempt to adapt to an LMI partner. The unit will try each state for the duration of the LMI Inactivity timer and then advance to the next one if satisfactory handshaking is not established. While in any of these states if full-duplex LMI handshaking does appear, the unit will immediately revert to the passthrough state. (1) initializing (2) Passthrough: not sourcing any LMI messages. (3) Status Enquiries out DTE interface: unit is emulating a Frame Relay DTE device out the its (physical) DTE interface. (4) Status Enquiries out WAN interface: unit is emulating a Frame Relay DTE device out the its WAN interface. (5) Status Responses out the DTE interface: unit is emulating a Frame Relay DCE device out the its (physical) DTE interface (provisioning the single default management DLCI). (6) Status Responses out the WAN interface: unit is emulating a Frame Relay DCE device out the its WAN interface (provisioning the single default management DLCI). (7) Disabled - LMI Inactivity timer is zero or unit not configured for a Frame Relay application. (8) Status Responses out both DTE and WAN interfaces: unit is configured for Fixed DCE mode of management and emulates a Frame Relay DCE independently on both ports (provisioning the single default management DLCI). Enumeration: 'status-rspns-to-dds': 6, 'status-rspns-to-dte': 5, 'status-enqs-to-dte': 3, 'passthrough': 2, 'status-enqs-to-dds': 4, 'disabled': 7, 'status-rspns-both': 8, 'initializing': 1.

Status of the DTE port. (1) No-connections: indicates the port is not completely to pass data to/from the WAN. (2) Active: port is configured and ready to pass data. (3) Test: diagnostic condition in process. Enumeration: 'active': 2, 'test': 3, 'no-connections': 1.

Status of the Request to Send (RTS) signal from the DTE port. (1) RTS Active (2) RTS Inactive Enumeration: 'on': 1, 'off': 2.

Status of the Data Terminal Ready (DTR) signal from the DTE port. (1) DTR Active (2) DTR Inactive Enumeration: 'on': 1, 'off': 2.

Status of the Data Carrier Detect (DCD) signal driven by this unit towards the DTE port (1) DCD Active (2) DCD Inactive Enumeration: 'on': 1, 'off': 2.

Status of the Data Set Ready (DSR) signal driven by this unit towards the DTE port. (1) DSR Active (2) DSR Inactive Enumeration: 'on': 1, 'off': 2.

Status of the Clear to Send (CTS) signal driven by this unit towards the DTE port (1) CTS Active (2) CTS Inactive Enumeration: 'on': 1, 'off': 2.

The Current status of the physical interface. Your network carrier can send Out-of-Service or Maintenance Mode codes. (1) in sync (2) out of service (3) out of frame (4) bipolar violations (5) loss of signal (6) simplex current loopback Enumeration: 'in-sync': 1, 'simplex-current-loopback': 6, 'out-of-frame': 3, 'out-of-service': 2, 'bpv-threshold-failure': 4, 'loss-of-signal': 5.

The estimated line attenuation (signal loss) on the DDS channel. Actual cable length can be estimated with the assumption that a good quality data grade cable is used. Use of lower quality cabling will produce greater line attenuation on shorter cable runs. (1) est. between 40 and 50dB line loss, equivalent to roughly 8 to 9 Kilometers of nominal cable length. (2) est. between 39 and 44dB line loss, equivalent to roughly 7 to 8 Kilometers of nominal cable length. (3) est. between 33 and 38dB line loss, equivalent to roughly 6 to 7 Kilometers of nominal cable length. (4) est. between 27 and 22dB line loss, equivalent to roughly 5 to 6 Kilometers of nominal cable length. (5) est. between 21 and 26dB line loss, equivalent to roughly 4 to 5 Kilometers of nominal cable length. (6) est. between 15 and 20dB line loss, equivalent to roughly 3 to 4 Kilometers of nominal cable length (7) est. between 8 and 14dB line loss, equivalent to roughly 2 to 3 Kilometers of nominal cable length (8) est. between 1 and 7dB line loss, equivalent to roughly .5 to 2 Kilometers of nominal cable length (9) est. 0dB line loss, equivalent to less than 1Km nominal cable length Enumeration: 'loss-33-38db': 3, 'loss-15-20db': 6, 'loss-27-32db': 4, 'loss-0db': 9, 'loss-1-7db': 8, 'loss-39-44db': 2, 'loss-21-26db': 5, 'loss-40-50db': 1, 'loss-8-14db': 7.

Allows the user to clear all the VBERT data collected in the VNIP topology database as long as the entry is not in a test status. (1) Clear all VBERT/VLOOP status information Enumeration: 'clear-vbert': 1.

This indicates the current status of LMI Auto Sensing if it's enabled. (1) Disabled: LMI is configured as Type 1, Annex-D, or Annex-A (2) Searching: unit is attempting to determine the LMI type of the attached equipment by issuing LMI messages of each LMI type and searching for responses. (3) Learned Annex-D: unit has successfully detected Annex-D LMI (ANSI T1.617 Annex D) (4) Learned Annex-A: unit has successfully detected Annex-A LMI (ITU/CCITT Q.933 Annex A) (5) Learned Type 1: unit has successfully detected Type 1 LMI (Cisco, Group of four, LMI) Enumeration: 'disabled': 1, 'learned-annex-a': 4, 'learned-type1': 5, 'learned-annex-d': 3, 'searching': 2.

The count of all management octets received. Same as ifInOctets in mib-2.

The count of management packets received that could not be delivered because of errors. Same as ifInErrors in mib-2.

The count of all management octets transmitted. Same as ifOutOctets in mib-2.

The current operational state. Same as ifOperStatus in mib-2. (1) link up (2) link down (30 test Enumeration: 'down': 2, 'testing': 3, 'up': 1.

The count of all management datagrams received. Same as ipInReceives in mib-2.

The count of management datagrams received that were discarded because of errors in their IP headers. Same as ipInHdrErrors in mib-2.

The count of management datagrams received that were discarded because unexpected or invalid IP addresses in their IP headers. Same as ipInAddrErrors in mib-2.

The count of management datagrams received that were discarded because of unsupported protocols. Same as ipInUnknownProtos in mib-2.

The count of management datagrams received that were discarded for reasons other than a problem with the datagram. Same as ipInDiscards in mib-2.

The count of management datagrams received that were delivered to IP client-protocols. Same as ipInDelivers in mib-2.

The count of all outgoing management datagrams originating in this node. Same as ipOutRequests in mib-2.

The count of outgoing management datagrams that were discarded for reasons other than a problem with the datagram. Same as ipOutDiscards in mib-2.

The count of outgoing management datagrams that were discarded because no route could be found for transmission. Same as ipOutNoRoutes in mib-2.

The count of all management ICMP messages received. Same as icmpInMsgs in mib-2.

The count of management ICMP messages received with errors. Same as icmpInErrors in mib-2.

The count of management ICMP Destination Unreachable messages received. Same as icmpInDestUnreachs in mib-2.

The count of management ICMP Time Exceeded messages received. Same as icmpInTimeExcds in mib-2.

The count of management ICMP Parameter Problem messages received. Same as icmpInParmProbs in mib-2.

The count of management ICMP Redirect messages received. Same as icmpInRedirects in mib-2.

The count of management ICMP Echo messages received. Same as icmpInEchos in mib-2.

The count of management ICMP Echo Reply messages received. Same as icmpInEchoReps in mib-2.

The count of all outgoing management ICMP messages originating in this node. Same as icmpOutMsgs in mib-2.

The count of outgoing management ICMP messages not transmitted due problems found by the ICMP layer. which this entity did Same as icmpOutErrors in mib-2.

The count of outgoing management ICMP Destination Unreachable messages. Same as icmpOutDestUnreachs in mib-2.

The count of outgoing management ICMP Parameter Problem messages. Same as icmpOutParmProbs in mib-2.

The count of outgoing management ICMP Redirect messages. Same as icmpOutRedirects in mib-2.

The count of management outgoing ICMP Echo messages. Same as icmpOutEchos in mib-2.

The count of management outgoing ICMP Echo Reply messages. Same as icmpOutEchoReps in mib-2.

The count of all management UDP datagrams received. Same as udpInDatagrams in mib-2.

The count of all management UDP datagrams sent. Same as udpOutDatagrams in mib-2.

The count of all management UDP datagrams received with no application at the destination port. Same as udpNoPorts in mib-2.

The count of the times management TCP connections have made a direct state transition from CLOSED to SYN-SENT. Same as tcpActiveOpens in mib-2.

The count of the times management TCP connections have made a direct state transition from CLOSED to SYN-RCVD. Same as tcpPassiveOpens in mib-2.

The count of the times management TCP connections have made a direct state transition from SYN-SENT or SYN-RCVD to CLOSED state, plus the count of the times TCP connections have made a direct state transition from SYN-RCVD to LISTEN. Same as tcpAttemptFails in mib-2.

The count of the management TCP connections in state ESTABLISHED or CLOSE-WAIT. Same as tcpCurrEstab in mib-2.

The count of all the management segments received. Same as tcpInSegs in mib-2.

The count of all the management segments sent. Same as tcpOutSegs in mib-2.

The throughput per interface table. These values are accumulated across all DLCIs.

An entry in the throughput per interface table.

Interface for which the statistics apply. (1) DTE interface (2) DDS interface Enumeration: 'dds': 2, 'dte': 1.

The number of framed bytes that have been received on this interface.

The number of framed bytes that have been transmit on this interface.

The number of frames that have been received on this interface.

The number of frames that have been transmit on this interface.

The number of frames with CRC errors received on this interface.

The number of aborted frames received on this interface.

The number of BPV errors received on this interface.

Layer 2 statistics on a per-DLCI basis. Transmit direction is from DTE to WAN and receive direction is from the WAN towards the DTE.

The Statistics for a particular Data Link Connection Management Interface (DLCI).

This value must be in the range 1-3. Other than that, this value is ignored as all three will return the same result.

The DLCI value in which the Statistics are associated.

The amount of time elapsed since this DLCI was first detected through traffic sensing or in an LMI message (in seconds).

The amount of elapsed time since this DLCI last changed state from active to inactive or vice versa (in seconds).

The number of bytes that have been received from the WAN towards the DTE on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number of bytes that have been transmit from the DTE towards the WAN on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number of frames that have been received from the WAN towards to the DTE on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number of frames that have been transmit from the DTE towards the WAN on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number frames received from the WAN towards the DTE that have had the Forward Explict Congestion Notification (FECN) bit set on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number frames received from the WAN towards the DTE that have had the Backward Explict Congestion Notification (BECN) bit set on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number frames received from the WAN towards the DTE that have had the Discard Eligibility (DE) bit set on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number frames transmit towards the WAN from the DTE that have had the Discard Eligibility (DE) bit set on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number of bits/sec received from the WAN on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The number of bits/sec transmit to the WAN on this DLCI. This count will include any frames that are terminated by the unit and do not pass through to the opposite interface (management and networking data).

The Committed Information Rate (CIR) for this DLCI. This can come form one of three sources: From the LMI Full Status Response, configured by the user, or the DTE line rate (default).

The total amount of time that the DLCI has been up as reproted by the LMI Full Status Response (in seconds).

The total amount of time that the DLCI has been declared down (in seconds). A DLCI is Down if it's explicitly declared Inactive through LMI or if it's missing from the LMI Full Status message or if there is no Full Status message at all.

The source of the CIR value for this DLCI. (1) CIR acquired from LMI message. Will override user configured CIR. This feature is not supported by all Frame Relay DCE (switches). (2) CIR configured by user. (3) CIR is DTE Line Rate. Default if CIR is not set by one of the other methods. Enumeration: 'cir-is-dte-datarate': 3, 'cir-configured-by-user': 2, 'cir-acquired-from-lmi': 1.

The current state of the DLCI: (1) DLCI marked active in last full status LMI (2) DLCI in last full status LMI but not marked active (3) DLCI has never been seen in a full status LMI (4) DLCI was seen at least once in a full status LMI but was not in the last full status LMI (5) the full status LMI has timed out; all previously active or inactive DLCIs are changed to this state (6) DLCI was detected in the traffic stream and a full status LMI has not been received so the state cannot be determined yet. Enumeration: 'pvc-lmi-timeout': 5, 'pvc-undetermined': 6, 'pvc-active': 1, 'pvc-not-in-lmi': 4, 'pvc-inactive': 2, 'pvc-unprovisioned': 3.

The number of times the smperPerfThruputPerDlciPvcState transitions from pvc-active or pvc-undetermined to one of the other (inactive) states.

The measure of the percentage time the DLCI is available: UpTime/CreateTime or zero if CreateTime = 0. (in 1/1000 per cent; i.e. availability = 1000 converts to 1%).

Mean Time Between Service Outages: UpTime/OutageCount or zero if OutageCount = 0 (in seconds).

Mean Time to ServiceRestoral: DownTime/OutageCount or zero if OutageCount = 0 (in seconds).

The encapsulation protocol seen in the last frame analyzed on this DLCI: (1) DLCI is the LMI DLCI or no frames have been analyzed (2) The encapsulation is per rfc1490 (3) The encapsulation is per Cisco proprietary (4) The encapsulation is per Annex-G (X.25 over frame relay) (5) The encapsulation is not one of the above. Enumeration: 'encap-other': 5, 'encap-1490': 2, 'encap-annex-g': 4, 'encap-cisco': 3, 'encap-na': 1.

The status of the per-DLCI utilization alarm in the receive direction. (1) there is no alarm condition; utilization is under the configured CIR percentage threshold; if traps are enabled and the alarm had been previously triggered, a utilization alarm clear trap will be sent. (2) the utilization has been over the configured CIR percentage threshold for less than the configured duration. (3) the utilization has been over the configured CIR percentage threshold for more than the configured duration; if traps are enabled a utilization exceeded trap will be sent. (4) the utilization has been under the configured CIR percentage threshold for less than the configured duration. Enumeration: 'alarm-under-threshold': 4, 'clear': 1, 'alarm': 3, 'over-threshold': 2.

The status of the per-DLCI utilization alarm in the transmit direction. (1) there is no alarm condition; utilization is under the configured CIR percentage threshold; if traps are enabled and the alarm had been previously triggered, a utilization alarm clear trap will be sent. (2) the utilization has been over the configured CIR percentage threshold for less than the configured duration. (3) the utilization has been over the configured CIR percentage threshold for more than the configured duration; if traps are enabled a utilization exceeded trap will be sent. (4) the utilization has been under the configured CIR percentage threshold for less than the configured duration. Enumeration: 'alarm-under-threshold': 4, 'clear': 1, 'alarm': 3, 'over-threshold': 2.

The Excess Information Rate. This is defined to be the maximum rate traffic is (supposed to be) allowed to burst to.

Allows the user to zero out all the interface statistics in the DTE portion of the ThruputPerIntf statistics table. (1) Clear DTE interface statistics command. Enumeration: 'clear-statistics': 1.

Allows the user to zero out all the interface statistics in the DDS portion of the ThruputPerIntf statistics table. (1) Clear WAN interface statistics command. Enumeration: 'clear-statistics': 1.

Allows the user to zero out all the statistics in the ThruputPerIntf statistics table. Enumeration: 'clear-statistics': 1.

Allows the user to zero out all the per-DLCI statistics in the ThruputPerDlci statistics table and the the short term statistics tables. (1) Clear layer 2 per-DLCI statistics command. Enumeration: 'clear-statistics': 1.

Allows the user to zero out all the statistics in the ThruputPerIntf and ThruputPerDlci statistics tables and in the short term statistics tables. (1) Clear all interface and layer 2 per-DLCI statistics. Enumeration: 'clear-statistics': 1.

Allows the user to remove a Dlci from the short term statistics tables.

Allows the user to replace one DLCI in the short-term statistics table with another one.

Allows the user to replace one DLCI in the short-term statistics table with another one.

A Dlci that is in the short-term stats table. Index by this Dlci value to identify the statistics entry to be replaced.

A Dlci that is to replace another in the short-term stats table. Index by this Dlci value to identify the statistics entry to do the replacing.

Allows the user to reset the availability statistics of an individual Dlci within the short-term stats table.

Allows the user to reset the availability statistics of all Dlci's within the short-term stats table.

Allows the user to reset the count statistics of an individual Dlci within the short-term stats table.

Allows the user to reset the count statistics of all Dlci's within the short-term stats table.

Allows the user to reset both the count and availability statistics of an individual Dlci within the short-term stats table.

Allows the user to reset both the count and the availability statistics of all Dlci's within the short-term stats table.

The Short Term Statistics on the Network Layer protocol for each DLCI. These are protocol-based per-DLCI statistics. The Short Term model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval).

The Network Layer Short Term Statistics for a particular DLCI. This table organizes statistics by high-layer network protocol.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value with which the Statistics are associated.

The total number of received Network Layer bytes that have been counted on this DLCI.

The total number of transmitted Network Layer bytes that have been counted on this DLCI.

The number of received IP bytes that have been counted on this DLCI.

The number of transmitted IP bytes that have been counted on this DLCI.

The number of received IPX bytes that have been counted on this DLCI.

The number of transmitted IPX bytes that have been counted on this DLCI.

The number of received SNA bytes that have been counted on this DLCI.

The number of transmitted SNA bytes that have been counted on this DLCI.

The number of received ARP bytes that have been counted on this DLCI.

The number of transmitted ARP bytes that have been counted on this DLCI.

The number of received Cisco protocol bytes that have been counted on this DLCI.

The number of transmitted Cisco protocol bytes that have been counted on this DLCI.

The number of received bytes on this DLCI from protocols that are not counted elsewhere in this table.

The number of transmitted bytes on this DLCI from protocols that are not counted elsewhere in this table.

The number of received VNIP protocol bytes that have been counted on this DLCI.

The number of transmitted VNIP protocol bytes that have been counted on this DLCI.

The number of received Annex G protocol bytes that have been counted on this DLCI.

The number of transmitted Annex G protocol bytes that have been counted on this DLCI.

The Short Term Statistics on Network Layer protocols summed across all DLCIs.

The Network Layer Short Term Statistics across all DLCIs.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The total number of received Network Layer bytes that have been counted across all DLCIs.

The total number of transmitted Network Layer bytes that have been counted across all DLCIs.

The number of received IP bytes that have been counted across all DLCIs.

The number of transmitted IP bytes that have been counted across all DLCIs.

The number of received IPX bytes that have been counted across all DLCIs.

The number of transmitted IPX bytes that have been counted across all DLCIs.

The number of received SNA bytes that have been counted across all DLCIs.

The number of transmitted SNA bytes that have been counted across all DLCIs.

The number of received ARP bytes that have been counted across all DLCIs.

The number of transmitted ARP bytes that have been counted across all DLCIs.

The number of received Cisco protocol bytes that have been counted across all DLCIs.

The number of transmitted Cisco protocol bytes that have been counted across all DLCIs.

The number of received bytes across all DLCIs from protocols that are not counted elsewhere in this table.

The number of transmitted bytes across all DLCIs from protocols that are not counted elsewhere in this table.

The number of received VNIP protocol bytes that have been counted across all DLCIs.

The number of transmitted VNIP protocol bytes that have been counted across all DLCIs.

The number of received Annex G protocol bytes that have been counted across all DLCIs.

The number of transmitted Annex G protocol bytes that have been counted across all DLCIs.

The Short Term Statistics on the IP protocol for each DLCI.

The IP Short Term Statistics for a particular DLCI.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value with which the Statistics are associated.

The total number of received IP bytes that have been counted on this DLCI.

The total number of transmitted IP bytes that have been counted on this DLCI.

The number of received TCP over IP bytes that have been counted on this DLCI.

The number of transmitted TCP over IP bytes that have been counted on this DLCI.

The number of received UDP over IP bytes that have been counted on this DLCI.

The number of transmitted UDP over IP bytes that have been counted on this DLCI.

The number of received ICMP over IP bytes that have been counted on this DLCI.

The number of transmitted ICMP over IP bytes that have been counted on this DLCI.

The number of received bytes on this DLCI from protocols over IP that are not counted elsewhere in this table.

The number of transmitted bytes on this DLCI from protocols over IP that are not counted elsewhere in this table.

The number of received IGRP over IP bytes that have been counted on this DLCI.

The number of transmitted IGRP over IP bytes that have been counted on this DLCI.

The Short Term Statistics on the IP protocol for each DLCI.

The IP Short Term Statistics across all DLCIs.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The total number of received IP bytes that have been counted across all DLCIs.

The total number of transmitted IP bytes that have been counted across all DLCIs.

The number of received TCP over IP bytes that have been counted across all DLCIs.

The number of transmitted TCP over IP bytes that have been counted across all DLCIs.

The number of received UDP over IP bytes that have been counted across all DLCIs.

The number of transmitted UDP over IP bytes that have been counted across all DLCIs.

The number of received ICMP over IP bytes that have been counted across all DLCIs.

The number of transmitted ICMP over IP bytes that have been counted across all DLCIs.

The number of received bytes across all DLCIs from protocols over IP that are not counted elsewhere in this table.

The number of transmitted bytes across all DLCIs from protocols over IP that are not counted elsewhere in this table.

The number of received IGRP over IP bytes that have been counted across all DLCIs.

The number of transmitted IGRP over IP bytes that have been counted across all DLCIs.

Short Term Statistics on the ICMP protocol for each DLCI.

The ICMP Short Term Statistics for a particular DLCI.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value in which the Statistics are associated.

The total number of ICMP bytes that have been counted on this DLCI.

The total number of ICMP bytes that have been counted on this DLCI.

The number of bytes in ICMP ECHO repies that have been counted on this DLCI.

The number of bytes in ICMP ECHO repies that have been counted on this DLCI.

The number of bytes in ICMP destination unreachables that have been counted on this DLCI.

The number of bytes in ICMP destination unreachables that have been counted on this DLCI.

The number of bytes in ICMP source quenches that have been counted on this DLCI.

The number of bytes in ICMP source quenches that have been counted on this DLCI.

The number of bytes in ICMP redirects that have been counted on this DLCI.

The number of bytes in ICMP redirects that have been counted on this DLCI.

The number of bytes in ICMP ECHO requests that have been counted on this DLCI.

The number of bytes in ICMP ECHO requests that have been counted on this DLCI.

The number of bytes in ICMP time exceededs that have been counted on this DLCI.

The number of bytes in ICMP time exceededs that have been counted on this DLCI.

The number of bytes in ICMP parameter problems that have been counted on this DLCI.

The number of bytes in ICMP parameter problems that have been counted on this DLCI.

The number of bytes in ICMP timestamp requests that have been counted on this DLCI.

The number of bytes in ICMP timestamp requests that have been counted on this DLCI.

The number of bytes in ICMP timestamp replies that have been counted on this DLCI.

The number of bytes in ICMP timestamp replies that have been counted on this DLCI.

The number of bytes in ICMP address mask requests that have been counted on this DLCI.

The number of bytes in ICMP address mask requests that have been counted on this DLCI.

The number of bytes in ICMP address mask replies that have been counted on this DLCI.

The number of bytes in ICMP address mask replies that have been counted on this DLCI.

The number of bytes in ICMP packet too bigs that have been counted on this DLCI.

The number of bytes in ICMP packet too bigs that have been counted on this DLCI.

The number of bytes in ICMP group membership queries that have been counted on this DLCI.

The number of bytes in ICMP group membership queries that have been counted on this DLCI.

The number of bytes in ICMP group membership reports that have been counted on this DLCI.

The number of bytes in ICMP group membership reports that have been counted on this DLCI.

The number of bytes in ICMP group membership reductions that have been counted on this DLCI.

The number of bytes in ICMP group membership reductions that have been counted on this DLCI.

Short Term Statistics on the ICMP protocol across all DLCIs.

The ICMP Short Term Statistics across all DLCIs.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The total number of ICMP bytes that have been counted across all DLCIs.

The total number of ICMP bytes that have been counted across all DLCIs.

The number of bytes in ICMP ECHO repies that have been counted across all DLCIs.

The number of bytes in ICMP ECHO repies that have been counted across all DLCIs.

The number of bytes in ICMP destination unreachables that have been counted across all DLCIs.

The number of bytes in ICMP destination unreachables that have been counted across all DLCIs.

The number of bytes in ICMP source quenches that have been counted across all DLCIs.

The number of bytes in ICMP source quenches that have been counted across all DLCIs.

The number of bytes in ICMP redirects that have been counted across all DLCIs.

The number of bytes in ICMP redirects that have been counted across all DLCIs.

The number of bytes in ICMP ECHO requests that have been counted across all DLCIs.

The number of bytes in ICMP ECHO requests that have been counted across all DLCIs.

The number of bytes in ICMP time exceededs that have been counted across all DLCIs.

The number of bytes in ICMP time exceededs that have been counted across all DLCIs.

The number of bytes in ICMP parameter problems that have been counted across all DLCIs.

The number of bytes in ICMP parameter problems that have been counted across all DLCIs.

The number of bytes in ICMP timestamp requests that have been counted across all DLCIs.

The number of bytes in ICMP timestamp requests that have been counted across all DLCIs.

The number of bytes in ICMP timestamp replies that have been counted across all DLCIs.

The number of bytes in ICMP timestamp replies that have been counted across all DLCIs.

The number of bytes in ICMP address mask requests that have been counted across all DLCIs.

The number of bytes in ICMP address mask requests that have been counted across all DLCIs.

The number of bytes in ICMP address mask replies that have been counted across all DLCIs.

The number of bytes in ICMP address mask replies that have been counted across all DLCIs.

The number of bytes in ICMP packet too bigs that have been counted across all DLCIs.

The number of bytes in ICMP packet too bigs that have been counted across all DLCIs.

The number of bytes in ICMP group membership queries that have been counted across all DLCIs.

The number of bytes in ICMP group membership queries that have been counted across all DLCIs.

The number of bytes in ICMP group membership reports that have been counted across all DLCIs.

The number of bytes in ICMP group membership reports that have been counted across all DLCIs.

The number of bytes in ICMP group membership reductions that have been counted across all DLCIs.

The number of bytes in ICMP group membership reductions that have been counted across all DLCIs.

The Short Term Statistics on the Application protocol for each DLCI.

The Application Short Term Statistics for a particular DLCI.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value with which the Statistics are associated.

The number of received SNMP bytes that have been counted on this DLCI.

The number of transmitted SNMP bytes that have been counted on this DLCI.

The number of received SNMP TRAP bytes that have been counted on this DLCI.

The number of transmitted SNMP TRAP bytes that have been counted on this DLCI.

The number of received HTTP bytes that have been counted on this DLCI.

The number of transmitted HTTP bytes that have been counted on this DLCI.

The number of received Telnet bytes that have been counted on this DLCI.

The number of transmitted Telnet bytes that have been counted on this DLCI.

The number of received SMTP bytes that have been counted on this DLCI.

The number of transmitted SMTP bytes that have been counted on this DLCI.

The number of received FTP bytes that have been counted on this DLCI.

The number of transmitted FTP bytes that have been counted on this DLCI.

The number of received TFTP bytes that have been counted on this DLCI.

The number of transmitted TFTP bytes that have been counted on this DLCI.

The number of received bytes of User Defined Protocol #1 that have been counted on this DLCI.

The number of transmitted bytes of User Defined Protocol #1 that have been counted on this DLCI.

The number of received bytes of User Defined Protocol #2 that have been counted on this DLCI.

The number of transmitted bytes of User Defined Protocol #2 that have been counted on this DLCI.

The number of received bytes of User Defined Protocol #3 that have been counted on this DLCI.

The number of transmitted bytes of User Defined Protocol #3 that have been counted on this DLCI.

The number of received bytes of User Defined Protocol #4 that have been counted on this DLCI.

The number of transmitted bytes of User Defined Protocol #4 that have been counted on this DLCI.

The Short Term Statistics on the Application protocol across all DLCIs.

The Application Short Term Statistics across all DLCIs..

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The number of received SNMP bytes that have been counted across all DLCIs.

The number of transmitted SNMP bytes that have been counted across all DLCIs.

The number of received SNMP TRAP bytes that have been counted across all DLCIs.

The number of transmitted SNMP TRAP bytes that have been counted across all DLCIs.

The number of received HTTP bytes that have been counted across all DLCIs.

The number of transmitted HTTP bytes that have been counted across all DLCIs.

The number of received Telnet bytes that have been counted across all DLCIs.

The number of transmitted Telnet bytes that have been counted across all DLCIs.

The number of received SMTP bytes that have been counted across all DLCIs.

The number of transmitted SMTP bytes that have been counted across all DLCIs.

The number of received FTP bytes that have been counted across all DLCIs.

The number of transmitted FTP bytes that have been counted across all DLCIs.

The number of received TFTP bytes that have been counted across all DLCIs.

The number of transmitted TFTP bytes that have been counted across all DLCIs.

The number of received bytes of User Defined Protocol #1 that have been counted across all DLCIs.

The number of transmitted bytes of User Defined Protocol #1 that have been counted across all DLCIs.

The number of received bytes of User Defined Protocol #2 that have been counted across all DLCIs.

The number of transmitted bytes of User Defined Protocol #2 that have been counted across all DLCIs.

The number of received bytes of User Defined Protocol #3 that have been counted across all DLCIs.

The number of transmitted bytes of User Defined Protocol #3 that have been counted across all DLCIs.

The number of received bytes of User Defined Protocol #4 that have been counted across all DLCIs.

The number of transmitted bytes of User Defined Protocol #4 that have been counted across all DLCIs.

The Short Term Statistics on the Routing protocol for each DLCI.

The Routing Short Term Statistics for a particular DLCI.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value with which the Statistics are associated.

The number of received OSPF bytes that have been counted on this DLCI.

The number of transmitted OSPF bytes that have been counted on this DLCI.

The number of received RIP bytes that have been counted on this DLCI.

The number of transmitted RIP bytes that have been counted on this DLCI.

The number of received Netbios bytes that have been counted on this DLCI.

The number of transmitted Netbios bytes that have been counted on this DLCI.

The Short Term Statistics on the Routing protocol across all DLCIs.

The Routing Short Term Statistics across all DLCIs.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The number of received OSPF bytes that have been counted across all DLCIs.

The number of transmitted OSPF bytes that have been counted across all DLCIs.

The number of received RIP bytes that have been counted across all DLCIs.

The number of transmitted RIP bytes that have been counted across all DLCIs.

The number of received Netbios bytes that have been counted across all DLCIs.

The number of transmitted Netbios bytes that have been counted across all DLCIs.

Short Term Statistics on the IPX protocol for each DLCI.

The IPX Short Term Statistics for a particular DLCI.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value in which the Statistics are associated.

The total number of IPX bytes that have been counted on this DLCI.

The total number of IPX bytes that have been counted on this DLCI.

The number of SPX over IPX bytes that have been counted on this DLCI.

The number of SPX over IPX bytes that have been counted on this DLCI.

The number of NCP over IPX bytes that have been counted on this DLCI.

The number of NCP over IPX bytes that have been counted on this DLCI.

The number of SAP over IPX bytes that have been counted on this DLCI.

The number of SAP over IPX bytes that have been counted on this DLCI.

The number of RIP over IPX bytes that have been counted on this DLCI.

The number of RIP over IPX bytes that have been counted on this DLCI.

The number of NETBIOS over IPX bytes that have been counted on this DLCI.

The number of NETBIOS over IPX bytes that have been counted on this DLCI.

The number of received bytes on this DLCI from protocols over IPX that are not counted elsewhere in this table.

The number of transmitted bytes on this DLCI from protocols over IPX that are not counted elsewhere in this table.

Short Term Statistics on the IPX protocol across all DLCIs.

The IPX Short Term Statistics across all DLCIs.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The total number of IPX bytes that have been counted across all DLCIs.

The total number of IPX bytes that have been counted across all DLCIs.

The number of SPX over IPX bytes that have been counted across all DLCIs.

The number of SPX over IPX bytes that have been counted across all DLCIs.

The number of NCP over IPX bytes that have been counted across all DLCIs.

The number of NCP over IPX bytes that have been counted across all DLCIs.

The number of SAP over IPX bytes that have been counted across all DLCIs.

The number of SAP over IPX bytes that have been counted across all DLCIs.

The number of RIP over IPX bytes that have been counted across all DLCIs.

The number of RIP over IPX bytes that have been counted across all DLCIs.

The number of NETBIOS over IPX bytes that have been counted across all DLCIs.

The number of NETBIOS over IPX bytes that have been counted across all DLCIs.

The number of received bytes across all DLCIs from protocols over IPX that are not counted elsewhere in this table.

The number of transmitted bytes across all DLCIs from protocols over IPX that are not counted elsewhere in this table.

Short Term Statistics on the SNA protocol for each DLCI.

The SNA Short Term Statistics for a particular DLCI.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value in which the Statistics are associated.

The total number of SNA bytes that have been counted on this DLCI.

The total number of SNA bytes that have been counted on this DLCI.

The number of SNA Subarea bytes that have been counted on this DLCI.

The number of SNA Subarea bytes that have been counted on this DLCI.

The number of SNA Periph bytes that have been counted on this DLCI.

The number of SNA Periph bytes that have been counted on this DLCI.

The number of SNA Appn bytes that have been counted on this DLCI.

The number of SNA Appn bytes that have been counted on this DLCI.

The number of SNA Netbios bytes that have been counted on this DLCI.

The number of SNA Netbios bytes that have been counted on this DLCI.

The number of received bytes on this DLCI from protocols over SNA that are not counted elsewhere in this table.

The number of transmitted bytes on this DLCI from protocols over SNA that are not counted elsewhere in this table.

Short Term Statistics on the SNA protocol across all DLCIs.

The SNA Short Term Statistics across all DLCIs.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The total number of SNA bytes that have been counted across all DLCIs.

The total number of SNA bytes that have been counted across all DLCIs.

The number of SNA Subarea bytes that have been counted across all DLCIs.

The number of SNA Subarea bytes that have been counted across all DLCIs.

The number of SNA Periph bytes that have been counted across all DLCIs.

The number of SNA Periph bytes that have been counted across all DLCIs.

The number of SNA Appn bytes that have been counted across all DLCIs.

The number of SNA Appn bytes that have been counted across all DLCIs.

The number of SNA Netbios bytes that have been counted across all DLCIs.

The number of SNA Netbios bytes that have been counted across all DLCIs.

The number of received bytes across all DLCIs from protocols over SNA that are not counted elsewhere in this table.

The number of transmitted bytes across all DLCIs from protocols over SNA that are not counted elsewhere in this table.

Short Term Statistics on the ARP protocol for each DLCI.

The ARP Short Term Statistics for a particular DLCI.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value in which the Statistics are associated.

The total number of ARP bytes that have been counted on this DLCI.

The total number of ARP bytes that have been counted on this DLCI.

The number of ARP request bytes that have been counted on this DLCI.

The number of ARP request bytes that have been counted on this DLCI.

The number of ARP reply bytes that have been counted on this DLCI.

The number of ARP reply bytes that have been counted on this DLCI.

The number of RARP request bytes that have been counted on this DLCI.

The number of RARP request bytes that have been counted on this DLCI.

The number of RARP reply bytes that have been counted on this DLCI.

The number of RARP reply bytes that have been counted on this DLCI.

The number of INARP request bytes that have been counted on this DLCI.

The number of INARP request bytes that have been counted on this DLCI.

The number of INARP reply bytes that have been counted on this DLCI.

The number of INARP reply bytes that have been counted on this DLCI.

The number of received bytes on this DLCI from ARP message types that are not counted elsewhere in this table.

The number of transmitted bytes on this DLCI from ARP message types that are not counted elsewhere in this table.

Short Term Statistics on the ARP protocol across all DLCIs.

The ARP Short Term Statistics across all DLCIs.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The total number of ARP bytes that have been counted across all DLCIs.

The total number of ARP bytes that have been counted across all DLCIs.

The number of ARP request bytes that have been counted across all DLCIs.

The number of ARP request bytes that have been counted across all DLCIs.

The number of ARP reply bytes that have been counted across all DLCIs.

The number of ARP reply bytes that have been counted across all DLCIs.

The number of RARP request bytes that have been counted across all DLCIs.

The number of RARP request bytes that have been counted across all DLCIs.

The number of RARP reply bytes that have been counted across all DLCIs.

The number of RARP reply bytes that have been counted across all DLCIs.

The number of INARP request bytes that have been counted across all DLCIs.

The number of INARP request bytes that have been counted across all DLCIs.

The number of INARP reply bytes that have been counted across all DLCIs.

The number of INARP reply bytes that have been counted across all DLCIs.

The number of received bytes across all DLCIs from ARP message types that are not counted elsewhere in this table.

The number of transmitted bytes across all DLCIs from ARP message types that are not counted elsewhere in this table.

Short Term Statistics on LMI protocol for each DLCI.

The LMI Short Term Statistics for a particular DLCI.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value with which the Statistics are associated.

The total number of received LMI bytes counted on this DLCI.

The total number of transmitted LMI bytes counted on this DLCI.

The number of bytes received in Link Integrity Verification Only (LIVO) enquiries on this DLCI.

The number of bytes transmitted in Link Integrity Verification Only (LIVO) enquiries on this DLCI.

The number of bytes received in Link Integrity Verification Only (LIVO) statuses on this DLCI.

The number of bytes transmitted in Link Integrity Verification Only (LIVO) statuses on this DLCI.

The number of bytes received in Full Status enquiries on this DLCI.

The number of bytes transmitted in Full Status enquiries on this DLCI.

The number of bytes received in Full Status messages on this DLCI.

The number of bytes transmitted in Full Status messages on this DLCI.

The number of received bytes on this DLCI from LMI protocols that are not counted elsewhere (other than Total) in this table.

The number of transmitted bytes on this DLCI from LMI protocols that are not counted elsewhere (other than Total) in this table.

Short Term Statistics on LMI protocol across all DLCIs.

The LMI Short Term Statistics across all DLCIs.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

OBSOLETE.

The total number of received LMI bytes counted on this DLCI.

The total number of transmitted LMI bytes counted on this DLCI.

The number of bytes received in Link Integrity Verification Only (LIVO) enquiries on this DLCI.

The number of bytes transmitted in Link Integrity Verification Only (LIVO) enquiries on this DLCI.

The number of bytes received in Link Integrity Verification Only (LIVO) statuses on this DLCI.

The number of bytes transmitted in Link Integrity Verification Only (LIVO) statuses on this DLCI.

The number of bytes received in Full Status enquiries on this DLCI.

The number of bytes transmitted in Full Status enquiries on this DLCI.

The number of bytes received in Full Status messages on this DLCI.

The number of bytes transmitted in Full Status messages on this DLCI.

The number of received bytes on this DLCI from LMI protocols that are not counted elsewhere (other than Total) in this table.

The number of transmitted bytes on this DLCI from LMI protocols that are not counted elsewhere (other than Total) in this table.

Long Term Statistics by DLCI, protocol, and interval. LT statistics are collected on a configurable set of DLCIs and protocols. There are 96 intervals maintained each with a duration defined by the Long Term Timer. Interval 96 is the current window and Interval 1 is furthest back in time (96xLT Timer seconds ago). (CfgFrPerfTimersLTInterval).

The Long Term Statistic for a particular DLCI, protocol and interval.

The DLCI monitored for the statistics. The Long Term DLCI filter must first be configured (CfgFrPerfLTDlciFilterEntry).

The type of protocol monitored for the statistics. Enumeration: 'gp-mem-report-icmp-ip-tx-bc': 69, 'addr-mask-req-icmp-ip-rx-bc': 62, 'src-quench-icmp-ip-tx-bc': 47, 'lmi-full-enq-tx-bc': 159, 'gp-mem-query-icmp-ip-tx-bc': 67, 'thru-de-rx-c': 136, 'other-ip-tx-bc': 75, 'annex-g-rx-bc': 172, 'snmptrap-udp-ip-rx-bc': 38, 'user-defined-2-rx-bc': 122, 'lmi-livo-stat-rx-bc': 158, 'icmp-ip-tx-bc': 41, 'sna-appn-rx-bc': 112, 'spx-ipx-rx-bc': 80, 'thru-byte-rx-bc': 128, 'icmp-ip-rx-bc': 42, 'cir-percent-range7-tx-bc': 149, 'netbios-ssn-tcp-ip-rx-bc': 16, 'netbios-ipx-rx-bc': 88, 'dest-unr-icmp-ip-rx-bc': 46, 'tftp-udp-ip-rx-bc': 30, 'snmp-udp-ip-rx-bc': 36, 'cir-percent-range4-rx-bc': 144, 'thru-de-tx-c': 135, 'cir-percent-range2-rx-bc': 140, 'echoreq-icmp-ip-tx-bc': 51, 'telnet-tcp-ip-tx-bc': 7, 'cir-percent-range1-tx-bc': 137, 'lmi-rx-bc': 154, 'user-defined-1-rx-bc': 120, 'udp-ip-rx-bc': 22, 'param-prob-icmp-ip-rx-bc': 56, 'vnip-tx-bc': 169, 'user-defined-4-rx-bc': 126, 'addr-mask-req-icmp-ip-tx-bc': 61, 'ncp-ipx-rx-bc': 82, 'ftp-tcp-ip-rx-bc': 6, 'rarp-rep-rx-bc': 100, 'cir-percent-range3-tx-bc': 141, 'sna-netbios-tx-bc': 113, 'smtp-tcp-ip-tx-bc': 9, 'netbios-ipx-tx-bc': 87, 'thru-fecn-tx-c': 131, 'snmp-udp-ip-tx-bc': 35, 'gp-mem-reduct-icmp-ip-rx-bc': 72, 'ip-rx-bc': 2, 'dest-unr-icmp-ip-tx-bc': 45, 'cir-percent-range2-tx-bc': 139, 'inarp-req-tx-bc': 101, 'arp-req-tx-bc': 93, 'addr-mask-rep-icmp-ip-rx-bc': 64, 'cisco-rx-bc': 116, 'rarp-rep-tx-bc': 99, 'redirect-icmp-ip-tx-bc': 49, 'other-ipx-rx-bc': 90, 'spx-ipx-tx-bc': 79, 'echorep-icmp-ip-tx-bc': 43, 'param-prob-icmp-ip-tx-bc': 55, 'ospf-ip-tx-bc': 73, 'echorep-icmp-ip-rx-bc': 44, 'redirect-icmp-ip-rx-bc': 50, 'thru-fecn-rx-c': 132, 'lmi-tx-bc': 153, 'http-tcp-ip-tx-bc': 13, 'cir-percent-range8-tx-bc': 151, 'sap-ipx-rx-bc': 84, 'thru-becn-tx-c': 133, 'sna-tx-bc': 105, 'other-ipx-tx-bc': 89, 'cir-percent-range4-tx-bc': 143, 'ipx-tx-bc': 77, 'echoreq-icmp-ip-rx-bc': 52, 'other-rx-bc': 118, 'cir-percent-range1-rx-bc': 138, 'smtp-tcp-ip-rx-bc': 10, 'thru-frame-rx-c': 130, 'total-downtime': 166, 'addr-mask-rep-icmp-ip-tx-bc': 63, 'vnip-rx-bc': 170, 'arp-rep-rx-bc': 96, 'user-defined-2-tx-bc': 121, 'annex-g-tx-bc': 171, 'rip-udp-ip-rx-bc': 40, 'arp-rx-bc': 92, 'src-quench-icmp-ip-rx-bc': 48, 'rip-ipx-tx-bc': 85, 'user-defined-3-tx-bc': 123, 'cir-percent-range3-rx-bc': 142, 'lmi-other-tx-bc': 163, 'lmi-full-enq-rx-bc': 160, 'user-defined-3-rx-bc': 124, 'igrp-rx-bc': 168, 'sna-periph-rx-bc': 110, 'arp-rep-tx-bc': 95, 'rip-udp-ip-tx-bc': 39, 'other-ip-rx-bc': 76, 'tftp-udp-ip-tx-bc': 29, 'netbios-dgm-udp-ip-tx-bc': 33, 'rarp-req-tx-bc': 97, 'lmi-other-rx-bc': 164, 'timestamp-rep-icmp-ip-rx-bc': 60, 'snmptrap-udp-ip-tx-bc': 37, 'pkt-too-big-icmp-ip-tx-bc': 65, 'cir-percent-range6-tx-bc': 147, 'cir-percent-range7-rx-bc': 150, 'lmi-livo-stat-tx-bc': 157, 'sna-netbios-rx-bc': 114, 'ip-tx-bc': 1, 'pkt-too-big-icmp-ip-rx-bc': 66, 'ncp-ipx-tx-bc': 81, 'user-defined-4-tx-bc': 125, 'lmi-livo-enq-tx-bc': 155, 'gp-mem-query-icmp-ip-rx-bc': 68, 'gp-mem-report-icmp-ip-rx-bc': 70, 'user-defined-1-tx-bc': 119, 'ospf-ip-rx-bc': 74, 'tcp-ip-rx-bc': 4, 'lmi-livo-enq-rx-bc': 156, 'udp-ip-tx-bc': 21, 'cisco-tx-bc': 115, 'rip-ipx-rx-bc': 86, 'arp-req-rx-bc': 94, 'thru-becn-rx-c': 134, 'sna-appn-tx-bc': 111, 'http-tcp-ip-rx-bc': 14, 'gp-mem-reduct-icmp-ip-tx-bc': 71, 'other-tx-bc': 117, 'igrp-tx-bc': 167, 'timestamp-req-icmp-ip-rx-bc': 58, 'timestamp-rep-icmp-ip-tx-bc': 59, 'time-excd-icmp-ip-rx-bc': 54, 'lmi-full-stat-tx-bc': 161, 'timestamp-req-icmp-ip-tx-bc': 57, 'ftp-tcp-ip-tx-bc': 5, 'netbios-ssn-tcp-ip-tx-bc': 15, 'time-excd-icmp-ip-tx-bc': 53, 'sna-periph-tx-bc': 109, 'sna-subarea-rx-bc': 108, 'telnet-tcp-ip-rx-bc': 8, 'netbios-dgm-udp-ip-rx-bc': 34, 'thru-byte-tx-bc': 127, 'lmi-full-stat-rx-bc': 162, 'inarp-req-rx-bc': 102, 'arp-tx-bc': 91, 'tcp-ip-tx-bc': 3, 'rarp-req-rx-bc': 98, 'thru-frame-tx-c': 129, 'inarp-rep-rx-bc': 104, 'cir-percent-range5-rx-bc': 146, 'ipx-rx-bc': 78, 'sna-subarea-tx-bc': 107, 'cir-percent-range5-tx-bc': 145, 'cir-percent-range6-rx-bc': 148, 'inarp-rep-tx-bc': 103, 'sna-rx-bc': 106, 'total-uptime': 165, 'sap-ipx-tx-bc': 83, 'cir-percent-range8-rx-bc': 152.

The time interval in which the value was collected. Long Term statistis are maintained for 96 intervals with the interval duration defined by (CfgFrPerfTimersLTInterval).

The statistic collected for the given DLCI and protocol and within the given time interval.

This is an alternative method to access the database of long term statistics. The statistics are indexed by DLCI and protocol and are returned in an OCTETSTRING.

The Long Term Statistic for a particular DLCI and protocol.

The DLCI monitored for the statistics.

The protocol monitored for the statistics. Enumeration: 'gp-mem-report-icmp-ip-tx-bc': 69, 'addr-mask-req-icmp-ip-rx-bc': 62, 'src-quench-icmp-ip-tx-bc': 47, 'lmi-full-enq-tx-bc': 159, 'gp-mem-query-icmp-ip-tx-bc': 67, 'thru-de-rx-c': 136, 'other-ip-tx-bc': 75, 'annex-g-rx-bc': 172, 'snmptrap-udp-ip-rx-bc': 38, 'user-defined-2-rx-bc': 122, 'lmi-livo-stat-rx-bc': 158, 'icmp-ip-tx-bc': 41, 'sna-appn-rx-bc': 112, 'spx-ipx-rx-bc': 80, 'thru-byte-rx-bc': 128, 'icmp-ip-rx-bc': 42, 'cir-percent-range7-tx-bc': 149, 'netbios-ssn-tcp-ip-rx-bc': 16, 'netbios-ipx-rx-bc': 88, 'dest-unr-icmp-ip-rx-bc': 46, 'tftp-udp-ip-rx-bc': 30, 'snmp-udp-ip-rx-bc': 36, 'cir-percent-range4-rx-bc': 144, 'thru-de-tx-c': 135, 'cir-percent-range2-rx-bc': 140, 'echoreq-icmp-ip-tx-bc': 51, 'telnet-tcp-ip-tx-bc': 7, 'cir-percent-range1-tx-bc': 137, 'lmi-rx-bc': 154, 'user-defined-1-rx-bc': 120, 'udp-ip-rx-bc': 22, 'param-prob-icmp-ip-rx-bc': 56, 'vnip-tx-bc': 169, 'user-defined-4-rx-bc': 126, 'addr-mask-req-icmp-ip-tx-bc': 61, 'ncp-ipx-rx-bc': 82, 'ftp-tcp-ip-rx-bc': 6, 'rarp-rep-rx-bc': 100, 'cir-percent-range3-tx-bc': 141, 'sna-netbios-tx-bc': 113, 'smtp-tcp-ip-tx-bc': 9, 'netbios-ipx-tx-bc': 87, 'thru-fecn-tx-c': 131, 'snmp-udp-ip-tx-bc': 35, 'gp-mem-reduct-icmp-ip-rx-bc': 72, 'ip-rx-bc': 2, 'dest-unr-icmp-ip-tx-bc': 45, 'cir-percent-range2-tx-bc': 139, 'inarp-req-tx-bc': 101, 'arp-req-tx-bc': 93, 'addr-mask-rep-icmp-ip-rx-bc': 64, 'cisco-rx-bc': 116, 'rarp-rep-tx-bc': 99, 'redirect-icmp-ip-tx-bc': 49, 'other-ipx-rx-bc': 90, 'spx-ipx-tx-bc': 79, 'echorep-icmp-ip-tx-bc': 43, 'param-prob-icmp-ip-tx-bc': 55, 'ospf-ip-tx-bc': 73, 'echorep-icmp-ip-rx-bc': 44, 'redirect-icmp-ip-rx-bc': 50, 'thru-fecn-rx-c': 132, 'lmi-tx-bc': 153, 'http-tcp-ip-tx-bc': 13, 'cir-percent-range8-tx-bc': 151, 'sap-ipx-rx-bc': 84, 'thru-becn-tx-c': 133, 'sna-tx-bc': 105, 'other-ipx-tx-bc': 89, 'cir-percent-range4-tx-bc': 143, 'ipx-tx-bc': 77, 'echoreq-icmp-ip-rx-bc': 52, 'other-rx-bc': 118, 'cir-percent-range1-rx-bc': 138, 'smtp-tcp-ip-rx-bc': 10, 'thru-frame-rx-c': 130, 'total-downtime': 166, 'addr-mask-rep-icmp-ip-tx-bc': 63, 'vnip-rx-bc': 170, 'arp-rep-rx-bc': 96, 'user-defined-2-tx-bc': 121, 'annex-g-tx-bc': 171, 'rip-udp-ip-rx-bc': 40, 'arp-rx-bc': 92, 'src-quench-icmp-ip-rx-bc': 48, 'rip-ipx-tx-bc': 85, 'user-defined-3-tx-bc': 123, 'cir-percent-range3-rx-bc': 142, 'lmi-other-tx-bc': 163, 'lmi-full-enq-rx-bc': 160, 'user-defined-3-rx-bc': 124, 'igrp-rx-bc': 168, 'sna-periph-rx-bc': 110, 'arp-rep-tx-bc': 95, 'rip-udp-ip-tx-bc': 39, 'other-ip-rx-bc': 76, 'tftp-udp-ip-tx-bc': 29, 'netbios-dgm-udp-ip-tx-bc': 33, 'rarp-req-tx-bc': 97, 'lmi-other-rx-bc': 164, 'timestamp-rep-icmp-ip-rx-bc': 60, 'snmptrap-udp-ip-tx-bc': 37, 'pkt-too-big-icmp-ip-tx-bc': 65, 'cir-percent-range6-tx-bc': 147, 'cir-percent-range7-rx-bc': 150, 'lmi-livo-stat-tx-bc': 157, 'sna-netbios-rx-bc': 114, 'ip-tx-bc': 1, 'pkt-too-big-icmp-ip-rx-bc': 66, 'ncp-ipx-tx-bc': 81, 'user-defined-4-tx-bc': 125, 'lmi-livo-enq-tx-bc': 155, 'gp-mem-query-icmp-ip-rx-bc': 68, 'gp-mem-report-icmp-ip-rx-bc': 70, 'user-defined-1-tx-bc': 119, 'ospf-ip-rx-bc': 74, 'tcp-ip-rx-bc': 4, 'lmi-livo-enq-rx-bc': 156, 'udp-ip-tx-bc': 21, 'cisco-tx-bc': 115, 'rip-ipx-rx-bc': 86, 'arp-req-rx-bc': 94, 'thru-becn-rx-c': 134, 'sna-appn-tx-bc': 111, 'http-tcp-ip-rx-bc': 14, 'gp-mem-reduct-icmp-ip-tx-bc': 71, 'other-tx-bc': 117, 'igrp-tx-bc': 167, 'timestamp-req-icmp-ip-rx-bc': 58, 'timestamp-rep-icmp-ip-tx-bc': 59, 'time-excd-icmp-ip-rx-bc': 54, 'lmi-full-stat-tx-bc': 161, 'timestamp-req-icmp-ip-tx-bc': 57, 'ftp-tcp-ip-tx-bc': 5, 'netbios-ssn-tcp-ip-tx-bc': 15, 'time-excd-icmp-ip-tx-bc': 53, 'sna-periph-tx-bc': 109, 'sna-subarea-rx-bc': 108, 'telnet-tcp-ip-rx-bc': 8, 'netbios-dgm-udp-ip-rx-bc': 34, 'thru-byte-tx-bc': 127, 'lmi-full-stat-rx-bc': 162, 'inarp-req-rx-bc': 102, 'arp-tx-bc': 91, 'tcp-ip-tx-bc': 3, 'rarp-req-rx-bc': 98, 'thru-frame-tx-c': 129, 'inarp-rep-rx-bc': 104, 'cir-percent-range5-rx-bc': 146, 'ipx-rx-bc': 78, 'sna-subarea-tx-bc': 107, 'cir-percent-range5-tx-bc': 145, 'cir-percent-range6-rx-bc': 148, 'inarp-rep-tx-bc': 103, 'sna-rx-bc': 106, 'total-uptime': 165, 'sap-ipx-tx-bc': 83, 'cir-percent-range8-rx-bc': 152.

The statistic collected for the given DLCI and protocol.

Allows the user to zero out all the statistics in the long term statistics tables. (1) Clear all Long Term statistics Enumeration: 'clear-statistics': 1.

Short Term Statistics on the percentage of CIR used on each DLCI. Each short term statistics interval, the count of bytes transmitted and received is used to calculate the percentage of CIR used. The byte count is then added to the appropriate bucket for the CIR percentage range.

The CIR Percentage Statistics for a particular DLCI. These calculations are done at the completion of each Short Term interval.

The Short Term statistics model maintains three intervals: current, previous, and cumulative totals. Interval duration is defined by the Short Term Timer (CfgFrPerfTimersSTInterval). (1) Currently active short term interval (2) Previously completed short term interval (3) Cumulative total since last cleared. Enumeration: 'previous-interval': 2, 'current-interval': 1, 'cumulative-counts': 3.

The DLCI value with which the Statistics are associated.

The number of received bytes counted on this DLCI during intervals where the percentage of CIR was in range 1 (0% of CIR).

The number of received bytes counted on this DLCI during intervals where the percentage of CIR was in range 2 (1-10% of CIR).

The number of received bytes counted on this DLCI during intervals where the percentage of CIR was in range 3 (11-20% of CIR).

The number of received bytes counted on this DLCI during intervals where the percentage of CIR was in range 4 (21-50% of CIR).

The number of received bytes counted on this DLCI during intervals where the percentage of CIR was in range 5 (51-80% of CIR).

The number of received bytes counted on this DLCI during intervals where the percentage of CIR was in range 6 (81-100% of CIR).

The number of received bytes counted on this DLCI during intervals where the percentage of CIR was in range 7 (101-150% of CIR).

The number of received bytes counted on this DLCI during intervals where the percentage of CIR was in range 8 (> 150% of CIR).

The number of transmitted bytes counted on this DLCI during intervals where the percentage of CIR was in range 1 (0% of CIR).

The number of transmitted bytes counted on this DLCI during intervals where the percentage of CIR was in range 2 (1-10% of CIR).

The number of transmitted bytes counted on this DLCI during intervals where the percentage of CIR was in range 3 (11-20% of CIR).

The number of transmitted bytes counted on this DLCI during intervals where the percentage of CIR was in range 4 (21-50% of CIR).

The number of transmitted bytes counted on this DLCI during intervals where the percentage of CIR was in range 5 (51-80% of CIR).

The number of transmitted bytes counted on this DLCI during intervals where the percentage of CIR was in range 6 (81-100% o0f CIR).

The number of transmitted bytes counted on this DLCI during intervals where the percentage of CIR was in range 7 (101-150% of CIR).

The number of transmitted bytes counted on this DLCI during intervals where the percentage of CIR was in range 8 (> 150% of CIR).

The current measurement of utilization as a percentage of CIR on each DLCI. Each short term statistics interval, the count of bytes transmitted and received is used to calculate the percentage of CIR used.

The utilization statistics for a particular DLCI.

The DLCI value with which the Statistics are associated.

The receive direction utilization as a percentage of CIR.

The transmit direction utilization as a percentage of CIR.

The aggregate utilization, the average of the receive and transmit utilization as a percentage of CIR.

The DTE interface utilization as a percentage of line rate.

The WAN interface utilization as a percentage of line rate.

The aggregate utilization of the unit, the average of the DTE and WAN interface utilizations as a percentage of line rate.

The alarm type of the most recent TRAP generated. Enumeration: 'dte-signal-rts-off': 56, 'local-dte-loopback-disabled': 18, 'local-dte-loopback-failure': 19, 'tftp-transferring': 258, 'bad-config-in-set': 1, 'bpv-threshold-acceptable': 70, 'remote-network-simplex-loopback-enabled': 71, 'local-unit-loopback-failure': 16, 'v54-loop-down-completed': 30, 'pvc-rx-utilization-cleared': 140, 'vbert-stopped': 96, 'lmi-sourcing-change-passthr': 50, 'config-local-update': 2, 'dte-signal-dtr-on': 57, 'bert-test-pattern-failure': 46, 'dte-signal-dtr-off': 58, 'trap-muting-inactive': 76, 'v54-loopback-disabled-by-remote': 32, 'tftp-requested': 257, 'dlci-td-threshold': 49, 'incoming-call': 67, 'local-network-loopback-failure': 28, 'remote-network-non-latching-loopback-enabled': 73, 'pvc-rx-utilization-exceeded': 138, 'local-dte-loopback-enabled': 17, 'lmi-non-incr-seq-num-dte': 59, 'vloop-up-via-remote': 92, 'config-install-success': 142, 'tftp-invalid-file': 264, 'lmi-sourcing-change-user-dte': 51, 'lmi-non-incr-seq-num-net': 60, 'dlci-inactive': 48, 'lmi-sourcing-change-net-dte': 52, 'lmi-seq-num-mismatch-net': 62, 'vloop-loop-up': 90, 'local-network-loopback-enabled': 26, 'lmi-sourcing-change-net-net': 54, 'local-unit-loopback-disabled': 15, 'local-network-loopback-disabled': 27, 'line-failure': 63, 'v54-loopback-enabled-by-remote': 31, 'dte-signal-rts-on': 55, 'bert-test-pattern-completed': 45, 'remote-network-simplex-loopback-disabled': 72, 'connected': 65, 'tftp-host-unreachable': 262, 'line-in-service': 64, 'vbert-request-failed': 97, 'bpv-threshold-exceeded': 69, 'tftp-aborted': 260, 'tftp-success': 261, 'disconnected': 68, 'vbert-started': 95, 'pvc-tx-utilization-exceeded': 139, 'dlci-active': 47, 'vloop-down-via-remote': 93, 'vloop-failed': 94, 'v54-loop-up-initiated': 29, 'v54-loopback-failure': 33, 'trap-muting-active': 75, 'tftp-no-file': 263, 'pvc-tx-utilization-cleared': 141, 'lmi-sourcing-change-user-net': 53, 'tftp-corrupt-file': 265, 'connect-failure': 66, 'tftp-programming': 259, 'vloop-loop-down': 91, 'bert-test-pattern-initiated': 44, 'remote-network-non-latching-loopback-disabled': 74, 'lmi-seq-num-mismatch-dte': 61, 'local-unit-loopback-enabled': 14.

The DLCI number for the most recent DLCI TRAP generated.

The interface most recently reported in a TRAP. Enumeration: 'dds': 2, 'dte': 1.

The IP address most recently reported in a TRAP.

This table contains the Event/Trap log. The entries are indexed by sequence number.

The event record for a particular event.

The sequence number associated with an event record.

The SNMP generic trap or event number.

The SNMP specific trap or event sub-identifier number.

The SNMP trap timestamp.

Variable Binding 1 for this SNMP Trap event.

Variable Binding 2 for this SNMP Trap event.

Variable Binding 3 for this SNMP Trap event.

This is an alternative method to access the database of the Event/Trap Log. The database is indexed by Sequence Number and Event/Trap log's are returned in an OCTETSTRING.

The Event/Trap Log for a particular sequence number.

The Sequence Number monitored for the Event Log

The Event / Trap log for the given sequence number.

The current index into the Event Log Table.

This freezes the Event/Trap Log. freeze(1) will prevent Events / Traps from being entered into the database, un-freeze(2) will allow Events / Traps to be logged into the database. An event will be logged indicating a set of this entry Enumeration: 'un-freeze': 2, 'freeze': 1.

This clears the Event/Trap Log. Enumeration: 'clear': 1.

The percent utilization for a DLCI most recently reported in a TRAP.

The percent utilization threshold for a DLCI most recently reported in a TRAP.

The IP address of the management station locking the configuration most recently reported in a TRAP.

A dfrapTrap trap signifies that the sending node had its `dfrapAlarmType` variable modified.

Unit has received a configuration update request through SNMP but the request was rejected due to an incorrect or inappropriate parameter.

Unit configuration has been updated locally (console port or front panel keypad) or remotely (telnet)

Unit is in a bi-directional unit loopback. Data is received from either interface, processed, and transmitted back towards the same interface. When configured for Frame Relay operation the unit will preserve the LMI path during this loopback. In Frame Relay mode, only valid frames are looped back (pseudorandom test patterns will be dropped).

Bi-directional unit loopback path is removed.

Bi-directional unit loopback request has been rejected by the unit. Typically, this is due to the presence of another loopback condition.

Unit is in a bi-directional DTE loopback. All data received at the DTE interface is looped back regardless of format or content (line loopback). All data received at the WAN interface is looped back regardless of format or content (line loopback) When configured for Frame Relay operation the unit will not preserve the LMI path during this loopback.

Bi-directional DTE loopback path is removed.

Bi-directional DTE loopback request has been rejected by the unit. Typically, this is due to the presence of another loopback condition.

Unit is in local network loopback. All data received from the WAN, regardless of format or content, is transmitted back out (line interface loopback) while still being sent to the DTE. When configured for Frame Relay operation the unit will not preserve the LMI path during this loopback.

Local network loopback path is removed.

Local network loopback request is rejected. Typically, this is due to the presence of another loopback condition.

Unit has sent the standard V54 loop up pattern out the WAN at the DTE rate. A compatible piece of equipment can sense this pattern and enter a loopback state - typically putting up a bi-directional DTE loopback path. After sending the V54 loop up pattern, the (local) unit returns to normal operation, expecting a loopback condition at the remote device.

Unit has sent the standard V54 loop down pattern out the WAN at the DTE rate. A compatible piece of equipment can sense this pattern remove the loopback state that is entered after receiving a loop up pattern - typically a bi-directional DTE loopback path. After sending the V54 loop down pattern, the unit returns to normal operation.

Unit has received a V54 loop up pattern from a compatible piece of equipment. A bi-directional DTE loopback is activated. All data received at the DTE interface is looped back regardless of format or content. All data received at the WAN interface is looped back regardless of format or content. When configured for Frame Relay operation the unit will not preserve the LMI path during this loopback.

Unit has received a V54 loop down pattern from a compatible piece of equipment. The bi-directional local DTE loopback is removed

Unit has rejected the request to send a V54 loop up. Typically, this is due to the presence of another loopback condition.

Unit is sending a pseudorandom test pattern (511 or QRSS) out the WAN and monitoring the WAN received data for the same pattern. This test may be ineffective in certain frame relay applications as pseudorandom data lacks appropriate framing.

Unit has stopped sending a pseudorandom test pattern out the WAN.

Unit has rejected the request to enter a BERT test state. Typically, this is due to the presence of another diagnostic condition.

Unit is reporting this DLCI as active and provisioned. An active DLCI is one that is explicitly declared ACTIVE in an LMI Full Status Response (typically coming from a frame relay switch).

Unit is reporting this DLCI as inactive. An inactive DLCI is determined inactive one of two ways: it is either explicitly declared inactive in an LMI Full Status Response (typically coming from a frame relay switch) or a Full Status Response is not seen causing a Full Status Timer expiry. Having the unit's full status timer too low could result in the unit falsely declaring DLCIs inactive (then active again). This does not interfere with any data activity on the DLCI but could result in excessive traps.

VNIP has measured a round-trip transit delay on this PVC to this peer which exceeds the user-defined threshold.

Unit is not sourcing any LMI messages. If this state persists then LMI is up and the proper handshaking is occurring independent of the unit. This may also be a transient state if the unit is in an LMI hunt mode. If this trap occurs repeatedly, separated by other LMI sourcing states, the unit is not seeing any of the expected LMI messages from either interface. Check LMI type, connectivity, and configuration of associated equipment.

Unit is acting as a source of LMI Status Requests (Link Integrity Verification, Keep Alive). If this state persists then the equipment attached to the DTE interface is configured as a Frame Relay DCE but a companion Frame Relay DTE device is not seen out the WAN. This could also be a transient state if the unit is in an LMI hunt mode. If this trap occurs repeatedly, separated by other LMI sourcing states, the unit is not seeing any of the expected LMI messages from either interface. Check LMI type, connectivity, and configuration of associated equipment.

Unit is acting as a source of LMI Status Responses (Link Integrity Verification, Keep Alive). If this state persists then the equipment attached to the DTE interface is configured as a Frame Relay DTE but a companion Frame Relay DCE device is not seen out the WAN. This could also be a transient state if the unit is in an LMI hunt mode. If this trap occurs repeatedly, separated by other LMI sourcing states, the unit is not seeing any of the expected LMI messages from either interface. Check LMI type, connectivity, and configuration of external equipment.

Unit is acting as a source of LMI Status Requests (Link Integrity Verification, Keep Alive). If this state persists then the equipment attached to the WAN interface is configured as a Frame Relay DCE but a companion Frame Relay DTE device is not seen out the DTE interface. This could also be a transient state if the unit is in an LMI hunt mode. If this trap occurs repeatedly, separated by other LMI sourcing states, the unit is not seeing any of the expected LMI messages from either interface. Check LMI type, connectivity, and configuration of associated equipment.