Convert an interface to a trunk

[glncalence]

I need to convert a CSS 11506 interface to a trunk. My question is do the CIRCUIT VLAN id numbers need to correlate with catalyst VLANs?

I did not use the switch VLAN numbers on the CSS. I used VLAN 1 (server side) and VLAN 2 (client side). These actually correlate on the Catalyst switch to VLAN 621 and 620 respectively. I have a pair of CSS setup for active/active using VIP and virtual-router/redundant interface failover.

The server side will now need to support a trunk. The catalyst switch server side VLANs are 621 and 622 (new).

If I must have CSS VLANs the same as catalyst then I assume I need to blow away CIRCUIT VLAN 1 configuration and create two new CIRCUIT VLANs on the CSS for 621 and 622. The relevant virtual router/interface redundancy would then be applied to these. Only after that I create a trunk interface and assign these VLAN.

The CIRCUIT VLAN configuration is below:

circuit VLAN1

ip address 192.168.21.10 255.255.255.0

ip virtual-router 1 priority 102 preempt

ip virtual-router 2 priority 101

ip redundant-interface 1 192.168.21.12

ip redundant-interface 2 192.168.21.13

ip critical-service 2 SRVWC20P80

ip critical-service 2 SRVWC21P80

ip critical-service 1 SRVAS28P443

ip critical-service 1 SRVAS29P443

ip critical-service 1 SRVAS26T443

ip critical-service 1 SRVAS27T443

ip critical-service 2 SRVWC30T80

ip critical-service 2 SRVWC31T80

[Gilles Dufour · Accepted solution]

yes, it needs to match the catalyst if you want to trunk, because now the CSS will pass the traffic with the vlan tag to the switch.

So, you will need to change your circuit vlan.

Gilles.

[glncalence]

thanks Gilles