User guide

Canopy System User Guide
pmp-0229 (Mar 2013)
234
Chapter 17: Preparing Components for
Deployment
Your test of the modules not only verified that they are functional, but also yielded data that you
have stored about them. Most efficiently preparing modules for deployment involves
• retrieving that data.
• systematically collecting the data into a single repository, while keeping a strong (quick)
association between the data and the module.
• immediately merging module access data into this previously stored data.
Correlating Component-specific Information
You can use the data that you noted or printed from the Status pages of the modules to
• store modules for future deployment.
• know, at a glance, how well-stocked you are for upcoming network expansions.
• efficiently draw modules from stock for deployment.
• plan any software updates that you
o wish to perform to acquire features.
o need to perform to have the feature set be consistent among all modules in a network
expansion.
You can make these tasks even easier by collecting this data into a sortable database.
Ensuring Continuing Access to the Modules
As you proceed through the steps under Configuring for the Destination on Page 236, you will set
values for parameters that specify the sync source, data handling characteristics, security
measures, management authorities, and other variables for the modules. While setting these, you
will also tighten access to the module, specifically in
• the Color Code parameter of Configuration page
• the Display-Only Access and Full Access password parameters of the Configuration page.
• the addressing parameters of the IP Configuration page.