Server |
Eth0 / NIC1 |
Eth1 / NIC2 |
Eth2 / NIC3 |
Avaya Solutions Platform 120 Appliance: Dell PowerEdge R640 |
Management Network/Public bridge0 (eno1) |
Services eno2 |
Out of band management bridgeOOB (eno3) |
Avaya Solutions Platform 120 Appliance: Dell PowerEdge R660xs |
Management Network/Public bridge0 (eno8303) |
Services eno8403 |
Out of band Management bridgeOOB (eno12399) |
Avaya Solutions Platform S8300 |
Management Network/Public bridge0 |
Services enps10 |
Out of band management bridgeOOB (enp3s0) |
Note:
The above table reflects a customer who has their management and security module (public) on different IP ranges. If the management and public interface are on the same IP range, use the default KVM on RHEL NIC1 bridge0 setup. If you have multiple IP ranges, you must associate the NICs with different port groups. The Avaya PLDS posted ASP 130/S8300 Release 6.0 (KVM on RHEL 8.10) qcow2 file default with NIC1 for both management and public and NIC2 for the services port. Configure NIC3 if you are using OoBM.
NIC1 Session Manager Management (public). Session Manager uses this port for HTTP/SIP (Security Module).
Eth1 / NIC1 Session Manager services port.
Eth2 / NIC2 Out of band management. Session Manager uses this port for management traffic (SSH, SNMP, System Manager interface, and others.) This is a change from previous releases where Session Manager used eth0 for management traffic.
Important:
Do not mix SIP TLS traffic with the administration traffic on the Eth2 port.
