Guest

Cisco Emergency Responder

Field Notice: FN - 62576 - IOS Upgrade to 12.2(25)SEE1 or 12.2(25)SEE2 Causes Incorrect Association of Emergency Response Locations by Cisco Emergency Responder (CER)


Revised October 9, 2007

October 31, 2006

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Products Affected

Cisco Emergency Responder 1.2(X) and 1.3(1a) - 1.2(X) and 1.3(1a)

Problem Description

Due to code changes in the SNMP ENTITY-MIB data, once an IOS upgrade to 12.2(25)SEE1 or 12.2(25)SEE2 is complete, Cisco Emergency Responder (CER) switch-port--to--Emergency Response Location (ERL) associations are incorrect in CER.

The IOS platforms affected by this upgrade are:

Catalyst 3750, Catalyst 2960, Catalyst 2970, and Catalyst 3560.

For example, using a Catalyst 3560 device, an ERL that was originally associated with port Fa0/1, is now associated with Fa0/3. In general, the ERL associations are "shifted" by 2 ports. As a result, when an emergency call is made, this incorrect association is used to determine phone location information. This may lead to incorrect routing of emergency calls and incorrect reporting of caller location to the Public Safety Answering Point (PSAP) and local security.

Background

During a post-upgrade verification process (to 12.2(25)SEE1 or 12.2(25)SEE2) it was noticed that the Emergency Location Identification Number (ELIN) and Location information was incorrect in CER. Customers not apt to perform this type of post-upgrade verification will likely be unaware of the change.

The investigation revealed that the value of entPhysicalParentRelPos that is used to identify the correct interface shows a shift of two ports. Thus an ERL that was originally associated with Fa0/1 would now show Fa0/3, rendering the Emergency Response location wrong.

Problem Symptoms

A call to 911 could be routed incorrectly, or the location of the caller could be reported incorrectly.

Workaround/Solution

If the switch was upgraded to IOS 12.2(25)SEE1 or 12.2(25)SEE2, perform the following.

Note: If you wish to remain on IOS 12.2(25)SEE1 or 12.2(25)SEE2, you must perform the manual workaround of resetting the assignments of switch ports to ERLs. This will have to be done by going to the switch port details page in CER Administration website and verifying that the ERL associations for each switch port of the affected switch is correct. If the association is found to be wrong, it will have to be corrected.

  1. Revert to IOS code that does not contain the ENTITY-MIB change. The ENTITY-MIB changes are contained in 12.2(25)SEE1 and 12.2(25)SEE2.

  2. Upgrade the IOS to 12.2(25)SEE3. This is available on Cisco Connection Online (CCO).

  3. This is also fixed in 12.2(35)SE and later versions of IOS, which can be downloaded from Cisco Connection Online.

If the switch is upgraded from IOS 12.2(25)SEE1 or 12.2(25)SEE2 to a later version:

The assignments of switch ports to ERLs must be corrected by the ERL Administrator after any IOS upgrade from 12.2(25)SEE1 or 12.2(25)SEE2 to a later release. This will have to be done by going to the switch port details page in CER Administration website and verifying that the ERL associations for each switch port of the affected switch is correct. If the association is found to be wrong, it will have to be corrected.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsg36094 (registered customers only)

ENTITY-MIB data has been changed during upgrade to 12.2(25)SEE1 or 12.2(25)SEE2

Revision History

Revision

Date

Comment

1.3

09-OCT-2007

Added list of upgrade options to Workaround/Solution section.

1.2

02-FEB-2007

The workaround section was updated accordingly

1.1

27-NOV-2006

Removed reference to a non-affected product from the Problem Description section

1.0

31-OCT-2006

Initial Public Release

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.