Versions Compared

Old Version 4

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 5

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
JIRAIDAUTHSBX-93058
REV5UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85c46b657015d4f66d18b001f, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5007d7, userName='null'}



Panel

In this section:

Table of Contents
maxLevel4



Info
iconfalse

Related articles:


Overview

Info
titleNote:

This feature is not supported in distributed SBC deployments.

For SBC SWe deployments that require two independent management ports, a second management port can be added in a VMware environment. 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 with a single management port.

Similar 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 first 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 a second management port on an SBC SWe in a VMware environment, you must add an additional port and then configure it as the second management port. Use one of the following procedures to add the port, depending on your VMware environment.

Adding a Port Using VMware vSphere Client 

If you manage your VMware network using the vSphere Client, use the following procedure to add a port to an existing deployment.

  1. Open the vSphere Client.
  2. Click to highlight the appropriate host in the left pane and then click the Configuration tab.

  3. In the Hardware section, click Networking. The current set of virtual switches and port groups appear.
    vSphere Client Configuration Tab


  4. On the upper-right, click the Add Networking link. The Add Network Wizard pop-up window opens showing Connection Type options.

  5. Click Virtual Machine as the connection type and then click Next. The Network Access options appear. 
    Add Network Wizard - Network Access Options


  6. Select the vSwitch connected to the second management network (mgt1) and click Next. The Connection Settings options appear.
  7. Enter a Network Label for the second management network and click Next.
  8. Review the configuration summary and click Finish.
  9. In the left pane, click to highlight the VM to which you are adding the second management port. 
  10. On the Getting Started tab, click the Edit virtual machine settings link. The Virtual Machine Properties pop-up window opens.

  11. On the Hardware tab, click Add to add a network adapter for the added vSwitch. The Add Hardware pop-up window opens showing the Device Type options.
    Add Hardware - Ethernet Adapter



  12. Click on Ethernet Adapter in the list of devices and then click Next. The Network Type options appear.
    Add hardware - Network Type Options


  13. In the Type list, select VMXNET3. Leave the other parameters with their default values and click Next. The Ready to Complete summary appears.
  14. Click Finish.

Adding a Port Using VMware ESXi Web Client

If you manage your VMware network using the VMware ESXi Web Client, use the following procedure to add a port to an existing deployment.
  1. Log into the VMware host.

  2. In the left panel, click Networking and then click on the Virtual switches tab.
    ESXi Networking


  3. Click the Add standard switch link to add a switch that is connected to the second management network (mgt1).  The Add standard virtual switch pop-up window opens.
    Add Standard Virtual Switch


  4. Enter a vSwitch Name, select the appropriate physical NIC for the network in the Uplink 1 list, and click Add.

  5. Click on the Port groups tab and click the Add port group link to add a port group for the new vSwitch. The Add port group pop-up window opens.
    Add Port Group



  6. In Name, enter the name for the port group for the second management network.
  7. In the Virtual switch list, select the virtual switch you just created and click Add.
  8. In the left pane, click to highlight the VM instance. Information and status of the instance appear in the right pane.
  9. Click the Shut down icon to shut down the instance.

  10. Click the Edit icon to edit the instance. The Edit setting pop-up window opens.
    Edit VM Settings



  11. Click New Network Adapter and then in the list of port groups provided, select the new port group you created.
  12. Click Save.
  13. Click the Restart icon to power on the instance.

Configuring the Second Management Port

Use the following command syntax to configure the parameters for a second management port, mgt1: 


Code Block
set system mgmtIpInterfaceGroup <group name> mgmtIpInterface <interface name> ceName <node name> ipAddressV4 <IPv4 address> prefixV4 <prefix> portName mgt1 state <disabled | enabled>


In the following example, the first command configures a second management port on the node named VM1. The second command enables the port, and the third command adds a management static route.


Code Block
titleExample
% set system mgmtIpInterfaceGroup mgmtGroup mgmtIpInterface mgmtIntf2 ceName VM1 ipAddressV4 10.12.14.16 prefixV4 24 portName mgt1
% commit
% set system mgmtIpInterfaceGroup mgmtGroup mgmtIpInterface mgmtIntf2 ceName VM1 ipAddressV4 10.12.14.16 prefixV4 24 portName mgt1 state enabled
% commit
% set system mgmtStaticRoute 0.0.0.0 0 10.12.14.1 mgmtGroup mgmtIntf2 preference 10
% commit