Content switch Trunk Configuration

[mehdi.amini]

Originally our CSS was servicing only one Network (Vlan3 166.125.134.x)...We needed to add additional network (Vlan6 166.125.22.x) to supprt other services so we reconfigured it to be a trunk connection.  We are having trouble accessing servers from the new Network.  When we ping a server, most of the time it fails...

We created two static routesL

ip route 0.0.0.0 0.0.0.0 166.125.134.1 1<<<<<<<Vlan 3

ip route 0.0.0.0 0.0.0.0 166.125.22.1 1<<<<<<<Vlan 6

In a trunk configuration, do I need these static routes?

I have not been able to find what is the issue.

[lal.antony]

@Mehdi

I am thinking it could be a packet routing issue at the CSS, when it comes to CSS treat it like a normal server not as a switch. So no trunks ports shouldn't be going into it. Multiple links should be going in if you want to have more bandwidth using Link Aggregation.

If you put together a diagram how you have it setup then I can be more helpful in sorting this out with you. Below is a simple diagram to show you how it should be as I think.

Client PC (New VLAN) -----> Cisco Switch (SW1) ----> CSS

SW1 does the Inter-VLAN routing and connections between Client PC and CSS are normal links.

Hope this helps, please rate if useful

Cheers

Lal Antony

www.lalantony.com

[mehdi.amini]

I hope below displys correctly.  Baically I access the VIP address that is defined on the CSS...The CSS, sprays between two hosts.

Host A   Host B

!            !

!            !

!            !

!            !

Server Switch

!

!

!

!

!

!<--------------------------------------------------------!

                                                           !

-------->Distribution switch-------->CSS (accessing the vip)

^

!

!

!

!

!

Core Switch

^

!

!

!

!

My PC (accessing the vip)