Can't update IP addresses in class maps, 5.3.3b6 GUI

[richwood]

Hi,

We've just upgraded all our WAAS devices to 5.3.3b6, and it is now not possible to add source or destination IP addresses to class maps.

All the devices including CM are on the same release of code.

The class map can be created and the fields (e.g. IP addresses, ports, etc)  entered and saved, but when the change is sumitted, any IP addresses are removed.

Anyone know if this is a known issue?

Regards,

Rick

[Kanwaljeet Singh · Accepted solution]

Hi Rich,

Are you able to add the class-map from accelerator CLI itself?

it could be related to DDTS: CSCuj14126  Unable to configure optimization Class-Map with certain match condition.

It has been found that if you are adding subnet ending with 0, you face that issue. For example if you are adding 192.1.1.0, you will face problem.

Regards,

Kanwal

[richwood]

Hi Kanwal,

Thanks, that is definitely the bug. If I try a subnet that does not end in 0 (e.g. 192.168.0.4 0.0.0.3) it works OK.

Anyone know when the release will be available on CCO? The bug says fxed in 5.3(5.9), but that's not available for download yet.

Regards,

Rick

[Kanwaljeet Singh]

Hi Rick,

Internal research shows that this DDTS is planned to be fixed in 5.4.1 and will release next year. No confirmed ETA yet.

Regards,

Kanwal

[Ryan Posey]

5.4.1 will not support generation 3 hardware 274, 474, 574, 674, 7341 or 7371. Is this still the case?

If the hardware running 5.3.3 is on a Gen3 platform you will have to downgrade to 5.3.1 or get crafty with the subnetting in the CM policies.

[richwood]

Hmm,

That's not terribly good news, all our estate is WAVE 274/474.

The subnet I'm trying to use is 172.30.0.0/15 so the wildcard mask is 0.1.255.255.

The GUI will accept 172.30.0.4 with 0.1.255.255 as the mask, and this does make it into the config of the WAVE box.

e.g.

class-map type waas match-any V8

description match all V8 traffic

match tcp source ip 172.30.0.4 0.1.255.255 destination ip 172.30.0.4 0.1.255.255 port 23

match tcp source ip 172.30.0.4 0.1.255.255 destination ip 194.201.232.4 0.0.0.255 port 23

Any idea if this will work correctly? I assume that only the first 15 bits of the IP address are significant, so the .4 on the end has no effect, other than to allow the GUI to work correctly.

Downgrading to 5.3.1 is not going to be pretty...

regards,

Rick