check_1_1_mksp_redundancy_status
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
check_1_1_mksp_redundancy_status [2020/05/15 14:08] – [Introduction] 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> | + | <color darkorange> |
---- | ---- | ||
Line 9: | Line 9: | ||
\\ | \\ | ||
There are several operations that the SPs are handling, and either SP can be the one doing an operation, these are: | There are several operations that the SPs are handling, and either SP can be the one doing an operation, these are: | ||
- | \\ | ||
\\ | \\ | ||
StatMux | StatMux | ||
Line 15: | Line 14: | ||
Scrambling CA | Scrambling CA | ||
MUX | 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. | 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. | + | Please note - You must you the <color #ed1c24>Management VIP</ |
\\ | \\ | ||
\\ | \\ | ||
Line 25: | Line 23: | ||
\\ | \\ | ||
http:// | http:// | ||
+ | \\ | ||
+ | You will see an output in your browser similar to below (with different instance names) - <color # | ||
+ | < | ||
+ | { | ||
+ | mongo_status: | ||
+ | rabbit_status: | ||
+ | statmux: { | ||
+ | active: { | ||
+ | SP01: [ | ||
+ | " | ||
+ | ], | ||
+ | SP02: [ ] | ||
+ | }, | ||
+ | inactive: { | ||
+ | SP01: [ ], | ||
+ | SP02: [ | ||
+ | " | ||
+ | ] | ||
+ | } | ||
+ | }, | ||
+ | psi: { | ||
+ | active: { | ||
+ | SP01: [ | ||
+ | " | ||
+ | ], | ||
+ | SP02: [ ] | ||
+ | }, | ||
+ | inactive: { | ||
+ | SP01: [ ], | ||
+ | SP02: [ | ||
+ | " | ||
+ | ] | ||
+ | } | ||
+ | }, | ||
+ | mux: { | ||
+ | active: { | ||
+ | SP01: [ | ||
+ | " | ||
+ | ], | ||
+ | SP02: [ ] | ||
+ | }, | ||
+ | inactive: { | ||
+ | SP01: [ ], | ||
+ | SP02: [ | ||
+ | " | ||
+ | ] | ||
+ | } | ||
+ | }, | ||
+ | simulcrypt: { | ||
+ | active: { | ||
+ | SP01: [ | ||
+ | " | ||
+ | ], | ||
+ | SP02: [ ] | ||
+ | }, | ||
+ | inactive: { | ||
+ | SP01: [ ], | ||
+ | SP02: [ | ||
+ | " | ||
+ | ] | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | In the output above we can see that <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | Now I will do a Mux switch from nCompass ESM. | ||
+ | < | ||
+ | { | ||
+ | mongo_status: | ||
+ | rabbit_status: | ||
+ | mux: { | ||
+ | active: { | ||
+ | SP01: [ ], | ||
+ | SP02: [ | ||
+ | " | ||
+ | ] | ||
+ | }, | ||
+ | inactive: { | ||
+ | SP01: [ | ||
+ | " | ||
+ | ], | ||
+ | SP02: [ ] | ||
+ | } | ||
+ | }, | ||
+ | psi: { | ||
+ | active: { | ||
+ | SP01: [ ], | ||
+ | SP02: [ | ||
+ | " | ||
+ | ] | ||
+ | }, | ||
+ | inactive: { | ||
+ | SP01: [ | ||
+ | " | ||
+ | ], | ||
+ | SP02: [ ] | ||
+ | } | ||
+ | }, | ||
+ | statmux: { | ||
+ | active: { | ||
+ | SP01: [ ], | ||
+ | SP02: [ | ||
+ | " | ||
+ | ] | ||
+ | }, | ||
+ | inactive: { | ||
+ | SP01: [ | ||
+ | " | ||
+ | ], | ||
+ | SP02: [ ] | ||
+ | } | ||
+ | }, | ||
+ | simulcrypt: { | ||
+ | active: { | ||
+ | SP01: [ ], | ||
+ | SP02: [ | ||
+ | " | ||
+ | ] | ||
+ | }, | ||
+ | inactive: { | ||
+ | SP01: [ | ||
+ | " | ||
+ | ], | ||
+ | SP02: [ ] | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | 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. | ||
\\ | \\ | ||
\\ | \\ | ||
check_1_1_mksp_redundancy_status.1589548137.txt.gz · Last modified: 2023/03/09 22:35 (external edit)