Cisco Cisco Prime Network 3.8 Release Notes

If a unit fails after executing network-conf, do the following:

For roll back to 3.8, copy the ~/Main/.ana and ~/Main/.version file from the location specified in 

, back to ~/Main. 

Copy $ANAHOME/Main/registry/ConfigurationFiles/UNIT_IP/avm99.xml file from the gateway 
to the corresponding unit (UNIT_IP) to $ANAHOME/Main/registry. The UNIT_IP  should be of the 
form 0.0.0.1.

Start the unit (anactl start (ANA 3.7.x) or networkctl start (3.8 onwards)) without running 
network-conf again.

If you have rolled back to 3.8, run networkctl start command to start the units or run anactl start 
command if you have rolled back to ANA 3.7.x.

Use Prime Network Administration(for 3.8) or ANA Manage (for 3.7.x) to reconnect standby units.

For units behind NAT, remove the newly created unit from the gateway.

You must perform the following steps after Cisco Prime Network installation or after an upgrade for the 
Network Discovery feature to work in Prime Network 3.8.1. For more details on the network discovery 
tool, see 

Log in to the Prime Network gateway machine OS shell as the Prime Network user.

Change the user to be the super user.

Enter the super user password.

Navigate to the scripts folder located under the home directory of the Prime Network user.

Change to tcsh shell.

Execute the setFpingPermissions script.

The setFpingPermissions script is executed to ensure successful functioning of the network discovery 
tool and sets some permissions to the Fping utility. You will get a Fping permissions set successfully 
message if the utility is successfully executed. If you do not receive this message, please contact your 
Cisco account representative for assistance.