Using the Device Manager
The chapter explains how to use the Device Manager, and contains the following topics:
•
How to Use the Device Manager
Overview
The 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
•Manage Interfaces: Bring up or shut down an CGR 1000 interface. See Manage Interfaces
•Change Configuration: Update the CGR 1000 configuration with a provided configuration file, and then reboot the router with the new configuration. See Change Configuration
•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
•Retrieve Report: Download and view the CGR 1000 system logs. See Retrieve Report
•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
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 Manager
Using 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
–When you can connect to the devices, review the CGR 1000 configuration information.
See Advanced Command
–When the configuration information is incorrect, you can update the configuration at
Update Configuration File on the CGR 1000 by adding a configuration file to the Device Manager, and then updating the CGR 1000 configuration. After you update the configuration (see Advanced Command) 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
•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 1000
You 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.
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 for troubleshooting suggestions.
Test Connectivity
The 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:
•Traceroute a Device IP Address
Add a Device IP Address
Follow 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 Address
The 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.
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.
Step 3 Click Exit to close the window or click Details to view the ping details.
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.
Traceroute a Device IP Address
When 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.
Remove a Device IP Address
After 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.
Manage Interfaces
You 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.
This section covers the following topics:
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
•To shut down an interface, proceed to Shut Down an Interface.
Bring Up an Interface
When 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.
Shut Down an Interface
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.
Change Configuration
The 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.
This section covers the following topics:
•Update Configuration File on the CGR 1000
Add a Configuration File
Follow 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 1000
After uploading the configuration file to Device Manager, you can use the file to update the CGR 1000 configuration.
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.
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.
Correct a Configuration File
A 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
Step 3 Add the updated configuration file to Device Manager. See Add a Configuration File
Step 4 Update the configuration file. See Update Configuration File on the CGR 1000.
Remove Configuration File
After 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.
Step 2 Click Remove.
Update Image
The 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.
This section covers the following topics:
Upload Image
Before 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
Replace Image
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.
Remove Image
After 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.
Step 2 Click Remove.
Retrieve Report
You 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)
Retrieve and Save Reports
Follow 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.
Advanced Command
The 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
Example File Output
This 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 clock
15: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 0
hostname CGR-1
vdc 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 telnet
feature crypto ike
crypto ike domain ipsec
policy 10
group 1
identity hostname
feature ospf
feature tunnel
feature crypto ipsec virtual-tunnel
feature c1222r
username admin password *** <fingerprint value> role network-admin
no password strength-check
ip domain-lookup
ip host nms.cisco.com 192.168.193.11
crypto 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:80
ip 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-traffic
policy-map type qos ce-traffic
class ce-traffic
set dscp 46
snmp-server user admin network-admin auth md5 <value> priv <value> localizedkey
rmon event 1 log trap public description FATAL(1) owner PMON@FATAL
rmon event 2 log trap public description CRITICAL(2) owner PMON@CRITICAL
rmon event 3 log trap public description ERROR(3) owner PMON@ERROR
rmon event 4 log trap public description WARNING(4) owner PMON@WARNING
rmon event 5 log trap public description INFORMATION(5) owner PMON@INFO
callhome
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 management
crypto ipsec transform-set trans1 esp-aes 128 esp-sha1-hmac
crypto ipsec profile MyIPSecProfile
set transform-set trans1
vlan 1
route-map CONN permit 10
match interface loopback0
chat-script gsm PROFILE1
wimax 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 home
wifi 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
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 Ethernet2/5
interface Ethernet2/6
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
ipv6 address use-link-local-only
clock timezone PST -8 0
line console
exec-timeout 0
line vty
exec-timeout 0
router ospf 1
redistribute direct route-map CONN
ip route 10.0.2.0/24 10.0.5.2
ip route 10.0.2.1/32 10.0.5.2
ip route 10.0.2.2/32 10.0.5.2
ip route 10.0.2.3/32 10.0.5.2
ip route 10.0.2.53/32 20.2.10.1
ip route 10.0.2.102/32 20.2.10.1
ip route 10.0.4.0/24 10.0.5.2 2
ip route 10.0.4.0/24 10.0.7.2
ip route 128.0.0.0/24 Cellular3/1
ip route 171.0.0.0/8 172.27.89.1
ip route 172.0.0.0/8 172.27.89.1
ip route 173.36.248.0/24 Cellular3/1
cgdm
registration start trustpoint Blue
ip http secure-server
ip http secure-port 8443
ip http secure-server trustpoint Blue
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] - kernel
2012 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 - kernel
2012 Feb 21 14:44:12 CGR-1 Feb 21 14:44:12 %KERN-3-SYSTEM_MSG: [ 1293.456847] - kernel
2012 Feb 21 14:44:13 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:47:02 CGR-1 last message repeated 1 time
2012 Feb 21 14:47:31 CGR-1 last message repeated 2 times
2012 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_SPACE
2012 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 - curl
2012 Feb 21 14:47:57 CGR-1 last message repeated 1 time
2012 Feb 21 14:47:57 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 14:47:57 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 14:48:01 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - dcos-ping
2012 Feb 21 14:49:39 CGR-1 last message repeated 2 times
2012 Feb 21 14:50:20 CGR-1 last message repeated 1 time
2012 Feb 21 14:50:20 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:50:21 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - dcos-ping
2012 Feb 21 14:50:34 CGR-1 last message repeated 1 time
2012 Feb 21 14:50:34 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:50:37 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - dcos-ping
2012 Feb 21 14:50:38 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:51:15 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - rm
2012 Feb 21 14:51:16 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - java
2012 Feb 21 14:51:16 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - pidof
2012 Feb 21 14:51:20 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 14:51:30 CGR-1 last message repeated 1 time
2012 Feb 21 14:51:30 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 14:51:31 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 14:51:38 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - su
2012 Feb 21 14:51:38 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - xmlsa
2012 Feb 21 14:51:39 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - dcos-traceroute
2012 Feb 21 14:52:11 CGR-1 last message repeated 1 time
2012 Feb 21 14:52:25 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:52:32 CGR-1 last message repeated 1 time
2012 Feb 21 14:52:32 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 14:52:33 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:52:33 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 14:53:10 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - vsh
2012 Feb 21 14:53:56 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 14:53:56 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 14:54:32 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:55:58 CGR-1 last message repeated 2 times
2012 Feb 21 14:55:58 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 14:55:59 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 14:57:13 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:57:53 CGR-1 last message repeated 2 times
2012 Feb 21 14:57:53 CGR-1 %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on console0
2012 Feb 21 14:57:53 CGR-1 %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on localhost@xml.7555
2012 Feb 21 14:57:54 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:57:55 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - vsh
2012 Feb 21 14:57:56 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 14:58:12 CGR-1 last message repeated 1 time
2012 Feb 21 14:58:12 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 14:58:13 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 14:58:53 CGR-1 %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on localhost@xml.7555
2012 Feb 21 14:58:54 CGR-1 %USER-3-SYSTEM_MSG: 1 dialer interface listed - xmlsa
2012 Feb 21 15:00:53 CGR-1 last message repeated 1 time
2012 Feb 21 15:00:53 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 15:00:53 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 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 time
2012 Feb 21 15:04:15 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 15:04:15 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 15:07:56 CGR-1 %CALLHOME-2-EVENT: REGISTRATION_NOTIFICATION
2012 Feb 21 15:07:56 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - curl
2012 Feb 21 15:10:51 CGR-1 %USER-3-SYSTEM_MSG: --- plcpm_im init is called - vsh
Disconnect from the CGR 1000
After 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
|
|
|
|
|---|---|---|
Support for Cisco CGR 1120 |
Cisco CG-DM Release 1.1 |
Initial support of the feature on the Device Manager |
Upload Image option on the Update Image page |
Frequently Asked Questions
This section contains information on frequently asked questions of the Device Manager.
"How do I check if the certificate is installed?"
"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.
"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 for details on installing the certificate.
Note Ensure that the clock is set to the correct time, otherwise the certificate will not be honored.
Feedback