Our company was concerned about bandwidth issues on our 100M int on the CSS v8.10. Currently we have the client vlan on a 1G vlan690 and server vlans on 100M. We are noticing high output drops on all the 6500 100M connected int to the CSS. We were planning on trunking all the vlans on the 1G and also upgrading the failover link from 100M to 1G (box2box red). I would like to know if this new config will work and is this redesign recommended for scalability purposes. I have the new configs attached. Thoughts?
Solved! Go to Solution.
personally I would chose vip/interface redundancy instead of box2box.
The reason is that you will avoid the need of a dedicated link between the 2 CSS, so you can reuse the 2nd gig link to connect to the server vlan.
The 2nd reason for using the other redundancy mode is the faster failover.
With box2box, it takes from 30 sec to a couple of minutes to failover, while with vip/interface redundancy it takes just a few seconds.
Box 2 box is only a good option if you do firewall loadbalancing.
Thx Giles, Understood sounds like a good failover option. One concern though, we have an SCA2 module in slot 3 on both CSS's does this change our failover if say the SCA2 module in slot 3 fails how will this affect vip/interface redundancy option vs box2box?
First, the ssl module that you put in a CSS slot is not an SCA but a CSS5-SSL module or simply an SSL module - just to avoid confusion.
If a module fails while the CSS is up and running, the box should force a reload which will result in the other CSS taking over mastership.
So, the recommended solution to use vip/interface redundancy is still valid.
Perfect, one last question Giles. How does this new vip/redundancy affect my config sync command? I was reading that you have to create seperate app session interfaces in order to execute the config sync command is this true?
I believe you already had APP configured, even with box2box redundancy.
The APP protocol is what we use to pass data between the CSS.
So, you have to create app using any ip belonging to the CSS.
There is then a commandto copy the config from master to backup.
The command is : commit_VipRedundConfig.
This is explained at :