Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Displaying Running CTP Bundle Configuration, State, and Counters (CTPView)

    This topic describes how to display the running configuration of your bundle, along with the state and various counters.

    Before you begin:

    • Log in to the CTPView software at least at the Net_Admin level.
    • Connect the CTPView server to the CTP device for which you want to change the status of the bundles.

    To view information about the bundle:

    1. In the side pane, select Bundle > Runtime Query.
    2. Run your mouse over the MouseOver to Display and Select Bundles to Display bar.
    3. In the table of bundles, select the bundles that you want to view, and click Display Selected Bundles. To select multiple bundles, hold down the CTRL key.

      The configuration of the bundle or bundles appears followed by the runtime state and counters.

      Table 1 describes the fields in the state and counters sections of the display.

      The signaling configuration appears only if you changed the signaling configuration from the default configuration.

    Table 1: CTP Bundle Runtime State and Counters in CTPView

    Field Name

    Field Description

    Run State

    Displays the current state of the bundle:

    • N/A—Bundle is disabled.
    • No Sync—The local CTP device is not able to communicate with the remote CTP device.
    • In Sync—The local CTP device is communicating properly with the remote device, but data is not flowing to the interface.
    • Running—The local CTP device is communicating and is synchronized with the remote CTP device. The circuit is established between the bundles.
    • Eval—The bundle is in the transition state between No Sync and In Sync.
    • TooSlow—Encountered when the bundle is configured for all clocking to be done by the external transmit timer (TT) clock. The error occurs when either no clock is provided by the external device or the rate is different from the configured rate.
    • TooFast—Encountered when the bundle is configured for all clocking to be done by the external TT clock. The error occurs when either no clock is provided by the external device or the rate is different from the configured rate.
    • TtFAIL—The TT differs from the configured value by more than 1/16.
    • MisCfg—A misconfiguration of the bundles between the local and remote devices prevents the circuit from being brought up. For example, incorrectly configured IP addresses and mismatched speeds.
    • CfgFail—The configuration of the bundle cannot be supported. If you encounter this error, delete the bundle and create a new bundle.
    • AutoWait—The bundle is waiting for the TT to stabilize.
    • DirDrv—The direct drive capability is enabled for the bundle. If the direct drive functionality is disabled, the “NotDirDrv” flag is displayed.

      Until CTPView Release 7.1R1, the direct drive feature is enabled by default and this functionality configuration is not displayed in the output of the bundle query. If you explicitly enabled the direct drive capability (using IP tables instead of direct drive for packet-forwarding) by using the selecting No for the Disable direct drive field in the Advanced Options screen of the Configuration window under Bundle Operations of the CTP Main Menu, bundle query displayed "NoDirDrv" when you run the bundle query from the Main Menu of CTP Menu by selecting 1) Query. Starting with CTPOS and CTPView Release 7.2, the default behavior is direct-drive disabled (IP table is turned on for forwarding of packets). With default configuration, the bundle query output does not display the direct drive settings. Only if you explicitly enable the direct-drive capability, the bundle query output displays "Bndl Config Flags: DirDrv" in bundle query. CTP bundle circuits that use route redundancy and port forwarding must have direct drive disabled to allow for asymmetric routing. When direct drive is disabled, packets are forwarded based on information in the kernel’s IP stack. When direct drive is enabled, packets are forwarded directly between drivers on the local and remote CTP device.

    Port Runtime Flags

    Displays the current configuration of BERTs and serial loops.

    • Inactive—No activity is detected on the serial input. The activity detector checks the serial input line every 500 milliseconds for any transitions on the line. Port Run Time flag of the serial CTP bundle shows the status as Inactive if no activity is detected on the serial input line. This flag is displayed only when the serial input line is inactive, which is an abnormal condition. No such flag is displayed if the serial input line is active.

      This flag applies only to a serial port that has a T1E1 DCARD installed and is in use. It does not apply to ports on a T1E1 card.

    • BertFrmNet—Used to receive the BERT from the network
    • BertFromIf—Used to receive the BERT from the interface
    • BertToNet—
    • BertToIf—
    • LoopToNet—Used to loop back the BERT to the network
    • LoopToIf—Used to loop back the BERT to interface

    IRIG-B Run Flags

    Displays the current status of the IRIG-B runtime

    • TxIpSync—Transmit mode is in sync with the remote CTP device.
    • TxSyncLost—Transmit mode is not in sync with the remote CTP device.
    • RxIpSync—Receive mode is in sync with the remote CTP device.
    • RxSyncLost—Receive mode is not in sync with the remote CTP device.

    T1E1 flags

    Appears for bundles on T1/E1 interfaces.

    • LOS—Loss of signal. This could mean that the cable is not attached. When LOS is detected, the CTP device puts the bundle into a loop so that the TX and RX clock are looped to each other.
    • LOF—Loss of frame.
    • AIS—Alarm indication signal.
    • RAI—Remote alarm indication (yellow alarm).
    • LOF_NB—Fractional T1 only. FPGA framer loss of frame network bound.
    • LOF_IB – Fractional T1 only. FPGA framer loss of frame interface bound.

    TT (Ext Clock)

    Displays the current speed of the transmit timing (TT) clock.

    The TT measurement is displayed only for a CTP bundle or a SAToP bundle that is attached to a T1E1 port on a T1E1 Daughter Card or a CTP bundle attached to a serial port with clock configuration set to Configured with TT, All Clocked by TT, Adaptive Rate, w/ User Clk (TT), or Autobaud Rate, w/ User Clk (TT).

    RT (Ext Clock)

    Displays the current speed of the receive timing (RT) clock.

    Appears if the bundle is configured as the DTE, and clocking is set to DTE, All Clocked by Ext Clk (ST/RT) .

    Adaptive State

    For bundles that are configured as the adaptive end for adaptive clocking, displays the current state of the adaptive clock:

    • Maintain (20 us)
    • Maintain (968 us)
    • N/A (Port Not RUNNING)

    Adap Recovered Freq

    For bundles that are configured as the adaptive end for adaptive clocking, displays the frequency currently being recovered from the master end.

    Input Signals

    Displays the running configuration of input signals.

    Output Signals

    Displays the running configuration of output signals.

    Checked out PPS

    Displays packets per second (PPS) for the current bundle, for all running bundles on the CTP device, and the maximum PPS for the CTP device.

    Note: For CESoPSN bundle, this field is available only in CTPOS release 7.0 and later.

    Counters

    I/F bound packets

    Packets received from the IP network destined for the bundle.

    NET bound packets

    Packets created by the bundle and sent to the IP network.

    Late pkts

    Packets that were delivered to the CTP device, but arrived too late to be processed. Significant numbers of late packets indicate that the size of the buffer needs to be increased.

    Missing pkts

    Packets that were not delivered to the CTP in time to process out the serial interface because they were either late or dropped by the IP network.

    Each time a packet is missed, the data fill pattern specified in the advanced port options is substituted for data in the missed packet. The substitution maintains the bit count integrity of the data sent to the DTE or encryptor, but results in what appears to be a burst of errors with a duration equal to the size of the packet.

    Buffer restarts

    Number of times the buffer was restarted.

    Buffer underflows

    Number of times that the average buffer state was less than the minimum buffer setting.

    Buffer overflows

    Number of times that the buffer state exceeded the maximum buffer setting.

    Buffer starves

    Indicates an exceeded threshold. The CTP device is designed to tolerate strings of consecutive missing packets without the loss of bit count integrity. The number of packets is configurable; the default is five. Exceeding this threshold is called a starvation, and a counter is incremented each time this event occurs.

    Buffer max samples

    Largest buffer sample observed.

    Buff Max/Avg/Min

    Maximum, average, and minimum buffer sizes observed.

    Buff Last Minute

    Maximum, average, and minimum buffer sizes observed in the last minute.

    BERT running sec

    Number of seconds the current update has been running.

    BERT sync sec

    Number of seconds that the local CTP device has been in sync with the remote CTP device.

    BERT error sec

    Number of seconds during which there were errors.

    BERT in sync

    Shows whether the CTP device is currently in sync with the remote CTP device

    Last counter clear

    Indicates the last time that the system counters were reset.

    This feature is supported on CTPOS release 6.6R3 and later for CESoPSN bundles created on CTP2000 series.

    Modified: 2016-01-29