Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Displaying the Running CTP Bundle Configuration, State, and Counters (CTP Menu)

 

To display a bundle using the CTP Menu:

  1. From the CTP Main Menu, select 1) Bundle Operations.
  2. Select the type of bundle.
  3. Select a bundle from the list.
  4. From the menu, select 1) Query. The configuration of the bundle appears followed by the runtime state and counters.

    Table 57 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 57: CTP Bundle Runtime State and Counters in the CTP Menu

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 (OAM packets), but data is not flowing.

    The bundle will remain In Sync when network bandwidth is insufficient to transmit the data packets. If the bundle is configured as demand on RTS high, and RTS is currently low, then also the bundle remains in the InSync state until RTS rises.

  • 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. The bundle is configured to use an external (TT) clock, and this clock is being measured to see if it is the proper frequency.

  • TooSlow—The CTP bundle configuration is not possible because it consumes too little resources. For example, the configured port parameters yield a data rate, which is less than or equal to 0.

  • TooFast—The CTP bundle configuration is not possible because it consumes too much resources. For example, the configured port speed and packet size gives a bundle packet rate that exceeds the maximum of 1000 packets per second.

  • TtFAIL—The CTP bundle reaches the TtFAIL state from the Eval state when the measured TT is more than 6.25% of the configured (expected) TT frequency

  • 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 configured for AutoBaud clocking and the user clock (TT) has recently changed. The state machine is waiting for the TT to stabilize before bringing the circuit up.

  • 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.

  • SdInactive—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—Receive BERT for this port is active and is monitoring the interface bound data. Receive BERT is only a monitoring function and does not affect the interface bound data.

  • BertFromIf—Receive BERT for this port is active and is monitoring the network bound data. Receive BERT is only a monitoring function and does not affect the network bound data.

  • BertToNet—Transmit BERT for this port is active and is sending the network bound data, thereby interrupting the normal data path from the interface.

  • BertToIf—Transmit BERT for this port is active and is sending the interface bound data, thereby interrupting the normal data path from the IP network.

  • LoopToNet—Interface bound data is looped back towards the IP network, thereby interrupting the normal network bound data. Interface bound data is not interrupted.

  • LoopToIf—Network bound data is looped back towards the interface, thereby interrupting the interface bound data. Network bound data is not interrupted.

IRIG-B Run Flags

Displays the current status of the IRIG-B runtime

  • TxIpSync—Transmit mode is in sync with the remote CTP device. The local IRIG module is able to recover the framed IRIG signal from the data arriving from the remote IRIG module through the IP network.

  • TxSyncLost—Transmit mode is not in sync with the remote CTP device. This flag is set whenever the TxIpSync flag is active after issuing the last port counter clear command. When activated, it remains active until you issue the next port counter clear command.

  • RxIrigSync—Receive mode is in sync with the remote CTP device. The local IRIG module is able to recover the IRIG signal from the data arriving from the IRIG signal arriving at the interface.

  • RxSyncLost—Receive mode is not in sync with the remote CTP device. This flag is set when the RxIrigSync flag is active after issuing the last port counter clear command. When activated, it remains active until you issue the next port counter clear command.

Bundle Config

DBase State

Displays whether the bundle is active or disabled.

Remote Addr

Displays the remote IP address.

Remote CID

Displays the remote circuit ID in the range 0-249.

Local CID

Displays the local circuit ID in the range 0-249.

Packet size

Displays the size of IP packets that are created from data received at the T1/E1 interface. The CTP software calculates a default packet size based on the number of time slots configured, the type of interface (T1 or E1), and the type of signaling (CCS or CAS).

Buf Max/Set/Min(ms)

Displays the maximum, running state, and minimum buffer sizes, in terms of milliseconds. The number that you entered varies depending on the type of interface and signaling. The set buffer size denotes the buffer size when the circuit enters a running state.

IP Hdr TOS

Displays the ToS byte to be used in IP headers of packets sent from the CTP device to the IP network. The ToS setting is applied to circuits created by the bundle for which the service type is configured.

IP Proto/OAM Port

Displays the port configured for IP protocol and OAM applications.

Port(s) in bundle

Displays the interfaces that are part of the configured bundle.

Bndl Desc

Displays the description of the bundle, which enables easy identification.

Bndl Config Flags

Displays the current configuration of the bundle:

  • PProtTx—Indicates that the packet protector is set to “Send cloned packets to NET”. The CTP device uses cloned packets that it receives when the IP network drops the original packet. If the device receives both the original and cloned packets, it ignores the cloned packet.

  • PProtRx—Indicates that the packet protector is set to “Expect cloned packets from NET”. The CTP device uses cloned packets that it receives when the IP network drops the original packet. If the device receives both the original and cloned packets, it ignores the cloned packet.

  • PProtTx PProtRx—Indicates that the packet protector is set to “Send & expect cloned packets”. The CTP device sends duplicated packets over the IP network. The CTP device uses cloned packets that it receives when the IP network drops the original packet.

  • PProtTxDel—Indicates that the packet protector is set to “Send delayed cloned packets to NET”. The CTP device sends duplicated packets after the interpacket delay of the circuit.

  • PProtTxDel PProtRx—Indicates that the packet protector is set to “Send delayed & expect cloned packets”. The CTP device sends duplicated packets after the interpacket delay of the circuit. The CTP device uses cloned packets that it receives when the IP network drops the original packet.

  • PProtRxXor—Indicates that the packet protector is set to “Expect cloned XOR packets”. The CTP device uses cloned XOR packets that it receives when the IP network drops the original packet to regenerate the missing packet. If the device receives both the original and cloned XOR packets, it ignores the cloned packet.

  • PProtTxXor PProtRxXor—Indicates that the packet protector is set to “Send & expect cloned XOR packets”. The CTP device sends duplicated XOR packets over the IP network. The CTP device uses cloned XOR packets that it receives to regenerate missing packets when the IP network drops the original packet.

  • PProtTxXor—Indicates that the packet protector is set to “Send cloned XOR packets”. The CTP device sends duplicated XOR packets over the IP network.

Port Config

Interface type

Displays the type of interface.

The type of interface that you select affects the default packet size and buffer sizes for the bundle.

Port Config Flags

Displays the current configuration of the port:

  • T1LoSCheck—Denotes that LOS detection is specified on a T1 port connected to a CTP bundle or a SAToP bundle

  • E1LoSCheck—Denotes that LOS detection is specified on a E1 port connected to a CTP bundle or a SAToP bundle

  • NoRdReclk flag—Signifies that the redundancy receiving (RX) clock is disabled. The NoRdReclk flag is also displayed because this flag is default enabled for a T1/E1 port, whereas it is usually not enabled for a serial port.

When you run the bundle query for CTP bundles and SAToP bundles, the T1E1 port type displays port configuration flags that are relevant to a T1E1 port.

Framing type

Displays the framing type for T1 interfaces.

  • ESF

  • D4

Redundancy Config

Displays the configured redundancy mode.

  • Disable—Y-cable redundancy is not enabled on this port.

  • eXclusive OR (XOR)—Redundancy is enabled. In this mode the Y cable is active only if the port is in RUNNING state and the serial port on the Y-cable link is not in RUNNING state. If both bundles are RUNNING, the Y cable remains inactive on both the ports.

  • ReVeRT (RVRT)—When you select this mode, a primary and a secondary path is enabled. The primary path drives the cable when its bundle is in RUNNING state, independent of the state of the secondary path. The secondary path is activated when the primary path is offline. Whenever the primary path comes back online, the path is switched back to the primary path.

  • NOnReVert (NORV)—When you select this mode, the circuit is not switched back to primary when the primary path comes back online after switching to secondary path. The circuit is switched to the primary path only when the secondary path fails.

  • Signal (SIG)—The primary path is activated only if the secondary CTS output is inactive. When CTS is active, secondary drives cable.

Primary/Secondary

Specifies whether it is a primary and a backup bundle. When the software link is enabled and link partners are specified, the software verifies that there is a matched primary and backup pair.

Pri/Sec Link Type

Specifies the link types for primary and back up bundle.

  • H/W link—When enabled, the Y-cable redundancy is supported only on serial ports, and the link between ports is a hardware signaling connection over a special Y cable that uses the output to cable(TM) and the input from cable(RL) to communicate redundancy state between port pairs, by using keepalive pulses. Its operation is similar to the default operation of the redundancy feature in CTPOS Release 6.5 and earlier.

  • S/W link—Allows Y-cable port pairs to maintain contact with each other by means of OAM packets instead of using a hardware signaling path. The software link has the following advantages:

    • The software link does not require a special signaling hardware, which means that Y-cable redundancy is supported on T1E1 ports as well as serial ports with a special Y cable. Serial ports can get TM/RL signals for user applications.

    • Software or OAM link packets can check link partners and identify configuration errors. They can also differentiate between dead and alive states.

IP Address

Specifies an IP address for the other port of the redundant primary and backup pair.

Line Buildout

Displays the line buildout for T1 interfaces.

  • 0) ~133 ft

  • 1) ~266 ft

  • 2) ~399 ft

  • 3) ~533 ft

  • 4) ~655 ft

  • 5) -7.5dB CSU

  • 6) -15dB CSU

  • 7) -22.5dB CSU

Clock Source

Displays the type of clocking for the port.

  • CTP is Clock Source—The PBX either returns the clock received from the CTP or it returns a clock that is traceable to the same source as the CTP node clock reference. You typically use this configuration when you configure the CTP device with a clock reference input.

  • CTP is Loop Timed—The PBX provides the clock and the CTP returns the same clock to the PBX. You typically use this configuration when the PBX has the more accurate clock source. You can configure the far end of the circuit with adaptive clocking to recover this clock if necessary.

  • CTP is Clock Source (Adaptive End)—The PBX returns the clock received from the CTP, and the CTP uses the adaptive recovered clock. You typically use this configuration when the CTP does not have a reference input and the PBX typically requires clock from the distant PBX.

    On CTP150 devices, If you set clocking to CTP is Clock Source (Adaptive End), the first bundle activated on the interface is assigned as the adaptive master bundle on which the transmit clock is adjusted. This bundle is also the last bundle to be deactivated on the interface.

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:

  • Aggressive—Bundle is running, and adaptive clocking is in training mode.

  • Maintain (20 us)—Bundle is running, and adaptive clocking is in steady state. The value specified parentheses is the current offset from the optimal buffer level. When adaptive clocking is functioning properly, it should hover around 0.

  • N/A (Port Not RUNNING)—Bundle is disabled.

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.

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 the buffer state was less than the minimum buffer setting.

Buffer overflows

Number of times the buffer reached the maximum set threshold.

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.

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.