Configuring high availability in BMC Service Resolution
You can achieve high availability in BMC Service Resolution by performing certain simple configurations.
The following topics are provided:
High-availability architecture in BMC Service Resolution
Refer to the following architecture diagram to understand the architecture.
Configurations/Setup required to enable failover
- Ensure that two BMC TrueSight instances are installed on separate hosts. See Installing from the BMC TrueSight online documentation.
- Configure the Cells of the two BMC TrueSight instances in HA mode. See To configure cells in HA mode.
- Configure the Cells of the two BMC TrueSight instances to propagate events using the One Of policy. See Creating a new propagation policy from the BMC TrueSight online documentation.
Failover scenarios
The following diagrams depict how failover is achieved when any one of the component fails:
- If Service Desk Integration Gateway goes down; failover is achieved because the event policy is configured to use the propagate to One Of option.
- If the Cell goes down on BMC TrueSight server: Failover is achieved because the Cells are configured to be in HA mode.
- If BMC TrueSight server goes down: Failover is achieved because the Cells are configured to be in HA mode.
Partial high-availability architecture
Refer to the following architecture diagram to understand the partial high-availability architecture in BMC Service Resolution.
In the partial high-availability architecture, there is no BMC TrueSight stand by server. Therefore, when the Primary server goes down, failover is not achieved.
However, failover can be achieved in the following scenarios:
- When the Cell 1 goes down, requests are routed through Cell 2. Failover to Cell 2 is achieved because the cells are configured to be in HA mode.
- When the SDiG 1 goes down, requests get routed through SDIG 2. Failover to SDIG 2 is achieved because the event policy is configured to use the Propagate to One of policy option.
To configure cells in HA mode
- On the Primary Infrastructure Management server, edit the mcell.dir file and add the following entries:
- Add an entry for the Primary server as follows:
cell Primary mc Primary:1828 Secondary:1828
- Add an entry for the Secondary server as follows:
cell Secondary mc Primary:1828 Secondary:1828
- Add entries for Primary and Secondary gateways as follows:
gateway.ibrsd IBRSD mc Primary:3115
gateway.ibrsd IBRSDSecondary mc Secondary:3115
- Add an entry for the Primary server as follows:
- On the Secondary Infrastructure Management server, edit the mcell.dir file and add the following entries:
- Add an entry for the Secondary server as follows:
cell Secondary mc Primary:1828 Secondary:1828
- Add an entry for the Primary server as follows:
cell Primary mc Primary:1828
Secondary
:1828 - Add entries for Primary and Secondary gateways as follows:
gateway.ibrsd IBRSD mc Primary:3115
gateway.ibrsd IBRSDSecondary mc Secondary:3115
- Add an entry for the Secondary server as follows:
- Restart JServer process.
Comments
Dear Experts ,
Can I create a HA Cell with the same TSIM somewhere else in DR site so my events always remains in sync .
What will happen at Presenatation server if this HA Configuration is enabled
Will there be duplicate events at TSPS ,
As without TSPS we cant login to TSIM
TSPS : Truesight Presentation Server
TSIM : Truesight Infrastruture Management
Regards
Abhay
Hi Team,
Could we please get this confirmed. What does the below statement mean :
On Primary TSIM server : Add entries for Primary and Secondary gateways as follows: gateway.ibrsd IBRSD mc Primary:3115
gateway.ibrsd IBRSDSecondary mc Secondary:3115
If we add :
gateway.ibrsd IBRSD mc Primaryservername:3115
gateway.ibrsd IBRSD mc Secondaryservername:3115
The secondary server IBRSD entry is ignored.
Thanks
Harshal
Hi Team, at "Configurations/Setup required to enable failover" are placed 2 wrong links. The "Installing" from the first point links to BMC 9.6 instead of TrueSight. The " creating a new propagation policy" also links to BMC 9.6 instead of TrueSight.
Regards
Log in or register to comment.