CSM sticky display changed-no linger displays real servers

Answered Question
Feb 26th, 2007

We are in the process of bringing up a new network core which will eventually replace the old. The old core has multiple 6509 Sup 1a and 2 engines and CSMs - Sw 4.1(5). The new core uses 6513s with SUP720s and CSMs with Sw 4.2(2). The new core also has FWSM on the 6513.

We are in the process of testing our first CSM connection on the new network to an SSL web app. With sticky connectivity. f

The displays appear to have changed. In the old network a sticky display would show the real server address and the timeout. In the new network I get ?garbage? for the real server. Could this be a change in the new code level or does the FWSM have something to do with this. Just trying to ensure this is not a problem.

EXAMPLE ?

OLD 6509 network.

C6509B#sh mod csm 8 stic

group sticky-data real timeout

----------------------------------------------------------------

6 ssl 0554E885:D2071294 10.xx1.87.61 2467

6 ssl A7C230C0:737E6FD1 10.xx1.87.61 3462

On the new network ? 6513_B SUP720 W/FWSM the display shows unreadable characters for the real server and they are changing in each re-display.

SS_6513_B#sh mod csm 4 stick

group sticky-data real timeout

----------------------------------------------------------------

6 ssl 626DFF23:DB0A75EA [email protected]^Z^D0D^C`X 3396

6 ssl 88320A95:EF580761 D^PulD^Z^D0D^C^Yx 3085

SS_6513_B#sh mod csm 4 stick

group sticky-data real timeout

----------------------------------------------------------------

6 ssl 626DFF23:DB0A75EA D^P`tD^Z^D0D^D+^X 3392

6 ssl 88320A95:EF580761 P46^DD^Z^D0D^D'8 3082

I have this problem too.
0 votes
Correct Answer by Gilles Dufour about 9 years 7 months ago

BTW, it's an IOS bug. you need version 12.2(18)SXF or later.

Also, you should probably stay with your old csm version 4.1.6 unless you need the new features of 4.2.x

And if you do need 4.2.x, go to the latest 4.2.6.

There is no reason to use the old version if this is a new install.

Gilles.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Gilles Dufour Mon, 02/26/2007 - 13:58

BTW, it's an IOS bug. you need version 12.2(18)SXF or later.

Also, you should probably stay with your old csm version 4.1.6 unless you need the new features of 4.2.x

And if you do need 4.2.x, go to the latest 4.2.6.

There is no reason to use the old version if this is a new install.

Gilles.

jseelbach Mon, 02/26/2007 - 14:35

Thanks Gilles,

I've found there are other issues with the 12.2(18)SXE4 which also affect us. Will be upgrading to 12.2(18)SXF6 and CSM 4.2(6) ASAP.

Actions

This Discussion