DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
In this section:
Logical Management IP addresses (Elastic IP/Public IP and the secondary IP) are associated to the instance during the instance creation using the HA template. Yoiu can view the Logical Management IP address both from the dashboard and the meta variable table.
To view the logical management IP addresses, perform the following steps:
Click Services drop-down list.
The Services list displays.
Select EC2 from the Compute services.
Select EC2 from the Services
Select the Running Instances link from the Resources option.
Select Running Instances from Resources Option
Right-click on the instance, select the Networking option.
Click Manage IP Addresses option from the available list.
(In the below example, the logical managment IP (52.20.101.52) is attached to the second private IP)
Manage IP Addresses
To view the IP address of the currently active instance, check the IPv4 Public IP address from the description of the active instance.
IPv4 Public IP
Log on to CLI of the currently active instance.
To view the metavariable
table, execute the following command:
> show table system metaVariable CE NAME NAME VALUE --------------------------------------------------------------- vsbc1-172.31.11.84 IF0.GWV4 172.31.10.1 vsbc1-172.31.11.84 IF0.IPV4 172.31.10.199 vsbc1-172.31.11.84 IF0.Port Mgt0 vsbc1-172.31.11.84 IF0.RNat True vsbc1-172.31.11.84 IF1.GWV4 172.31.11.1 vsbc1-172.31.11.84 IF1.IPV4 172.31.11.84 vsbc1-172.31.11.84 IF1.Port Ha0 vsbc1-172.31.11.84 IF1.RNat True vsbc1-172.31.11.84 IF2.GWV4 172.31.12.1 vsbc1-172.31.11.84 IF2.IPV4 172.31.12.52 vsbc1-172.31.11.84 IF2.Port Pkt0 vsbc1-172.31.11.84 IF2.RNat False vsbc1-172.31.11.84 IF3.GWV4 172.31.13.1 vsbc1-172.31.11.84 IF3.IPV4 172.31.13.124 vsbc1-172.31.11.84 IF3.Port Pkt1 vsbc1-172.31.11.84 IF3.RNat False vsbc1-172.31.11.84 IF0.FIPV4 34.200.21.214 vsbc1-172.31.11.84 IF0.PrefixV4 24 vsbc1-172.31.11.84 IF1.PrefixV4 24 vsbc1-172.31.11.84 IF2.PrefixV4 24 vsbc1-172.31.11.84 IF3.PrefixV4 24 vsbc1-172.31.11.84 LOGICAL_MGMT_IP.IP 172.31.10.64 vsbc1-172.31.11.84 secondaryIPList.Mgt0 ['172.31.10.64'] vsbc1-172.31.11.84 secondaryIPList.Pkt0 ['172.31.12.52'] vsbc1-172.31.11.84 secondaryIPList.Pkt1 ['172.31.13.124'] vsbc1-172.31.11.84 LOGICAL_MGMT_IP.FIPV4 52.20.101.52 vsbc1-172.31.11.84 LOGICAL_MGMT_IP.IFName IF0 vsbc2-172.31.11.25 IF0.GWV4 172.31.10.1 vsbc2-172.31.11.25 IF0.IPV4 172.31.10.246 vsbc2-172.31.11.25 IF0.Port Mgt0 vsbc2-172.31.11.25 IF0.RNat True vsbc2-172.31.11.25 IF1.GWV4 172.31.11.1 vsbc2-172.31.11.25 IF1.IPV4 172.31.11.25 vsbc2-172.31.11.25 IF1.Port Ha0 vsbc2-172.31.11.25 IF1.RNat True vsbc2-172.31.11.25 IF2.GWV4 172.31.12.1 vsbc2-172.31.11.25 IF2.IPV4 172.31.12.52 vsbc2-172.31.11.25 IF2.Port Pkt0 vsbc2-172.31.11.25 IF2.RNat False vsbc2-172.31.11.25 IF3.GWV4 172.31.13.1 vsbc2-172.31.11.25 IF3.IPV4 172.31.13.124 vsbc2-172.31.11.25 IF3.Port Pkt1 vsbc2-172.31.11.25 IF3.RNat False vsbc2-172.31.11.25 IF0.FIPV4 52.72.12.230 vsbc2-172.31.11.25 IF0.PrefixV4 24 vsbc2-172.31.11.25 IF1.PrefixV4 24 vsbc2-172.31.11.25 IF2.PrefixV4 24 vsbc2-172.31.11.25 IF3.PrefixV4 24 vsbc2-172.31.11.25 LOGICAL_MGMT_IP.IP 172.31.10.64 vsbc2-172.31.11.25 secondaryIPList.Mgt0 ['172.31.10.64'] vsbc2-172.31.11.25 secondaryIPList.Pkt0 ['172.31.12.52'] vsbc2-172.31.11.25 secondaryIPList.Pkt1 ['172.31.13.124'] vsbc2-172.31.11.25 LOGICAL_MGMT_IP.FIPV4 52.20.101.52 vsbc2-172.31.11.25 LOGICAL_MGMT_IP.IFName IF0 [ok]
Once the active and standby instances are running and come up with their assigned roles, the Logical Management IP must be activated.
Log on to CLI of the currently active instance.
To activate the Logical Management IP Address, execute the following commands:
Ensure to execute the command in the following order. It is observed that, if the Logical Management IP is configured and enabled together, the Logical Management IP does not work.
% set system logicalMgmtIpInterface mgt mgmtIpInterfaceGroupName mgmtGroup ipVar LOGICAL_MGMT_IP.IP [ok] % commit % set system logicalMgmtIpInterface mgt state enabled [ok] % commit Commit complete
To verify if the the Logical Management IP address is activated, execute the following command:
> show table system logicalMgmtIpInterfaceStatus LOCAL NAME OPER STATUS IP TYPE FIXED IP ------------------------------------------------- mgt active learned 172.31.10.64 [ok]
If the Logical Management IP address is activated, the ping/ssh can be performed by using the Logical Management IP address.
If the Logical Management IP address is not activated, the status is set to disabled instead of active.
Restart the SBC application if the Logical Management IP address is not activated.