Table Of Contents
Cisco Transport Manager Release 7.0 ML Provisioning Methodology
Point-to-Point Base Card Configuration
PoS, Ethernet, and SPR Port Provisioning
Flow Control (Send) Provisioning
Configuring Best-Effort Class Map
Configuring Advanced Class Map
Bandwidth Data Service Provisioning
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Transport Manager Release 7.0 ML Provisioning Methodology
This document describes the methodology that Cisco Transport Manager (CTM) Release 7.0 uses to provision ML-series cards.
Contents
This document describes the following topics:
•
PoS, Ethernet, and SPR Port Provisioning
•
•
Introduction
CTM is an advanced management system that provides functionality at the element and network management levels for Cisco network elements (NEs) and devices. CTM supports fault, configuration, performance, and security management functional areas. CTM also serves as a foundation for integration into a larger overall operations support system (OSS) environment by providing northbound gateway interfaces to higher layer management systems.
CTM supports data service provisioning over the ML-series cards. Data service provisioning consists of provisioning the Layer 2 topology using optical circuits, and then provisioning the Layer 2 service on top of the Layer 2 topology.
Alarm notification and performance monitoring features on the data cards (ML-series cards) are SNMP based. To allow CTM to support alarm and event notification and performance monitoring on data cards, the SNMP trap forwarding mechanism must be set up on each node of the data card.
The scope of this application note is to provide the set of Cisco IOS commands issued by CTM during the Layer 2 topology and Layer 2 service provisioning. The syntax used for the commands needs to be respected for services provisioned directly using Cisco IOS so that the provisioned services are recognized by CTM.
SNMP Trap Destination Setup
For the cards to have full CTM support, the SNMP trap destination must be set up for each node where there is a data card inserted:
•
•
•
•
Figure 1 NE Explorer Window—SNMP Trap Destination Setup
Table 1 details possible SNMP configurations.
When performing SNMP trap destination setup:
1.
2.
3.
4.
Overview
A Layer 2 topology can be a point-to-point optical circuit; Resilient Packet Ring (RPR) consisting of a chain of optical circuits; or hub and spoke, consisting of multiple optical circuits connected in a hub-and-spoke fashion. Hub-and-spoke topologies are supported as multiple point-to-point topologies.
For a point-to-point topology, the following card combinations are supported:
•
•
•
•
•
When deployed as hub and spoke, the ML-series card can be placed at the spoke locations, with the G-series card providing an extension of the traffic to a Cisco 7600, which forms the hub of the architecture. This arrangement provides a cost-effective way to interface to the Cisco 7600. Alternatively, the ML-series card can be deployed at both the hub and the spoke sites.
When deployed as an RPR, all sites contain ML-series cards (ML-1000-2, ML-100T-12, or ML-100T-8). A minimum of two ML-series cards is required to configure an RPR.
CTM provisions ML-series cards by opening a Telnet session to each card. Before this can be done, each ML-series card must be provisioned and have a password configuration that allows CTM to log in. For this purpose, a barebone file is provided on the CTM server disk (Disk 1).
Note
A different file is provided for the following cards:
•
•
•
Caution
Reset the ML card after loading the barebone file and wait for 5 minutes before provisioning topologies and services. The login and password are reported in the Control Panel window. You can create other profiles on ML-series cards by using the IOS Users table (available under Administration > CTC-based NEs > IOS Users Table).
After entering command-line interface (CLI) commands through the Telnet session, CTM issues a write or copy run start command to write the Cisco IOS configuration file to the Timing Communications and Control (TCC) flash. When the Cisco IOS configuration file is written to the TCC flash (by CTM or by another user), CTM is notified. To verify that CTM has been notified, enter the write command after any CLI change.
CTM provides a GUI wizard to facilitate provisioning of L2 topologies and related L1 circuits. Refer to the "Provisioning Data Services" section of Chapter 7, "Provisioning Services and Connections" in the Cisco Transport Manager Release 7.0 User Guide. Create an RPR or point-to-point topology involving some of the ML-series cards in the network. Based on the L2 topology circuit type and size that you specify, CTM creates related L1 circuits and installs a base card configuration on each ML-series card in the RPR ring.
The Create Layer 2 Service wizard guides you through the VLAN creation. There is no CLI to create a circuit VLAN. An RPR supports from 1 to 4095 VLANs, and these VLANs are enabled at all times. All that is required is to configure the endpoint to connect a ring VLAN to an Ethernet port (or port VLAN). Only ML devices are supported on an RPR.
Point-to-point topologies are supported for ML-ML, ML-G1000, and ML-OC cards. Point-to-point topology creation is similar to RPR creation in that based on the L2 topology circuit type and size that you specify, CTM creates related L1 circuits and installs a base card configuration on each ML-series card in the point-to-point topology.
CLI Configuration Details
Note the following CLI conventions:
•
[notes]
•
[match any]
•
<parameter>
•
{parameter_1 | parameter_2 | parameter_3}
Base Card Configuration
The base card configuration is a set of commands entered during the L2 topology creation. The parameters used are defined in the Layer 2 Topology Bandwidth pane (Figure 2) of the Create Layer 2 Topology wizard.
Note
Figure 2 Create Layer 2 Topology Wizard
RPR Base Card Configuration
For creation of an RPR topology, the base card configuration must be applied to all ML-series cards involved in the RPR. The ring is not functional and is reported as L2 Not Ready until the base card configuration is applied to all cards. You can select an L2 Not Ready RPR in the L2 Topology table and enable the L2 service provisioning by choosing Configuration > Enable L2 Service.
Caution
CTM defines the unique card number within the ring. The actual range is from 1 to 251 in any order. Refer to the NE hardware documentation for the number of ML-series cards allowed per RPR.
cos priority-multicast <Class Of Service> percent <Multicast Group %1> [If Multicast Group 1 has been enabled]cos priority-multicast <Class Of Service> percent <Multicast Group %2> [If Multicast Group 2 has been enabled]class-map match-any SP_MANAGEMENT [If SP Management (%) is greater than 0]match cos <SP Management Class of Service> [If SP Management (%) is greater than 0]class-map match-any AVVID_VOICE_VIDEOmatch cos <Low Latency Queue Class of Service>class-map match-any AVVID_CONTROL [If AVVID Control(%) is greater than 0]match cos <AVVID Control Class of Service> [If AVVID Control(%) is greater than 0]class-map match-any CIR [If Committed Rate (%) is greater than 0]match cos <Committed Rate Class of Service> [If Committed Rate (%) is greater than 0]class-map match-all BEST_EFFORTmatch anyPolicy-map POLICY_QOS_OUTclass SP_MANAGEMENT [If SP Management (%) is greater than 0]bandwidth percent <SP Management (%)>[If SP Management (%) is greater than 0]class AVVID_VOICE_VIDEOPriority 8 [Fixed value not configurable]class AVVID_CONTROLbandwidth percent <AVVID Control (%)> [If AVVID Control(%) is greater than 0]class CIR [If Committed Rate (%) is greater than 0]bandwidth percent <Committed Rate (%)> [If Committed Rate (%) is greater than 0]class BEST_EFFORTBandwidth percent <Default Best Effort (%)>Cos commit <CoS Commit>Vlan dot1q tag nativeL2protocol-tunnel cos 2 [Fixed Value]interface SPR1Spr station-id <Card#> [Valid Range is 1..254. It is not Spr node <Card#>][The following commands are not issued by CTM, these are default ML settings]no ip addressno keep alivehold-queue 150 inInterface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]no ip route-cacheinterface POS0Spr-intf-id 1Service-policy output POLICY_QOS_OUT[The following commands are not issued by CTM, these are default ML settings]No ip addressNo ip route-cacheCrc 32interface POS1Spr-intf-id 1Service-policy output POLICY_QOS_OUT[The following commands are not issued by CTM, these are default ML settings]No ip addressNo ip route-cacheCrc 32
Note
Note
Point-to-Point Base Card Configuration
For a point-to-point topology involved in at least one ML card, the other card can be ML, OC, or G1000. The point-to-point base card configuration must be applied only on the ML card(s) involved in the topology.
Note
Note
cos priority-multicast <Class Of Service> percent <Multicast Group %1> [If Multicast Group 1 has been enabled]cos priority-multicast <Class Of Service> percent <Multicast Group %2> [If Multicast Group 2 has been enabled]class-map match-any SP_MANAGEMENT [If SP Management (%) is greater than 0]match cos <SP Management Class of Service> [If SP Management (%) is greater than 0]class-map match-any AVVID_VOICE_VIDEOmatch cos <Low Latency Queue Class of Service>class-map match-any AVVID_CONTROL [If AVVID Control(%) is greater than 0]match cos <AVVID Control Class of Service> [If AVVID Control(%) is greater than 0]class-map match-any CIR [If Committed Rate (%) is greater than 0]match cos <Committed Rate Class of Service> [If Committed Rate (%) is greater than 0]class-map match-all BEST_EFFORTmatch anyPolicy-map POLICY_QOS_OUTclass SP_MANAGEMENT [If SP Management (%) is greater than 0]bandwidth percent <SP Management (%)>[If SP Management (%) is greater than 0]class AVVID_VOICE_VIDEOPriority 8 [Fixed value not configurable]class AVVID_CONTROLbandwidth percent <AVVID Control (%)> [If AVVID Control(%) is greater than 0]class CIR [If Committed Rate (%) is greater than 0]bandwidth percent <Committed Rate (%)> [If Committed Rate (%) is greater than 0]class BEST_EFFORTBandwidth percent <Default Best Effort (%)>Cos commit <CoS Commit>Vlan dot1q tag nativel2protocol-tunnel cos 2 [Fixed Value][The following commands are not issued by CTM, these are default ML settings]Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]no ip route-cacheinterface POS0service-policy output POLICY_QOS_OUTCrc {16|32} [Crc 16 between ML and E-Series, otherwise is Crc 32][The following commands are not issued by CTM, these are default ML settings]No ip addressNo ip route-cacheinterface POS1service-policy output POLICY_QOS_OUTCrc {16|32} [Crc 16 between ML and E-Series, otherwise is Crc 32][The following commands are not issued by CTM, these are default ML settings]No ip addressNo ip route-cache
Note
PoS, Ethernet, and SPR Port Provisioning
CTM allows you to provision the parameters detailed in Table 2, using the Create Layer 2 Service wizard, Modify Ports dialog box, Modify VLANs dialog box, Add L2 Service Drops wizard, or the Modify L2 Drops wizard.
Ethernet port provisioning involves configuring the following (see Figure 3):
•
•
•
•
PoS port provisioning involves configuring the following (see Figure 3):
•
•
Figure 3 Create Layer 2 Service—Modify Port Properties
Enable
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]No shutdownDisable
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]shutdownMTU Provisioning
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]mtu <MTU> [MTU=64..9000]Speed Provisioning
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]speed <Speed> [Speed=10/100/auto]Duplex Provisioning
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]duplex <Duplex> [Duplex=half/full/auto]Flow Control (Send) Provisioning
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]flowcontrol send <Flow Control(send)> [Flow Control=desired/off/on]Enable (No Shut)
Interface {POSN} [N=0 or 1]No shutdownDisable (Shutdown)
Interface {POSN} [N=0 or 1]shutdownMTU Provisioning
Interface {POSN} [N=0 or 1]mtu <MTU> [MTU=64..9000]Wrapping Status
When a PoS port participating in a Layer 2 topology is shut down, CTM raises an alarm to indicate that the L2 topology has entered wrap state. The status of the Layer 2 topology changes from the original state (Complete or Incomplete) to Complete-Wrapped or Incomplete-Wrapped (see Figure 4).
Figure 4 Example Layer 2 Topology Table—Complete-Wrapped State
The Alarm Browser (see Figure 5) displays the wrapped-state alarm:
Figure 5 Example Alarm Browser—Complete-Wrapped State
Creating Service Connections
CTM provides an L2 service provisioning wizard to facilitate provisioning of VLANs over a defined L2 topology. You can define each Ethernet port as UNI (user interface) or NNI. VLANs on an Ethernet port are referred to as port VLANs. VLANs on Packet Over SONET (POS) and Shared Packet Ring (SPR) ports (and their connected circuits) are referred to as service provider VLANs (or circuit VLANs).
You cannot mix NNI and UNI connections on the same port. CTM supports the following types of service configurations:
•
•
•
•
The circuit VLAN range is from 1 to 4095. On an RPR, all valid circuit VLANs can be used; however, due to limited bridge-group resources, each ML card can access only 255 circuit VLANs. Due to limited card-level bridge-group resources, only 255 circuit VLANs can be used on a point-to-point circuit.
Note
Using the QoS Policy Template
You must configure the following information in the L2 service provisioning and QoS profile wizards:
•
•
•
CTM assigns an unused bridge group (BG) to the card. The range is from 1 to 255.
Table 3 lists the configuration information for a best-effort QoS profile. You can select the predefined profile and customize it, or create a new customized profile by using the Advanced option.
Table 4 lists the configuration information for the committed information rate/peak information rate (CIR/PIR) QoS profile. You can select the predefined profile and customize it, or create a new customized profile by using the Advanced option.
Note
CTM allows you to define a QoS policy template starting from the above predefined policies, customizing them within the following predefined ranges:
•
–
–
–
–
–
–
•
–
–
–
–
You can create your own advanced QoS policy. You can input the customized QoS configuration based on the following parameters:
•
•
•
•
•
•
•
You must configure the following information in the L2 service provisioning and QoS profile wizards:
•
•
•
CTM assigns an unused BG to the card. The range is from 1 to 255.
Note
For each selected service drop, the configuration is done in three steps:
1.
2.
3.
The following sections describe the commands entered for each step.
1. Class Map Configuration
Configuring CIR/PIR Class Map
[Class Map Configuration for CIRPIR]Class-map match-all CLASS_BG<BG>_CIRPIRmatch bridge-group <BG>Configuring Best-Effort Class Map
[Class Map Configuration for BESTEFFORT]Class-map match-all CLASS_BG<BG>_BESTEFFORTmatch bridge-group <BG>Configuring Advanced Class Map
Figure 6 shows an example of how to create an advanced QoS profile.
Figure 6 Create QoS Profile Wizard—Advanced Class Map Configuration
[Class Map Configuration for ADVANCED]class-map match-all CLASS_BG<BG>_ADVANCED_<Service Drop Port>_N [N number of Policer will be configured on the <Service Drop Port>=0,1 for GigaEthernet and <Service Drop Port>=0..11 for FastEthernet.]match bridge-group <BG>[match ip dscp <Match DSCP>][if Match DSCP has been selected - Valid Range is 0-63][match ip precedence <Match IP Precedence>][if Match IP Precedence has been selected - Valid Range is 0-7][match cos <Match CoS>][if Match CoS has been selected - Valid Range is 0-7]2. QoS Profile Configuration
CIR/PIR QoS Profile
Figure 7 shows an example of how to create a CIR/PIR QoS profile.
Figure 7 Create QoS Profile Wizard—CIR/PIR
[Policy Map Configuration command for CIR/PIR QoS Profile]Policy-map POLICY_{GIGE|FE}<port>_INClass CLASS_BG<BG>_CIRPIR[1. Case Line Rate selection]Police 96000 8000 conform-action set-cos-transmit 2 exceed-action set-cos-transmit 2[2. Case Rate Limited selection Excess Traffic Discarded]Police <Committed Rate> <Committed Burst Size> conform-action set-cos-transmit 1 exceed-action drop[3. Case Rate Limited selection Excess Traffic Allowed]Police <Committed Rate> <Committed Burst Size> <Peak Burst> pir <Peak Rate> conform-action set-cos-transmit 2 exceed-action set-cos-transmit 1 violate-action dropBest-Effort QoS Profile
Figure 8 shows an example of how to create a best-effort QoS profile.
Figure 8 Create QoS Profile Wizard—Best Effort
[Policy Map Configuration for BESTEFFORT QoS Profile]Policy-map POLICY_{GIGE|FE}<port>_INClass CLASS_BG<BG>_BESTEFFORT[1. Case Line Rate selection]Police 96000 8000 conform-action set-cos-transmit 0 exceed-action set-cos-transmit 0[2. Case Rate Limited selection]Police <Max Rate> <Max Burst> conform-action set-cos-transmit 0 exceed-action dropAdvanced QoS Profile
Figure 9 shows an example of how to create an advanced QoS profile.
Figure 9 Create QoS Profile Wizard—Advanced
[Policy Map Configuration for ADVANCED QoS Profile]Policy-map POLICY_{GIGE|FE}<port>_INClass CLASS_BG<BG>_ADVANCED_<Service Drop Port>_N[N number of Policer will be configured on the <Service Drop Port>=0,1 for GigaEthernet and <Service Drop Port>=0..11 for FastEthernet]police <Committed Rate> <Committed Burst Size> [<Peak Rate> pir <Peak Burst>] conform-action {transmit|set-cos-transmit <Committed CoS Marking Value>} [exceed-action {drop|set-cos-transmit <Excess CoS Marking Value>}][violate-action {drop|set-cos-transmit <Violation CoS Marking Value>}][[<Peak Rate> pir <Peak Burst>] is applied only if Excess Traffic is Allowed] [exceed-action drop is applied only if Excess Traffic is Discarded][Trust option is never selectable for Excess Traffic or Violation tab, Mark CoS option is always used when the Excess or Violations is Allow][violation-action drop is applied only if Excess Traffic is Allowed and Violate Traffic is Discarded]Bandwidth Data Service Provisioning
Check the Enable Bandwidth DSP check box (in the Control Panel > ONS NE Service pane for CTC-based NEs) to enable the bandwidth data service provisioning (DSP) check during L2 service provisioning. The bandwidth utilization report shows available and used bandwidth for each L2 topology. This report can be used during L2 service provisioning to verify whether the requested CIR is available on the topology. Based on the report, an error is returned if there is not enough bandwidth available for a drop port.
3. Interface Configuration
Adding UNI QinQ Access
Any port with mode dot1q-tunnel is a UNI QinQ Access connection. Figure 10 shows an example for adding UNI QinQ access using the Create Layer 2 Service wizard.
Figure 10 Create Layer 2 Service Wizard—Adding UNI QinQ Access
[Interface Configuration]Interface {GigabitEthernet<port>|FastEthernet<port>}Description <QoSProfileName>[CTM will issue `L2protocol-tunnel all' command and the result will be the following set of commands]l2protocol-tunnel cdpl2protocol-tunnel stpl2protocol-tunnel vtpno cdp enableMode dot1q-tunnelBridge-group <BG>Service-policy input POLICY_{GIGE|FE}<port>_INService-policy output POLICY_QOS_OUT[The following command in not issued by CTM, these are default ML settings] Bridge-group <BG> spanning-disableInterface SPR1.<Service Provider VLAN>Encapsulation dot1q <Service Provider VLAN>Bridge-group <BG>[The following command in not issued by CTM, these are default ML settings] Bridge-group <BG> spanning-disableRemoving UNI QinQ Access
[Note the reverse order of commands]Interface SPR1.<Service Provider VLAN>No Bridge-group <BG>No Encap dot1q <Service Provider VLAN>No Interface SPR1.<Service Provider VLAN> [Ignore warning message]Interface {GigabitEthernet<port>|FastEthernet<port>}No Bridge-group <BG>No Mode dot1q-tunnelNo L2protocol-tunnel allNo descriptionNo class-map CLASS_BG<BG>_{CIRPIR|BESTEFFORT|ADVANCED_<Service Drop Port>_N}[Remove all the N number of Class Maps in case of Advanced QoS][When removing last connection from a port]No Policy-map POLICY_{GIGE|FE}<port>_INNo Service-policy output POLICY_QOS_OUTAdding UNI dot1Q Access
Figure 11 shows an example for adding UNI dot1Q access using the Create Layer 2 Service wizard.
Figure 11 Create Layer 2 Service Wizard—Adding UNI dot1Q Access
The port is recognized as UNI if the service-policy input command is entered on the port interface; otherwise, the port is recognized as NNI. Every subinterface is a dot1q connection. The classification of UNI versus NNI is based on the port-level parsing. A connection is untagged if the encap dot1q 1 command is entered. The multiple class map and QoS policer configurations for advanced QoS are similar to the QinQ Access example shown in Figure 11.
[Interface Configuration][First time only - First dot1q on this UNI port]Interface {GigabitEthernet<port>|FastEthernet<port>}Service-policy input POLICY_{GIGE|FE}<port>_INService-policy output POLICY_QOS_OUTInterface {FastEthernet<port>|GigabitEthernet<port>}.<Port VLAN>Description <QoSProfileName>Encapsulation dot1q <Port VLAN>Bridge-group <BG>[The following command executed by CTM only RSTP has not been enabled]Bridge-group <BG> spanning-disableInterface SPR1.<Service Provider VLAN>Encapsulation dot1q <Service Provider VLAN>Bridge-group <BG>[The following command executed by CTM only RSTP has not been enabled]Bridge-group <BG> spanning-disableRemoving UNI dot1Q Access
[Note the reverse order of commands]Interface SPR1.<Service Provider VLAN>No Bridge-group <BG>No Encap dot1q <Service Provider VLAN>No Interface SPR1.<Service Provider VLAN> [Ignore warning message]Interface <port>.<Port VLAN>No Bridge-group <BG>No Encap dot1q <Port VLAN>No descriptionNo Interface <port>.<Port VLAN> [Ignore warning message]Policy-map POLICY_{GIGE|FE}<port>_INNo Class BG<BG>_{CIRPIR|BESTEFFORT|ADVANCED_<Service Drop Port>_N}[Remove all the N number of Class Maps in case of Advanced QoS]No class-map CLASS_BG<BG>_{CIRPIR|BESTEFFORT|ADVANCED_<Service Drop Port>_N}[Remove all the N number of Class Maps in case of Advanced QoS][When removing last connection from a port]No Policy-map POLICY_{GIGE|FE}<port>_INNo Service-policy output POLICY_QOS_OUTAdding UNI Untagged Access
UNI untagged access is similar to UNI dot1Q access with port VLAN ID = 1.
Adding NNI dot1Q Access
[Interface Configuration][First time only - First Connection on this port]Interface {FastEthernet<port>|GigabitEthernet<port>}Service-policy output POLICY_QOS_OUTInterface {FastEthernet<port>|GigabitEthernet<port>}.<Port VLAN>Encap dot1q <Port VLAN>Bridge-group <BG>Interface spr 1.<Server Provider VLAN>Encap dot1q <Server Provider VLAN>Bridge-group <BG>Removing NNI dot1Q Access
[Note the reverse order of commands]Interface spr 1.<Server Provider VLAN>No Bridge-group <BG>No Encap dot1q <Server Provider VLAN>No Interface spr 1.<Circuit VLAN> [Ignore warning message]Interface <port>.<Port VLAN>No Bridge-group <BG>No Encap dot1q <Port VLAN>No Interface {FastEthernet<port>|GigabitEthernet<port>}.<Port VLAN> [Ignore warning message][When removing last connection from a port]No Service-policy output POLICY_QOS_OUTEnabling or Disabling RSTP
You can enable rapid spanning tree protocol (RSTP) on UNI dot1Q, UNI Untagged, and NNI dot1Q ports by selecting the RSTP for the selected drop port and then selecting the RSTP Enable check box (see Figure 12). You can disable RSTP by selecting the RSTP for the selected drop port and then deselecting the RSTP Enable check box.
Note
Figure 12 Create Layer 2 Service Wizard—RSTP Enable
The following command is issued beside the command specified for adding a drop, when the RSTP Enable check box is checked.
[Configure RSTP,this command is issued once for VLAN]bridge <BG> protocol rstp[Enable RSTP on the selected drop]Interface {FastEthernet<port>|GigabitEthernet<port>}.<Port VLAN>Bridge-group <BG>The following command is issued when you disable RSTP from a drop:
[Disable RSTP on the selected drop]Interface {FastEthernet<port>|GigabitEthernet<port>}.<Port VLAN>Bridge-group <BG>Bridge-group <BG> spanning-disabled [Disable RSTP on the selected drop]
Note
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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
Copyright © 2006 Cisco Systems, Inc. All rights reserved.
Guest
