You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

In this section:

Related articles:

Overview

Note:

This feature primarily targets SBCaaS deployments and is only supported for integrated SBC (I-SBC) systems deployed in an OpenStack cloud environment using Heat Templates. This feature is not supported in distributed SBC deployments.


For SBC SWe deployments in an OpenStack cloud environment that require two independent management ports, SBC SWe can be instantiated with a second management port. When two management ports are configured, each of the management ports supports equivalent capabilities and either port can be used for the management functions that are supported on typical deployments which have a single management port.

Similarly to single management port deployments, the life cycle agent performs the IP address and route configuration for the second management port. A logical management IP address can be configured for the second management port. All default system ACLs and aggregate policers that apply to the management interface also apply to the second management port. User-defined ACLs can be configured on either management port. The second management port supports link detection configuration just like the first. Alarms and traps that apply to the management port are supported by both management ports if a second management port is implemented.

To deploy two management ports on an SBC SWe in an OpenStack cloud environment, you must create an additional network for the second management port prior to instantiating your system. Refer to Creating Tenant Networks. Then, when you launch the SBC SWe instance, ensure to attach either 5 ports (deployments without port redundancy) or 7 ports (deployments implementing packet port redundancy). The SBC treats the last port (5 or 7) in the Heat Template as a second management port and renames it to "mgt1." Refer to the example Heat Templates that

Unable to show "metadata-from": No such page "_space_variables"
provides for information on what your Heat Template must contain to implement a second management port.


Deployment ModelPorts
5 ports
  1. mgmt 0
  2. mgmt 1
  3. HA
  4. pkt0
  5. pkt1
7 ports
  1. mgmt 0
  2. mgmt 1
  3. HA
  4. pkt0 primary
  5. pkt0 secondary
  6. pkt1 primary
  7. pkt1 secondary

Administration and Monitoring

If you are deploying in 1:1 HA mode (ha_mode is 1to1), the name mgmtIntf2 is assigned to the mgt1 port management interface on the active instance and mgmtIntf4 on the standby instance. The port index assigned to the mgt1 management interface is 3. 

The following CLI output is an example of the values assigned to an SBC SWe OpenStack cloud system with two management ports:

Example
admin@vsbc1 > show table system mgmtIpInterfaceGroup   (partial output shown)


                                   IP
                      CE     PORT  ADDRESS PREFIX                                                                                                                                                                                    
NAME       NAME       NAME   NAME  V4       V4    
--------------------------------------------------------------
mgmtGroup  mgmtIntf1  vsbc1  mgt0  -        -
           mgmtIntf2  vsbc1  mgt1  -        -              
           mgmtIntf3  vsbc2  mgt0  -        -
           mgmtIntf4  vsbc2  mgt1  -        -
 
 
admin@vsbc1 > show table system ethernetPort mgmtAdmin
 CE     PORT  PORT
 NAME   NAME  INDEX
----------------------
vsbc1   mgt0  0
vsbc1   mgt1  3
vsbc2   mgt0  0	
vsbc2   mgt1  3
  • No labels