Cisco Cisco IPICS Release 1.0 Important Safety Instructions

Page of 120
   
Open Caveats for Cisco IPICS - Release 1.0(2)
62
Release Notes for Cisco IPICS Release 1.0(2)
OL-9281-01
Step 7
A window displays the bug group(s) that you have saved. From this window, you 
can click a bug group name to see the bugs and the saved searches; you can also 
edit the search criteria.
Open Caveats for Cisco IPICS - Release 1.0(2)
 describes possible unexpected behaviors by Cisco IPICS release 1.0(2), 
sorted by component.
Tip
For more information about an individual defect, click the associated Identifier in 
 to access the online record for that defect, including workarounds.
Understanding the To-be-fixed and the Integrated-releases Fields in the Online Defect 
Record
When you open the online record for a defect, you may see data in the 
“To-be-fixed” or “Integrated-releases” fields. The information that displays in 
these fields identifies the list of Cisco IPICS interim versions in which the defect 
was fixed. These interim versions then get integrated into Cisco IPICS releases.
Some versions include identification for Maintenance Releases (MR), Service 
Releases (SR) and/or Engineering Specials (ES). The following examples show 
the version number and its mapping to MR, SR, and ES releases: 
1.0(1.1) = Cisco IPICS release 1.0 MR1 SR1
1.0(3.2.1) = Cisco IPICS release 1.0 MR3 SR2 ES1
1.2(2.0.201) = Cisco IPICS release 1.2 MR2 ES1 (in this example, no SR was 
released between MR2 and ES1)
The following examples show how you can decode the maintenance release 
interim version information. These examples show you the format of the interim 
version along with the corresponding Cisco IPICS release that includes that 
interim version. You can use these examples as guidance to better understand the 
presentation of information in these fields.
1.0(1.008) = Cisco IPICS release 1.0(2)
1.1(0.012) = Cisco IPICS release 1.1(1)