02-11-2004 03:42 AM
Hi together,
after updating 2 css to Version 7.20 Build 109,
the "local active connections" counter is wrong.
css01 is Master CSS, css02 is Backup.
If you have a look at the services in FARM1 all local active connections have an utopian value (greater then 4000).
On the backup machine the counter are fine (here you see the local backup connections).
On FARM2 the counters on css01 seem to be ok for 8 of 10 services. service muesrbd-026e_v2 and muesrbd-058e_v2 have a wrong value.
css01# show ver
Version: sg0720109s (7.20 Build 109)
css02# sh ver
Version: sg0720109s (7.20 Build 109)
css01# show rule <FARM1> L4_HTTPS services
Rule Services:
Local Load Threshold: 254
PrimarySorryServer: None
SecondSorryServer: None
VIP Ping Response Decision: Local Services Only
Name: Hits: Wgt: State: Ld: KAlive: Conn: DNS:
----- ----- ----- ------ --- ------- ----- ----
nita 68,951 S-1 Alive 61 HTTP:GET 4928 0
nahum 73,212 S-1 Alive 15 HTTP:GET 7322 0
nemsi 61,670 S-1 Alive 11 HTTP:GET 6937 0
ninon 67,577 S-1 Alive 7 HTTP:GET 5583 0
nixon 59,064 S-1 Alive 7 HTTP:GET 6095 0
norfried 79,248 S-1 Alive 14 HTTP:GET 8276 0
css02# show rule <FARM1> L4_HTTPS services
Rule Services:
Local Load Threshold: 254
PrimarySorryServer: None
SecondSorryServer: None
VIP Ping Response Decision: Local Services Only
Name: Hits: Wgt: State: Ld: KAlive: Conn: DNS:
----- ----- ----- ------ --- ------- ----- ----
nita 0 S-1 Alive 2 HTTP:GET 16 0
nahum 0 S-1 Alive 2 HTTP:GET 4 0
nemsi 0 S-1 Alive 2 HTTP:GET 9 0
ninon 0 S-1 Alive 2 HTTP:GET 5 0
nixon 0 S-1 Alive 2 HTTP:GET 2 0
norfried 0 S-1 Alive 2 HTTP:GET 6 0
css01# show rule <FARM2> L4_HTTP services
Rule Services:
Local Load Threshold: 254
PrimarySorryServer: None
SecondSorryServer: None
VIP Ping Response Decision: Local Services Only
Name: Hits: Wgt: State: Ld: KAlive: Conn: DNS:
----- ----- ----- ------ --- ------- ----- ----
muesrbd-010e_v2 1,044,201 S-1 Alive 11 HTTP:GET 127 0
muesrbd-011e_v2 1,042,967 S-1 Alive 45 HTTP:GET 103 0
muesrbd-012e_v2 1,033,791 S-1 Alive 58 HTTP:GET 125 0
muesrbd-013e_v2 1,077,955 S-1 Alive 30 HTTP:GET 135 0
muesrbd-026e_v2 1,046,702 S-1 Alive 36 HTTP:GET 11119 0
muesrbd-042e_v2 1,060,432 S-1 Alive 23 HTTP:GET 257 0
muesrbd-043e_v2 1,021,603 S-1 Alive 24 HTTP:GET 117 0
muesrbd-044e_v2 1,044,223 S-1 Alive 25 HTTP:GET 106 0
muesrbd-045e_v2 1,046,956 S-1 Alive 18 HTTP:GET 181 0
muesrbd-058e_v2 1,061,355 S-1 Alive 30 HTTP:GET 13802 0
css02# show rule <FARM2> L4_HTTP services
Rule Services:
Local Load Threshold: 254
PrimarySorryServer: None
SecondSorryServer: None
VIP Ping Response Decision: Local Services Only
Name: Hits: Wgt: State: Ld: KAlive: Conn: DNS:
----- ----- ----- ------ --- ------- ----- ----
muesrbd-010e_v2 0 S-1 Alive 2 HTTP:GET 132 0
muesrbd-011e_v2 0 S-1 Alive 2 HTTP:GET 104 0
muesrbd-012e_v2 0 S-1 Alive 2 HTTP:GET 124 0
muesrbd-013e_v2 0 S-1 Alive 2 HTTP:GET 131 0
muesrbd-026e_v2 0 S-1 Alive 2 HTTP:GET 55 0
muesrbd-042e_v2 0 S-1 Alive 2 HTTP:GET 262 0
muesrbd-043e_v2 0 S-1 Alive 2 HTTP:GET 119 0
muesrbd-044e_v2 0 S-1 Alive 2 HTTP:GET 108 0
muesrbd-045e_v2 0 S-1 Alive 2 HTTP:GET 190 0
muesrbd-058e_v2 0 S-1 Alive 2 HTTP:GET 121 0
any ideas or explanantions for that ???
thanks in advance
sascha
02-11-2004 11:37 PM
Sascha,
It looks like a bug.
Can I assume this is using ASR?
If so, can you verify whether the index numbers for the problem numbers match on both CSSs? You can see the index number with "show service
CSCeb82432 was for a problem for a connection counter issue when the service had a different index number on each CSS. Index numbers are assigned when the service is created. The bug above was fixed in 7.20B2.06. This bug talks about the connection count on the backup CSS being incremented incorrectly, which doesn't sound like a true match, so you should verify that CSS02 is not the master at the time of the shor rule. I would recommend upgrade to the latest maintenance release of 7.20. That would be build 3.05 from http://www.cisco.com/cgi-bin/tablebuild.pl/css11500-maint
I could not find any other related issues with this.
If this fails to resolve the issue, you should open a TAC case, unless you would prefer to open the TAC case first.
02-12-2004 12:46 AM
Hi,
the index number on both css are matching correctly.
So I think, I run in a new problem.
css01# show service nita
Name: nita Index: 93
Type: Local State: Alive
Rule ( 172.29.100.187 TCP ANY )
Session Redundancy: Enabled
Redundancy Global Index: 1202
Redirect Domain:
Redirect String:
Keepalive: (HTTP:GET:/admin/Ping.simple 55 2 10 )
Keepalive Hash: e0aa021e21dddbd6d8cecec71e9cf564
Last Clearing of Stats Counters: 02/10/2004 21:13:20
Mtu: 1500 State Transitions: 6
Total Local Connections: 206939 Total Backup Connections: 0
Current Local Connections: 4928 Current Backup Connections: 0
Total Connections: 206939 Max Connections: 65534
Total Reused Conns: 0
Weight: 1 Load: 10
DFP: Disable
css01# show service nahum
Name: nahum Index: 73
Type: Local State: Alive
Rule ( 172.29.100.248 TCP ANY )
Session Redundancy: Enabled
Redundancy Global Index: 1203
Redirect Domain:
Redirect String:
Keepalive: (HTTP:GET:/admin/Ping.simple 55 2 10 )
Keepalive Hash: e0aa021e21dddbd6d8cecec71e9cf564
Last Clearing of Stats Counters: 02/10/2004 21:13:20
Mtu: 1500 State Transitions: 6
Total Local Connections: 216886 Total Backup Connections: 0
Current Local Connections: 7323 Current Backup Connections: 0
Total Connections: 216886 Max Connections: 65534
Total Reused Conns: 0
Weight: 1 Load: 7
DFP: Disable
css02# show service nita
Name: nita Index: 93
Type: Local State: Alive
Rule ( 172.29.100.187 TCP ANY )
Session Redundancy: Enabled
Redundancy Global Index: 1202
Redirect Domain:
Redirect String:
Keepalive: (HTTP:GET:/admin/Ping.simple 55 2 10 )
Keepalive Hash: e0aa021e21dddbd6d8cecec71e9cf564
Last Clearing of Stats Counters: 02/10/2004 22:39:56
Mtu: 1500 State Transitions: 6
Total Local Connections: 0 Total Backup Connections: 16975
Current Local Connections: 0 Current Backup Connections: 11
Total Connections: 16975 Max Connections: 65534
Total Reused Conns: 0
Weight: 1 Load: 2
DFP: Disable
css02# show service nahum
Name: nahum Index: 73
Type: Local State: Alive
Rule ( 172.29.100.248 TCP ANY )
Session Redundancy: Enabled
Redundancy Global Index: 1203
Redirect Domain:
Redirect String:
Keepalive: (HTTP:GET:/admin/Ping.simple 55 2 10 )
Keepalive Hash: e0aa021e21dddbd6d8cecec71e9cf564
Last Clearing of Stats Counters: 02/10/2004 22:39:55
Mtu: 1500 State Transitions: 6
Total Local Connections: 0 Total Backup Connections: 23881
Current Local Connections: 0 Current Backup Connections: 5
Total Connections: 23881 Max Connections: 65534
Total Reused Conns: 0
Weight: 1 Load: 2
DFP: Disable
on the other hand, I have the problem on the master css, not at the backup css, as described in CSCeb82432
css01 is the master, css02 is the backup.
regards
sascha
02-12-2004 01:05 AM
I agree, it looks like a bug and since the sequence numbers match, it is not likely to be CSCeb82432.
02-12-2004 01:13 AM
thanks for support.
I´ll open a case
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide