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?
"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.
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.
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
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...