Questions regarding Ethernet Ports Resolved

7. Troubleshooting Troubleshooting
1

Hi,

After configuring, it appears that the ethernet ports on sbc1 showed as down because sbc2 was active. Once I re-booted sbc2 which forced the switch to sbc1 and the ethernet ports on both sbc1 & sbc2 showed as green/connected. I have some questions regarding the operation of sbc1 & sbc2.

  1. If sbc2 is active, will be ethernet ports for sbc1 always show as down or not connected?

  2. What would cause the switch from sbc1 to sbc2?

  3. Since, in this case, it does not appear that anything was wrong with sbc1, why did sbc2 stay active & why didn’t sbc1 become active?

  4. Other than re-booting sbc2, is there any other way to switch back to sbc1?

2
  1. If sbc2 is active, will be ethernet ports for sbc1 always show as down or not connected?

when the sbc2 is active, the IPs are activated on the sbc2, so the status on the sbc1 is not important, though I agree it should still show UP to avoid the confusion

  1. What would cause the switch from sbc1 to sbc2?

the switchover is automated with some criteria, e.g. if tboamapp lost communication active gateway on sbc1 for more than 4s, it will then
switch to the gateway on sbc2, and make it become the active one, same for other apps. And if the tbsip switches, the IP interfaces will also switch.

  1. Since, in this case, it does not appear that anything was wrong with sbc1, why did sbc2 stay active & why didn’t sbc1 become active?

as explained above, the switchover mechanism is automatic by the system, and it doesn’t require human intervention, and no impact on the active calls, we will need to check in the logs to know what exactly caused the switchover, and it doesn’t necessary means something really went wrong.

  1. Other than re-booting sbc2, is there any other way to switch back to sbc1?

Yes, there are multiple easier approaches:

  1. Stop toolpack on the sbc2:
    Ssh to the sbc2 host and to the below shell command to stop toolpack: tbtoolpack stop
    wait until all switch back to sbc1, then start toolpack: tbtoolpack start

  2. Via web portal:
    In Hosts → Applications → Status: set the active apps on sbc2 to “don’t run” and Apply
    Wait until it switches back to sbc1 and Set it back to “Run”