CSM 4.2.1 redundancy changes

[shamilton-wilkes]

The docs aren't very clear: bit's of them still show different IP's configured on each blade, and an alias command to create one IP to be the gateway for the reals. Then the new Configuring Redundancy chapter shows the new option of configuring the IP only on the primary with the alt keyword, then the secondary modules IP.

So aliases are no longer required right? The way to go is to use my current alias IP as the IP for the primary module now? (This is great as it saves an IP per subnet)

TIA

Simon

[Gilles Dufour]

Simon

the alias is still required.

Nothing changed in terms of functionality.

The only difference is that you can now configure the secondary CSM from the primary using the ALT keyword.

Regards,

Gilles.

[shamilton-wilkes]

Thanks Gilles, the thing confusing me (and making me gunshy from testing in a production environment) is the docs saying that now I MUST configure the alt address from the primary, as other IP addresses on the secondary will be removed when the config is synced.

Simon

[mruuth]

Hi,

If i upgrade from 4.1.2 to 4.2.1 and have active/standby state, can I just follow the instructions for hitless upgrade and after that invoke the command hw-module csm x standby config-sync without any other change?

Regards

Mats