Symptom On the CGR, "%Please shutdown the interface before removing it" displays when you configure the dialer as a default interface.
Conditions Dialer is already in a shutdown state, and the console displays "%Please shutdown the interface before removing it". Dialer is configured as a default interface.
Workaround Remove Dialer Pool and then the default interface dialer 1 command executes with no errors.
Minimal Support for SNMP write on ciscoWan3gMib for Security Reasons
The read-write operation only permits the following OIDS in CISCO-WAN-3G-MIB.
Note: See related ciscoWan3gMib caveats in this section CSCuh85612, CSCuh88771, CSCuh88904, CSCuh88968, CSCui00861, CSCui01208, CSCui01347, CSCui03505
Symptom A write on c3gGsmRoamingPreference results in commit failed."
SNMP write on most of ciscoWan3gMib is not supported for security reasons.
Conditions When you issue snmp set on c3gGsmRoamingPreference, you get the error message “Commit failed.”
Workaround There is no workaround. Limitation is by design for security reasons.
Symptom c3gMsisdn shows an empty string in an SNMP walk.
Conditions SNMPget on c3gMsisdn.
Workaround There is no workaround. This issue is carrier dependent. When this issue is seen in the field, check with your service provider to see whether MsIsdn is populated by the service provider. For example, AT&T does provide the MsIsdn value and T-Mobile does not.
Symptom When a SNMP set is issued to create a row in the PDP profile table, commitFailed was seen.
snmpset -v 3 -u sgbublr -l authPriv -a MD5 -A cisco1234 -x AES128 -X cisco1234 172.27.168.114 c3gGsmPdpProfileRowStatus.22.2 i 4
Failed object: CISCO-WAN-3G-MIB::c3gGsmPdpProfileRowStatus.22.2
Conditions SNMP set operations are not allowed on c3gGsmPdpProfileTable for security reasons.
Workaround Use the CLI to create a new profile for profile 3 as shown in the example below:
cgr1000# cellular 3/1 gsm profile create 3 PRO3
Profile 3 will be created with the following values:
Profile 3 written to modem
Symptom ciscoWan3Gmib does not support a write function for the c3gGsmChv1 object.
Conditions When a user issues a set c3gGsmChv1 command, the set fails. By design, the write function (disabled by default) does not work on most of the ciscoWan3gMib for security reasons.
Workaround Enter the command cellular slot/port gsm sim change-pin Old-PIN New-PIN to set Card Holder Verification 1 (CHV1). Example below:
CGR1K# cellular 5/1 gsm sim change-pin 0000 1111
Symptom A write on c3gCdmaSecurityTable results in commit failed.
1: c3gCdmaPinSecurityStatus.23 (INTEGER) unknown(1)
***** SNMP SET-RESPONSE END *****
Conditions User uses snmp create a row in the security table as the MIB has access to create a row. This results is failure as write is not supported in IOS for this MIB.
Workaround There is no workaround for this issue. SNMP write on most of ciscoWan3gMib is not supported for security reasons.
Either objects are pre-set or can be set through CLI. SNMP set is not supported.
Symptom The OID c3gHdrDdtmPreference is not writable even though it is a read-write object. SNMP write on c3gHdrDdtmPreference is not supported for security reasons.
Conditions The requested set on c3gHdrDdtmPreference always results in Commit Failed errors.
Workaround Enter the [ no ] cdma ddtm command to set the c3gHdrDdtmPreference for a cellular preference as enabled or disabled. For example:
To enable cdma ddtm for cellular 3/1:
CGR1000(config)#controller cellular 3/1
CGR1000(config-controller)# cdma ddtm
Symptom MIB OID c3gCdmaRoamingPreference does not have corresponding CLI. The write operation of c3gCdmaRoamingPreference results in "Commit failed" errors. The write of c3gCdmaRoamingPreference is not supported due to security reasons.
Conditions User wants to identify the Roaming Preference through CLI. its not shown. It is available only via mib get.
The write of c3gCdmaRoamingPreference results in "Commit failed" errors.
Workaround Use c3gCdmaRoamingPreference get to retrieve the Roaming Preference value.
Symptom Issue snmpset on any of c3gMdn,c3gCurrentNid, c3gCurrentSid,c3gSipUsername or c3gSipPassword MIB objects. The following occurs:
1: c3gSipUsername.23 (DisplayString) email@example.com [126.96.36.199.188.8.131.52.184.108.40.206.7A.220.127.116.11E.63.6F.6D (hex)]
Conditions SNMP write on most of the ciscoWan3gMib is not supported for security reasons.
Workaround There is no workaround.
Symptom Cannot SSH into the CGR with SSHv2 protocol.
Conditions SSH process is operating in its default configuration. That is, it is neither configured with ip ssh version X nor is it configured with ip ssh version 2.
In addition, the SSH process is not configured with ip ssh rsa keypair-name XXXX to specify a SSH host key.
Subsequently, SSH process uses the SUDI RSA key as SSH host key.
User should manually create a new SSH host key by following these steps:
1) To generate a new key, enter command crypto key generate rsa modulus 2048 label XXXX in configuration (config) command mode.
2) To specify the use of key XXXX as SSH host key, enter command ip ssh rsa keypair-name XXXX in config command mode.
3) To specify the use of the SSHv2 protocol, enter command ip ssh version 2 in config command mode.
Symptom When using Airspan base station with CGR1000 dot16 modules, the latency may increase if the dot16 uplink throughput is very low (around 200 Kbps or less).
Conditions If the uplink throughput is very low (around 200 Kbps or less), the latency may increase (especially with the Best Effort service-class). This is because Airspan base stations expect a certain minimum rate of traffic before processing the traffic.
Workaround Configure a QoS scheduling method like rTPS on the base station to minimize the increase in the uplink latency at very low traffic rates.
Symptom You cannot download the software image bundle for this release when operating with SSHv1.
Conditions By default, the GOS image that comes with the software bundle image only supports SSHv2. You must enable SSHv2 in Cisco IOS in order to download any TPMC package or application to the GOS.
Workaround Enable SSH2 in Cisco IOS.
Symptom The system reset-reason may show “Thermal Trip” after a power outage.
Conditions When a CGR is power-cycled due a power loss event, the system reset-reason may show a false “Thermal Trip” reset instead of “Power-on”. This is because the unstable voltage on the mainboard may trigger a false “Thermal Trip” reset-reason.
Workaround After the CGR comes back up, issue show environment temperature to check the sensor temperature. If they show normal values, the Thermal Trip reset-reason can be ignored and no further action needs to be taken.
Symptom The line protocol on the dot16 interface may not go down after restoring the interface to default configuration.
Conditions Configure the necessary settings for the dot16 interface to come online. Restore the interface to default settings. The dot16 interface line protocol may stay up.
Workaround Perform a shutdown on the interface.