Second Management Port for SWe Deployed on KVM Hypervisor

In this section:

Overview

Note:

This feature is not supported in distributed SBC deployments.

For SBC SWe deployments that require two independent management ports, you can add a second management port 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 KVM Hypervisor environment, you must add an additional port and then configure it as the second management port.

For additional information, refer to Creating a New SBC SWe Instance on KVM Hypervisor.

Adding a Port to a KVM Instance

Use the following procedure to add a port to an existing SWe deployment in a KVM Hypervisor environment.

Log on to the host system as the root user through SSH using a telnet client such as PuTTY.

Create a bridge for the second management network (mgt1):

Use the following command to change to the network-scripts directory:
```
# cd /etc/sysconfig/network-scripts
```
Use the vi editor to create an open a bridge file named ifcfg-MGT1:
```
vi ifcfg-MGT1
```
Enter the following information in the bridge file you just created (GATEWAY varies based on your configuration):
```
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes
DEVICE=MGT1
NETMASK=255.255.255.0
GATEWAY=xx.xx.xx.xx
```
Save the file.
Use the vi editor to update the appropriate adapter file for the interface so it includes the name of the new bridge. In this example the file name would be ifcfg-em4.
```
TYPE=Ethernet
BOOTPROTO=none
ONBOOT=yes
DEVICE=em4
BRIDGE=MGT1
```
Run the following command to apply your changes:
```
service network restart
```

Run the brctl show command to check that the mgt1 interface is included in the output. An example appears below.

# brctl show
 
  bridge name     bridge id               STP enabled     interfaces
  HA0             8000.e4434b5be61d         no              em2
                                        vnet1
                                        vnet6
  HA1             8000.e4434b5be61e         no              em3
                                        vnet3
  MGT0            8000.e4434b5be61c         no              em1                                                       
                                        vnet0                                                       
                                        vnet2
                                        vnet5
  MGT1            8000.e4434b5be61f         no              em4                                                      
                                        vnet4                                                       
                                        vnet7
  virbr0          8000.525400331f59         yes             virbr0-nic

Open the Virtual Machine Manager GUI by issuing the following commands, specifying your own system IP address for <System_IP>:
```
# export DISPLAY=<System_IP>:0.0
# virt-manager
```
The Virtual machine Manager opens showing a list of VMs.
Click to highlight the VM instance to which you are adding the second management port.
Virtual Machine manager VM List
Turn of the highlighted instance by right-clicking to open a pop-up menu and selecting Shut Down > Force Off.
Force Off Option
Open the individual instance by right-clicking to open a pop-up menu and selecting Open.
Click Show virtual Hardware details.
Hardware Details
On the lower-left, click Add Hardware. The Add New Virtual Hardware pop-up window opens.
In the list on the left, select Network as the hardware type. to open the Network options.
Add New Virtual Hardware - Network Options
Select the bridge you previously created as the Network source.
Select virtio as the Device model.
Click Finish.
Click to highlight the VM instance and right-click to open a pop-up menu. Click Run to restart the instance.

Configuring the Second Management Port

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

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.

Example

% 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

Space shortcuts

Page tree

Overview

Adding a Port to a KVM Instance

Configuring the Second Management Port