PMP 320 - Set CPE Access Tool for CNUT
***** How to Load the Set CPEAccess File
1. Locate the SetCPEAcess.jar file below compressed in “SetCPEAccess.zip” this attached message.
2. Verify that the software package was not corrupted using a checksum calculator
Use an after-market checksum calculator to verify that the software package was not corrupted by loading the MD5 file into the aftermarket product. An example of the MD5 file name is MD5 Checksum: ad9cdbe995c419fbaff568336b71b19a. The MD5 Checksum Calculator is freeware available on the Internet and is used to check the integrity of the software file.
The MD5 Checksum is cac89ac73bb8e218352f9f4fc52cba8b.
3. Copy the SetCPEAccess.jar file and paste the file into the tools folder where the CNUT application is installed (for example, on Windows C:‘Canopy’NetworkUpdater’Tools’ folder )
4. Launch the CNUT application.
5. Once the CNUT application has launched, go to the CNUT menu bar and select Tools > Add External Tool
NOTE : Do not click the Supports Help box or add any text in the Command Line box in the Tool Help menu.
6. In the Name field provide a descriptive name for the external tool (for this example, “Set CPE Access” is used in step 3 below).
7. In the Command Line field - add the following text to the Command line of the pop up window
java –cp C:'Canopy’NetworkUpdater’tools’SetCPEAccess.jar SetCPEAccess.Dlg SetCPEAccess
8. Check the Send Network Element Information box in the Tool Input selection area.
9. Click OK.
The SetCPEAccess add-on tool has been added to the CNUT application.
***** How to use the Set CPE Acess jar file
After the SetCPEAccess tool has been loaded the CPEs can be configured from the add-on tool. To configure the CPEs, select the CPE’s you wish to configure and then launch the SetCPEAccess tool by selecting the tool from the Tool menu on selection in the Canopy Network Updater application.
1. Launch the CNUT tool.
2. Enter the appropriate user ID and password when prompted.
3. Select the radio button for selected network elements in the Canopy Network Updater menu. The boxes are checked for the CPEs that will be updated using the Set CPE Access tool.
From the CNUT menu select Tools > <unique user tool name> For example, as in the installation procedure above the Tool Settings Name can be “Set CPE Access”.
4. The Launch External Tool pop-up menu displays, click OK.
5. The external SetCPEAccess tool launches and a pop-up menu appears.
6. To disable the DMZ settings on the selected CPE units, click the Enable/Disable DMZ and then click the Disable radio button. You could also choose one of the other options like “Web Access” in place of the “DMZ” setting used in this step.
7. Select OK
The SetCPEAccess tool processes the request and pushes the changes to the CPEs that were selected via check mark in the CNUT tool and reboots them.
8. The CPEs that were modified have all been rebooted.
Note that the DMZ settings that were changed must be re-enabled after the new software version has been pushed to the CPE units.
** Tips ********
If the tool is used to change the SNMP Community string, the SNMP Community string must be updated in the Modify Network Element Access field in the CNUT application.
- 1) Double click the CPE in the CNUT tool
If the CNUT application is upgraded at a later date, the SetCPEAccess.jar file must be reloaded back into the External Tool section of the CNUT application.
The device cannot be in a Not Responding state in CNUT. The device must be pingable, and the SNMP Community string must be enabled on the CPE in order to use the SetCPEAccess tool.
The operator can use the Set CPE Access add-on tool in future releases to manipulate various settings of the CPEs including the following:
- 1) Enable/Disable Web Access – this setting is used to control the Web Access settings of the radio wired side.
2) Enable/Disable DMZ – a security setting that adds an additional layer of security of the LAN. This setting must be disabled for the 1.1 software to be loaded to the CPE.
3) Change the Read/Write Community string – this setting can be changed to control access. The SNMP community string must be at least eight characters, preferably mixed letters, numbers and must include special characters such as: !@#$%^&.