General Network Configuration Manager errors

The following table lists general errors and solutions in Network Configuration Manager.

Error	Solution
To conserve per-device communication resources, Network Configuration Manager migrates active sessions between user and privilege modes. Each driver class provides the specifications of this process in the commands for Cisco driver classes. The "disable" command is used when the session is deemed to be in the privilege mode. When the external authentication provides the account credential in the privilege mode, the usage of saved commands executes in the user mode, which requires issuing the "disable" command in terminal communications. The Cisco common driver code checks for the existence of a privilege password. If it does not exist, the process fails to guard against locking out of the session, and returns to the privilege mode.	This scenario can be overcome by saving a privilege password for a device in the Communications tab, this can also be done for multiple devices by appropriately highlighting the devices before accessing the tab.
A database failure warning message was displayed on a Windows server. Recurring Daily Network Pull Job failed to schedule and remained in the approved status or executed at a wrong time.	This is a table corruption issue. The recurring jobs were created and they occupy a part of the cm_job table. A workaround for this issue is to cluster the table by executing the following steps: Stop services Run the following command at the database prompt: cluster cm_job_pkey on cm_job; at the database prompt Restart services Observe the behavior of the Job on the next run.
JBOSS core dump is observed on Linux platforms	Check for the JAVA_OPTS value. The MaxPermSize should be 512m. Restart JBOSS.
Launching of the user interface fails when it is launched using http.	Stop the iptables service using the command /etc/init.d/iptables stop Relaunch the user interface.
Out of memory error in the client log. When large number of device configuration is selected for saving, the out of memory error is observed.	The maximum number of device configuration that can be saved is 400 only.
Catalina displays the following error message: The lock box stable value threshold was not met because the system fingerprint has changed. To reset the system fingerprint, open the lock box using the pass phrase. : File : /opt/smarts-ncm/lockbox/xml/csp.clb	Perform the following steps: cd /opt/smarts-ncm/bin source /etc/voyence.conf cmd ./cstdriver -lockbox ../data/lockb.clb -passphrase <passphrase for lockbox> Restart vcmaster.