Cisco
CallManager Release 4.1(2)
Service Release 1: Release Notes Version
2
February
10, 2005
These
Service Release (SR) release notes contain important information about
installation procedures and resolved caveats for Cisco CallManager release
4.1(2)SR1.
For
a list of the resolved caveats for Cisco CallManager release 4.1(2)SR1, see the
“Resolved Caveats for Cisco CallManager - Release 4.1(2)SR1
section. Updates for these release
notes occur with every Cisco CallManager SR release.
Note: Before you install this Cisco CallManager Service Release, Cisco recommends that you review the “Important Notes” section for information about issues that may affect your system.
These
release notes include the topics that are outlined in the Table of
Contents.
Determining
the Software Version. 3
Compatibility
Matrix and Supported Upgrades 3
Locale
Installer for Cisco CallManager 4
Resolved
Caveats for Cisco CallManager - Release 4.1(2)SR1. 9
Cisco Product Security Overview. 17
Reporting
Security Problems in Cisco Products 17
Obtaining Technical Assistance. 18
Cisco
Technical Support Website. 18
Submitting
a Service Request 18
Definitions
of Service Request Severity. 19
Obtaining Additional Publications and
Information. 19
This
document provides installation instructions for Cisco CallManager
4.1(2)SR1. It also contains a list
of Cisco CallManager 4.1(2)SR1 issues that have been resolved by this Service
Release.
Note: Please review all sections in this document pertaining to installation before you install this Service Release. Failure to install this Service Release as described may result in inconsistent Cisco CallManager behavior.
Make
sure that you install and configure this release of Cisco CallManager on a
Cisco Media Convergence Server (MCS).
You
may install Cisco CallManager on a Cisco-approved HP server configuration or on
a Cisco-approved IBM server configuration.
Note: You must follow the exact configuration for the installation to complete successfully.
You
can access the correct Cisco-approved server configuration for IBM or HP servers
at the following URL: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html.
You
can determine the version of Cisco CallManager software that is running on your
server by accessing Cisco CallManager Administration and then clicking
Details.
The
following information displays:
You
can find the minimum versions with which Cisco CallManager release 4.1(2) has
been tested and which previous release of Cisco CallManager has upgrade support
by accessing the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm.
Note:
Be aware that the release of Cisco IP
telephony products does not always coincide with Cisco CallManager releases. If
a product is not compatible with
Cisco CallManager, you must wait until a
compatible version of that product becomes available before you can upgrade to
this release of Cisco CallManager.
For the most current compatibility combinations and defects, refer to the
documentation that is distributed with the Cisco IP telephony
products.
For optimal performance, be sure
that you use the Cisco IP Telephony Locale Installer that is specific to the
version of Cisco CallManager that you use.
Be aware that all phrases may not display in the desired locale when you
upgrade to a different version of Cisco CallManager. Refer to the readme file that is posted
with the Cisco IP Telephony Locale Installer software on the following URL for
the complete list of supported languages:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/locinst/index.htm.
Each release of Cisco CallManager
may support a different number of locales. The full suite of Locale Installers
that work with each applicable version of Cisco CallManager can be found on
http://www.cisco.com about 8-10 weeks after the
English version becomes available. You can download the Locale Installers for
all languages that are supported with Cisco CallManager from the following
location: http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/locale-installer.shtml.
Note: When using locales, Cisco recommends that you wait until the locale installer that specifically supports the version of Cisco CallManager that you use becomes available before you upgrade your system. Because some incompatibilities may exist between releases, be sure to only use the locale installer that specifically supports your version of Cisco CallManager.
For
additional information about Cisco CallManager, refer to the following
documentation:
Release
Notes for Cisco CallManager Release 4.1(2)
– Refer to the following URL for
maintenance release notes that are relevant to this release of Cisco
CallManager:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/rel_note/412cmrn.htm
Cisco
CallManager Document Guide
– Refer to the following URL for a list of documents that are related to Cisco
CallManager release 4.1(2):
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/doc_gd/dg412.htm
To
access the documentation suite for voice products, navigate to the following
URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/.
To
access the latest software upgrades and related documentation for
Cisco
CallManager, navigate to the following URL and then choose the applicable
version: http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.
This
Service Release is a cumulative update that incorporates all of the fixes and
changes from Cisco CallManager 4.1(2)ES10, along with additional changes that
are specific to this Service Release.
Note: If you are running Cisco CallManager 4.1(2)ES11 or higher, you must uninstall the Engineering Special (ES) before you can install this Service Release. (You may lose fixes that were added after ES10 and not included in the SR.)
Note: Service Releases do not impact system compatibility unless specifically stated.
Cisco
provides the following guidance to help you successfully install and/or upgrade
Cisco CallManager software:
·
To minimize
call-processing interruptions during the upgrade process, register all devices
to servers that are running the same version of Cisco CallManager software.
Make sure that you register all devices to the backup
Cisco
CallManager server or to the primary Cisco CallManager server, but not to both the backup and primary
servers.
·
Upgrade all
servers to Cisco CallManager 4.1(2) and make sure that the servers are online
before you begin this SR installation; otherwise, pre-upgrade checks may fail or
return faulty information.
·
If you are
using Microsoft Windows OS version 2000.2.4SR5 or 2000.2.5 with McAfee Netshield
2000 or McAfee VirusScan Enterprise Edition, you may encounter authentication
problems with Cisco CallManager Administration or problems accessing some Cisco
CallManager Administration windows.
In either case, Cisco CallManager displays an “HTTP Error 500–12
Application Restarting” error message.
To resolve this problem, you must upgrade McAfee Netshield and McAfee
VirusScan to run VirusScan Engine version 4.2.60 or later. You can obtain the latest McAfee
VirusScan updates from the Network Associates website.
·
For optimum
performance, apply the most current OS upgrade and SR before you install the
Cisco CallManager SR. For more
information, refer to Cisco IP Telephony
Operating System, SQL Server, Security Updates at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/osbios.htm.
·
If you are
using Cisco CallManager Security Agent, you must DISABLE this software and then
restart your system before you proceed with this
installation.
·
Service
Releases contain firmware loads, however, Cisco recommends that you always
download the latest firmware load from the
·
All
nodes in the cluster run through a database replication check during the upgrade
process as an extra measure, even though the publisher's database replication
check should catch any replication errors clusterwide.
If you encounter a
warning message on any node during this check, make sure that you stop the
installation process and check the log files. Follow the recommendations listed
below if the log file displays any of the following
messages:
·
“All
agent-implementing jobs are waiting to start”
·
“At
least one agent-implementing job is attempting to execute after a previous
failure“
·
“At
least one agent-implementing job has failed to execute successfully“
Note: To verify that the installation completed successfully, follow the instructions in Step 4 in the Installation Instructions section.
Recommendations:
·
Make sure that
you are using the correct version of Cisco CallManager software. Cisco supports upgrades from any Cisco
CallManager 4.1(2) release up to 4.1(2)ES10. This SR is based on Engineering Special
10.
·
Be sure to
DISABLE any antivirus and intrusion detection software, along with any other
security services; then, restart your server before you run the upgrade
process. You must manually
re-enable these services after the installation is complete.
·
Make
sure that you disable the following Cisco-verified platform agents and
applications; these products may interfere with the Cisco CallManager
installation:
Ø
Server
management agents
Ø
VOIP
monitoring/performance monitoring
Ø
Remote
access/remote management agents
Note:
It
is very important to disable platform agents and services, such as NetIQ and
Prognosis performance monitoring, antivirus (Cisco-verified McAfee services) and
intrusion detection software, remote management services, and any other
monitoring applications that automatically restart services; this action ensures
that your system does not encounter issues that are associated with these
services.
The
following procedure provides details about how to install Cisco CallManager
4.1(2)SR1.
Note:
Cisco recommends that you apply this Service
Release during a maintenance window.
·
This
Service Release upgrades the affected services and files and then it restarts
the server when the upgrade has completed successfully.
·
Apply
this patch to all of your Cisco CallManager servers, beginning with the
publisher server and TFTP server.
Perform the following
procedure to install Cisco CallManager 4.1(2)SR1:
1.
From
the
Make a note of the location
where you saved the file.
2.
Double-click the ciscocm.4-1-2-sr1.exe executable file
to begin the installation.
3.
Click
Next when the installation process
displays a message that asks if you want to install this
SR.
The remainder of the
installation process continues without any additional user input. The system
displays a message when the installation is complete.
4.
Verify
that the installation completed successfully by taking the following
actions:
a.
Click Yes when the system prompts you to view
the log file.
b.
Scroll down to the end
of the log file; if errors occurred during the installation, the errors section
at the bottom of the log file will be updated with a corresponding
severity.
5.
After
you have rebooted the server and completed the upgrade on all servers in the
cluster, go to Cisco CallManager Administration on the client machine, navigate
to the Application > Install
Plugins menu.
6.
Choose
the applicable plug-in, run the program from its current location, and follow
the installation instructions that the system displays.
Note:
This Service Release can take up to 20
minutes to complete the installation.
The
following procedure provides details about how to uninstall Cisco CallManager
4.1(2)SR1. (The SR uninstallation
process does not change the device defaults to the version that was installed
before the SR.)
Note: Uninstall the SR on all servers in the cluster in the same order in which you performed the installation.
Perform the following
procedure to uninstall Cisco CallManager 4.1(2)SR1:
1.
Navigate to Start > Settings > Control Panel >
Add/Remove Programs > Cisco CallManager 4.1(2)SR1
Uninstall.
A dialog box displays
to confirm that you want to uninstall this SR.
2.
Click
Next and then Yes to continue.
3.
Click
No at the next prompt.
A dialog box displays to confirm that you
want to remove the uninstall shortcut from Add/Remove
Programs.
4.
Verify
that the uninstallation process completed successfully by taking the following
actions:
a.
Click Yes when the system prompts you to view
the log file.
b.
Scroll down to the end
of the log file; if errors occurred during the installation, the errors section
at the bottom of the log file will be updated with a corresponding
severity.
5.
After
you have rebooted the server and completed the uninstall on all servers in the
cluster, you need
to revert to the prior version
of the plug-in after the uninstallation is complete, navigate to the Application > Install Plugins menu
from Cisco CallManager Administration.
6.
Choose
the applicable plug-in on the client machine, run the program from its current
location, and follow the uninstallation instructions that the system
displays.
The
system may create or edit the following log files during the installation or
uninstallation process:
o
c:\program
files\common files\cisco\logs\CCMPatch\Cisco CallManager 4.1(2)sr1 Installation
YYYY-MM-DD HH.mm.log (this file is also accessible by navigating to the Start
menu shortcut "Cisco Install Logs" under the CCMPatch folder)
o
c:\install\dbinstall\dbinstallXXX.txt
o
c:\program
files\common files\cisco\logs\sqlX.txt
o
c:\program
files\common files\cisco\logs\history.log
This
Service Release includes the following resolved
caveats:
|
CSCed60928:
ComponentVersions updated inconsistently for
CAR |
|
CSCee16325:
ACClients cannot login |
|
CSCee46987:
Callback does not monitor operator console via hunt
group |
|
CSCef09178:
AC should retain orig. called info. in calldetails display
string |
|
CSCef10129:
acconfig.bat is not saving queue params for multiple pilot
points |
|
CSCef16104:
when using JRE, blank window pops up when updating DN
page |
|
CSCef33842:
SDL folder for Trace is not created
automatically |
|
CSCef37349:
TCD Causing High Memory Utilization |
|
CSCef64304:
Locations bandwidth leak |
|
CSCef64897:
Callback fails over QSIG ICT due to CbCancel APDU with
broadcast |
|
CSCef73178:
VM: Intermittentremote scripting error VM PORT
wizrad |
|
CSCef74122:
HuntGroup not working with Personal preference when Reroute
enable |
|
CSCef74520:
Errors thrown on updating GW Config when CMgroup not
selected |
|
CSCef77425:
Callback screens not displayed for line key in partition on
sidecar |
|
CSCef83048:
Missing jtapi event when caller dropped after completed consult
xfer |
|
CSCef87142:
failed to unhold active call causes aborted
call |
|
CSCef92845:
H323 GW to H323 GW call: MXTimeout may pop when switching to
T.38 |
|
CSCef96835:
Callback in conn-ret is not canceled when EM user logs
out |
|
CSCef98079:
7970 calls to the pstn over BRI request unrest. digital
bearer |
|
CSCeg03604:
AC client takes long time to login |
|
CSCeg04186:
4.1(2) install adds device type for 7961 phone |
|
CSCeg18293:
7971 phone icon missing from CM Admin page |
|
CSCeg29662:
7971 device type and load need to be added to CM
releases |
|
CSCeg31641:
Not to dump encryption key info into trace
file |
|
CSCeg34270:
Device Protocol Options (T1-CAS/PRI) needed for
VIC2-xMFT-T1 |
|
CSCeg34621:
CCM opens Data channel as PassThru always |
|
CSCeg35771:
Maximum Number of Registered Devices needs to be
Documented |
|
CSCeg36225_2:
CMIs srvc registration behavior change in 4.0(2a)SR1 sue to
CIA176 |
|
CSCeg37962:
No media from sccp ep in a conf, through SIP trunk to |
|
CSCeg39579:
Second TCS from H.323 Tandberg is not handled properly by
CCM |
|
CSCeg40693:
QSIG MWI Failing when Avaya Definity G3 is Message Centre
PINX |
|
CSCeg45808:
Callback to a 7971 fails to activate |
|
CSCeg50337:
MLA filter prevents WWW service to start if DBL is
Stopped |
|
CSCeg52925:
CSS for ForwardALL corruption during migration to
4.0(2a) |
|
CSCeg54135:
Exception thrown cause thread hangs |
|
CSCeg55857:
7970/7971 display instance file and IP Phone Rules xml files wrong
|
|
CSCeg56342:
CallReroute sends transformed calledNr versus
pretransformed |
|
CSCeg58745:
PI6 based features commit to CCM branches |
|
CSCeg58869:
Max Call and Max Hold Duration timers help text
incorrect |
|
CSCeg58897:
Backspace key does not delete asterisk when used with
FAC |
|
CSCeg62123:
DNA warning in Application logs when CCM is upgraded to
4.0(2a)SR1 |
|
CSCeg62706:
StartMultiMediaTrasmission PassThruPartyID not set
correctly |
|
CSCeg62733:
Unnecessary MediaCoordinator error messages in CCM
Traces |
|
CSCeg62988:
Not able to insert a MGCP Gateway |
|
CSCeg64434:
Potential memory corruption in QsigAsnTrace
processing |
|
CSCeg65779:
Error on phone page in DNA |
|
CSCeg66942:
7971 Device Devpak for CCM 4.0(2)sr1a has missing
GUI |
|
CSCeg75458:
AdminUtility may not show all nodes in a CM
cluster |
|
CSCeg78217:
CM terminates with unknown exception,
RaiseException |
|
CSCeg83684:
MaxNumof Reg Devices param should not list product names like
Vega |
|
CSCeg87145:
Location Bandwidth Leak With Hunt Lists and Line
Groups |
|
CSCeg88745:
Need to bump the SDL version number |
|
CSCin82213:
IPMA not working after network outage ( lan cable removed from
CCM) |
|
CSCuk55138:
1 way speech path call from CME FWD to operator transfer to ip
phone |
|
CSCuk55378:
CTI Manager may restart after rcving H323 audio call from Video
terminal |
|
CSCeb63141:
Negative value for 6608 counter Total Rx RTP Lost
Pkts |
|
CSCef79218:
6608T1 CAS HookFlash is detected in Call Disconnect
State |
|
CSCef79318:
6608T1 CAS Glare Recovery may not work
correctly |
|
CSCef80640:
configurable non-linear comfort noise attenuation for
6608 |
|
CSCef84762:
6608 does not send RSIP forced to CCM when a reset comes from
CCM |
|
CSCef94661: 6608: Support for
T1 CAS Guard time |
|
CSCeg00010:
6608 T1 cas gateway fails to clear line for unallocated
numbers |
|
CSCeg06661: 6608 Fax Relay
debugs in D00404 firmware need to be same as
D00403 |
|
CSCeg31788: 6608 inbound call
mistaken for hookflash |
7970G
|
CSCee92103:
7970 not put active call in focus after incoming call
disconnected |
Cisco
CallManager 4.1(2)SR1 includes the following file
versions:
|
Aupair.exe
4.1.2.10110 |
|
CallBackservice
3.3.2.3 |
|
ccm.exe
4.1.2.13110 |
|
CcmPerfMon.dll |
|
CcmServRtmtPlugin.exe
4.10.0002 |
|
CiscoAttendantConsoleClient.exe
1.4.1.1 |
|
CiscoMessagingInterface.exe
4.1.2.10010 |
|
CiscoJTAPIClient.exe
- 2.1(2.5) |
|
CiscoTSP.exe
- 4.1(1.2)ES01 |
|
CmiPerfMon.dll |
|
ctftp.exe
4.1.2.10010 |
|
CTIManager.exe
4.1.2.10110 |
|
CtiMgrPerfMon.dll |
|
DBConvert.dll
4.1.0.6 |
|
DBInstall.dll |
|
DBL.dll
4.1.2.10009 |
|
DBLR.dll
4.1.2.10004 |
|
DBLRT.DLL
4.1.2.10003 |
|
DNASetup.exe
3.0(SR1) |
|
DriverMonitor.exe
4.0.0.4 |
|
emservice.war |
|
Ipvmsapp.exe
4.0.0.15 |
|
IpVms.sys
4.0.0.19 |
|
ipvmsrend.ax |
|
JavaNcsClient.jar |
|
MA.war |
|
MediaAppPerfMon.dll |
|
MMFSpy.exe |
|
QRTFileMgr.exe
4.1.2.10010 |
|
RisDC.exe
4.0.0.3 |
|
RISX.dll
4.1.2.10003 |
|
RISPort.dll
4.0.0.1 |
|
SOAPISAPI.dll
4.1.0.6 |
|
TcdSrvPerfMon.dll |
|
TftpPerfMon.dll |
|
UMAccessDll.dll |
Service
Releases contain firmware loads, however, Cisco recommends that you always
download the latest firmware load from the
Cisco
CallManager 4.1(2)SR1 includes the following firmware
versions:
|
4.1(2)Devpack
09 |
|
Digital
Access WS-X6608 Load - D00404000017 |
|
IP
Phone 7902G - CP7902050000SCCP041007A |
|
IP
Phone 7905G - CP7905050000SCCP041115A |
|
IP
Phone 7912G - CP7912050000SCCP041115A |
|
IP
Phone 7940G/7960G - No new default set in this
SR |
|
IP
Phone 7970G/7971G -
TERM70.6-0-2SR1-0s |
Cisco
documentation and additional literature are available on Cisco.com. Cisco also
provides several ways to obtain technical assistance and other technical
resources. These sections explain how to obtain technical information from Cisco
Systems.
Cisco.com
You
can access the most current Cisco documentation at this
URL:
http://www.cisco.com/univercd/home/home.htm
You
can access the Cisco website at this URL:
You
can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Cisco
documentation and additional literature are available in a Documentation DVD
package, which may have shipped with your product. The Documentation DVD is
updated regularly and may be more current than printed documentation. The
Documentation DVD package is available as a single unit.
Registered Cisco.com users (Cisco
direct customers) can order a Cisco Documentation DVD (product number
DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco
Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco
Marketplace:
http://www.cisco.com/go/marketplace/
You
can find instructions for ordering documentation at this
URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You
can order Cisco documentation in these ways:
You
can send comments about technical documentation to [email protected].
You
can submit comments by using the response card (if present) behind the front
cover of your document or by writing to the following
address:
Cisco
Systems
Attn:
Customer Document Ordering
We
appreciate your comments.
Cisco
provides a free online Security Vulnerability Policy portal at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From
this site, you can perform these tasks:
A
current list of security advisories and notices for Cisco products is available
at this URL: http://www.cisco.com/go/psirt
If
you prefer to see advisories and notices as they are updated in real time, you
can access a Product Security Incident Response Team Really Simple Syndication
(PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Cisco is
committed to delivering secure products. We test our products internally before
we release them, and we strive to correct all vulnerabilities quickly. If you
think that you might have identified a vulnerability in a Cisco product, contact
PSIRT:
We
encourage you to use Pretty Good Privacy (PGP) or a compatible product to
encrypt any sensitive information that you send to Cisco. PSIRT can work from
encrypted information that is compatible with PGP versions 2.x through 8.x. Never use a revoked or an expired
encryption key. The correct public key to use in your correspondence with PSIRT
is the one that has the most recent creation date in this public key server
list:
http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on
In an
emergency, you can also reach PSIRT by telephone:
For
all customers, partners, resellers, and distributors who hold valid Cisco
service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning
technical assistance. The Cisco Technical Support Website on Cisco.com features
extensive online support resources. In addition, Cisco Technical Assistance
Center (TAC) engineers provide telephone support. If you do not hold a valid
Cisco service contract, contact your reseller.
The
Cisco Technical Support Website provides online documents and tools for
troubleshooting and resolving technical issues with Cisco products and
technologies. The website is available 24 hours a day, 365 days a year, at this
URL:
http://www.cisco.com/techsupport
Access
to all tools on the Cisco Technical Support Website requires a Cisco.com user ID
and password. If you have a valid service contract but do not have a user ID or
password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note:
Use
the Cisco Product Identification (CPI) tool to locate your product serial number
before submitting a web or phone request for service. You can access the CPI
tool from the Cisco Technical Support Website by clicking the Tools &
Resources link under Documentation & Tools. Choose Cisco Product
Identification Tool from the Alphabetical Index drop-down list, or click the
Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool
offers three search options: by product ID or model name; by tree view; or for
certain products, by copying and pasting show command output. Search results
show an illustration of your product with the serial number label location
highlighted. Locate the serial number label on your product and record the
information before placing a service call.
Using
the online TAC Service Request Tool is the fastest way to open S3 and S4 service
requests. (S3 and S4 service requests are those in which your network is
minimally impaired or for which you require product information.) After you
describe your situation, the TAC Service Request Tool provides recommended
solutions. If your issue is not resolved using the recommended resources, your
service request is assigned to a Cisco TAC engineer. The TAC Service Request
Tool is located at this URL: http://www.cisco.com/techsupport/servicerequest
For
S1 or S2 service requests or if you do not have Internet access, contact the
Cisco TAC by telephone. (S1 or S2 service requests are those in which your
production network is down or severely degraded.) Cisco TAC engineers are
assigned immediately to S1 and S2 service requests to help keep your business
operations running smoothly.
To
open a service request by telephone, use one of the following
numbers:
Asia-Pacific:
+61 2 8446 7411 (
EMEA:
+32 2 704 55 55
For a
complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
To
ensure that all service requests are reported in a standard format, Cisco has
established severity definitions.
Severity
1 (S1)—Your network is “down,” or there is a critical impact to your business
operations. You and Cisco will commit all necessary resources around the clock
to resolve the situation.
Severity
2 (S2)—Operation of an existing network is severely degraded, or significant
aspects of your business operation are negatively affected by inadequate
performance of Cisco products. You and Cisco will commit full-time resources
during normal business hours to resolve the situation.
Severity
3 (S3)—Operational performance of your network is impaired, but most business
operations remain functional. You and Cisco will commit resources during normal
business hours to restore service to satisfactory levels.
Severity
4 (S4)—You require information or assistance with Cisco product capabilities,
installation, or configuration. There is little or no effect on your business
operations.
Information
about Cisco products, technologies, and network solutions is available from
various online and printed sources.
·
Cisco
Marketplace provides a variety of Cisco books, reference guides, and logo
merchandise. Visit Cisco Marketplace, the company store, at this URL: http://www.cisco.com/go/marketplace/
·
Cisco
Press
publishes a wide range of general networking, training and certification titles.
Both new and experienced users will benefit from these publications. For current
Cisco Press titles and other information, go to Cisco Press at this URL: http://www.ciscopress.com/
·
Packet
magazine is the Cisco Systems technical user magazine for maximizing Internet
and networking investments. Each quarter, Packet delivers coverage of the latest
industry trends, technology breakthroughs, and Cisco products and solutions, as
well as network deployment and troubleshooting tips, configuration examples,
customer case studies, certification and training information, and links to
scores of in-depth online resources. You can access Packet magazine at this
URL: http://www.cisco.com/packet
·
iQ
Magazine is
the quarterly publication from Cisco Systems designed to help growing companies
learn how they can use technology to increase revenue, streamline their
business, and expand services. The publication identifies the challenges facing
these companies and the technologies to help solve them, using real-world case
studies and business strategies to help readers make sound technology investment
decisions. You can access iQ Magazine at this URL: http://www.cisco.com/go/iqmagazine
·
Internet
Protocol
Journal is a quarterly journal published by Cisco Systems for engineering
professionals involved in designing, developing, and operating public and
private internets and intranets. You can access the Internet Protocol Journal at
this URL: http://www.cisco.com/ipj
·
World-class
networking training is available from Cisco. You can view current offerings at
this URL: http://www.cisco.com/en/US/learning/index.html
This
document is to be used in conjunction with the documents listed in the Related
Documentation
section.
CCSP, the
Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of
Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick
Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet,
ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco
Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco
Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet
Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step,
FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ
Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys,
MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar,
Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare,
SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way
to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks
of Cisco Systems, Inc. and/or its affiliates in the United States and certain
other countries.
All other
trademarks mentioned in this document or Website are the property of their
respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (0501R)
Copyright ©
2005 Cisco Systems, Inc. All rights reserved.