User guide

Configuring Components for DHCP Discovery Provisioning Strategy
7-15
AlliedView NMS Administration Guide (Provisioning the iMG/RG)
and (substring (option agent.circuit-id,2,2)="\x00\xC8")
and (option vendor-class-identifier="RG613TX"));
option tftp-server-name "172.16.18.99"; #<--IP address of TFTP Server (NMS)
option vendor-class-identifier "RG613TX";
}
Note 1: The VLAN VID is in decimal and the value in the DHCP server in this example mst be in HEX, i.e.:
• 200 = C8 for TEST, so string is "\x00\xC8"
• 201 = C9 for AI01, so string is "\x00\xC9"
• 300 = 12C for TEST, so string is"\x01\x2C"
• 301 = 12D for AI01, so string is"\x01\x2D"
• 400 = 190 for TEST, so string is"\x01\x90"
• 401 = 191 for AI01, so string is "\x01\x91"
• 500 = 1F4 for TEST, so string is"\x01\xF4"
• 501 = 1F5 for AI01, so string is"\x01\xF5"
• 600 = 258 for TEST, so string is "\x02\x58"
• 601 = 259 for AI01, so string is "\x02\x59"
You need a class defined for all the iMG/RG types expected/planned to be used in each Access Island in the network. Fol-
lowing are some examples. (For a complete list refer to the iMG/RG Software Reference Manual, Preface.)
• RG613TX
• RG613SH
• RG613LH
• RG613BD
• iMG646BD
• iMG606BD
• iMG646BD-ON
• iMG646PX-ON
• RG656BD
• RG624A
• RG634A
• RG624B
• RG634B
The above example shows that when the message comes in over VLAN 200 (usually the bootstrap VLAN for the RG for this
Access Island), there is a pointer to the tftp IP address and a bootstrap filename. If the message comes in over VLAN 300
(RGMgmt), there is no pointer to the tftp IP address with no bootstrap file name.