Forum Discussion
Path to Remote UCS File Missing
Recently, I've inherited a pair of Virtual Edition F5s in an Azure Cloud network. A Microsoft Consultant added 2 nics to the standby F5, and rebooted the device. After waiting 30 minutes, I determined something was wrong, and logged into the CLI. The device is labeled as (cfg-sync unknown)(inoperative). The message "Re-starting apmd" is constantly being displayed, so I ran the command stop sys service apmd. Logged back into the GUI and noticed that the automatically generated config file (created from auto back up iapp) is missing. The consultant noticed that the CIFS mount is failing. The device comes up as unknown for it's status, so I can't simply sync it with the operational Active F5. How can I get the configuration back and properly sync these F5s?
i would contact support, they can jump into a remote session and work this out.
the large number of possibilities make it tricky to work through it here.
if you don't have support i would just rebuild the system and after the basics (IP / VLANs and such) are done sync from the working one.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com