Primary to Standby Central Manager

[bradleyordner]

Hi,

We have migrated to a new Central Manager. I would like to turn the existing Central Manager into a standby, although we did have some issues with this box i.e config not deploying, statistics not displaying.

When it becomes a standby is everything it had in its database wiped clean or should i do a clean install of the WAAS software first?

Thanks

Brad

[smnambia]

Hi Brad,

As per the following WAAS documentation link

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/configuration/guide/maint.html#wp1162642

" When you switch a WAAS Central Manager from primary to standby, the configuration on the Central Manager is erased. The Central Manager, after becoming a standby, will begin replicating its configuration information from whichever Central Manager is now the primary. If standby and primary units are not synchronized before switching roles, important configuration information can be lost. "

So to answer your question,I don't think you need a fresh install of WAAS.Just make sure your primary and standy CM are running the same WAAS version and use the above link for standy CM configuration migration.

Hope the above information helps

Regards

-Smita

Cisco PDI HelpDesk

http://www.cisco.com/go/pdihelpdesk

[bradleyordner]

I have done what the documentation has said an it worked. Although we are running 4.1.5c and it states if using Print Services -

Before you configure a standby Central Manager, you  must manually install your print drivers if you are using WAAS print  services. Print drivers are not automatically replicated from the  primary Central Manager database to the standby device.

How do I manually install Print Drivers? I am thinkign i may have to remove it as a standby and make it primary again.

Thanks

Brad

[smnambia]

For printing are you using the windows print accelerator or are you using the legacy WAAS Print services?

If using the legacy WAAS print services then below is the procedure to install print drivers on WAAS print servers

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/configuration/guide/printsvr.html#wp1043006

But if you are using the windows print accelerator you don't need to do the above procedure,just make sure that the windows print accelerator is checked

as per the below document on individual wae devices

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/configuration/guide/policy.html#wp1066936

search for "Windows Print Accelerator"

If you have already deployed Print server in your data center then the WAAS Windows print accelerator will enable employees located at branch office to print documents located in their own branch location quickly.

If  you want to keep the print server at branch office itself then they can do so by deploying Cisco WAAS virtualization capable WAE appliances (WAxE-x74). These WAEs will allow them to run Windows Server 2008 (core) on which they can configure Windows Print Server.

We do suggest Legacy print services users should migrate to the Windows Print accelerator starting WAAS 4.2.1.

Also the Windows Print Accelerator is enabled by default when you enable the CIFS accelerator on WAAS 4.1.x and above

Hope the above information helps

Regards

-Smita

[bradleyordner]

I beleive we are using the Legacy Print Servers so all WAE's at remote branches are Print Servers and we distribute the drivers from the central manager.

So if our primary fails and we promote our standby central manager to primary then i need the drivers on standby.

I thought Print Services were being removed in later version of Waas code?