Juniper CTP Series Manual page 146

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