Table Of Contents
Release Notes for Cisco Emergency Responder 2.0(2)
Contents
Hardware and Software Requirements
Related Documentation
Installation Notes
Supported Upgrades
Important Upgrade Notes
Caveats
Using Bug Toolkit
Open Caveats
Resolved Caveats
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Emergency Responder 2.0(2)
Updated December, 2007
These release notes describe the feature enhancement and caveats for Cisco Emergency Responder (Cisco ER) 2.0(2).
Contents
These release notes provide the following information:
•
Hardware and Software Requirements
•Related Documentation
•Installation Notes
•Caveats
•Obtaining Documentation and Submitting a Service Request
Hardware and Software Requirements
Cisco ER 2.0 supports a variety of hardware and software components, as shown in the following tables.
Note The type of support can differ between types of hardware; read the tables carefully to determine how Cisco ER will work with the devices you use.
Table 1 lists other software that you must install to use Cisco ER 2.0.
Table 1 Required Software
Item
|
Supported Software Version
|
Description
|
Data Migration Assistant (DMA)
|
•Release 6.0(1)
|
Before you can upgrade from Cisco ER 1.3 to Cisco ER 2.0, you must use the Data Migration Assistant (DMA) tool to create a migration file containing your Cisco ER 1.3 configuration information. As part of the upgrade process, you will be prompted to provide the location of this migration file.
|
Cisco Unified CallManager and
Cisco Unified
Communications Manager
|
•Cisco Unified CallManager 4.2
•Cisco Unified CallManager 4.3
•Cisco Unified Communications Manager 5.0
•Cisco Unified Communications Manager 5.1
•Cisco Unified Communications Manager 6.0
•Cisco Unified Communications Manager 6.1
|
The software that runs the telephony network.
Note When you configure Cisco ER in support of Cisco Unified Communications Manager 6.1, choose Cisco Unified Communications Manager 6.0 as the supported version when prompted during the installation of Cisco ER or choose Cisco Unified Communications Manager 6.0 as the Cisco Unified Communications Manager version in Cisco ER Administration Utility.
|
Web browser
|
Microsoft Internet Explorer 6.0
|
|
Table 2 contains optional software that is recommended for use with Cisco ER 2.0.
Table 2 Recommended Software
Item
|
Minimum Software Version
|
Description
|
E-mail server
|
Any SMTP e-mail server
|
Used to send e-mail notifications to onsite alert (security) personnel. If you use an SMTP e-mail paging server, personnel are paged instead of e-mailed.
|
Cisco Unified Operations Manager
Note CiscoWorks IP Telephony Environment Monitor (ITEM) 2.0 is also supported.
|
Version 1.0
|
Used to monitor the health and functionality of Cisco ER.
|
Table 3 lists the different types of phones that support Cisco ER 2.0. The type of support Cisco ER 2.0 supplies differs depending on the type of phone and the type of switch port to which the phone is attached.
Table 3 Supported Phones
Phones
|
Description
|
Phones automatically tracked using CDP
•SCCP protocol on Cisco Unified IP Phone 7975, 7971, 7970, 7965, 7962, 7961, 7960, 7945, 7942, 7941, 7940, 7937, 7936, 7935, 7931, 7912, 7911, 7910, 7906, 7905, 7902, 7985
•All other SCCP phones with CDP support, with the exception of ATA devices
•SIP protocol on Cisco Unified IP Phone 7975, 7971, 7970, 7965, 7962, 7961, 7960, 7945, 7942, 7941, 7940, 7931, 7912, 7911, 7906, 7905, 3911
•Cisco IP Communicator
|
These phones do not require special Cisco ER configuration. However, ensure that you enable Cisco Discovery Protocol (CDP) on the switches.
Note Although ATA phones support CDP and SCCP, Cisco ER cannot automatically track them. You can add ATA phones manually and assign them to an Emergency Response Location (ERL). Cisco ER will route calls from ATA phones based on the assigned ERL.
|
Phones automatically tracked using CAM tables
•Cisco Unified IP Phone 12 SP+ and VIP 30
|
To automatically track these phones, you must enable content-addressable memory (CAM) tracking when you add the switches to the Cisco ER configuration. Phones that do not use CDP are tracked using the CAM table on all supported switch platforms for Native and AUX VLANs.
|
Phones that you can track using IP subnet
•Wireless phones, such as Cisco Unified Wireless IP Phone 7920/7921, and Cisco IP SoftPhones running on 802.11b
•Supported Cisco Unified IP Phones connected to Cisco or third-party switches that are not discovered or recognized by Cisco ER
•Cisco Unified Personal Communicator
•Third-party SIP phones
|
To track these phones, you must configure the subnet and then assign ERLs to the configured subnets.
Note The use of CAM table tracking can result in the inadvertent discovery and unsupported use of wireless IP phone MACs for tracking purposes. To avoid mis-tracking of wireless IP phones, if CAM table tracking is enabled for a switch, the ERL configured for any switch port connected to a wireless access point must agree with the ERL configured for the IP subnet that will contain the phones connected to that access point.
|
Phones that you can manually define
•Analog phones, for example, phones connected to VG 224/248 and ATA devices
•Generic H.323 or SIP endpoints. Supported H.323 phones include Microsoft NetMeeting and video-enabled H.323 endpoints
•Any phone otherwise supported for automatic tracking that is connected to an unsupported switch port
|
These phones are only supported if their calls are routed by Cisco Unified Communications Manager.
|
Note Cisco ER supports SNMP version 1, version 2, and version 2c of a LAN switch.
Table 4 lists the switches that are supported for automatic tracking. You can use other switches, but you might have to manually define phones attached to those switches.
Table 4 Supported Voice-Ready LAN Switches
Series
(Ethernet ports only)
|
Notes
|
Device Supported
|
System Object ID from CISCO-PRODUCTS-MIB
|
Catalyst 500 Express Switch
|
|
500-24TT
|
1.3.6.1.4.1.9.1.724
|
500-24LC
|
1.3.6.1.4.1.9.1.725
|
500-24PC
|
1.3.6.1.4.1.9.1.726
|
500G-12TC
|
1.3.6.1.4.1.9.1.727
|
Catalyst 2900 XL
|
12.01.5.WE12 and higher
|
2908 XL
|
1.3.6.1.4.1.9.1.170
|
2916 MXL
|
1.3.6.1.4.1.9.1.171
|
| |
2924 XL
|
1.3.6.1.4.1.9.1.183
|
2924 CXL
|
1.3.6.1.4.1.9.1.184
|
2924 XLV
|
1.3.6.1.4.1.9.1.217
|
2924 CXLV
|
1.3.6.1.4.1.9.1.218
|
2912 XL
|
1.3.6.1.4.1.9.1.219
|
2924 MXL
|
1.3.6.1.4.1.9.1.220
|
2912 MXFL
|
1.3.6.1.4.1.9.1.221
|
2900
|
1.3.6.1.4.1.9.5.12
|
2926
|
1.3.6.1.4.1.9.5.35
|
2948 G
|
1.3.6.1.4.1.9.5.42
|
Catalyst 2940
|
Cisco IOS 12.1(22)EA1
|
2940-8TT-S
|
1.3.6.1.4.1.9.1.540
|
2940-8TF-S
|
1.3.6.1.4.1.9.1.542
|
Catalyst 2948
|
CatOS
|
2948G-GE-TX
|
1.3.6.1.4.1.9.5.62
|
Catalyst 2950
|
12.1.9.EA1 and higher
|
2950-12
|
1.3.6.1.4.1.9.1.323
|
2950-24
|
1.3.6.1.4.1.9.1.324
|
2950-24SX
|
1.3.6.1.4.1.9.1.480
|
2950-48SX
|
1.3.6.1.4.1.9.1.560
|
2950-48T
|
1.3.6.1.4.1.9.1.559
|
2950C-24
|
1.3.6.1.4.1.9.1.325
|
2950T-24
|
1.3.6.1.4.1.9.1.359
|
2950G-12
|
1.3.6.1.4.1.9.1.427
|
2950G-24
|
1.3.6.1.4.1.9.1.428
|
2950G-48
|
1.3.6.1.4.1.9.1.429
|
2950S-24
|
1.3.6.1.4.1.9.1.430
|
2950G-24DC
|
1.3.6.1.4.1.9.1.472
|
Catalyst 2960
|
Cisco IOS 12.2(25)SED
|
2960-24TC-L
|
1.3.6.1.4.1.9.1.694
|
2960-48TC-L
|
1.3.6.1.4.1.9.1.695
|
2960G-24TC-L
|
1.3.6.1.4.1.9.1.696
|
2960G-48TT-L
|
1.3.6.1.4.1.9.1.697
|
2960-24TT-L
|
1.3.6.1.4.1.9.1.716
|
2960-48TT-L
|
1.3.6.1.4.1.9.1.717
|
| |
2960-8TC-L
|
1.3.6.1.4.1.9.1.798
|
2960G-8TC-L
|
1.3.6.1.4.1.9.1.799
|
Catalyst 3500 XL
|
Cisco IPS 12.0(5)XU or higher
If you are using Catalyst 3500 clusters, you must assign an IP address to each Catalyst 3500 switch.
|
3508 GXL
|
1.3.6.1.4.1.9.1.246
|
3512 XL
|
1.3.6.1.4.1.9.1.247
|
3524 XL
|
1.3.6.1.4.1.9.1.248
|
3548 XL
|
1.3.6.1.4.1.9.1.278
|
3524 PWR XL
|
1.3.6.1.4.1.9.1.287
|
Catalyst 3550
|
12/1/6/EA1a or higher
|
3550-24
|
1.3.6.1.4.1.9.1.366
|
3550-24PWR
|
1.3.6.1.4.1.9.1.485
|
3550-48
|
1.3.6.1.4.1.9.1.367
|
3550-12T
|
1.3.6.1.4.1.9.1.368
|
3550-12G
|
1.3.6.1.4.1.9.1.431
|
3550-24DC
|
1.3.6.1.4.1.9.1.452
|
Catalyst 3560
|
Cisco IOS 12.2(20)SE or higher
|
3560-24PS
|
1.2.6.1.4.1.9.1.563
|
3560-48PS
|
1.2.6.1.4.1.9.1.564
|
3560-24TS-S/-E
|
1.2.6.1.4.1.9.1.633
|
3560-48TS-S/-E
|
1.2.6.1.4.1.9.1.615
|
3560G-24TS-S/-E
|
1.2.6.1.4.1.9.1.634
|
3560G-48TS-S/-E
|
1.2.6.1.4.1.9.1.617
|
3560G-24PS-S/-E
|
1.2.6.1.4.1.9.1.614
|
3560G-48PS-S/-E
|
1.2.6.1.4.1.9.1.616
|
| |
3560-8PC-S
|
1.3.6.1.4.1.9.1.797
|
Catalyst 3560E
|
Cisco IOS Release 12.2(35)SE2 or higher
|
3560E-48TD-S
|
1.3.6.1.4.1.9.1.794
|
3560E-48TD-E
|
1.3.6.1.4.1.9.1.794
|
3560E-48PD-SF
|
1.3.6.1.4.1.9.1.796
|
3560E-48PD-S
|
1.3.6.1.4.1.9.1.796
|
3560E-48PD-EF
|
1.3.6.1.4.1.9.1.796
|
3560E-48PD-E
|
1.3.6.1.4.1.9.1.796
|
3560E-24TD-S
|
1.3.6.1.4.1.9.1.793
|
3560E-24TD-E
|
1.3.6.1.4.1.9.1.793
|
3560E-24PD-S
|
1.3.6.1.4.1.9.1.795
|
3560E-24PD-E
|
1.3.6.1.4.1.9.1.795
|
Catalyst 3750
|
Cisco IOS 12.2(20)SE or higher
|
3750-24
|
1.3.6.1.4.1.9.1.511
|
3750-24FS-S
|
1.3.6.1.4.1.9.1.656
|
3750-48
|
1.3.6.1.4.1.9.1.512
|
3750-24TS
|
1.3.6.1.4.1.9.1.513
|
3750-24T
|
1.3.6.1.4.1.9.1.514
|
37XX Stack
|
1.3.6.1.4.1.9.1.516
|
3750G-12Sfp
|
1.3.6.1.4.1.9.1.530
|
3750-48PS
|
1.3.6.1.4.1.9.1.535
|
3750-24PS
|
1.3.6.1.4.1.9.1.536
|
3750G-16TD
|
1.3.6.1.4.1.9.1.591
|
3750G-24PS
|
1.3.6.1.4.1.9.1.602
|
3750G-48PS
|
1.3.6.1.4.1.9.1.603
|
3750G-48TS
|
1.3.6.1.4.1.9.1.604
|
3750G-24TS1U
|
1.3.6.1.4.1.9.1.624
|
3750G-24TS1U/-EIU
|
1.3.6.1.4.1.9.1.624
|
Catalyst 3750E
|
Cisco IOS Release 12.2(35)SE2 or higher
|
3750E-48TD-S
|
1.3.6.1.4.1.9.1.790
|
3750E-48TD-E
|
1.3.6.1.4.1.9.1.790
|
3750E-48PD-SF
|
1.3.6.1.4.1.9.1.791
|
3750E-48PD-S
|
1.3.6.1.4.1.9.1.791
|
3750E-48PD-EF
|
1.3.6.1.4.1.9.1.791
|
3750E-48PD-E
|
1.3.6.1.4.1.9.1.791
|
3750E-24TD-S
|
1.3.6.1.4.1.9.1.789
|
3750E-24TD-E
|
1.3.6.1.4.1.9.1.789
|
3750E-24PD-S
|
1.3.6.1.4.1.9.1.792
|
3750E-24PD-E
|
1.3.6.1.4.1.9.1.792
|
Catalyst 3750ME
|
Cisco IOS 12.2(25)EY
|
3750-24TE-M
|
1.3.6.1.4.1.9.1.574
|
Catalyst 4000
|
Cisco IOS 12.1(13)EW
|
4000 C
|
1.3.6.1.4.1.9.1.448
|
4503
|
1.3.6.1.4.1.9.1.503
|
4506
|
1.3.6.1.4.1.9.1.502
|
4507
|
1.3.6.1.4.1.9.1.501
|
4510R
|
1.3.6.1.4.1.9.1.537
|
4948-S-S/-E
|
1.3.6.1.4.1.9.1.626
|
4948-10GE-S/-E
|
1.3.6.1.4.1.9.1.627
|
Catalyst 4000/4500
|
Catalyst OS 5.5 or higher
|
4003
|
1.3.6.1.4.1.9.5.40
|
4912 G
|
1.3.6.1.4.1.9.5.41
|
4006
|
1.3.6.1.4.1.9.5.46
|
4500
|
1.3.6.1.4.1.9.1.14
|
4503
|
1.3.6.1.4.1.9.5.58
|
4506
|
1.3.6.1.4.1.9.5.59
|
Catalyst 4900 Metro
|
|
ME-4924-10GE
|
1.3.6.1.4.1.9.1.706
|
Catalyst 4948
|
Cisco IOS 12.2(20)EWA
|
4948
|
1.3.6.1.4.1.9.1.626
|
4948-10GE
|
1.3.6.1.4.1.9.1.627
|
Catalyst 5000
|
Catalyst OS 6.x
|
5000
|
1.3.6.1.4.1.9.5.7
|
5002
|
1.3.6.1.4.1.9.5.29
|
Catalyst 5500
|
|
5500
|
1.3.6.1.4.1.9.5.17
|
5505
|
1.3.6.1.4.1.9.5.34
|
5509
|
1.3.6.1.4.1.9.5.36
|
Catalyst 6500
|
Catalyst OS
|
6503
|
1.3.6.1.4.1.9.5.56
|
6509 NEB-A chassis
|
1.3.6.1.4.1.9.5.61
|
Catalyst OS 5.5 or higher
If using an MSFC module, Cisco IOS 12.1(3a)XL
|
6006
|
1.3.6.1.4.1.9.5.38
|
6009
|
1.3.6.1.4.1.9.5.39
|
6509
|
1.3.6.1.4.1.9.5.44
|
6506
|
1.3.6.1.4.1.9.5.45
|
6509 SP
|
1.3.6.1.4.1.9.5.47
|
6513
|
1.3.6.1.4.1.9.5.50
|
Catalyst 6500
|
Cisco IOS
|
6503
|
1.3.6.1.4.1.9.1.449
|
6006
|
1.3.6.1.4.1.9.1.280
|
6009
|
1.3.6.1.4.1.9.1.281
|
6506
|
1.3.6.1.4.1.9.1.282
|
6509
|
1.3.6.1.4.1.9.1.283
|
6509 NEB-A chassis
|
1.3.6.1.4.1.9.1.534
|
6509 SP
|
1.3.6.1.4.1.9.1.310
|
6513
|
1.3.6.1.4.1.9.1.400
|
Cisco 2800 Integrated Services Routers
|
Cisco IOS 12.3(8)T4
|
Cisco 2811
Cisco 2821
Cisco 2851
|
1.3.6.1.4.1.9.1.576
|
1.3.6.1.4.1.9.1.577
|
1.3.6.1.4.1.9.1.578
|
Cisco 3725 Multiservice Access Router
|
Image version:
IOS 12.2(8)T5
|
|
1.3.6.1.4.1.9.1.414
|
Cisco 3745 Multiservice Access Router
|
Image version:
IOS 12.2(13)T
|
|
1.3.6.1.4.1.9.1.436
|
Cisco 3800 Integrated Services Routers
|
Cisco IOS
|
Cisco 3825
|
1.3.6.1.4.1.9.1.543
|
Cisco 3845
|
1.3.6.1.4.1.9.1.544
|
Cisco ER 2.0 supports the Cisco MCS Unified Communications Manager Appliance platforms shown in Table 5; Table 7 lists capacity for these platforms.
Note The number of ERLs that can be deployed is determined by the number of route patterns and translation patterns configurable in Cisco Unified Communications Manager.
Note Cisco ER does not support Cisco Integrated Communications System (ICS) 7750 servers.
Table 5 lists the supported Media Convergence Server (MCS) platforms.
Note You must upgrade servers with less than 2 GB memory or less than 72 GB hard disk drive space.
Table 5 Supported MCS Platforms
Cisco MCS Server
|
Equivalent OEM Server
|
CPU
|
MCS-7816-H3-IPC1
|
|
3.2 GHz
|
MCS-7816-I3-IPC1
|
|
3.2 GHz
|
MCS-7825H-2.2-EVV1
|
HP DL320-G2
|
2.26 GHz
|
MCS-7825H-3.0-IPC1
|
HP DL320-G2
|
3.06 GHz
|
MCS-7825H-3.0-IPC2
|
HP DL320-G2
|
3.06 GHz
|
MCS 7825I-3.0-IPC1
|
IBM x306
|
3.06 GHz
|
MCS-7825-H1-IPC1
|
HP DL320-G3
|
3.4 GHz
|
MCS-7825-I1-IPC1
|
IBM x306
|
3.4 GHz
|
MCS-7825-H2-IPC1
|
HP DL320-G4
|
2.8 GHz
|
MCS-7825-I2-IPC1
|
IBM x306m
|
2.8 GHz
|
MCS-7825-H2-IPC2
|
HP DL320-G4
|
3.4 GHz
|
MCS-7825-I2-IPC2
|
IBM x306m
|
3.4 GHz
|
MCS-7825-H3-IPC1
|
HP DL320-G5
|
2.13 GHz
|
MCS-7825-I3-IPC1
|
IBM x3250
|
2.13 GHz
|
MCS-7835H-2.4-EVV1
|
HP DL380-G3 (1 CPU)
|
2.4 GHz
|
MCS-7835I-2.4-EVV1
|
IBM x345 (1 CPU)
|
2.4 GHz
|
MCS-7835H-3.0-IPC1
|
HP DL380-G3 (1 CPU)
|
3.06 GHz
|
MCS-7835I-3.0-IPC1
|
IBM x345 (1 CPU)
|
3.06 GHz
|
MCS-7835-H1-IPC1
|
HP DL380-G4 (1 CPU)
|
3.4 GHz
|
MCS-7835-I1-IPC1
|
IBM x346 (1 CPU)
|
3.4 GHz
|
MCS-7835-H2-IPC1
|
HP DL380-G5 (1 CPU)
|
2.33 GHz
|
MCS-7835-I2-IPC1
|
IBM x3650 (1 CPU)
|
2.33 GHz
|
MCS-7845H-2.4-EVV1
|
HP DL380-G3 (2 CPUs)
|
2.4 GHz
|
MCS-7845H-3.0-IPC1
|
HP DL380-G3 (2 CPUs)
|
3.06 GHz
|
MCS-7845I-3.0-IPC1
|
IBM x345 (2 CPUs)
|
3.06 GHz
|
MCS-7845-H1-IPC1
|
HP DL380-G4 (2 CPUs)
|
3.4 GHz
|
MCS-7845-I1-IPC1
|
IBM x346 (2 CPUs)
|
3.4 GHz
|
MCS-7845-H2-IPC1
|
HP DL380-G5 (2 CPUs)
|
2.33 GHz
|
MCS-7845-I2-IPC1
|
IBM x3650 (2 CPUs)
|
2.33 GHz
|
Table 6 lists the supported Media Convergence Server (MCS) platforms for upgrades from Cisco ER 1.3 only. These servers are not supported for new installations.
Table 6 Supported MCS Platforms for Upgrades from Cisco ER 1.3 Only
Cisco MCS Server
|
Equivalent OEM Server
|
CPU
|
MCS-7815I-3.0-IPC1
|
|
3.06 GHz
|
MCS-7815I-3.0-IPC2
|
|
3.06 GHz
|
MCS-7815-I1-IPC1
|
|
3.4 GHz
|
MCS-7815-I1-IPC2
|
|
3.4 GHz
|
MCS-7815-I1-IPC3
|
|
3.4 GHz
|
MCS-7815-I1-IPC4
|
|
3.4 GHz
|
MCS-7815-I2-IPC1
|
|
2.8 GHz
|
Table 7 gives capacity information for Cisco Emergency Responder, assuming one synthetic voice alert per emergency call.
Table 7 System Capacity
| |
Cisco 7816
|
Cisco 7825
|
Cisco 7835
|
Cisco 7845
|
Automatically tracked phones
|
6,000
|
12,000
|
20,000
|
30,000
|
Manually configured phones
|
1,000
|
2,500
|
5,000
|
10,000
|
Roaming phones (per Cisco Emergency Responder cluster)
|
600
|
1,200
|
2,000
|
3,000
|
Switches
|
200
|
500
|
1,000
|
2,000
|
Switch ports
|
12,000
|
30,000
|
60,000
|
120,000
|
ERLs
|
1,000
|
3,000
|
7,500
|
10,000
|
Related Documentation
Cisco Emergency Responder Documentation
Refer to the publications for Cisco ER 2.0. Navigate from the following documentation URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps842/tsd_products_support_series_home.html
Cisco Unified Communications Manager Documentation
Refer to the Cisco Unified Communications Manager Documentation Guide and other publications specific to your Cisco Unified Communications Manager release. Navigate from the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html
Cisco Unified Communications Manager Business Edition Documentation
Refer to the Cisco Unified Communications Manager Business Edition Documentation Guide and other publications that are specific to your Cisco Unified Communications Manager release. Navigate from the following URL:
http://www.cisco.com/en/US/products/ps7273/tsd_products_support_series_home.html
Installation Notes
This section describes upgrade information for Cisco ER 2.0(2) and includes these topics:
•Supported Upgrades
•Important Upgrade Notes
Supported Upgrades
You must upgrade to Cisco ER 1.3.x or later, including Cisco ER 2.0(1). You cannot upgrade directly to Cisco ER 2.0(2) from earlier versions of Cisco ER.
Important Upgrade Notes
Once you upgrade your system to Cisco ER 2.0(2), you can downgrade to Cisco ER 2.0(1) only.
Note It is not recommended to downgrade your system from Cisco ER 2.0(2) to Cisco ER 2.0(1) because of known issues in Cisco ER 2.0(1).
If you have a Cisco ER version earlier than 2.0(2) on your system, you cannot downgrade your system to earlier Cisco ER versions.
Caveats
This section includes these topics:
•Using Bug Toolkit
•Open Caveats
•Resolved Caveats
Using Bug Toolkit
Known problems (bugs) are graded according to severity level. These release notes contain descriptions of:
•All severity level 1 or 2 bugs.
•Significant severity level 3 bugs.
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•Internet connection
•Web browser
•Cisco.com user ID and password
To use the Software Bug Toolkit, follow these steps:
Procedure
Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2 Log in with your Cisco.com user ID and password.
Step 3 To look for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field, then click Go.
Open Caveats
Table 8 lists Severity 1, 2 and 3 defects that are open for Cisco ER 2.0(2).
For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.
Because defect status continually changes, be aware that Table 8 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit as described in the Using Bug Toolkit.
Resolved Caveats
Table 9 lists Severity 1, 2 and 3 defects that are resolved for Cisco ER 2.0(2).
For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.
Because defect status continually changes, be aware that Table 9 reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of resolved defects, access Bug Toolkit as described in the Using Bug Toolkit.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
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.
© 2007 Cisco Systems, Inc. All rights reserved.
Feedback
