Conversation
agrawalkaushik
requested review from
BenMatase,
haberkornsam and
mdzwil-JNPR
BenMatase
changed the title
| exit | ||
| ``` | ||
|
|
||
| ### Key Configuration Points |
There was a problem hiding this comment.
1 and 2 are specific to AWS TGW so make sense under its example. The others can be applied to both Azure and AWS so maybe have before the config examples?
…hnology/docs into kagrawal/cloud-ha-azure-vnet
…gy/docs into kagrawal/cloud-ha-azure-vnet
|
|
||
| The command `request cloud-ha become-active router <router> node <node>` will try to force the given node to become active and try to tell the other node to become inactive. If the peer node is not accessible at the time of the command, the command will not fail. | ||
|
|
||
| This command can be useful if the routes have been modified outside of the plugin and they need to be fixed. |
There was a problem hiding this comment.
@BenMatase can you clarify this section? "If the peer node is NOT accessible at the time of the command, the command will NOT fail."? That doesn't make sense. Are you saying that if the peer node is not accessible, no failure message is generated? Or that if it is not accessible, it just continues to attempt to make it active?
And the next sentence implies that the routes modified outside the plugin were modified, they are broken.
There was a problem hiding this comment.
I guess what I was trying to convey was that we will make the node that the command is targetted to active. Then we try to make the peer node inactive. If that peer operation fails (main reason would be that the HA connection is not functioning), no failure message is generated since it is a "nice to have" operation. It will only try once.
5 participants
Uh oh!
There was an error while loading. Please reload this page.