Juniper CTP Series Manual page 152

Using Bundles to Create Logical Configurations for Physical Interfaces, CTP Release 7.3, CTPView Release 7.3
Table 59: 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.
146 Copyright © 2018, Juniper Networks, Inc.