Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Transponder Mode on the ACX6360

Understanding Transponder Mode on the ACX6360

The ACX6360 can be used as either a transponder or a router. As a transponder, the ACX6360-OX has sixteen 100-Gbps ports that provide 1-to-1 cross-connects for pass-through connections of client interface traffic to line optical interfaces. As a router the ACX6360-OR provides IP/MPLS routing services. (For information on changing the operational mode, see Changing Operational Modes on the ACX6360.)

When in transponder mode, circuit cross-connect (CCC) is used to provide transparent point-to-point connections. This can be in the form of interface to interface, LSP to LSP, interface to LSP, or LSP to interface.

Figure 1 shows how the ACX6360-OX transponder can be used in your network.

Figure 1: The ACX6360-OX Transponder in Your NetworkThe ACX6360-OX Transponder in Your Network

The Transport-CCC Forwarding Sandbox

Figure 2 shows the logical view of the sandboxes that are created in the system for the transport-ccc. The default sandbox sb-ccc is owned and managed by the CCC client. When the CCC client opens the sb-ccc sandbox, it gets a complete list of the available ports in the ACX6360-OX. The ports that are visible in the sb-ccc sandbox are virtual ports. Each virtual port corresponds to one physical et-0/x/y port.

Figure 2: Transport-ccc SandboxTransport-ccc Sandbox

The default sandbox configuration should not be modified. If the sandbox configuration is modified for any reason, you must restart the circuit cross-connect process or reboot the system. Only one forwarding sandbox can be configured on the ACX6360-OX.

Following is the default sandbox configuration. The startup script on the ACX6360-OX automatically creates the default sandbox configuration.

The Circuit Cross-Connect Configuration

The default circuit cross-connect configuration is configured through the startup script at system startup. You can define or modify the circuit cross-connects based on your requirements. Following is the default circuit cross-connect configuration.

Understanding Ethernet Fault Propagation

On the ACX6360-OX, when a local fault is received on the line side (et-0/1/y), it sends the local fault out on the client side (et-0/0/x). The client port then receives a remote fault (RF), which is then sent over on the line side (et-0/1/y). Figure 3 shows the local fault (LF) detection on the line side.

Figure 3: Local Fault Detection on the Line SideLocal Fault Detection on the Line Side

On the ACX6360-OX, when the client port (et-0/0/x) sends a local fault to the connected router, it receives a remote fault on the client port (et-0/0/x) and then it sends the remote fault out on the line side (et-0/1/y). Figure 4 Shows the local fault detected by the client-side router.

Figure 4: Local Fault Detection by the Client-side RouterLocal Fault Detection by the Client-side Router

On the ACX6360-OX, when the client port (et-0/0/x) receives a local fault, it sends the local fault out on the line side (et-0/1/y) and then forwards the received remote fault (et-0/1/y) to the client port (et-0/0/x). Figure 5 shows a local fault detected by the client-side interface.

Figure 5: Local Fault Detection by the Client-side InterfaceLocal Fault Detection by the Client-side Interface

When a remote fault is sent by another ACX6360-OX, the remote fault is forwarded transparently to the client-side router. On the ACX6360-OX, when a line port (et-0/1/y) receives a remote fault, it forwards the remote fault out on the client port (et-0/0/x). Figure 6 shows the remote fault handling.

Figure 6: Remote FaultRemote Fault

Verifying the Circuit Cross-Connect Configuration

Purpose

Use the following procedure to verify that your circuit cross-connect configuration is correct:

Action

  1. Verify the contents of the /var/db/scripts/jet folder:

  2. Verify the Juniper Extension Toolkit (JET) infrastructure configuration:

  3. Verify that the circuit cross-connect Yang package is installed.

    If the Yang circuit cross-connect package is not installed, do the following to install the package:

    1. On the shell, go to the /var/db/scripts/jet folder.

    2. Start the CLI and enter the following command:

      user@host> request system yang add package ccc module circuit-cross-connect.yang action-script ccc.py

  4. Verify that all the circuit cross-connect related processes are running on the shell:

    1. Verify that the JET service process (jsd) is running on the routing engine:

    2. Verify that jsd is listening on TCP port 51051:

    3. Verify that the circuit cross-connect configuration handling script is running on the routing engine:

Resetting the Circuit Cross-Connect Defaults

If you are facing any issues related to circuit cross-connect creation and want to reset the system to its default configuration, follow these steps:

  1. Remove the sandbox and the circuit cross-connect configuration:
  2. Delete the CCC Yang package:
  3. Configure the system by running the startup script manually from the shell:
  4. Verify that the Yang package is installed:
  5. Verify that the default sandbox configuration and the circuit cross-connects are installed on the box. See Verifying the Circuit Cross-Connect Configuration.

Troubleshooting Information

The circuit cross-connect log files are located at the following locations:

/var/log/ccc.py- user-cfg.log /var/log/ccc.py-regress-op.log /var/log/jet.log /var/log/jsd

You can use the following CLI commands to troubleshoot circuit cross-connects:

  • To verify endpoints:

  • To verify all circuit cross-connects:

  • To verify individual circuit cross-connects: