Smarts: Failover Manager server shows SAM and OI domains Status UP and Role UNKNOWN
search cancel

Smarts: Failover Manager server shows SAM and OI domains Status UP and Role UNKNOWN

book

Article ID: 331987

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:


Smarts SAM and OI Domains are not initializing with the Failover Manager properly.

Failover Manager is up and running while one or more SAM or OI servers are showing up in the failover status with P-Status: UP and Role: UNKNOWN,
 
All non-SAM and non-OI servers have up in the failover status with proper p-Status and Role.  

Smarts IP, BGP, and MBIM initialize properly with the correct status and role UP and Active, or UP and Standby per expectations.

Environment

VMware Smart Assurance - SMARTS

Cause

The most common cause of this issue, is the subscriptions in the Active and Backup domain are not configured properly for the SAM and OI domains.  

1. There are no subscriptions to the peer SAM/OI servers in his SAM Console.
2. There are subscriptions to peer SAM /OI setup but they are incorrect
3. There are subscriptions to peer SAM/OI setup but they are not enabled and disabled properly
4. Customer subscriptions to MBIM in the Active/ Backup SAM configuration are incorrect.

Resolution

This resolution applies to each possible cause above
 
A. Check customer's failover configuration.
  
  1. Go to each host where customer has started his SAM/OI server.
  2. Execute the command "hostname". Make note of the output.
  3. Open conf/failover/failover.conf from the installation from where the customer starts his failover server.
  4. Verify his configuration for that SAM/OI server
    a. Verify customer uses the exact hostname returned in step 2. Exact!
    b. Verify the other details should be consistent and correct.
    c. Make note of hostname, port ans servername
        
B. Check the customer subscriptions using the Global Manager Admin Console.
  1. Verify Primary SAM/OI server first
    a. Connect to the primary SAM/OI using the Console. <hostname>:<port>/<servername>
    b. Check the underlying server
    c. For SAM and OI it goes
        |-------------------------------------------------------------------------
        |Subscription                                                Enable/Disable
        |-------------------------------------------------------------------------
        |<Secondary SAM Host>:<Its port>/<Secondary SAM server>     Disabled
        |Other Intended underlying servers                          Enabled
        |-------------------------------------------------------------------------
    d. Additionally for SAM, If you have MBIMs, For each MBIM
        |-------------------------------------------------------------------------
        |Subscription                                                Enable/Disable
        |-------------------------------------------------------------------------
        |<Primary   MBIM Host>:<Its port>/<Primary   MBIM server>    Enabled
        |<Secondary MBIM Host>:<Its port>/<Secondary MBIM server>    Disabled
        |-------------------------------------------------------------------------
    e. Note, the details of serverNames, ports and hostnames should be exactly the same as what we saw in failover.conf. Reiterating, exact!
    f. After making the changes [if any] make sure you reconfigure the server.
    
  2. Verify Secondary SAM/OI server next
    a. Connect to the secondary SAM/OI using the Console. <hostname>:<port>/<servername>
    b. Check the underlying server
    c. For SAM and OI it goes
        |-------------------------------------------------------------------------
        |Subscription                                                Enable/Disable
        |-------------------------------------------------------------------------
        |<Primary SAM Host>:<Its port>/<Primary SAM server>         Enabled
        |Other Intended underlying servers                          Disabled
        |-------------------------------------------------------------------------
    d. Additionally for SAM, If you have MBIMs, For each MBIM
        |-------------------------------------------------------------------------
        |Subscription                                                Enable/Disable
        |-------------------------------------------------------------------------
        |<Primary   MBIM Host>:<Its port>/<Primary   MBIM server>    Disabled
        |<Secondary MBIM Host>:<Its port>/<Secondary MBIM server>    Disabled
        |-------------------------------------------------------------------------
    e. Note, the details of serverNames, ports and hostnames should be exactly the same as what we saw in failover.conf. Reiterating, exact! Change any subscriptions that do not match the above style.
    f. After making the changes [if any] make sure you reconfigure the server.
    


Additional Information

You will need to directly access the Active SAM and OI domains via the Global Management Console to update the subscriptions on the Primary and the Backup Server each domain.