[c-nsp] FWSM traffic distribution across internal etherchannel
NMaio at guesswho.com
NMaio at guesswho.com
Wed Oct 28 06:51:30 EDT 2009
David,
It appears that I might have misunderstood the original question since it was only pertaining to traffic from the FWSM. My apologies.
Thanks,
Nick
From: David White, Jr. (dwhitejr) [mailto:dwhitejr at cisco.com]
Sent: Tuesday, October 27, 2009 10:32 PM
To: Nicholas Maio
Cc: j4bles at gmail.com; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] FWSM traffic distribution across internal etherchannel
Hi Nick,
Changing the SUP's load-balancing algorithm (which is what is described in the link provided) only affects the traffic that egresses the switch and ingresses the FWSM. It does not impact the packet distribution in the reverse direction (egress the FWSM and ingress on the switch).
I didn't indicate that I would need to know the traffic profile to determine the correct SUP load-balancing algorithm, but rather to explain why ports 3 and 6 were mainly utilized for traffic egressing the FWSM - which was Jack's original question.
Sincerely,
David.
NMaio at guesswho.com<mailto:NMaio at guesswho.com> wrote:
David,
The section named "Customizing the FWSM Internal Interface" in the following page
http://www.cisco.com/en/US/docs/security/fwsm/fwsm31/configuration/guide/switch_f.html
would be helpful.
As you stated you would need to know the traffic profile to detemine the correct algorithm but why would you say that there aren't any commands to change this? The command is not run in the fwsm but rather the switch/router.
Nick
________________________________________
From: cisco-nsp-bounces at puck.nether.net<mailto:cisco-nsp-bounces at puck.nether.net> [cisco-nsp-bounces at puck.nether.net<mailto:cisco-nsp-bounces at puck.nether.net>] On Behalf Of David White, Jr. (dwhitejr) [dwhitejr at cisco.com<mailto:dwhitejr at cisco.com>]
Sent: Tuesday, October 27, 2009 8:29 PM
To: jack b
Cc: cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
Subject: Re: [c-nsp] FWSM traffic distribution across internal etherchannel
Hi Jack,
Yes, it is most likely that this is normal. There are no CLI commands
on the FWSM to adjust this. I would have to understand your traffic
profile along with your config to tell you why the given profile is
almost exclusively utilizing ports 3 and 6.
Sincerely,
David.
jack b wrote:
I have a FWSM running 2.3(4)11 in slot 4 of a 6509. I have noticed that I am
getting unequal traffic distribution on the links that make up the ether
channel bundle between the FWSM and 6509.
Here is a snapshot of the traffic distribution
4/1 in 28.99mbps out 458.10mbps
4/2 in 12.37mbps out 248.31mbps
4/3 in 960.86mbps out 294.95mbps
4/4 in 34.07mbps out 505.22mbps
4/5 in 15.08mbps out 243.10mbps
4/6 in 950.63mbps out 262.68mbps
In is traffic from the FWSM to the switch and out is traffic from the switch
to the FWSM.
Is this normal operation, or is there a way to distribute the traffic from
the FWSM to the switch more evenly?
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list