Differences

This shows you the differences between two versions of the page.

--- check_1_1_mksp_redundancy_status [2020/05/15 13:54] – created walkeradmin
+++ check_1_1_mksp_redundancy_status [2023/03/09 22:35] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-Check 1+1 MKSP Redundancy Status
+====== Check 1+1 MKSP Redundancy Status ======
+<color darkorange>May 2020</color>
+----
+==== 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 <color #ed1c24>Management VIP</color> 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) - <color #ed1c24>If your output is one long line or lines of text, then install a JSON viewer plugin in to your browser.</color>
+<file>
+{
+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"
+        ]
+    }
+}
+}
+</file>
+In the output above we can see that <color #00a2e8>Mongo</color> and <color #00a2e8>Rabbit</color> status are <color #00a2e8>ok</color>. <color #00a2e8>statmux</color>, <color #00a2e8>psi</color>, <color #00a2e8>mux</color> and <color #00a2e8>simulcrypt</color> are all <color #00a2e8>active</color> on <color #00a2e8>SP01</color> (this is the active SP on the nCompass ESM).
+\\
+\\
+Now I will do a Mux switch from nCompass ESM.
+<file>
+{
+mongo_status: "ok",
+rabbit_status: "ok",
+mux: {
+    active: {
+        SP01: [ ],
+        SP02: [
+            "mux_52_1_1"
+        ]
+    },
+    inactive: {
+        SP01: [
+        "mux_52_1_1"
+        ],
+        SP02: [ ]
+    }
+},
+psi: {
+    active: {
+        SP01: [ ],
+        SP02: [
+            "mux.mux_52_1_1.outputs.TS1"
+        ]
+    },
+inactive: {
+        SP01: [
+            "mux.mux_52_1_1.outputs.TS1"
+        ],
+        SP02: [ ]
+    }
+},
+statmux: {
+    active: {
+        SP01: [ ],
+        SP02: [
+            "MK01"
+        ]
+    },
+    inactive: {
+        SP01: [
+            "MK01"
+        ],
+        SP02: [ ]
+    }
+},
+simulcrypt: {
+    active: {
+        SP01: [ ],
+        SP02: [
+            "mux_52_1_1"
+        ]
+    },
+inactive: {
+        SP01: [
+            "mux_52_1_1"
+        ],
+        SP02: [ ]
+    }
+}
+}
+</file>
+As we can see from above, all the mux components are now being handled by Mux2 (SPO2).
+\\
+\\
+I have seen examples where some elements are being handled by one mux, and the remainder by the other mux. While it seems slightly odd that this happens, it is perfectly normal operation.
+\\
+\\