Known Issues and Workarounds
This following is the list of known issues in Cisco Configuration Professional Express Release 3.2:
Symptom: In the Interface screen (in both the Admin view and the EndUser view), the Edit VLAN and Edit Interface dialog boxes do not reflect the correct values for the attributes displayed on the Summary screen.
Condition: This issue occurs when the Interfaces feature is in use, and an interface or a VLAN is being edited.
Workaround: Upgrade your Cisco IOS Software Release to 15.2(4)M or later.
Symptom: The Cisco Configuration Professional Express interfaces screen displays a blank page.
Condition: This issue occurs when the Cisco IOS Release that is being used is earlier than Release 15.2, and router has cellular interfaces.
Workaround: Upgrade to Cisco IOS Release 15.2.4M2 or later, or Release 15.3.1T or later for all SKUs.
Symptom: While creating a user very first time in a new router the password is not encrypted..
Condition: The user will be prompted to create a new user while logging in to the router for the first time with default username and password. The newly created user is not encrypted. The password will be visible when anyone tries to check the running configuration.
Workaround: Login to router and execute a CLI “service password-encryption” in config mode. Otherwise navigate to “Configure CLI” menu and execute the same CLI in config mode.
Symptom: NAT translations do not happen if stale NAT translation CLIs present in the configuration.
Condition: This problem is seen when interface enabled for NAT feature is deleted using CCP Express 3.0 [on supported Cisco Routers]
This problem occurs with the following conditions:
1. Enabling NAT during Interface configuration and deleting it
2. Configuring an interface as Primary WAN interface and deleting it
3. Configuring an interface as Secondary WAN interface and deleting it
In above conditions following CLIs are sent to router from CCPExpress software and stays in configuration as stale entries when deleted
! //**** Below CLI sent as part of interface configuration enabled for NAT**** //
ip nat inside source list <Nat-list_name> interface <Interface_name> overload
!//**** Below CLI sent as part of Primary/Secondary WAN interface configuration**** //
ip nat inside source route-map <route_map_name> interface <Interface_name> overload
1. If the interface part of NAT overload configuration is deleted then create that interface (see example below)
2. Delete the stale NAT overload CLI
3. Delete the created interface
4. Execute "clear nat translations forced"
Below entry may exist on the device causing NAT translations to not work properly.
ip nat inside source list nat-list interface Dialer4 overload
(config)# no ip nat inside source list nat-list interface Dialer4 overload
Symptom: Unable to access the Internet. Traffic is not going through the configured WAN interface.
Condition: When the WAN interface gets its IP and default gateway from DHCP server, CCP Express should not push "ip route 0.0.0.0 0.0.0.0 'primary WAN interface'" configuration to the router. With this configuration the traffic is not flowing through the device, when already the default route (GW IP received from DHCP server) is installed on the router.
Workaround: Remove the CLI manually in the router like “no ip route 0.0.0.0 0.0.0.0 'primary WAN interface'” or using CCP Express “anyCli” feature to execute the CLI
Symptom: The protocol 914c/g protocol is not listed under net-admin application list in the Policy screen.
Condition: This particular protocol not be configured using CCP Express.
There is no workaround. If we configure "match protocol 914c/g" under any of the class-maps using CLI on the router, then UI will throw "parsing error" while accessing some features eg. CWS