check_1_1_mksp_redundancy_status
This is an old revision of the document!
Check 1+1 MKSP Redundancy Status
May 200
Introduction
When using 1+1 Stream Processors (and for this example I am using 1+1 SP in Compact Mode). The 1+1 SP servers
There are several operations that the SPs are handling, and either SP can be the one doing an operation, these are:
StatMux PSI Scrambling CA MUX
I am unsure of how tightly coupled these components are, i.e. do Mux and PSI always follow each other, I am unsure. StatMux and CA do seem to be quite independent though.
Please note - You must you the Management VIP for the IP Address for this to work.
In a web browser, enter the following:
http://your_MKSP_VIP_address:8080/api/mfsp/activeStandby/status?version=11.3
You will see an output in your browser similar to below (with different instance names)
{ mongo_status: "ok", rabbit_status: "ok", statmux: { active: { SP01: [ "MK01" ], SP02: [ ] }, inactive: { SP01: [ ], SP02: [ "MK01" ] } }, psi: { active: { SP01: [ "mux.mux_52_1_1.outputs.TS1" ], SP02: [ ] }, inactive: { SP01: [ ], SP02: [ "mux.mux_52_1_1.outputs.TS1" ] } }, mux: { active: { SP01: [ "mux_52_1_1" ], SP02: [ ] }, inactive: { SP01: [ ], SP02: [ "mux_52_1_1" ] } }, simulcrypt: { active: { SP01: [ "mux_52_1_1" ], SP02: [ ] }, inactive: { SP01: [ ], SP02: [ "mux_52_1_1" ] } } }
check_1_1_mksp_redundancy_status.1589548941.txt.gz · Last modified: 2023/03/09 22:35 (external edit)