User guide

Provisioning Strategy Configuring Components for DHCP Discovery
AlliedView NMS Administration Guide (Provisioning the iMG/RG)
7-16
7.2.5.4 DHCP Relay Configured on the iMAPs (VLAN Configuration)
The DHCP Relay configuration in the iMAP associated with the RG must be data filled so that DHCP instances match the cor-
rect IP address for the tftp server and are associated with the correct VLAN.
The iMAP should be provisioned with at least two DHCP relay instances where data service VLANs (like RGBootstrap,
RGVoice, Video, Internet VLANs) are in one relay instance (e.g. MAIN) and the management VLAN (e.g. RGMgmt) is in the
second instance (called for example MGMT). Each of these instances should be configured to relay to the specific service pro-
vider’s operational DHCP server(s) supporting option 82. The second DHCP relay instance (MGMT) will be configured to
copy to the AlliedView NMS tftp server as well as to the service providers operational DHCP server(s) supporting option 82.
Following is the example for MAIN.
DHCP Instance Name Mode Remote ID Servers
------------------------------ ----------- -----------------------
MAIN RELAY DVLKND-AI01-MN1X71 10.10.10.1 *(dhcpsvr1)
This MAIN relay instance provides relay service for the example VLANs:
• RGBootstrap - 201
• RGVoice - 601
• Internet - 401 (non-UFO)
• InternetUFO - 451 - In most cases the service VLANs should be UFO.
• Video - 501
Following is the example for MGMT.
DHCP Instance Name Mode Remote ID Servers
------------------------------ ----------- -----------------------
MGMT RELAY DVLKND-AI01-MN1X71 10.10.10.2 *(dhcpsvr2)
10.10.11.1 * (NMS)
This MGMT relay instance provides relay service for the example VLAN:
• RGMgmt - 301 - Note that the RGMgmt VLAN must have its own instance.
Note: TLS services should not have DHCP relay enabled for the customer’s VPN TLS VLAN. Also, the QoS
policy should use classifiers/filters to allow and remark packets appropriately.
Note: RGMgmt does not support NAT, FW, and VPN between the AlliedView NMS and iMG/RG.
If desired, there could be multiple instances for the service VLANs, usually when each server (set) is for a separate service (and
its associated VLANs, such as 501 for Video).
The iMAP should be provisioned with a unique DHCP “Remote ID” so that the DHCP server can clearly identify where DHCP
messages are coming from. Refer to 7.2.6 for an overview of naming conventions that should be followed so that administra-
tors can easily label and configure the iMG/RG configuration.
Caution: Ensure that DHCP is enabled on the iMAP network (upstream) interfaces, as well as the interfaces
to the iMG/RG. Otherwise, DHCP will not work.
Note: For each Access Island, a unique RGMgmt VLAN and subnet must be provided. All DHCP-related
configurations for each Access Island are placed in separate configuration files. SInce each file must
declare shared networks, all iMAPs (relay agents) that are in the same Access Island must be declared in
the same configuration file. (Includes are supported by dhdpd configuration.) Refer to the Appendix for an
example.
7.2.5.5 DHCP Relay Configured on the AlliedWare Plus Devices (VLAN Configuration
The DHCP Relay configuration in the AW+ devices associated with the RG must be data filled so that the DHCP/VLAN con-
figuration matches the correct IP address for the tftp server and is associated with the correct VLAN.