topic FWSM active-active config( Intra chassis) in Network Security

FWSM active-active config( Intra chassis)

Madhan Kumar — Mon, 11 Mar 2019 19:13:53 GMT

Hi all,

Is anybody is having configuration for same chasis acctive-active configuration( intra cheass) ?. I am going to install the 2 fwsm in the same chasis with active-active configuratuion. In cisco site only the inter chasis configuration is available.If anybody is having the config kindly send me the same.

Thanks & Regards

R.MADHANKUMAR

Re: FWSM active-active config( Intra chassis)

Marcin Latosiewicz — Sun, 28 Nov 2010 23:06:38 GMT

Hi,

Intra-chassis failover and inter-chassis failover - there is no difference in configuring them on FWSM-side. The FWSM is not aware if the peer device is in same or another chassis.

The only difference on the chassis side is that you need to push same set of vlan-groups to both modules.

Active/active or active/standby configuration is differentitiated on FWSM.

Marcin

Re: FWSM active-active config( Intra chassis)

Madhan Kumar — Mon, 29 Nov 2010 05:53:17 GMT

Hi,

Thanks for your reply. In intra chasis we are using the same MSFC, I mean the same router for uplinks for both modules, Whereas in inter chasis we are using different MSFC. My doubt is we really require a HSRP config on the SVIs created for outside vlans on intra-chasis failover?.

Thanks & Regards

R.MADHANKUMAR

India.

Re: FWSM active-active config( Intra chassis)

Madhan Kumar — Mon, 29 Nov 2010 06:01:39 GMT

Dear Marcin,

Thanks for your reply.

In inter-chasis failover we using different MSFC,I mean different routers, whereas in intra-chasis failover we are using the same MSFC. My doubt is we really require a HSRP config on the switch for outside SVIs?.

Thanks & Regards

R.MADHANKUMAR

India.

Re: FWSM active-active config( Intra chassis)

Marcin Latosiewicz — Mon, 29 Nov 2010 09:00:55 GMT

Purely from FWSM's point of view HSRP is not required on the chassis in either of the scenarios, there is not problem to run traffic to a single SVI.

However one might think of a problem when for some reason L3 intreface becomes unavible on chassis 1 and usally this should be taken up by chassis 2.

That being said, FWSM does not even require that L3 address is configured on the chassis, it can be configured on any other device, L2 adjacant of course.

The device was built to be agnostic of the operation of MSFC (except "firewall ..." configuration).

Marcin