VUE EM allows you to configure VIPs and routes for all interfaces on a VUE application server. This is done instead of statically configuring both IPs and routes for a server. Using VIPs makes it easier to modify, add, or delete IPs and routes. For any given interface, more than one VIP and/or route may be defined. All IPs used for data ingress/egress in servers that are in a redundancy cluster must be VIPs. Likewise, IPs used on the management to communicate with legacy video managers/devices (for example, SDV ERM, DAC, NC1500, etc.) may need to be VIPs.
The only IP address that must be statically configured is the management IP of each VUE application server.
VIP configuration
You can add VIPs and routes in Classless Inter-Domain Routing (CIDR) notation. To add a VIP, enter the following information:
- IP/subnet bitmask (Example: 10.172.26.32/24)
- Role (HB or other)
The role defines if the VIP can be used as a high availability heartbeat (HB) or can be used for reception or transmission of data/video. If the role is defined as HB, the VIP can be assigned to a redundancy cluster, but cannot be used for data reception/transmission. If the VIP role is defined as other, that IP address cannot be used for high availability HBs.
Dynamic routing support
You can configure routes for any interface through the Element Manager. Routes are needed to receive multicast from specific source inputs. Routes should not be statically configured. A default gateway for the management interface should be the only route statically configured.
Route configuration
You can add routes in CIDR notation. To add a route, enter the following information:
- Route/subnet bitmask (Example: 10.101.0.0/16)
- Gateway IP (Example: 10.172.26.1)