|
|
Table Of Contents
Release Notes for Cisco ONS 15530
for Cisco IOS Release 12.1(12c)EVDetermining the Software Version
New Features in Release 12.1(12c)EV
New Features in Release 12.1(10)EV4
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco ONS 15530
for Cisco IOS Release 12.1(12c)EV
This document describes caveats for Cisco IOS Release 12.1(12c)EV for the Cisco ONS 15530.
Date: January 27, 2003
Text Part Number: OL-3630-01
Contents
This document includes the following information:
•
Caveats
•
•
Introduction
The Cisco ONS 15530 is a modular, scalable optical switching and aggregation platform designed to supplement the Cisco ONS 15540 ESP. With the Cisco ONS 15540 ESP, users can take advantage of the availability of dark fiber to build a common infrastructure that supports data, SAN (storage area network), and TDM (time-division multiplexing) traffic. For more information about DWDM technology and applications, refer to the Introduction to DWDM Technology publication and the Cisco ONS 15530 Planning Guide.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.1(10)EV4 and includes the following sections:
•
Memory Requirements
The DRAM memory configuration is 64 MB, which is the default for the Cisco ONS 15530.
Hardware Supported
Table 1 lists the hardware components supported on the Cisco ONS 15530 and the minimum software version required. See the "Determining the Software Version" section for information on determining your software version.
Determining the Software Version
Note
To determine the version of Cisco IOS software currently running on a Cisco ONS 15530 system, log in to the system and enter the show version EXEC command. The following sample output is from the show version command. The software version number is shown on the second line of the sample output.
Switch# show versionCisco Internetwork Operating System SoftwareIOS (tm) ONS-15530 Software (ONS15530-I-M), Version 12.1(10)EV4
<Information deleted>Upgrading the System Image
To ensure proper system functioning, follow the system image upgrading procedure described in the Cisco ONS 15530 Software Upgrade Guide.
Note
Caution
Feature Set Table
The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. Table 2 lists the Cisco IOS software feature sets available for the Cisco ONS 15530.
Table 2 Feature Sets Supported by the Cisco ONS 15530
Inband message channel
X
X
X
Gigabit Ethernet
X
X
X
Fast Ethernet
X
X
X
Ethernet
X
X
X
ATM OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16
X
X
X
X
X
X
POS3
X
X
X
IBM Sysplex coupling link
X
X
X
Fibre Channel (1 Gbps)
X
X
X
Fibre Channel (2 Gbps)
X
X
X
FDDI4
X
X
X
ESCON5 aggregation (2.5 Gbps)
X
X
X
FICON6 (800 Mbps)
X
X
X
Token ring
X
X
X
SNMP
X
X
X
CiscoView
X
X
X
Cisco Transport Manager
X
X
X
IP packets
X
X
X
OSCP7
X
X
X
APS8 channel protocol
X
X
X
Point-to-point
X
X
X
Hubbed ring
X
X
X
Meshed ring
X
X
X
IBM Sysplex ETR/CLO
X
X
X
1 SONET = Synchronous Optical Networking
2 SDH = Synchronous Digital Hierarchy
3 POS = Packet over SONET
4 FDDI = Fiber Distributed Data Interface
5 ESCON = Enterprise Systems Connection
6 FICON = Fiber Connection
7 OSCP = Optical Supervisory Channel Protocol
8 APS = Automatic Protection Switching
New and Changed Information
This section lists new features that appear in this and previous releases of Cisco IOS Release 12.1. The new features are sorted by release number.
New Features in Release 12.1(12c)EV
The following new hardware features are available for the Cisco ONS 15530 in Cisco IOS Release 12.1(12c)EV:
•
•
–
–
•
•
The following new software features are available for the Cisco ONS 15530 in Cisco IOS Release 12.1(12c)EV:
•
•
•
•
•
•
–
–
–
–
New Features in Release 12.1(10)EV4
No new features are available for the Cisco ONS 15530 in Cisco IOS Release 12.1(10)EV4.
Caveats
This section lists the caveats for the12.1(12c)EV release. Use Table 3 to determine the status of a particular caveat. In the table, "C" indicates a corrected caveat, and "O" indicates an open caveat.
This section describes the caveats in the Cisco ONS 15530.
Symptom: Unchecked buffer boundary in NTP.
Workaround: None.
Symptom: When the NME is connected to an auto-sensing switch/hub, going from 10 Mbs/half to 100 Mbs/half (or similarly 10 Mbs/full to 100 Mbs/full) on FastEthernet0 results in the link going down.
Workaround: Configure FastEthernet0 as duplex auto and speed auto.
Symptom: A change in optical threshold condition at a WB-VOA or PB-OE module power monitor may not be detected if the condition is temporary and does not last for more than a second.
Workaround: None
Symptom: When swapping the ESCON line card with the 10-G ITU trunk line card in a given slot, the following error message is seen four times:
%BPE-3-NOT_REGISTERED: Interface[EthernetDcc9/0/0] MAC is not registered.
Workaround: None.
Symptom: The CPU LED for alarms is not cleared even though the Optical Power Monitoring alarm gets cleared. There is no functionality problem. On a CPU switchover this alarm LED is cleared and gives the correct alarm status.
Workaround: OIR the card on which the alarm was generated.
Symptom: When both wavepatches are in an administrative down state, a low alarm does not appear on the standby wavepatch after a no shutdown is done on the wave interface.
Workaround: Do a shutdown and a no shutdown command sequence on the interface; the low alarm is then reported for this interface.
Symptom: Interface reports up/up even when there is no light source connected.
Workaround: Perform a shut and then a no shut on the interface.
Symptom: A transparent interface carrying Gigabit Ethernet traffic and configured with gigabit Fibre Channel encapsulation shows good quality signal on the show interfaces transparent command output and does not assert any ingress alarms. The wave interface assert loss of lock and loss of sync alarms.
Workaround: Remove and reinsert the transponder module to bring it to the correct state.
Symptom: LoF (loss of frame) alarms are not reasserted after a shutdown/no shutdown command sequence on both the transparent and wave interfaces on the transponder module.
Workaround: Disable and reenable monitoring on the transparent interface to reassert the alarms.
Symptom: The show facility-alarm command status does not report existing LoF/LoSync/LoLock alarms after
OIR/hw-mod power off/on.
Workaround: Disable and enable monitoring back will reassert existing alarms in the show facility-alarm status.
Symptom: A software compatibility problem causes the active CPU to reset the standby CPU.
Workaround: None.
Symptom: The show hardware command output displays information about the CPU that has been removed from the system.
Workaround: None.
Symptom: OSC wave and ethernetdcc interfaces come up with default traffic-shaping parameters. Since this is considered as default, on removing the configuration using the no form of the command, the parameter value should revert back to the default value, which is not being done.
Workaround: Reconfigure the traffic-shaping parameters.
Symptom: If a line card that was removed prior to switchover is inserted during switchover, the line card may not come up properly.
Workaround: Insert the line card after switchover is complete.
Symptom: The system crashes at is_optical_ifstatus_up.
Workaround: None.
Symptom: Performing a shutdown command on the active wavepatch of a nonsplitter card brings the waveethernetphy interface down and reports "Loss of Light" in the output of the show interface command, but the traffic continues to flow.
Workaround: If the intent is to stop traffic, do a shutdown on the waveethernetphy interface.
Symptom: Following a CPU crash and switchover, the show redundancy command shows "Not known", without any additional information.
Workaround: Enter show version from the standby CPU console to see the additional information.
Symptom: The getnext and getbulk commands do not function properly after a CPU switchover.
Workaround: None.
Symptom: APS traps mode mismatch takes 30 minutes for completion.
Workaround: None.
Symptom: Low alarm is not cleared on the wavepatch interface for the transponder.
Workaround: Perform a shutdown/no shutdown command sequence on the wavepatch where it is seen.
Symptom: CVRD, CRC or CDL HEC error counters are not incremented, but the CDL HEC SF condition is exceeded.
Workaround: None.
Symptom: When trying to modify cApsConfigSpan through SNMP set to an unsupported value, no error is reported.
Workaround: None.
Symptom: Administrative shutdown on a WaveEthernetPhy sub-interface does not take affect. It shows up in the display as "admin shut" but all the traffic flows through and the sub-interface is fully functional.
Workaround: None.
Symptom: Alarms are created on the wave interface by pulling out the cable.
Workaround: The shutdown command will clear all of the alarms on the wave interface.
Symptom: Spurious memory access is seen when issuing the show tech command on the standby CPU; the show align command shows an increase in the spurious memory errors after each show tech command is issued.
Workaround: None
Symptom: PTOPO configuration rows can be configured for nonexistent interfaces.
Workaround: None.
Symptom: The show connect intermediate command output does not display all the protection paths when a switch fabric cross connect is used.
Workaround: Display the information using the show connect command.
Symptom: Active CPU incorrectly detects a faulty switch fabric port, causing a switchover to the standby CPU.
Workaround: None.
Symptom: When copying or reading a file to or from Compact flash (disk0), a transient error with the following message may appear and read/write access to compact flash is terminated:
ATA_Status timeout waiting for <1/2/3>
Workaround: None.
Symptom: Defect-indication error message does not give information if the defect-indication bit was cleared or asserted for that interface.
Workaround: None.
Symptom: Some interfaces are not be available to the NMS station since the agent does not create them on OIR.
Workaround: Reload the box after removal/insertion of the cards.
Symptom: APS message channel configured for UDP/IP does not work over two IP hops. The UDP/IP packets get dropped at the end of the second hop.
Workaround: None.
Symptom: Loopback interfaces cannot be deleted from configuration.
Workaround: None.
Symptom: Switch fabric protection is not disabled if the nonactive CPU is in rommon. As a result if an RxFail is noticed on any fabric port, that fabric port will switch over its receive to the nonactive CPU.
Workaround: None.
Symptom: The redundancy reload shelf command on the Active CPU can cause a switchover if the peer CPU is in rommon.
Workaround: Use the reload command to reload the Active CPU, if the peer CPU is in rommon.
Symptom: Issuing getbulk command to retrieve PM parameters returns 0 row.
Workaround: None.
Symptom: The ciscoFlashPartitionFileCount returns an incorrect number of files on the flash card.
Workaround: None.
Symptom: ciscoFlashDeviceChangeTrap should be supported on ONS155xx platforms since it is a basic operation. Whenever a removable flash device is removed or inserted, this trap should be generated.
Workaround: None.
Symptom: When FLC (forward laser control) is disabled on all 10 esconphy ports and they are administratively shut down, packets are still being sent to the backplane.
Workaround: None.
Symptom: OPM feature does not work for nonsplitter transponders.
Workaround: None.
Symptom: Invalid mac-address or ip-address can be made via SNMP. No error check is done.
Workaround: Delete the entry through SNMP or with the topology neighbor disable command.
Symptom: Egress Loss of Signal alarm is not reasserted in the show facility alarm status output after the hardware module power is turned off and turned back on.
Workaround: None.
Symptom: The wave interface remains down when the signal quality is GOOD, after the hardware module power is turned off and turned back on.
Workaround: None.
Symptom: When wave interface is in SHUT mode, the corresponding active wavepatch interface is brought down and a low alarm is asserted.
Workaround: None.
Symptom: When IOS is rebooted on a system and a transient link failure condition occurs on 10 G DWDM Uplink cards, system may continously send the backward defect indication.
Workaround: None.
Symptom: Error messages appear when the 10-GE line card cross-connect to the switch fabric is removed.
Workaround: None.
Symptom: The wavepatche interfaces are stuck in the down state after using the show wave interface command with splitter APS after the trunk fiber has been cut.
Workaround: None.
Symptom: After a fiber cut, the OSC interface remains up with signal quality good.
Workaround: Use the shut/no shut command.
Symptom: The standby CPU can get stuck in trying to register control ports.
Workaround: Enter redundancy reload peer on the active CPU.
Symptom: In bidirectional APS, if both NEs have the same priority request, the master/slave determination fails, leading to both claiming the control and resulting in not sending a REVERSE-REQUEST.
Workaround: None.
Symptom: When a shutdown/noshutdown command sequence is done on a waveethernetphy interface that is in the UP state, the Signal Condition shows Loss of Lock.
Workaround: None.
Symptom: In bidirectional line card protection, if the APS group is associated with working cross connect invalid and protection cross connect 'active', APS erroneously sets the aps channel request on working to WAIT-TO-RESTORE. This does not recover even when the working cross connect is made dormant by the connection manager. As a result both NEs are pegged to protection until an event (that has higher priority than WTR) is triggered.
Workaround: None.
Symptom: Splitter APS protection comes up as active on bootup.
Workaround: None.
Symptom: Dynamic discovery of topology via CDP on the tengigethernetphy interface is not configurable.
Workaround: None.
Symptom: In a preconfigured APS group (for the case when the interfaces do not exist), if the group is configured for revertive mode, it cannot be enabled.
Workaround: None.
Symptom: The CPU crashes after midnight with optical performance monitoring on when an interface capable of performance monitoring is shut down before 00-00hrs and unshut after midnight.
Workaround: None.
Symptom: In unidirectional revertive APS, after OIR removal is followed by OIR insertion of working and protection elements on both NEs, the active signal may be received from theprotection line instead of the working line.
Workaround: Do a manual or force switch to working line.
Symptom: SEF errors are repeatedly asserted on the console and are not soaked.
Workaround: None.
Symptom: When an interface is shut down administratively, the show aps detail command shows the channel request as sf-lp; however, a get on the object cApsChanStatusCurrent does not reflect sf-lp in the corresponding bits.
Workaround: None.
Symptom: Connection to a different subinterface on the same 10-G card is accepted, but crossconnection fails in the switch fabric.
Workaround: None.
Symptom: The MTU setting on the 10-GE line card interface is not displayed in the show interface command output. Transmit side is reporting oversize frames.
Workaround: None.
Symptom: APS group is displayed as "not associated" in show aps detail command output.
Workaround: Do a shutdown/no shutdown command sequence to either or both interfaces in the APS group. This causes a state change of the interfaces. You can also do a disable/enable to the APS group.
Symptom: Y-cable transponder protection does not come up as active after removing lockout.
Workaround: Do a disable/enable to the APS group.
Symptom: With linecard protection configured, the switch fabric on both the active CPU and the standby CPU are out of sync.
Workaround: Insert all the cards and perform a no connect command and then connect command.
Symptom: CDR loss of lock is not reported after Sysplex CLO/ETR encapsulation on a transparent interface.
Workaround: Perform a shutdown/no shutdown command sequence on the interface to correct the CDR loss of lock reporting.
Symptom: Tx CRC and CDL-HEC error counters do not show the proper values in the show interface command output for the 10-GE interface.
Workaround: None.
Symptom: Wave interfaces see a continuous flap when shutting the wavepatch on a non-splitter card.
Workaround: None.
Symptom: Wavepatch configurations are retained when swapping a 10-GE, 2.5-Gbps ITU trunk, or transponder card.
Workaround: Find out the card type and reuse the wavepatch id by cleaning up the config.
Symptom: Loss of connectivity via the ethernetdcc interface occurs when splitter protection is configured and the waveethernetphy interface is shut down while protection on the wavepatch is active and the working wavepatch is down.
Workaround: Do not shut down the waveethernetphy interface while the working wavepatch is down.
Symptom: PSM is incorrectly recognized as mux/demux card with IOS images that do not have support for the PSM.
Workaround: Upgrade software to 12.1(12c)EV.
Symptom: When lockout on working is removed with a signal failure on working, the splitter switches back and forth between protection and working on 2.5-Gbps and 10-Gbps splitter protected cards.
Workaround: None.
Symptom: While performing an OIR of a protection card in a y-cacle configuration, the local and remote working port is flooded with CRC errors.
Workaround: Disconnect the standby branch of the y-cable during standby line card or SFP insertion.
Symptom: 10-Gbps ITU trunk line cards fail during power-on diagnostics at Quadphy loopback test (qphy-fabric-lb).
Workaround: None.
Symptom: Traffic loss of 30-45 sec might occur when a y-cable APS configuration with protection switchover is used with the Catalyst 6000 family.
Workaround: Disable auto-negotiation and enable debounce timer with 100-ms delay on Catalyst 6000 family using the set port debounce mod/port enable command sequence.
Symptom: Update alarms and add new alarms for new cards.
Workaround: None.
Symptom: Controller type for the backplane is not displayed in the show hardware detail command output.
Workaround: None.
Symptom: The show optical filter command output shows invalid information regarding the interface wavelength for filters.
Workaround: None.
Symptom: The system crashes when WB-VOA and WB-PE modules are removed.
•
Symptom: Transmit failure is cleared before APS is notified of failure and does not take correct action.
Workaround: Shut and unshut the interface.
Symptom: Disconnecting a 10-port ESCON or 8-port FC/GE aggregation card from a 2.5-Gbps ITU trunk card can cause two ports to have the same CDL flow identifier.
Workaround: Avoid assigning same CDL flow identifier to the ports in the portgroup.
Symptom: The gt-interrupt and interrupt0 tests on the CPU fail.
Workaround: None.
Symptom: Because of the inability to synchronize the standby CPU switch module (with latest IOS image) has lower capabilities than the active processor (older EV4 image). The following alarm appears:
%CPU_REDUN-3-CAPABILITIES: Alarm: ASSERT, MINOR, PSC card 5, Standby with lower capabilities.Workaround: None.
Symptom: The WB-VOA functional image version is different in the show hardware and show controllers command output.
Workaround: None.
Symptom: On a splitter APS switchover based on a CVRD SF condition, the SF threshold exceeded count is not incremented. There is also no log or event on the console that differentiates between switches overdue to CVRD SF or loss-of-lock.
Workaround: None.
Symptom: High alarm and low alarm status not cleared for WB-VOA or PB-OE modules when optical power is in a high warning or low warning state.
Workaround: None.
Symptom: Card access failure is seen when a new line card is inserted, but no alarm is reported to the network management station.
Workaround: None.
Symptom: Removing the configured threshold for CDL and CRC removes the template (and default values) resulting in CDL and CRC errors.
Workaround: Apply a threshold group for CRC/CDL-HEC from CLI and remove it.
Symptom: When removing a 2.5-Gpbs ITU Trunk card from the shelf, the following error message may appear:
%LC_2P5G-3-INTERNAL_CRITICAL: physubcard/idprom NULL in city_island_get_laser_frequency
Workaround: None.
Symptom: When WaveEthernetPhy interface on a 2.5-Gbps ITU trunk card with splitter APS configured, loss-of-lock and loss-of-lync alarms are reported in the output of the show facility-alarm status command.
Workaround: None.
Symptom: When ESCON data traffic is mixed with Gigabit Ethernet traffic cross connected to same 10-Gbps ITU trunk cards, the ESCON traffic will experience errors. Ports on ESCON Director might not even come up.
Workaround: Assign all 10 ports on ESCON aggregation card with valid flow identifiers.
Symptom: The tx-buffer size command on the portgroup interface on the ESCON aggregation card. This command has to be moved to the esconphy interfaces.
Workaround: Configure the command from the portgroup interface.
on the ESCON card.
Symptom: OFC (Open Fiber Control) is not supported with Fibre Channel on the 8-port FC/GE aggregation card. The link may not initialize if an 8-port FC/GE aggregation card is used with older Fibre Channel equipment which employ OFC laser safety mechanisms.
Workaround: None.
Limitations and Restrictions
This section provides limitations and restrictions for Cisco ONS 15530 hardware and software.
Transponder Modules
This section contains limitiations and restrictions that apply to transponder modules.
•
Data errors or link-down conditions for 2-Gbps Fibre Channel might occur when used with certain client laser sources. Transmitters in some client GBIC and SFP transceiver units might send large overshoots in optical power with signal bit transitions, causing momentary overload conditions on the transponder client side receiver. The average transmitted power level from the GBIC does not violate the overload specification of the transponder client side receiver, so a power meter does not detect the overload.
The workaround is to attenuate the signal from the client equipment to a recommended level of -12 dBm when transmitting 2-Gbps Fibre Channel services.
CPU Switch Modules
This section contains limitations and restrictions that apply to transponder modules.
•
Note
Related Documentation
Refer to the following documents for more information about the Cisco ONS 15530:
•
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation
Cisco provides several ways to obtain documentation, 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 on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
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:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•
•
•
•
Cisco TAC Website
You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Posted: Tue Jun 8 12:13:57 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
