Configuring a second network bond using Cockpit

Last Updated : Jan 20, 2026 |

About this task

The updated network script configNetwork available with ASP R6.0.0.4.0 and later can now configure a second bond (bond1) on a second bridge (bridge1). For more information, see ASP 130 R6.0.0.4 and Later- VLAN & VLAN TRUNKING CONFIGURATION GUIDE-Rev1.

Putting VoIP and Data on separate networks is a best recommended, industry standard. Isolating VoIP traffic from Data/Management traffic helps to enhance network security and enables customers to implement QoS adequately. It also helps by simplifying network traffic management and troubleshooting as each network can be monitored independently. By independently monitoring each network, a network administrator can quickly identify and address issues specific to either VoIP or data/management services, improving response times and minimizing downtime.

Note:

Call signaling in VoIP communications, whether directed to Communication Manager (CM), Session Manager (SM), or media servers, is still classified as VoIP traffic, even if media (RTP packets) is not transmitted as part of the call signaling process.

Before you begin

  • An existing bond for the management and application traffic is expected to be already configured. Reference to Adding a bond using the network configuration script if required prior to proceeding.

  • Two available network interfaces in the host.

  • Connect the designated server ports to the customer data switch, referencing the provided cable diagram to ensure proper wiring configuration.

Procedure

  1. Using a Web browser tab, navigate to the KVM on RHEL server IP Address e.g.: https://192.11.13.6:9090
  2. Authenticate using the existing custadm credentials.
  3. If not already in “Administrative access”, click on the upper-right corner “Limited access” and enter the password for the custadm account.
  4. From the left pane menu, select Networking > Add Bond.
  5. Select the following:

    • Name: bond1.

    • Interfaces: check boxes for eno12399 & eno12419.

      Note:

      This configuration does not support Out-of-Band Management (OOBM) and Communication Manager (CM) Duplex mode simultaneously, due to the lack of sufficient, supported network interface cards (NICs) in this release.

      Note:

      If OOBM is already configured DO NOT use eno12399. If this KVM host is not part of a CM Duplex solution as an alternative eno12429 can be used.

    • Mode (leave default selection): Active backup.

    • MAC, Primary, Link monitoring, Monitoring interval, link up delay, link down delay: Leave default values.

  6. Click Add button to create bond.
  7. From the left pane menu, click on Networking > Add bridge.
  8. Select the following:

    • Name: bridge1

    • Ports: previously created bond1.

  9. Click Add button to create bridge.
  10. Under Interfaces, select the newly created bridge1.
  11. Click edit for IPv4 and validate the following:

    • Address is set to disabled.

    • There are no entries grayed out for DNS, DNS search domains and routes.

  12. Click Save.
  13. Repeat steps for IPv6.
  14. Migrate Avaya Aura® applications virtual network interfaces to the newly created bridge accordingly.
    Note:

    To make network changes to virtual machines, these must be in a power off state.

    Note:

    When segregating networks a new network segment for VoIP will be provisioned. Work with the customer network administrators to ensure Avaya Aura® applications are re-IP accordingly.