Technical Note: 'No Servers found' error in Secondary Server UI

[cmaheu]

Description
Unexpected behavior when the following sequence is performed while the Secondary Server is in control:
1. Stop management processes on Primary Server (shutdownNAC -kill)
2. Reboot or shutdown Primary Server


Symptoms:
- Administration UI is accessible on Primary and Secondary Servers
- Secondary Server Administration UI displays "No Servers found verify .networkConfig" in Dashboard

- Yams processes are running on both Primary and Secondary Servers

- CampusManager process not running on the Secondary Server (should be in control)

Secondary Server CLI Example:
> jps
19670 Yams
34137 TomcatAdmin
60763 Jps
20059 TomcatPortal
19788 Yams

Scope
Version:  8.8

Solution

Procedure to clear condition:

Login to CLI of both appliances as root

1. Secondary Server type

shutdownNAC -kill

2. Primary Server type

shutdownNAC -kill

3. Secondary Server type

startupNAC

4. Wait until processes are up and running on Secondary Server

5. Primary Server type

startupNAC

6. Primary Server: Verify "Status=2" in /bsc/campusMgr/bin/.networkconfig file (indicates Secondary Server in control)

7. Resume control to the Primary Server.

UI Method: Secondary Server UI Summary panel in dashboard - click Resume Control (this will take several minutes to complete)   

CLI Method: See related KB article below

Workaround:
To prevent this behavior, use one of the following options if management is already down on the Primary Server prior to a shutdown or a reboot.

Option 1:

1. Primary Server:  Modify /bsc/campusMgr/bin/.networkConfig

2. Change  "Status=1" to “Status=2” and save file

Option 2:

1. Primary Server type
shutdownNAC -kill

2. Wait until Secondary Server is running and in control

3. Primary Server type
startupNAC

4. Secondary Server UI: Wait for the Primary Server status to change from "Management Down" to "Running - Not in Control"

5. Primary Server: Shutdown or reboot

To shutdown type
shutdown now

To reboot type
reboot

Solution:  Under investigation.

ID 0681256

Related Articles

Technical Note: Manual High Availability (HA) restore in a L3 environment via CLI