User guide

Provisioning the iMG/RG Provisioning Strategy
656
AlliedView NMS Administration Guide
TABLE 7-2 RG/iMG Boot Load Configurator Tool - Release 2 and Release 3 Tabs
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.
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)
Recovery Load File Another zip file, like the release load file, but contains the recovery software, which
will also be unpacked from the software repository.
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, for ADSL iMG/RGs the path could be ADSL/
AI01.) The load name must match what is in dhcpd.conf (refer to 7.2.5.3).
Configuration Type This specifies which type of im.conf file to use in the new load. There 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.
TFTP Discovery When selected, after the RG reboots it sends a DHCP discovery message to the
DHCP server (over the RGMgmt VLAN). The iMG/RG then sends a tftp request to
the NMS, containing its MAC and IP address. The NMS uses its tftp listener to
discover the iMG/RG with this IP and MAC Address. With the IP and MAC Address,
the AlliedView NMS can proceed with discovery and provisioning.
Load Type This specifies whether a complete load is to be created or if only SNMP configuration
files will be created. SNMP-only can be used for the special case of a one-time SNMP
reconfiguration that can be accomplished at the next TFTP restart, which will
download only SNMP files and leave the existing release on the device otherwise
unchanged. Be sure to select the correct Recovery Load File, which is the source of
the basic SNMP configuration to be modified, or else SNMP reconfiguration will fail
after the device restarts.