Broker Registration of Services not managed by Failover Manager
search cancel

Broker Registration of Services not managed by Failover Manager

book

Article ID: 410799

calendar_today

Updated On:

Products

VMware Telco Cloud Service Assurance

Issue/Introduction

  •  You have Failover Manager configured with both the Failover Manager service and the active Broker being on the Standby server.

  • For services not managed by Failover Manager, you need confirmation which Broker the service on the Active and Standby servers should be registering with? This particularly relates to MPLS VPN-Tagging service, Topology Split Manager service and Syslog Manager service.

Environment

All supported releases of Smart

Resolution

  • The services which are started without being configured under failover.conf will act as a standalone domain registered with the local broker and if the local broker is down then domain will not be accessible.

  • It depends on the domain which broker it is registered with, you can get these domains registered to any broker and the domains will be registered to that particular domain only.