If required, login to the VLNC6x.

Result:

The User EXEC prompt [(ALU switching)>] displays.

Enter the Global Config mode:

1. From the User EXEC prompt, enter enable to enter the Privileged EXEC mode.

2. From the Privileged EXEC prompt, enter config to enter the Global Config mode.

Configure VLNC6x circuit emulation mode. From the Global Config mode, enter ces-mode {ethernet | mpls-php-enable | mpls-php-disable} to set the CES mode. Default is mpls-php-disable.

Example: (ALU Switching)(Config)# ces-mode mpls-php-enable.

If you change the mode from Ethernet to MPLS (MPLS PHP disable or MPLS PHP enable) and vice versa, the system resets after clearing the configuration. If you change the mode from MPLS PHP disable to MPLS PHP enable and vice versa, the system resets, but without clearing the configuration.

If required, set the differential timestamp frequency for the system. From the Global Config mode, enter system-differential-timestamp-frequency {77.76 | 25}.

The values are specified in MHz. Default is 77.76 MHz.

You must ensure that the system at the other endpoint of the Circuit Emulation Service has the same timestamp frequency that you set on this system.

Configuring this parameter will reset the circuit pack.

Configure VLNC64 OC3/STM1 interfaces, as required.

Procedure 17-2.1: Configure VLNC64 OC3/STM1 interfaces

Configure T1/E1 and Ethernet interfaces at remote and hub ends.

Reference:

Procedure 17-2.2: Configure T1/E1 and Ethernet interfaces

Configure IP addresses and routes, if required. Not required if ces-mode is set to “ethernet”.

MEF-8 (ces-mode ethernet) is supported only on Ethernet switching networks. Therefore, only a system level IP address is required (CLI commands: network parms, serviceport.)

Reference:

Procedure 17-2.3: Configure IP addresses and routes

If required, configure VLANs on which the Ethernet interface(s) participates. The VLANs created will be used later in configuring the PSN tunnel.

Reference:

Procedure 17-2.4: Configure VLANs for Ethernet interface.

Configure Timing.

Reference:

Procedure 17-2.5: Configure timing for VLNC6x Circuit Emulation Service (CES)

Configure Tunnel 1 and Tunnel 3 outgoing parameters at the Remote end, and Tunnel 1 and Tunnel 3 incoming parameters at Hub end.

Configure Tunnel 2 and Tunnel 4 incoming parameters at Remote end, and Tunnel 2 and Tunnel 4 outgoing parameters at Hub end.

Reference:

Procedure 17-2.7: Configure Tunnel parameters

Configure BFD sessions on all four of the tunnels.

From the Global Config mode, enter psntunnel <name>, where name is the name of the tunnel you are configuring. For example: (ALU Switching) (Config)# psntunnel Tunnel 1.

Refer to the Alcatel-Lucent 1850 Transport Service Switch (TSS-5) Command Line Interface Guide, and configure the following:

• udp <udp-port-id> — enables udp port configuration on outgoing PSN Tunnels. Example: udp 49152.

• local-discriminator <local-discriminator-value> — enables the local discriminator configuration. Example: local-discriminator 10.

• remote-discriminator <local-discriminator-value> — enables the remote discriminator configuration. Example: remote-discriminator 20.

• min-rx-interval <rx-interval-value> — minimum interval, in milliseconds, between received BFD Control packets. Example: min-rx-interval 100.

• min-tx-interval <tx-interval-value> — minimum interval, in milliseconds, between transmitted BFD Control packets. Example: min-tx-interval 100.

• multiplier <multiplier-value> — negotiated transmit interval, multiplied by this value, provides the detection time for the transmitting pack in Asynchronous mode. Example: multiplier 3

• bfd-flap-count <flap-count-value> — total number of flaps before the BFD session enters dampening state. A flap is defined as a transition of the BFD session from up to down state. Example: bfd-flap-count 15.

• bfd-flap-monitor-time <flap-monitor-time-value> — time interval (in seconds) in which the flaps are detected for the BFD session. Example: bfd-flap-monitor-time 15.

• bfd-max-dampening-time <max-dampening-time-value> — time interval (in minutes) during which the BFD session will remain in dampening state. In the dampening state, the pack will not monitor incoming BFD messages. This state protects the pack from continuous transition between up and down state which could be caused due to network events. Example: bfd-max-dampening-time 15.

  Value 0 implies that the dampening mechanism is disabled for the session. 999 implies that once the BFD session enters dampening state it remains in it forever until you explicitly enable the session.

From the PSN Tunnel Config Mode, enter bfd enable to enable BFD signalling on the tunnel.

Repeat this step for all applicable tunnels.

Associate Tunnels 1 and 3, and Tunnels 2 and 4 as protection pairs.

From the Global Config mode, use the psn-tunnel-protect <tunnel-name-1> <tunnel-name-2> command to specify the protection pair.

For example: (ALU Switching) (Config)# psn-tunnel-protect Tunnel1 Tunnel3 or psn-tunnel-protect Tunnel2 Tunnel4

Tunnel-name-1 and tunnel-name-2 must be in the same direction, inbound or outbound. The two Tunnels must be on two different interfaces. The command should be run twice, for Tunnels in the inbound and outbound directions.

Configure pseudowire (PWE).

Reference:

Procedure 17-2.8: Configure pseudowire (PWE)

Connect the Pseudowire with Tunnel1 and Tunnel2 in the outgoing and incoming directions. The PSN Tunnels must already be configured on the circuit pack on the same physical interface. Note that outgoing-tunnel-name/incoming-tunnel-name at one end is incoming-tunnel-name/outgoing-tunnel-name at the other end.

From the Pseudowire Config Mode, enter connect-psntunnel <outgoing-tunnel-name> <incoming-tunnel-name> where:

• outgoing-tunnel-name - specifies the tunnel in the outgoing direction. Range is a 1 to 31 alphanumeric character string.

• incoming-tunnel-name - specifies the tunnel in the incoming direction. Range is a 1 to 31 alphanumeric character string.

Example: (ALU Switching) (Config-tdmpwe1)# connect-psntunnel Tunnel1 Tunnel2.

When the PWE to PSN Tunnel association must be changed, you must explicitly remove the existing association with the no connect form of the command, and create new associations using the connect form of the command.

Attach T1/E1 interface to Pseudowire (PWE). This command associates a Pseudowire to an interface. Once this association is done, the traffic on the interface is emulated through the Pseudowire.

From the Pseudowire Con[filig ]g Mode, enter connect-interface <interface-number> where interface-number is a T1/E1 port on the VLNC6x circuit pack.

Example: (ALU Switching) (Config-tdmpwe1)# connect-interface a-1-1 or connect-interface m1-1-1-1-1.

From the Pseudowire Config Mode, enter no shutdown to enable the Pseudowire (PWE).

Example: (ALU Switching) (Config-tdmpwe1)# no shutdown.

For configurations using UPSR/SNCP protection, the protection mode at the Hub end VLNC64s must be enabled.

From the Global Config mode, use the protectionmode {enable | disable} command at both VLNC64 Hub nodes to enable protection.

Example: (ALU Switching) (Config)# protectionmode enable.

For configurations on the VLNC64 using UPSR/SNCP protection, configure the PSN Tunnel associated with the Pseudowire to be primary, secondary, or none.

From the Pseudowire Config Mode, enter psntunnel-role {primary | secondary | none} where:

• primary — the Pseudowire is enabled for data transmission whenever the PSN Tunnel is operationally up.

• secondary — the Pseudowire is disabled for data transmission. When the BFD session associated with its PSN Tunnel receives a notification that the PSN Tunnel at the other VLNC64 is down, it activates this Pseudowire for data transmission.

• none — the Pseudowire is enabled for data transmission only when it receives traffic from the remote site.

  Using the values primary and secondary enable end-to-end protection switchover time of the about 50 milliseconds. The value none is supported for backward compatibility of software up to Release 5.1. Using the value none will cause protection switchover time to be about 5 seconds.

Example: (ALU Switching) (Config-tdmpwe1)# psntunnel-role primary.

This command is applicable only when protectionmode is enabled on the pack. This parameter is required only when UPSR compatible protection is offered on the pack, for example, it is one of the 2 VLNC64 packs connecting to a DACS node to offer UPSR compatible protection. See figure below for a typical configuration.

End of steps