Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

abnormal traffic flooding is killing our cat6513 including csm module.

Hi everyone

First of all below is our environment explanation.

Our datacenter have 4*6513 switches.

2 switch do core role which connect distribute

switches so their names is core1, core2.

2 switch do datacenter role which connect many

servers so their name is datacenter1, datacenter2.

and one "A" named server is connected to core1,2

using hsrp.

and one Backup db server for "A" server is connected

to datacenter1, datacenter2 using hsrp.

and Datacenter switches have a csm module per

switch.

csm module have a role to load balance "B"named

servers using vip.

and csm module is configured not to load balance

backup db server for "A".

Then our problem is when "A" server forward traffics

to backup db server for "A", These traffics also is

unexpectively flooded to "B" servers.

So many ports is experenced traffics over 90%.

I believe It is abnormal.

Could you understand my speaking? But it is true.

I gather It may be a bug. I am very frustrated.

Would you help me asap.

Thanks for reading.

4 REPLIES
Cisco Employee

Re: abnormal traffic flooding is killing our cat6513 including c

sounds more like a config issue than a bug.

Could you post your config.

Are B servers using multicast mac addresses ?

What's your CSM software version ?

There was indeed a bug where the csm would accept traffic that was not for it.

Anything lower than 3.1.4 I would recommend an upgrade.

Gilles.

New Member

Re: abnormal traffic flooding is killing our cat6513 including c

hi Gilles

thnks for your reply.

our csm s/w version is 3.1.3.

below is show runnig -config in our problem switch.

----------------- show running-config ------------------

Building configuration...

Current configuration : 22785 bytes

!

! Last configuration change at 15:27:32 KST Thu Dec 18 2003

! NVRAM config last updated at 18:31:24 KST Wed Dec 17 2003

!

version 12.1

service timestamps debug uptime

service timestamps log datetime localtime

service password-encryption

!

hostname DATA_CENTER_2

!

boot system flash sup-bootflash:

boot system flash slot0:

enable password 7

!

clock timezone KST 9

diagnostic level minimal

ip subnet-zero

no ip source-route

!

!

no ip domain-lookup

!

mls flow ip destination

mls flow ipx destination

!

spanning-tree extend system-id

spanning-tree vlan 20 priority 28672

module ContentSwitchingModule 4

vlan 11 client

ip address 169.140.128.58 255.255.255.224

gateway 169.140.128.33

!

vlan 12 server

ip address 169.140.128.58 255.255.255.224

!

vlan 20 client

ip address 169.140.60.6 255.255.255.0

gateway 169.140.60.1

!

vlan 21 server

ip address 169.140.60.6 255.255.255.0

!

probe AP_7779 tcp

interval 5

failed 10

!

probe AP_6001 tcp

interval 600

!

probe E-CAMPUS_80 tcp

interval 5

failed 10

!

probe E-CAMPUS_8282 tcp

interval 5

failed 10

!

probe MTS-TEST_8001 tcp

interval 5

failed 10

!

probe YARD-TEST_8002 tcp

interval 5

failed 10

!

probe MAS-TEST_8003 tcp

interval 5

failed 10

!

probe MTS-PATCH_8001 tcp

interval 5

failed 10

!

probe YARD-PATCH_8002 tcp

interval 5

failed 10

!

probe MAS-PATCH_8003 tcp

interval 5

failed 10

!

probe MES-TEST_80 tcp

interval 5

failed 10

!

probe MES-MAIN_80 tcp

interval 5

failed 10

!

probe MTS_8001 tcp

interval 5

failed 10

!

probe MTS_8002 tcp

interval 5

failed 10

!

probe YARD_8001 tcp

interval 5

failed 10

!

probe MTS-TEST_8002 tcp

interval 5

failed 10

!

probe MTS-TEST_8003 tcp

interval 5

failed 10

!

probe YARD-TEST_8001 tcp

interval 5

failed 10

!

serverfarm E-CAMPUS_80

nat server

no nat client

predictor leastconns

real 169.140.60.101

inservice

real 169.140.60.103

inservice

probe E-CAMPUS_80

!

serverfarm E-CAMPUS_8282

nat server

no nat client

predictor leastconns

real 169.140.60.101

inservice

real 169.140.60.103

inservice

probe E-CAMPUS_8282

!

serverfarm MAS-PATCH_8003

nat server

no nat client

predictor leastconns

real 169.140.60.53

inservice

real 169.140.60.54

inservice

probe MAS-PATCH_8003

!

serverfarm MAS-TEST_8003

nat server

no nat client

predictor leastconns

real 169.140.60.46

inservice

real 169.140.60.47

inservice

probe MAS-TEST_8003

!

serverfarm MES-MAIN_80

nat server

no nat client

predictor leastconns

real 169.140.60.151

inservice

real 169.140.60.152

inservice

real 169.140.60.131

inservice

real 169.140.60.132

inservice

probe MES-MAIN_80

!

serverfarm MES-TEST_80

nat server

no nat client

predictor leastconns

real 169.140.60.42

inservice

real 169.140.60.43

inservice

real 169.140.60.46

inservice

real 169.140.60.47

inservice

probe MES-TEST_80

!

serverfarm MTS-PATCH_8001

nat server

no nat client

predictor leastconns

real 169.140.60.53

inservice

real 169.140.60.54

inservice

probe MTS-PATCH_8001

!

serverfarm MTS-TEST_8001

nat server

no nat client

predictor leastconns

real 169.140.60.42

inservice

real 169.140.60.43

inservice

probe MTS-TEST_8001

!

serverfarm MTS-TEST_8002

nat server

no nat client

predictor leastconns

real 169.140.60.42

inservice

real 169.140.60.43

inservice

probe MTS-TEST_8002

!

serverfarm MTS-TEST_8003

nat server

no nat client

predictor leastconns

real 169.140.60.42

inservice

real 169.140.60.43

inservice

probe MTS-TEST_8003

!

serverfarm MTS_8001

nat server

no nat client

predictor leastconns

real 169.140.60.151

inservice

real 169.140.60.152

inservice

probe MTS_8001

!

serverfarm MTS_8002

nat server

no nat client

predictor leastconns

real 169.140.60.151

inservice

real 169.140.60.152

inservice

probe MTS_8002

!

serverfarm STS_AP

nat server

no nat client

predictor leastconns

real 169.140.128.43

inservice

real 169.140.128.44

inservice

probe AP_7779

!

serverfarm STS_YARD_6001

nat server

no nat client

predictor leastconns

real 169.140.128.43

inservice

real 169.140.128.44

inservice

probe AP_6001

!

serverfarm YARD-PATCH_8002

nat server

no nat client

predictor leastconns

real 169.140.60.53

inservice

real 169.140.60.54

inservice

probe YARD-PATCH_8002

!

serverfarm YARD-TEST_8001

nat server

no nat client

predictor leastconns

real 169.140.60.46

inservice

real 169.140.60.47

inservice

probe YARD-TEST_8001

!

serverfarm YARD-TEST_8002

nat server

no nat client

predictor leastconns

real 169.140.60.46

inservice

real 169.140.60.47

inservice

probe YARD-TEST_8002

!

serverfarm YARD_8001

nat server

no nat client

predictor leastconns

real 169.140.60.131

inservice

real 169.140.60.132

inservice

probe YARD_8001

!

I will post one more message because of over bytes.

continued.

New Member

Re: abnormal traffic flooding is killing our cat6513 including c

sticky 5 netmask 255.255.255.255 timeout 20

!

vserver AP_6001

virtual 169.140.128.42 tcp 6001

serverfarm STS_YARD_6001

replicate csrp connection

persistent rebalance

inservice

!

vserver AP_7779

virtual 169.140.128.42 tcp 7779

serverfarm STS_AP

sticky 20 group 5

replicate csrp sticky

replicate csrp connection

persistent rebalance

inservice

!

vserver E-CAMPUS_80

virtual 169.140.60.100 tcp www

serverfarm E-CAMPUS_80

replicate csrp connection

persistent rebalance

inservice

!

vserver E-CAMPUS_8282

virtual 169.140.60.100 tcp 8282

serverfarm E-CAMPUS_8282

replicate csrp connection

persistent rebalance

inservice

!

vserver MAS-PATCH_8003

virtual 169.140.60.52 tcp 8003

serverfarm MAS-PATCH_8003

replicate csrp connection

persistent rebalance

inservice

!

vserver MAS-TEST_8003

virtual 169.140.60.45 tcp 8003

serverfarm MAS-TEST_8003

replicate csrp connection

persistent rebalance

inservice

!

vserver MES-MAIN_80

virtual 169.140.60.149 tcp www

serverfarm MES-MAIN_80

replicate csrp connection

persistent rebalance

inservice

!

vserver MES-TEST_80

virtual 169.140.60.40 tcp www

serverfarm MES-TEST_80

replicate csrp connection

persistent rebalance

inservice

!

vserver MTS-PATCH_8001

virtual 169.140.60.52 tcp 8001

serverfarm MTS-PATCH_8001

replicate csrp connection

persistent rebalance

inservice

!

vserver MTS-TEST_8001

virtual 169.140.60.41 tcp 8001

serverfarm MTS-TEST_8001

replicate csrp connection

persistent rebalance

inservice

!

vserver MTS-TEST_8002

virtual 169.140.60.41 tcp 8002

serverfarm MTS-TEST_8002

replicate csrp connection

persistent rebalance

inservice

!

vserver MTS-TEST_8003

virtual 169.140.60.41 tcp 8003

serverfarm MTS-TEST_8003

replicate csrp connection

persistent rebalance

inservice

!

vserver MTS_8001

virtual 169.140.60.150 tcp 8001

serverfarm MTS_8001

replicate csrp connection

persistent rebalance

inservice

!

vserver MTS_8002

virtual 169.140.60.150 tcp 8002

serverfarm MTS_8002

replicate csrp connection

persistent rebalance

inservice

!

vserver YARD-PATCH_8002

virtual 169.140.60.52 tcp 8002

serverfarm YARD-PATCH_8002

replicate csrp connection

persistent rebalance

inservice

!

vserver YARD-TEST_8001

virtual 169.140.60.45 tcp 8001

serverfarm YARD-TEST_8001

replicate csrp connection

persistent rebalance

inservice

!

vserver YARD-TEST_8002

virtual 169.140.60.45 tcp 8002

serverfarm YARD-TEST_8002

replicate csrp connection

persistent rebalance

inservice

!

vserver YARD_8001

virtual 169.140.60.130 tcp 8001

serverfarm YARD_8001

replicate csrp connection

persistent rebalance

inservice

!

ft group 1 vlan 100

priority 100

===abbreviation====

that is our config all.

the above switch which shows config is backup datacenter switch.

we are using 2 switchs(active/backup) for box to box redundancy.

so active and backup switch are using the same h/w, s/w version.

and active switch do not have any problem.

just only backup switch have this problem

I can not understand that active switch is no problem

and backup switch is problem even though two switchs are using the same h/w, s/w version.

How can i search a bug where the csm would accept traffic that was not for it?

please help me know what is the possible causes and possible solutions.

tnanks for reading.

kimsunjoo

Cisco Employee

Re: abnormal traffic flooding is killing our cat6513 including c

I was thinking about this bug :

CSCea02255: CSM responds to packets not destined for its MAC addresses

But your version includes the fix.

Did you open a case with the TAC yet ?

This will probably requirer a deeper analysis than just a look at the config.

Gilles.

122
Views
0
Helpful
4
Replies