User guide

Provisioning the iMG/RG Provisioning Strategy
659
AlliedView NMS Administration Guide
TABLE 7-3 RG/iMG Boot Load Configurator Tool - Release 4 Tab
Attribute Value
Mgmt VLAN ID The VLAN identifier that will be placed into the im.conf file. This is the final RGMgmt
vlan which the RG will use while it is in service for a particular customer in a
particular access island.
(If the same customer moves and takes the RG it will not work if the new residence is
not serviced from the same Access Island. The RG must go through bootstrap again
and then it will work again.)
Note that this can be the same for all Access Islands, as long as the SNMP Community
values are the same (see below).
Read Community the read SNMP community (default public) that will go into snmpinit.
Note: snmp comm strings for all iMG/RG should be the same for the entire network.
R/W Community the read/write SNMP community (default friend) that will go into snmpinit.
Note: snmp comm strings for all iMG/RG should be the same for the entire network.
Trap Host The SNMP trap host (default none) that will go into snmpd.cnf. This will allow
configuring multiple trap destination IP addresses separated by a comma. Multiple IP
addresses should only be used when creating boot configuration for devices that
support it.
Inform Interval TR69 inform interval - the interval at which the iMG checks for updates, defaulted to
5 minutes
Release Load File This is the zip file that will be unpacked from the NMS’s built-in RG/iMG software
repository. The files are named after their releases. The Browse button pops up a file
chooser from the software repository. (The path of the software repository will be
displayed in the beginning of the Messages window)
New Load Name This is the name of the directory path that will be added to the TFTP server directory
to contain the new load. The TFTP root path will be displayed in the beginning of the
Messages window. Names should not begin with a slash since these directories will be
placed under the TFTP root. Subdirectories relative to the TFTP root can be specified
by including slashes in the name. (Forward slashes work on both Windows and
Solaris, but backslashes only work on Windows) If the directory already exists, its
contents will be overwritten (after user confirmation), which can be used for
correcting mistakes. (In the example, the path could be iMG1505/4_1.) The load name
must match what is in dhcpd.conf (refer to 7.2.5.3)
ACS Authentication Username and Password iMGs will use to connect to the Auto Configuration Server
(ACS).
CPE Authentication Username and Password ACS will use to connect to iMGs.
ACS IP Address Normally this is the NMS server IP. If the server has more than one IP, this will be a
drop down list.
Configuration Type This specifies which type of bootstrap file to use in the new load. This is a pull-down
for devices for the user to select when creating the correct configuration for that
release. This is because some of the releases do not use a configuration compatible to
other releases of same type.
Messages Messages show the progress and status of each load creation. The initial messages
include the path to the software repository (where the zip files reside), the path to
the TFTP server root (where the loads will be placed), and a summary of any existing
loads already residing in the TFTP directory tree. All messages should be reviewed
carefully per the cautionary note stated above. Errors will be reported here, as well.
Refresh Only valid for the Summary tab.