cisco connected grid device manager installation and user … · 1-3 cisco connected grid device...

Cisco Connected Grid Device Manager Installation and User Guide, Release 1.1October 2012

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-28081-01

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

No combinations are authorized or intended under this document.

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco Connected Grid Device Manager Installation and User Guide © 2012 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

OL-28081-01

C O N T E N T S

C H A P T E R 1 Introduction 1-1

Overview 1-1

Application 1-1

Tasks 1-2

Additional Information 1-4

C H A P T E R 2 Installation 2-1

Required Expertise 2-1

System Requirements 2-1

Certificate Installation 2-2

Device Manager Installation 2-6

Device Manager Removal 2-7

C H A P T E R 3 Using the Device Manager 3-1

Overview 3-1

How to Use the Device Manager 3-2

Connect to the CGR 1000 3-3

Test Connectivity 3-6

Add a Device IP Address 3-7

Ping a Device IP Address 3-7

Failed Ping 3-9

Traceroute a Device IP Address 3-10

Remove a Device IP Address 3-10

Manage Interfaces 3-11

Bring Up an Interface 3-12

Shut Down an Interface 3-13

Change Configuration 3-15

Add a Configuration File 3-16

Update Configuration File on the CGR 1000 3-16

Correct a Configuration File 3-17

Remove Configuration File 3-17

iiiCisco Connected Grid Device Manager Installation and User Guide

Contents

Update Image 3-18

Upload Image 3-19

Replace Image 3-19

Remove Image 3-20

Retrieve Report 3-21

Retrieve and Save Reports 3-22

Advanced Command 3-23

Example File Output 3-24

Disconnect from the CGR 1000 3-29

Feature History 3-29

Frequently Asked Questions 3-30

ivCisco Connected Grid Device Manager Installation and User Guide

OL-28081-01

Cisco ConnecteOL-28081-01

C H A P T E R 1
Introduction
This chapter provides an overview of the Cisco Connected Grid Device Manager (Device Manager) and includes the following sections:

• Overview, page 1-1

• Additional Information, page 1-4

OverviewThis section includes the following topics:

• Application

• Tasks

ApplicationThe Cisco Connected Grid Device Manager (Device Manager) is a Windows-based application that field technicians can use to manage the Cisco 1000 Series Connected Grid Routers (CGR 1000) remotely. Cisco CG-NMS manages multiple CGR 1000 routers whereas the Device Manager connects and manages a single CGR 1000 at a time.

Cisco CGR 1000 routers are multi-service communications platforms designed for use in field area networks. The portfolio consists of two models–Cisco CGR 1240 and Cisco CGR 1120–both ruggedized to varying degrees for outdoor and indoor deployments. Both models are modular and support a wide-range of communications interfaces such as 2G/3G, Ethernet, and WiFi.

Device Manager connects to the Cisco CGR 1000 by using a secure Ethernet or WiFi link. See Figure 1-1

1-1d Grid Device Manager Installation and User Guide

Chapter 1 Introduction Overview

Figure 1-1 Device Manager Application Within a Connected Grid Network

TasksThe Device Manager enables you to:

• Troubleshoot connectivity between a CGR 1000 and the devices connected to the router. See Test Connectivity, page 3-6

• Bring up or shut down an CGR 1000 interface.

See Manage Interfaces, page 3-11

• Check and update the current CGR 1000 configuration.

See Advanced Command, page 3-23 and Change Configuration, page 3-15

• Update the CGR 1000 image and reset the router.

See Update Image, page 3-18

• View real-time CGR 1000 configuration information for troubleshooting. See Retrieve Report, page 3-21

• Use advanced commands to troubleshoot the CGR 1000.

See Advanced Command, page 3-23

You initiate all tasks from the At a Glance page. See Figure 1-2

IPSec Tunnel

IPSec Tunnel

3031

04

CGR 1240Router

Head-endRouter

Head-endRPDON server

CG-NMS

IPv4/IPv6LAN

IPv6 link 6LoWPANs

Field Technician withDevice Manager

Field Technician withDevice Manager

Metering DataCollection System

CGR 1240RouterIPv4 link

IPv4 linkUtility

Network

1-2Cisco Connected Grid Device Manager Installation and User Guide

OL-28081-01

Chapter 1 Introduction Overview

Figure 1-2 At a Glance Page for the CGR 1120

In addition to supported tasks (right-side), the At a Glance page provides a view of the CGR 1000 router to which the Device Manager is connected (left-side).

At the bottom of the page, you can find the following information:

• Name of the router

• Version of the software

• Model number of the CGR 1000

• Serial number of the CGR 1000

• Door status of the system casing, (Open or Closed) for the router (CGR 1240 only)

• Battery status, when an optional backup battery is installed (CGR 1240 only)

• Slots within the system and modules installed in those slots (CGR 1120 only)

• Storage status including amount of storage available

• Connection method of the Device Manager to the CGR 1000 (WiFi or Ethernet)

• Certificate status

• Authorization indicates the user role of the connected user

Tip To refresh the At a Glance page, click the Refresh icon (lower right-side).


OL-28081-01

Chapter 1 Introduction Additional Information

Additional InformationYou can find configuration guides and release notes for Cisco 1000 Series Connected Grid products at:

www.cisco.com/go/cgr1000-docs


OL-28081-01



C H A P T E R 2
Installation
This chapter explains how to install the Device Manager software, and contains the following topics:

• Required Expertise, page 2-1

• System Requirements, page 2-1

• Certificate Installation, page 2-2

• Device Manager Installation, page 2-6

• Device Manager Removal, page 2-7

Required ExpertiseThis guide is intended for Field Technicians who have experience with Cisco CGR 1000s.

System RequirementsThe Device Manager has the following system requirements:

• Microsoft Windows 7 Enterprise / Professional or Windows XP (with Service Pack 3)

• 2 GHz or faster processor recommended

• 1 GB RAM minimum (for potential large log file processing)

• WiFi or Ethernet interfaces

• 4 GB disk storage space

• Windows login enabled

• Utility-signed Certificate Authority (CA) and Client Certificate for router authentication (obtained from your IT department)


Chapter 2 Installation Certificate Installation

Certificate InstallationBefore you can install the Device Manager, you must install the client identity and CA certificates in the computer.

Follow these steps to install the certificate on the computer running the Device Manager:

Step 1 Contact your IT Department for the PKCS #12 formatted certificate, which should contain the client identity and CA certificates (along with the private key and its password to import the certificates onto the laptop).

Step 2 Copy the certificate (provided by your IT Department) to your computer, for example, on the Desktop.

Step 3 Double-click the certificate to open the Installation Wizard.

Step 4 Click Next to start the installation.


OL-28081-01


Step 5 The file name of the certificate file auto-populates. Click Next.

Step 6 Enter the password, and ensure that the only selected check box is the Include all extended properties option (default setting). Click Next.


OL-28081-01


Step 7 Keep the default setting of Automatically select the certificate store based on the type of certificate, and then click Next.

Step 8 Click Finish.


OL-28081-01


Step 9 Click OK to complete installation of the certificate.

The default certificate name is ConnGridDevMgr.

Follow these steps to verify the client certificate (optional):

Step 1 (Optional) Verify the client certificate in the Internet Explorer browser:

IE browser\Tools\Internet Options\Content\Certificates\Personal

Step 2 (Optional) Verify the CA certificate in the Internet Explorer browser:

IE browser\Tools\Internet Options\Content\Certificates\Trusted Root Certification Authorities

Step 3 (Optional) Delete the C:\ProgramData\Cisco\CGDManager folder. Run the Device Manager to automatically generate this folder, and then quit the Device Manager without any actions (to clean up any previous settings).

Note The program data directory for the Device Manager is hidden, by default. To view this directory, open an Explorer window, select Folder Options from the Tools menu, and then select the View tab. Select Show hidden files and folders, and then click OK.


OL-28081-01

Chapter 2 Installation Device Manager Installation

Device Manager InstallationFollow these steps to install the Device Manager:

Step 1 Double-click CGDManager executable to start installation.

Step 2 Click Next.

Step 3 Select the check box to accept the terms of the License Agreement, and then click Next.


OL-28081-01

Chapter 2 Installation Device Manager Removal

Step 4 Click Finish to exit the Setup Wizard and launch the Device Manager.

If a valid Certificate Common Name is not found in the registry, then Device Manager will launch the Settings page instead. By default, the Certificate Common Name is ConnGridDevMgr. You only need to enter a value in the Settings page, if the Certificate Common Name of the certificate file differs from that assigned by default.

Device Manager RemovalTo remove the Device Manager application, click Start > All Programs > Cisco CGD Manager > Uninstall Cisco CGD Manager, or use Add or Remove Programs from the Control Panel.


OL-28081-01

Chapter 2 Installation Device Manager Removal


OL-28081-01


C H A P T E R 3
Using the Device Manager
The chapter explains how to use the Device Manager, and contains the following topics:

• Overview, page 3-1

• How to Use the Device Manager, page 3-2

• Connect to the CGR 1000, page 3-3

• Test Connectivity, page 3-6

• Manage Interfaces, page 3-11

• Change Configuration, page 3-15

• Update Image, page 3-18

• Retrieve Report, page 3-21

• Advanced Command, page 3-23

• Disconnect from the CGR 1000, page 3-29

• Frequently Asked Questions, page 3-30

OverviewThe At a Glance page displays after securely connecting to the CGR 1000. From this page, you can perform the following tasks:

• Test Connectivity: Verify access to a device (IP address) to the CGR 1000, by using ping to check link connectivity and quality; and, initiate a traceroute for an inaccessible IP address. See Test Connectivity, page 3-6

• Manage Interfaces: Bring up or shut down an CGR 1000 interface. See Manage Interfaces, page 3-11

• Change Configuration: Update the CGR 1000 configuration with a provided configuration file, and then reboot the router with the new configuration. See Change Configuration, page 3-15

• Update Image: Upload a copy of a software image onto the CGR 1000 for immediate installation or for a deferred update of the image. See Update Image, page 3-18

• Retrieve Report: Download and view the CGR 1000 system logs. See Retrieve Report, page 3-21


Chapter 3 Using the Device Manager How to Use the Device Manager

• Advanced Command: Provides a console-like interface to troubleshoot the CGR 1000 by using CLI commands. Supported queries include verifying the system time, viewing the current router configuration, saving the current configuration, viewing the current file directory, rebooting the router, or saving the window output to a file. See Advanced Command, page 3-23

Figure 3-1 At a Glance Page for the CGR 1240

The CGR 1000 image that displays with the At a Glance page, provides a view of the CGR 1000 router to which the Device Manager is connected (left-side). The CGR 1000 image also displays the Connected Grid Modules installed, as well as LEDs which indicate if the modules are operating. You can also view interfaces, available module slots, and other information. The information can be refreshed at any time by clicking the Refresh icon, located at the bottom right-hand corner of the page.

How to Use the Device ManagerUsing a work order that you receive from the back-end system of the Utility network, you can log in to the Device Manager, and connect to a CGR 1000 to troubleshoot devices connected to the router.

Following are a few examples of how to use the Device Manager:

• Your work order states that there are devices connected to a CGR 1000 that cannot be reached. You need to start Device Manager, connect to the router, and then check connectivity to the device. See Test Connectivity, page 3-6

– When you can connect to the devices, review the CGR 1000 configuration information. See Advanced Command, page 3-23


OL-28081-01

Chapter 3 Using the Device Manager Connect to the CGR 1000

– When the configuration information is incorrect, you can update the configuration at Update Configuration File on the CGR 1000, page 3-16 by adding a configuration file to the Device Manager, and then updating the CGR 1000 configuration. After you update the configuration (see Advanced Command, page 3-23) the router automatically resets and restarts with the new configuration. You are now ready to disconnect from the Device Manager.

• Your work order states that the CGR 1000 needs to have a software image update. Start the Device Manager, add the new image file, and then update the router with the new image. The router automatically restarts after you update the software image. You are now ready to disconnect from the Device Manager. See Update Image, page 3-18

• Your work order states that there are newly deployed CGR 1000s; however, they are not appearing in the back-end system. Start the Device Manager and review the router graphic on the main screen. Check the installed modules and their LEDs to verify their operation. When the LEDs are not flashing, check the installation status of the modules. Refer to the configuration guide for the module.

• (CGR 1240 Only) Your work order states that the door of the CGR 1000 is open. Start the Device Manager and check the status of the door (bottom of the At a Glance page). When the door status indicates as status of System Casing Open, you must physically access the CGR 1240 to verify the status of the door. After closing the door, click the Refresh icon (bottom, right-hand) on the Device Manager and verify that the door status is now System Casing Closed. You are now ready to disconnect from the Device Manager.

Connect to the CGR 1000You can connect to a CGR 1000 by either Ethernet or WiFi. The WiFi connectivity control ensures data traffic between the Device Manager and the router are protected by WPA Layer 2 security, once the association and key handshake are complete. The Ethernet connection is secured by HTTPS only.

Connect to the Device Manager by employing one of the following methods:

• Auto Discovered IPv6 address (preferred method for the field)

• IPv4 address (such as 128.128.128.128)

• IPv6 address (such as fe80::d81f:6402:2ae4:4ea8)

Follow these steps to start the Device Manager:

Step 1 After installing the Device Manager on your laptop, double-click on the Cisco CGD Manager icon on your Desktop, or select Start > All Programs > Cisco CGD Manager.

The application opens the Settings page.

The default certificate name (ConnGridDevMgr) and default Service Port (8443) value automatically populate the screen.

Step 2 At the Settings page, click Save.

The Connect to Router page appears.


OL-28081-01



OL-28081-01


Step 3 Select the connection method: Over WiFi, Over Ethernet, or Auto Detect.

Step 4 Enter the SSID and Passphrase if connecting over WiFi.

Step 5 Optional. Enter the address, or select the checkbox to auto-detect the address.

Note When you select Auto Detect, the laptop running Device Manager must be directly connected to the CGR 1000 via Ethernet or WiFi to automatically discover IPv6 addresses.

Step 6 Click Connect.

Tip If you have problems connecting to the Device Manager, refer to Frequently Asked Questions, page 3-30 for troubleshooting suggestions.


OL-28081-01

Chapter 3 Using the Device Manager Test Connectivity

Test ConnectivityThe Test Connectivity task allows you to confirm connectivity to a device from the CGR 1000.

Tip Before you can check a device connection or route to a CGR 1000, you must add the IP address of the device to the Device Manager. The IP address can be either IPv4 or IPv6.

This section covers the following topics:

• Add a Device IP Address

• Ping a Device IP Address

• Traceroute a Device IP Address

• Remove a Device IP Address


OL-28081-01


Add a Device IP AddressFollow these steps to add a device IP address:

Step 1 From the At a Glance page, click Test Connectivity.

The opening page displays defined sample devices and/or target addresses.

Step 2 Click Add to create a target IP address.

An entry panel appears to enter the target description and address for the device.

Step 3 In the Target Description field, enter a description of the device.

Step 4 In the Target IP Address field, enter the IP address (IPv4 or IPv6) of the device.

Step 5 Click OK.

You are now ready to test the connectivity to the device you just added into Device Manager.

Ping a Device IP AddressThe Ping feature allows you to verify connectivity to a device by querying the target IP address.

Follow these steps to test connectivity between the CGR 1000 and the device:

Step 1 At the Test Connectivity page, click on a target IP address from the listing on the page (left-side).

Step 2 Click Ping Target.


OL-28081-01


An In Progress panel displays.

When the system successfully pings the device the Target Reached panel appears.

When the system does not successfully ping a device, refer to Failed Ping, page 3-9.

Step 3 Click Exit to close the window or click Details to view the ping details.


OL-28081-01


Failed Ping

Follow these steps if the ping of the target IP address is unsuccessful:

Step 1 At the Failed to Reach panel. click Details to view the reason the system could not reach the IP address.

Step 2 At the Target Error page, click Exit after reviewing the reason for the error.

Proceed to Traceroute a Device IP Address, page 3-10.


OL-28081-01


Traceroute a Device IP AddressWhen an IP address cannot be reached using Ping, you can use the Traceroute feature to check the route taken to reach the device IP address.

Follow these steps to trace the route of the IP address:

Step 1 At the Test Connectivity page, select the device IP address from the list.

Step 2 Click Traceroute:

• If the traceroute is successful, click Exit on the Traceroute panel.

• If the traceroute is unsuccessful, proceed to Remove a Device IP Address, page 3-10.

Remove a Device IP AddressAfter you have tested a target IP address and verified its connectivity, you can remove the device entry from the Device Manager. Another reason to remove an IP address, occurs when you enter an incorrect device address that the system identifies during failed pings and traceroute attempts.

Follow these steps to remove a target IP address:

Step 1 At the Test Connectivity page, select the target IP address from the list.

Step 2 Click Remove.


OL-28081-01

Chapter 3 Using the Device Manager Manage Interfaces

Manage InterfacesYou can bring up or shut down an interface on the Manage Interfaces page.

• When an interface is up (displays as green), the line protocol is currently active. When an interface is down (displays as red), it means the line protocol is not active.

• When an interface is administratively down (displays as grey), the line interface was taken down by the administrator.

All interfaces installed in the CGR 1000, display automatically.


• Bring Up an Interface

• Shut Down an Interface


OL-28081-01


Follow these steps to view or manage selected router interfaces:

Step 1 From the At a Glance page, click Manage Interfaces.

The opening page displays.

Step 2 Select an interface:

• To bring up an interface, proceed to Bring Up an Interface, page 3-12

• To shut down an interface, proceed to Shut Down an Interface, page 3-13.

Bring Up an InterfaceWhen an interface is shut down for any reason, you can attempt to bring up the interface, by doing the following:

Step 1 At the Manage Interfaces page, select an interface and then click Bring Up Interface.

The In progress panel appears. When the interface is up, the Interface Up panel appears.


OL-28081-01


Shut Down an Interface

Caution Do not shut down the interface on which the Device Manager is communicating with the CGR 1000 or the connection will be lost.

Follow these steps to shut down an interface:

Step 1 At the Manage Interfaces page, select an interface and then click Shut Down.

The In Progress panel appears. When the process completes, the Interface Down panel appears.


OL-28081-01



OL-28081-01

Chapter 3 Using the Device Manager Change Configuration

Change ConfigurationThe Change Configuration task allows you to upload a configuration file to the Device Manager, and then use that file to update the configuration of the CGR 1000. The configuration file information must include version, username and password, Ethernet and WiFi interfaces, and Device Manager (CGDM) and IP HTTPS configurations.

Note The configuration file must be a complete and valid CGR 1000 configuration. When the configuration file contains missing fields, the Device Manager does not update the configuration properly. When you receive an error while updating the configuration file, check the configuration file for missing information.


• Add a Configuration File

• Update Configuration File on the CGR 1000

• Correct a Configuration File

• Remove Configuration File


OL-28081-01


Add a Configuration FileFollow these steps to add a configuration file to the Device Manager:

Step 1 From the At a Glance page, click Change Configuration.

Step 2 Click Add.

An entry panel appears.

Step 3 At the Add Configuration panel:

a. Enter a file description for the configuration file that you are going to upload.

b. Click Browse to navigate to the configuration file location and select the file.

c. Click OK.

Update Configuration File on the CGR 1000After uploading the configuration file to Device Manager, you can use the file to update the CGR 1000 configuration.

Caution Updating the configuration file causes the router to reboot. All connections to the router are lost during the update. After this task starts, there is no way to cancel the event. Be careful when using this feature.


OL-28081-01


Follow these steps to update the configuration file on the CGR 1000:

Step 1 At the Change Configuration page, select the desired configuration file.

Step 2 Click Update Configuration.

• If a confirmation panel appears, click Confirm to verify that you would like to change the router configuration.

• If an error panel appears, the file did not upload to the CGR 1000.

Proceed to Correct a Configuration File, page 3-17.

Correct a Configuration FileA configuration file upload fails because the configuration file has missing fields such as version, username and password, Ethernet and WiFi interfaces, and Device Manager (CGDM) and IP HTTPS details.

To correct a configuration file error:

Step 1 Check the configuration file for errors. If errors or missing information exist, make corrections.

Step 2 Remove the current configuration file from the Device Manager. See Remove Configuration File, page 3-17

Step 3 Add the updated configuration file to Device Manager. See Add a Configuration File, page 3-16

Step 4 Update the configuration file. See Update Configuration File on the CGR 1000, page 3-16.

Remove Configuration FileAfter you have updated the CGR 1000 with the new configuration file, you can remove the file from Device Manager. You can also used this function to remove unwanted or duplicate configuration files.

Follow these steps to remove a configuration file:

Step 1 At the Change Configuration page, select the configuration file you want to remove from the list.



OL-28081-01

Chapter 3 Using the Device Manager Update Image

Update ImageThe CGR 1000 image bundle contains information that the router uses when starting up and operating. The information in the image contains information on FPGA, 3G, wireless drivers, and so on. The only acceptable file format for the Cisco CGR 1000 image file is a zip bundle, which contains a manifest file with information on versioning and files. Any missing files in the zip bundle, cancel the update. You can find the official Cisco CGR 1000 zip bundle on Cisco.com.


• Upload Image

• Replace Image

• Remove Image


OL-28081-01


Upload ImageBefore you can update an image on the CGR 1000, you must upload the image to the Device Manager.

The Upload Image option allows you to upload and store a copy of a software image on the CGR 1000 without initiating an immediate image install. This capability allows operations personnel to use CG-NMS or a Utility management tool to install and reboot the CGR 1000, when network conditions allow.

Follow these steps to upload a image:

Step 1 From the At a Glance page, click Update Image.

Step 2 At the Update Image page, select the CGR 1000 software image that you want to upload.

Note If the software image that you want to install on the CGR 1000 is not listed, click Add and browse to the image; and, then click OK to upload the image.

Step 3 Click Upload Image.

The new image is stored on the CGR 1000 router until you are ready to replace the image on the router. See Replace Image, page 3-19

Replace Image

Caution Updating the CGR 1000 software image might take awhile to complete, and all connections to the router will be unavailable while the image is updating. After this tasks starts, there is no way to cancel the event. Be careful when using this feature.

Follow these steps to replace an image:

Step 1 At the Update Image page, select an CGR 1000 image.

Step 2 Click Replace Image.

A confirmation panel appears.

Step 3 To begin the replace image process, click Confirm.

Step 4 After the router software update completes, the router restarts.


OL-28081-01


Remove ImageAfter you update an image, you can remove the image file from the Device Manager. You can also use the Remove image option, to remove a image file you added mistakenly.

Follow these steps to remove an image:

Step 1 At the Update Image page, select an CGR 1000 image.



OL-28081-01

Chapter 3 Using the Device Manager Retrieve Report

Retrieve ReportYou can retrieve real-time reports log events from the CGR 1000 and view them at the Retrieve Report page or save the information to a .txt file.

• You can specify that you want to retrieve and view all CGR 1000 log events (Retrieve All) or view a specified number of log events (200 or 1000)

• You can specify that you want to save a report the log events that display on the Retrieve Report page to your laptop (Save Report)


OL-28081-01

Chapter 3 Using the Device Manager Retrieve Report

Retrieve and Save ReportsFollow these steps to retrieve real-time reports from the CGR 1000:

Step 1 From the At a Glance page, click Retrieve Report.

Step 2 At the Retrieve Report page, click the type of report that you want to view in the Device Manager window:

• Retrieve Last 200–Displays the last 200 log events of the CGR 1000.

• Retrieve Last 1000–Displays the last 1000 log events of the CGR 1000.

• Retrieve All–Displays all current log events of the CGR 1000.

• Save Report–Saves a copy of the retrieved log events (displayed on the page) to a default file, systemlog.txt. By default, the application saves this file in the Documents folder. However, you can specify where the location for the file.

For an example of the report output, refer to SYSTEMLOG.TXT SAMPLE, page 3-28.


OL-28081-01

Chapter 3 Using the Device Manager Advanced Command

Advanced CommandThe Advanced Command task provides access to the CGR 1000 to fine-tune or troubleshoot the router. You must be familiar with Cisco CG-OS commands. For details on supported commands, refer to the CGR 1000 software configuration guides at: www.cisco.com/go/cgr1000-docs

Note Not all interactive commands are supported. Configuration commands must be concatenated together, as follows: configuration terminal ; interface ethernet2/1 ; shutdown ; end

Step 1 From the At a Glance page, click Advanced Command.

Step 2 You have the following choices:

• Click System Time to displays the current setting of the system clock for the router.

• Click Show Configuration to display the current configuration of the router.

• Click Save Configuration to save the current router configuration to startup-config file.

• Click File Directory to display the router file directory.

• Click Reboot to reboot the router.

• Click Save Output to save the output displayed on the page to a file, windowslog.txt.

By default, the application saves the windowslog.txt file to the Documents folder. See WINDOWSLOG.TXT SAMPLE, page 3-24


OL-28081-01


Chapter 3 Using the Device Manager Example File Output

Example File OutputThis section contains sample output examples for files generated at the Retrieve Report and Advanced Command pages of the Device Manager.

WINDOWSLOG.TXT SAMPLE

The following example represents typical content that might be found in the windowslog.txt file generated at the Advanced Commands page.

CGR-1# show clock15:13:37.311 PST Tue Feb 21 2012

CGR-1# show running

!Command: show running-config!Time: Tue Feb 21 15:13:38 2012

version 5.2(1)CG2(1)logging level feature-mgr 0hostname CGR-1vdc CGR-1 id 1 limit-resource vlan minimum 16 maximum 4094 limit-resource vrf minimum 2 maximum 4096 limit-resource u4route-mem minimum 9 maximum 9 limit-resource u6route-mem minimum 24 maximum 24 limit-resource m4route-mem minimum 58 maximum 58 limit-resource m6route-mem minimum 8 maximum 8

feature telnetfeature crypto ikecrypto ike domain ipsec policy 10 group 1 identity hostnamefeature ospffeature tunnelfeature crypto ipsec virtual-tunnelfeature c1222r

username admin password *** <fingerprint value> role network-adminno password strength-checkip domain-lookupip host nms.cisco.com 192.168.193.11crypto key param rsa label Blue modulus 2048 crypto ca trustpoint Blue enrollment profile Blue rsakeypair Blue 2048 revocation-check none enrollment retry count 3 enrollment retry period 5 serial-number fingerprint <fingerprint value>crypto ca profile enrollment Blue enrollment url http://10.0.2.2:80ip access-list ce-traffic statistics per-entry 10 permit tcp any any eq 1153 class-map type qos match-all ce-traffic match access-group name ce-trafficpolicy-map type qos ce-traffic class ce-traffic


OL-28081-01


set dscp 46snmp-server user admin network-admin auth md5 <value> priv <value> localizedkeyrmon event 1 log trap public description FATAL(1) owner PMON@FATALrmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICALrmon event 3 log trap public description ERROR(3) owner PMON@ERRORrmon event 4 log trap public description WARNING(4) owner PMON@WARNINGrmon event 5 log trap public description INFORMATION(5) owner PMON@INFOcallhome email-contact root@localhost phone-contact +1-000-000-0000 streetaddress a-street-address destination-profile nms destination-profile nms format netconf destination-profile nms transport-method http destination-profile nms http https://nms.cisco.com:9121 trustpoint Blue destination-profile nms alert-group all enable

vrf context managementcrypto ipsec transform-set trans1 esp-aes 128 esp-sha1-hmaccrypto ipsec profile MyIPSecProfile set transform-set trans1vlan 1

route-map CONN permit 10 match interface loopback0 chat-script gsm PROFILE1wimax scan-list airspan2344 channel index 1 frequency 2344000 bandwidth 10000 nap id C1:5C:00 priority 1 channel-index 1 nsp id C1:5C:00 homewifi ssid CGDM authentication key-management wpa2 wpa2-psk ascii encrypted 7 1234567890

interface Tunnel1 ip address 20.5.20.3/31 tunnel source loopback0 tunnel destination 20.2.10.1 description GRE tunnel no keepalive no shutdown

interface Tunnel19 ip address 20.4.20.2/24 ip ospf cost 100 ip ospf mtu-ignore ip router ospf 1 area 0.0.0.1 tunnel mode ipsec ipv4 tunnel source Wimax6/1 tunnel destination 10.0.4.8 description ipsec tunnel through wimax no keepalive tunnel protection ipsec profile MyIPSecProfile no shutdown

interface Tunnel20 ip address 20.3.20.2/24 ip ospf cost 200 ip ospf mtu-ignore ip router ospf 1 area 0.0.0.1 tunnel mode ipsec ipv4


OL-28081-01


tunnel source Cellular3/1 tunnel destination 173.36.248.197 description ipsec tunnel through ATT 3G no keepalive tunnel protection ipsec profile MyIPSecProfile no shutdown

interface Tunnel21 service-policy type qos output ce-traffic ip address 20.1.20.2/24 ip ospf cost 300 ip ospf mtu-ignore ip router ospf 1 area 0.0.0.1 tunnel mode ipsec ipv4 tunnel source Ethernet2/1 tunnel destination 10.0.4.8 description ipsec tunnel through E2/1 no keepalive tunnel protection ipsec profile MyIPSecProfile no shutdown

interface Dialer1 dialer persistent dialer pool 1 dialer string gsm no shutdown

interface Ethernet2/1 description ==sol-3750-1 ip address 10.0.5.1/24 no shutdown

interface Ethernet2/2 description ==2.3.094 blue ip address 172.27.89.56/25 no shutdown

interface Ethernet2/3 no shutdown

interface Ethernet2/4



interface loopback0 ip address 20.2.10.2/32 ip router ospf 1 area 0.0.0.1

interface Cellular3/1 dialer pool-member 1 no shutdown

interface Wimax6/1 no shutdown scan-list airspan2344 ip address 10.0.7.3/24

interface Wpan4/1

interface Wifi2/1 ssid CGDM no shutdown


OL-28081-01


ipv6 address use-link-local-onlyclock timezone PST -8 0line console exec-timeout 0line vty exec-timeout 0router ospf 1 redistribute direct route-map CONNip route 10.0.2.0/24 10.0.5.2ip route 10.0.2.1/32 10.0.5.2ip route 10.0.2.2/32 10.0.5.2ip route 10.0.2.3/32 10.0.5.2ip route 10.0.2.53/32 20.2.10.1ip route 10.0.2.102/32 20.2.10.1ip route 10.0.4.0/24 10.0.5.2 2ip route 10.0.4.0/24 10.0.7.2ip route 128.0.0.0/24 Cellular3/1ip route 171.0.0.0/8 172.27.89.1ip route 172.0.0.0/8 172.27.89.1ip route 173.36.248.0/24 Cellular3/1

cgdm registration start trustpoint Blueip http secure-serverip http secure-port 8443ip http secure-server trustpoint Blue


OL-28081-01


SYSTEMLOG.TXT SAMPLE

The following example output shows what the systemlog.txt file looks like when you save a report on the Retrieve Reports page.

The following example represents typical content that might be found in the systemlog.txt file generated at the Retrieve Reports page.

2012 Feb 21 14:44:12 CGR-1 Feb 21 14:44:12 %KERN-3-SYSTEM_MSG: [ 1293.456678] - kernel2012 Feb 21 14:44:12 CGR-1 Feb 21 14:44:12 %KERN-3-SYSTEM_MSG: [ 1293.456830] /1_0_cdma_qos/third-party/src/linux/kernel/wrl3/linux-2.6.27_wrl30/drivers/i2c/busses/ioh/ioh_i2c_hal.c:ioh_i2c_wait_for_xfer_complete returns 0 - kernel2012 Feb 21 14:44:12 CGR-1 Feb 21 14:44:12 %KERN-3-SYSTEM_MSG: [ 1293.456847] - kernel2012 Feb 21 14:44:13 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:47:02 CGR-1 last message repeated 1 time2012 Feb 21 14:47:31 CGR-1 last message repeated 2 times2012 Feb 21 14:47:31 CGR-1 %PLATFORM-2-DISK_ALERT: Disk Status Alert : disk partition '/bootflash' is at high usage level (91%). 2012 Feb 21 14:47:31 CGR-1 %CALLHOME-2-EVENT: LOW_FLASH_SPACE2012 Feb 21 14:47:31 CGR-1 %PLATFORM-2-DISK_ALERT: Disk Status Alert : disk partition '/isan' is at high usage level (91%). 2012 Feb 21 14:47:32 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 14:47:57 CGR-1 last message repeated 1 time2012 Feb 21 14:47:57 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 14:47:57 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 14:48:01 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - dcos-ping2012 Feb 21 14:49:39 CGR-1 last message repeated 2 times2012 Feb 21 14:50:20 CGR-1 last message repeated 1 time2012 Feb 21 14:50:20 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:50:21 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - dcos-ping2012 Feb 21 14:50:34 CGR-1 last message repeated 1 time2012 Feb 21 14:50:34 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:50:37 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - dcos-ping2012 Feb 21 14:50:38 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:51:15 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - rm2012 Feb 21 14:51:16 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - java2012 Feb 21 14:51:16 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - pidof2012 Feb 21 14:51:20 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 14:51:30 CGR-1 last message repeated 1 time2012 Feb 21 14:51:30 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 14:51:31 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 14:51:38 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - su2012 Feb 21 14:51:38 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - xmlsa2012 Feb 21 14:51:39 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - dcos-traceroute2012 Feb 21 14:52:11 CGR-1 last message repeated 1 time2012 Feb 21 14:52:25 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:52:32 CGR-1 last message repeated 1 time2012 Feb 21 14:52:32 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 14:52:33 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:52:33 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 14:53:10 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - vsh2012 Feb 21 14:53:56 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 14:53:56 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 14:54:32 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:55:58 CGR-1 last message repeated 2 times2012 Feb 21 14:55:58 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 14:55:59 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 14:57:13 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:57:53 CGR-1 last message repeated 2 times2012 Feb 21 14:57:53 CGR-1 %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on console02012 Feb 21 14:57:53 CGR-1 %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on [email protected]


OL-28081-01

Chapter 3 Using the Device Manager Disconnect from the CGR 1000

2012 Feb 21 14:57:54 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:57:55 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - vsh2012 Feb 21 14:57:56 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 14:58:12 CGR-1 last message repeated 1 time2012 Feb 21 14:58:12 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 14:58:13 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 14:58:53 CGR-1 %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on [email protected] Feb 21 14:58:54 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa2012 Feb 21 15:00:53 CGR-1 last message repeated 1 time2012 Feb 21 15:00:53 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 15:00:53 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 15:03:08 CGR-1 %DIALER-5-DIALER_MODEM_UP: Modem active 2012 Feb 21 15:04:15 CGR-1 last message repeated 1 time2012 Feb 21 15:04:15 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 15:04:15 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 15:07:56 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION2012 Feb 21 15:07:56 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl2012 Feb 21 15:10:51 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - vsh

Disconnect from the CGR 1000After finishing your work on the CGR 1000, click Connection (upper-left) to disconnect the Device Manager from the router.

The Connect to Router page appears.

Feature History

Feature Name Release Feature Information

Support for Cisco CGR 1120 Cisco CG-DM Release 1.1 Initial support of the feature on the Device ManagerUpload Image option on the

Update Image page


OL-28081-01

Chapter 3 Using the Device Manager Frequently Asked Questions

Frequently Asked QuestionsThis section contains information on frequently asked questions of the Device Manager.

“How do I check if the certificate is installed?”

See Certificate Installation, page 2-2.

“After I click Connect, I received a connection error message”

If the Device Manager is connected to the CGR 1000 over Ethernet and the IP address is configured, ensure that you can ping this IP address from the Device Manager laptop. If the IP address is auto-detected, ensure that the Device Manager computer Ethernet is connected to the router directly, and that the router interface is configured with ipv6 address use-link-local-only.

If the Device Manager is connected to the CGR 1000 using WiFi, first ensure the WiFi parameters (SSID and passphrase) match the configuration of the router. If you still cannot connect using WiFi, verify that Windows Wireless Zero Configuration is enabled on the laptop.

Ensure there is no third-party wireless client tool controlling the WiFi interface. For example, if you are using a third-party client tool (such as Intel PROSet Wireless Client Tool), change the settings from that tool to enable Windows Wireless Zero Configuration.

You can also refer to the following steps to enable Windows Wireless Zero Configuration:

Step 1 Click Start > Settings > Control Panel.

Step 2 Double-click Network Connections.

Step 3 Right-click Wireless Network Connection.

Step 4 Click Properties.

Step 5 Click Wireless Networks tab.

Step 6 Check the Use Windows to configure my wireless network settings check box.

Step 7 Click OK. This confirms the third-party WiFi utility is not configured to mange your WiFi interface.


OL-28081-01


“I cannot log into Device Manager”

This message displays when the application cannot find a valid certificate. When this condition occurs, the Settings page opens.

See Certificate Installation, page 2-2 for details on installing the certificate.

Note Ensure that the clock is set to the correct time, otherwise the certificate will not be honored.


OL-28081-01



OL-28081-01