User guide
Provisioning the iMG/RG Provisioning Strategy
662
AlliedView NMS Administration Guide
------------------------------ ----------- -----------------------
MAIN RELAY SPSI-AI00-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 SPSI-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.
Following is an example with one Relay instance per service.
DHCP Instance Information
-------------------------
DHCP Instance Mode CID Format Shelf ID Remote ID VLAN
Name Vid
list
--------------- ----- ------------ ----------------- ----------------- -------
MAIN RELAY AUTO 00:0C:25:1F:80:10 00:0C:25:1F:80:10 None
RGBoot RELAY AUTO 00:0C:25:1F:80:10 SPSI-AI00-MAP5x4 200
RGMgmt RELAY AUTO 00:0C:25:1F:80:10 SPSI-AI00-MAP5x4 300
RGVoice RELAY AUTO 00:0C:25:1F:80:10 SPSI-AI00-MAP5x4 400
Internet RELAY AUTO 00:0C:25:1F:80:10 SPSI-AI00-MAP5x4 600
Video RELAY AUTO 00:0C:25:1F:80:10 SPSI-AI00-MAP5x4 500
-------------------------------------------------------------------------------
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
administrators can easily label and configure the iMG/RG configuration.
Caution: Ensure that DHCP Relay 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
configuration matches the correct IP address for the tftp server and is associated with the correct VLAN.
Here is an example of the config required for dhcp relay on aw+ for the service, rgboot, and rgmgmt vlans:
interface vlan201 //rgboot
ip address 10.52.110.177/28