|
|
The Cisco 6400 Equipment Model supports the Cisco 6400 Universal Access Concentrator (UAC). The Cisco 6400 UAC is a multi-technology access concentrator that offers conventional ATM switching functions with full support for different QoS classes as well as a unique set of aggregation and routing capabilities, including:
The Cisco 6400 Equipment Module provides full support for the following network interface cards (referred to as Node Line Cards):
The Equipment Module works directly with the Cisco 6400 UAC.
The Equipment Module provides an event logging daemon to track event log changes from the Cisco 6400. The daemon is started/stopped in the workstation boot and runs independently of CPC.
 |
Note In order to configure the Cisco 6400 Equipment Module you must have installed it during the CPC Server and Client installation procedures. For more information about installing CPC, refer to the NetProvision CPC Installation and Administration Guide. |
To configure the Equipment Module to make CPC operational, you must complete the following steps:
Step 2 Cisco 6400 Configuration and Preprovisioning (NRP/NSP)
Step 3 Event Logging and Daemon Installation
Step 4 Workstation Upload and Configuration (enabling TFTP)
Step 5 Configuring the 6400 for RADIUS Awareness
Step 6 RADIUS Server Requirements
Step 7 Installing the 6400 Equipment Module Utility Package
Step 8 Configuring the RADIUS Clients File
Step 9 Initial System Upload
Step 10 Re-Upload (if configuration information has changed)
Step 11 Add Inter-Network links (Topology) Information
Step 12 Create Logical Ports (as required)
Step 13 Create Service Element Profiles
Step 14 Configure Service Elements (as required)
Step 15 Cisco Equipment Module Maintenance
The Cisco 6400 Equipment Module supports the versions of software/firmware indicated in Table 10-1 below.
| Vendor | Product | Version | Notes |
|---|---|---|---|
Cisco | Cisco IOS (NRP) | 12.11 or later | Firmware in network elements must be compatible with this release. |
Cisco IOS (NSP) | 12.07 or later | ||
Merit | RADIUS server | 3.6B | Acquired independently of CPC. Merit RADIUS server installation requires Sparc-Solaris 2.5.1 or above and ftp/telnet capability, read the UNIX manual page for ftdp by entering man ftpd or man teleneted at a UNIX prompt. |
The CPC Server system file must be configured to receive traps from the Cisco 6400. To configure the CPC for communication with the Cisco 6400, complete the following steps:
Step 2 Navigate to the/etc/inet directory on the CPC server.
Step 3 Add the following line to the services file:
c4trapd 5999/udp
This line specifies that when the C4trapd program is running, it uses the port #5999 and udp protocol for communication with the Cisco 6400.
Step 4 Find the process ID number for inetd.
ps -ef | grep inetd
Step 5 Kill the inetd process:
kill -9 pid
where
pid -- the process Id.
Step 6 Restart the inetd process:
inetd -s
Preprovisioning must be done for each Node Router Processor (NRP) and the Node Switch Processor (NSP) individually in order to facilitate the creation, modification, deletion and management of DSL services using the Cisco 6400 UAC. Before separate provisioning of the NRP and NSP and upload functions can occur, each NSP and NRP must have the following parameters configured:
For more information on configuring the above parameters, refer to the appropriate Cisco 6400 user documentation.
You must preprovision each Cisco 6400 NRP before launching the event logger. For more information on configuring the NRP, refer to the appropriate Cisco 6400 user documentation. The following procedure uses an NRP to illustrate the configuration process. Configuration requires a thorough understanding of Cisco IOS software. To configure the NRP:
telnet 192.1.1.128
Step 2 Enter the username and password.
Step 3 The user EXEC prompt (Router>) will appear. Configuration changes must be made from enable mode. To enter enable mode from the user EXEC prompt, issue the following commands:
Router>enable
password:password
Step 4 Enter configuration mode.
config terminal
Step 5 Enable Event Logger requirements by entering the following ISO commands:
snmp-server community PUBLIC RO snmp-server community PRIVATE RW snmp-server community trap-timeout 10 snmp-server community enable traps config snmp-server community enable traps snmp snmp-server community host <IP address> traps version 2c PUBLIC udp-port 5999 exit
where:
IP address--The IP Address of the CPC server host with Event Logger.
|
Note You enable other traps in addition to the ones specified in the above example. For a complete list of traps, refer to the appropriate Cisco 6400 user documentation. |
Step 6 Verify the NRP configuration by issuing the following command:
show running-config
You must preprovision the Cisco 6400 NSP before launching the event logger. For more information on on configuring the NSP, refer to the appropriate Cisco 6400 user documentation. The following procedure uses an NSP to illustrate the configuration process. Configuration requires a thorough understanding of Cisco IOS software.
To configure the NSP:
telnet 192.1.1.147
Step 2 Enter the username and password.
Step 3 The user EXEC prompt (Switch>) will appear. Configuration changes must be made from enable mode. To enter enable mode from the user EXEC prompt, issue the following commands:
Switch>enable password:password
Step 4 Enter configuration mode.
config terminal
Step 5 Enable Upload and Event Logger requirements by entering the following IOS commands:
snmp-server community PUBLIC RO snmp-server community PRIVATE RW snmp-server trap-timeout 10 snmp-server enable traps config snmp-server enable traps entity snmp-server enable traps chassis-fail snmp-server enable traps chassis-change snmp-server host <IP Address> traps version 2c PUBLIC udp-port 5999 exit
where:
IP Address--The IP Address of the CPC server host with Event Logger.
Step 6 Verify the NRP configuration by issuing the following command:
show running-config
|
Note You can enable other traps in addition to the ones specified in the above example. For a complete list of traps, refer to the appropriate Cisco 6400 user documentation. |
An event logging daemon must be installed on the CPC Server host for any event logging to become operational. The event logger is distributed through the Cisco 6400 Equipment Module installation procedure. The event logger is a standalone daemon independent of CPC functions. Launching CPC does not activate the event logger, and shutting down CPC does not terminate the event logger. The event logger will continue to log events from the 6400 if CPC is shut down. When CPC is restarted, the CPC server system file will update the log files by checking in the event log directory.
The Cisco 6400 UAC and the CPC server system file must be properly configured before the event logger can be used. You must launch the event logger separately by issuing the following command at the command line in the CPC runtime environment:
C4trapd -f $CCP_LOG/event/C4eventLog
To enable proper upload functionality, the TRTP server must be enabled on each workstation that is running CPC. To enable the TRTP server, follow the following procedure:
Step 2 Navigate to the /etc/inet/directory on the CPC server.
Step 3 Edit the inetd.conf file by changing the following line from:
#trtp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s / tftpboot to: tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd
Step 4 Restart the inetd process:
inetd -s
Before the provisioning of services can occur, you must individually configure each NRP to recognize and communicate with the RADIUS server. Configuration of each NRP involves three steps:
Step 2 Default authentication--Specify the default authentication protocol to be used in order to authenticate users.
Step 3 Network Access Server (NAS) port format--Specify the ATM VC extended format for the NAS port field. This format is denoted by the letter d.
An awareness of the RADIUS server must be established on the 6400 to allow the exchange of authorization and authenticating information. This process must be done for each NRP within the 6400. The configuration is implemented using Cisco IOS commands on the router. To configure an NRP to be aware of a RADIUS server, issue the following IOS commands at the privileged EXEC prompt:
aaa new-model aaa authentication ppp default group radius aaa nas port extended radius-server attribute nas-port format d
once each NRP installed with the 6400 has been configured to be aware of a RADIUS server, further preprovisioning must be done to specify the location of the RADIUS server host, the authentication and accounting port addresses on the server host, and the RADIUS password. These preprovisioning steps are required for the NRP to recognize a specific RADIUS server and where it is located. To configure RADIUS access, issue the following IOS commands at the privileged EXEC prompt:
radius-server host <ip address> auth-port 1645 act-port 1646 radius-server key <key>
where:
ip address--The IP address of the RADIUS server
key--The encryption key used on the RADIUS server. This encryption key must be identical in IOS and in the RADIUS server clients file. For more information, consult your RADIUS documentation.
Configuration of the username authentication system is required, when logging into the NRP. The NRP acts as a client NAS (Network Access Server). The NAS is the aggregation point of PPP sessions into an L2TP tunnel. To configure the username authentication system for the NAS, enter the following IOS commands at the privileged EXEC prompt:
config terminal
Step 2 Specify the host name or user name and a password in the following format:
username <name> [ no password | password <encryption type> <password> ]
where:
name--A username or the machine name
encryption type--A number that represents a certain encryption type - 0 indicates a cleartext password
password--A unique password
for example:
username C4 password 0 ABCPassword
|
Note For more information on configuring an NRP as a NAS, refer to the appropriate Cisco User Documentation. |
You must configure the 6400 NRP to be aware of single hop and multihop tunnels. Tunnels that are created using L2TP are used by Virtual Private Dial-Up Networking (VPDN) to extend a PPP session across a wide area network. NRPs must be configured to look for tunnel definitions on a L2TP Network Server (LNS). Issue these IOS commands at the privileged EXEC prompt to enable VPDN:
config terminal
Step 2 Enable VPDN and inform a router to look for a tunnel definitions on an LNS:
vpdn enable
Step 3 Enable multihop tunneling:
vpdn multihop
Step 4 Specify how the NAS is to perform VPDN tunnel authorization searches:
vpdn search-order multihop-hostname domain
Configuration of the Merit RADIUS server is an integral part of provisioning Layer Two Tunneling Protocol (L2TP) single hop services on Cisco 6400 UAC equipment. The RADIUS server carries information on subscriber tunnels and service lists. The server acts as a repository of tunnels. Each tunnel has a Service Name key used to bind subscribers to a particular tunnel.
The Cisco 6400 Equipment Module uses a Merit RADIUS server for user authentication and authorization.Data transfer between the CPC server host and the Merit server host is accomplished through FTP and TELNET session.
To install the Merit RADIUS server, perform the following steps on the host where the RADIUS server is to be installed. It is assumed that you have obtained a copy of the Merit RADIUS server software independently of CPC.
Step 2 Display the admintool interface by entering.
admintool
Step 3 Select Groups from the Browse pull-down menu
Step 4 Select Add from the Edit pull-down menu
Step 5 Table 10-2 specifies the values that should be entered during the setup of the group account.
| Attribute | Description | Sample Value |
|---|---|---|
Group Name | Specifies a name used by the system to identify a user's group. A group name is a text strong composed of lowercase alphabetical characters (a-z) and digits (0-9). A group name can be 1-8 characters. | staff |
Group ID | Specifies a group identification number used by the system to crete a user's primary group. By default the next available number displays here. | 102, 103 |
Members List | Optional. Specifies users or groups who belong to this group. If there is more than one member in the list, then separate names with a comma but do not use any spaces. | bill,bob,bamey
|
Step 6 Select Users from the Browse pull-down menu.
Step 7 Select Add from the Edit pull-down menu. Table 10-3 specifies the values that should be entered during the setup of the group account.
| Attribute | Description | Sample Value |
|---|---|---|
User Name | Required. Specifies the login name the operating system will use to identify this user. The user name must be a unique name composed of uppercase or lowercase alphabetical characters (a-z) or digits (0-9). A user name can be 1-8 characters long. | meritP |
UserID | Required. Specifies a number by which the operating system can identify a user. The user's UID is typically a number between 100 and 60000. | 1003, 1004 |
Primary Group | Required. Specifies a group number or a group name. The operating system will assign the group number to files created by the user. | staff
|
Secondary Groups | Optional. Specifies other groups this user will belong to. |
|
Comment | Optional. Specifies other groups this user will belong to. |
|
Login Shell | Required. Specifies a login shell for the user. The Korn shell is mandatory. | Korn |
Password | Required. Specifies the means by which a user sets up a password. | Select Normal Password from the drop down menu and enter a password for the user. |
Min Change | Optional. Specifies the minimum number of days allowed between password changes. |
|
Max Change | Optional. Specifies the maximum number of days a user can go without having to set up a new password. |
|
Max Inactive | Optional. Specifies the maximum number of days the user account can be inactive before the user must set up a new password. |
|
Expiration Date | Optional. Specifies the expiration day, month, and year for a user's password. |
|
Warning | Optional. Specifies when users will start receiving warning messages about their password expiring. |
|
Create Home Dir | Required. Specifies whether or not the user's home directory is to be set up automatically. By default, the user's home directory is set up automatically. | /usr/private/etc/raddb |
Path | Required. Specifies the path for the user's home directory. The path is where admintool will place the user's initialization files. If Create Home Dir is selected you must specify a path. | /usr/private/etc
|
Step 8 Exit the admintool interface and login as the user meritP.
su - meritP
Step 9 Change to the directory where the Merit RADIUS server is to installed.
cd /usr/private/etc
Step 10 Copy the Merit RADIUS server file from a source directory into the current directory.
Step 11 Extract the Merit RADIUS server. This will install the software.
cd /usr/private/etc
Step 2 Start the Merit daemon:
$ ./radius
It is recommended that you test the Merit RADIUS server to determine whether the server is operational and to determine if the server will correctly authenticate a user.
su - meritP
Step 2 Navigate to the directory containing the Merit server installation:
cd /usr/private/etc
Step 3 Issue the radcheck command to determine whether the Merit server is operational:
radcheck -p 1645 -r 1 <hostname>
The server is working if a similar output to the following is displayed:
MF: vp=1703/1692 auth=2/1 waldo=1/1 redo=0/0 DNS-MF: client=2/0 addr=78/78 name=78/77 CLIENT-MF: vendor=10/0 vendor_list=158/157 (found=1) auth queue: 1/1(1/0), acct queue: 0/0(0/0), maxtime: 0 (000107.143023) auth stats: 2/0/0, acct stats: 0/0/0 authfile: 2, clients: 1, user: 1, 000107.143022 fsmid: STD, dictid: 1.14, vendid: 1.4 cleanup_delay: 6, avg-delay 1 (of 100) Version 3.6B sun "hostname(1645)" is responding
Step 4 Authenticate a sample user by using the radpwtst command:
radpwtst -p 1645 -s <hostname> -r 1 -w smart -u ppp smartuser
If authentication is successful, the server will prompt:
"smartuser" authentication OK
You can enable the RADIUS server to start up automatically when the system is booted. To automate the Merit RADIUS server startup process, follow the following procedure on the RADIUS server host:
# RADIUS protocol radius 1645/udp radacct 1646/udp
Step 2 Add the following entry in the /etc/inetd. conf file on the Merit RADIUS server host:
radius dgram udp wait meritP /usr/private/etc/radiusid radiusid
The Cisco 6400 Equipment module includes a utilities package that must be installed separately on the RADIUS server host if you are doing your own installation of a RADIUS server. This package must be installed in the utility directory under the database directory. The package includes the C4buildDBM, C4userFilter, and C4userMerge executables.
To install the package, complete the following procedure:
cd usr/private/etc/raddb
Step 2 Copy the C4buildDBM, C4userFilter, and C4userMerge executables from the CPC server host. These files are contained in the C4Utils.tar file located in the $CCP_BIN directory on the CPC server host. Copy the tar file to the RADIUS server host.
cp /net/host/disk2/SY/CPC/Server/sys/bin/c4Utils/tar.
Step 3 Extract the utilities.
tar xvf c4Utils.tar
|
Note Ensure that the RADIUS server database directory is the login directory for RADIUS server user accounts. By doing this, you avoid having to modify scripts to change from the working to directory to the database directory when an FTP or TELNET session is initialized. |
In order to enable the RADIUS server to allow an NRP authentication request from the 6400, the NRP must be recognized as a client of the RADIUS server. The clients file must specify the IP address of each NRP that intends to use the RADIUS server for user authorization and authentication. The structure of the clients file will be similar to the following dialog:
#Client Name Key [type] [version] [prefix] #-------------------------------------------------------------------------------- 192.1.10.151 password type = Merit: PROXY #10.1.2.3:256 test type = nas v2 pfx #pm1 %^%#*(&!(*&)+ type = nas pm1.
|
Note The key specified in the RADIUS clients file must be identical to the key specified for the RADIUS Server in the NRP IOS as outlined in the section "Configuring RADIUS Access" |
For more information on configuring the Merit RADIUS server clients file, visit the Merit Server AAA Configuration clients file page at http://www.merit.edu/aaa/clients.html
In order to provision services, the CPC database must have detailed knowledge of the managed subnetworks. Using a procedure called upload, objects are created within the CPC database that represent objects of the managed network.
|
Note The term upload does not refer to the creation of inter-network links because they are outside the scope of any single Equipment Module. See the section titled "Adding Inter-Network Links (Topology) Information" later in this chapter. |
CPC supports the following types of upload:
The upload function takes precedence over any Transactions which are running at the time of upload. If the upload function makes a change back to the fabric which affects a running Transaction (such as deleting a logical port that the threader has decided to use) then this Transaction fails and must be restarted.
A network object must be created in order to perform an Upload.
One network object must be created for each network. The following steps explain how to create and upload a network object:
Step 2 Click the Cisco DSL Network folder to highlight it.
Step 3 Click the Subset Viewer button on the toolbar.
Step 4 Enter the attribute values in the available row of cells.
When creating a network object, the Subset Viewer provides the following attribute fields:
Step 5 Save the Network Object by clicking the save button on the toolbar.
Step 6 Apply the Transaction by clicking the apply button on the toolbar.
One node object must be created for each Cisco 6400 in the network. The following steps explain how to create and upload a node object:
Step 2 Double-click the Cisco DSL Network folder.
Step 3 Double-click the specific network folder.
Step 4 Click on the Cisco DSL 6400 Node folder to highlight it.
Step 5 Click the Object Viewer button on the toolbar.
When creating a node object, the Object Viewer provides the following attribute fields:
Step 6 Save the Network Object by clicking the save button on the toolbar.
Step 7 Apply the Transaction by clicking the apply button on the toolbar.
Upload the fabric elements such as physical ports for a particular node by completing the following steps:
Step 2 Double-click the Cisco DSL Network folder to open it. You can select objects in the Cisco DSL Network list or you can filter your request for specific criteria. Refer to the section "Filtering" in the chapter titled "GUI Navigation" for more information on filtering in the Tree Viewer.
Step 3 Double-click a network object folder to open it.
Step 4 Click the Cisco DSL 6400 Node folder to highlight it. Enter search criteria in the appropriate filter fields to find the node you want to upload for and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco 6400 Node folder.
Step 5 Click the node from the list to highlight it.
Step 6 Select load fabric from the Element menu. The upload begins.
Step 7 When the upload is complete, a status window appears. If there were errors during the upload they appear in this window.
This upload is used for incremental uploads. It finds all connection objects attached to the node. This procedure is not part of the initial Service element uploading. Before beginning a service upload on a node, it is important for you to verify that each NRP has been correctly configured with an Access Name, Access Password and Enable Password. If any of these items has not been configured, you must do so now in order to ensure a successful upload.
Upload the Service elements of a particular node by completing the following steps:
Step 2 Double-click the Cisco DSL Network folder to open it. You can select objects in the Cisco DSL Network list or you can filter your request for specific criteria. Refer to the section "Filtering" in the chapter titled "GUI Navigation" for more information on filtering in the Tree Viewer.
Step 3 Double-click a network object folder to open it.
Step 4 Click the Cisco DSL 6400 Node folder to highlight it. Enter search criteria in the appropriate filter fields to find the node you want to upload for and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco 6400 Node folder.
Step 5 Click the node from the list to highlight it.
Step 6 Click load services from the Element menu. The upload begins.
Step 7 When the upload is complete, a status window appears. If there were errors during the upload they appear in this window.
Upload the fabric and service elements or a particular node by completing the following steps:
Step 2 Double-click the Cisco DSL Network folder to open it. You can select objects in the Cisco DSL Network list or you can filter your request for specific criteria. Refer to the section "Filtering" in the chapter "GUI Navigation" for more information on filtering in the Tree Viewer.
Step 3 Double-click a network object folder to open it.
Step 4 Click the Cisco DSL 6400 Node folder to highlight it. Enter search criteria in the appropriate filter fields to find the node you want to upload for and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco 6400 Node folder.
Step 5 Click the node from the list to highlight it.
Step 6 Select load both from the Element menu. The upload begins.
Step 7 When the upload is complete, a status window appears. If there were errors during the upload they appear in this window.
CPC allows you to upload tunnel information and service lists for single hop tunnels from a RADIUS server.
You must create a RADIUS object before you can perform an upload. The following steps explain how to create a RADIUS object.
Step 2 Click the Cisco DSL 6400 RADIUS Server folder to highlight it.
Step 3 Click the Object Viewer button on the toolbar.
Step 4 Enter the appropriate values under the Common Attributes, RADIUS, and Attributes tabs. Refer to Table 10-4 for attribute information.
Step 5 Save the RADIUS object by clicking the save button on the toolbar.
Step 6 Apply the Transaction by clicking the apply button on the toolbar.
|
Note LDAP attributes are supplied for future compatibility. |
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
RADIUS | |||
RADIUS Version | This is the RADIUS version. CPC supports Merit RADIUS version 3.6B | none, Merit_AAA_3.B | Merit_AAA_3.6B |
RADIUS User Name | Specify a valid user name for the RADIUS server. | Text string (up to 64 characters) |
|
RADIUS Password | Specify a valid password for user name that you have entered for the RADIUS server. | Text string (up to 32 characters) |
|
Primary RADIUS Server | Specify the hostname of the primary RADIUS server. | Text string (up to 64 characters) |
|
Primary RADIUS Auth Port | This is the authentication port on the Primary RADIUS server. |
| 1645 |
Primary RADIUS Acct Port | This is the accounting port on the Primary RADIUS server. |
| 1646 |
Backup RADIUS User Name | Specify a valid user name for the backup RADIUS server. |
|
|
Backup RADIUS Password | Specify a valid password for the user name that you have entered for the backup RADIUS server. |
|
|
Backup RADIUS Server | Specify the hostname of the backup RADIUS server. |
|
|
Backup RADIUS Auth Port | This is the authentication port on the Backup RADIUS server. |
| 1645 |
Backup RADIUS Acct Port | This is the accounting port on the Backup RADIUS server |
| 1646 |
Tunnel information stored on an existing RADIUS server can be uploaded similar to a node upload. RADIUS upload requires the creation of a RADIUS object within CPC.
When a RADIUS object is created, both a Primary RADIUS server and a Backup RADIUS server are specified. Tunnel information (Service Lists is uploaded from the Primary server. If Primary server upload fails, Backup server upload will be attempted. To upload RADIUS, perform the following procedure.
Step 2 Double-click the Cisco DSL 6400 RADIUS Server folder to open it.
Step 3 Click the specific RADIUS server that you want to upload to highlight it.
Step 4 Select load services from the Element menu. This upload begins.
Step 5 When the upload is complete, a status window appears. If there were errors during the upload they appear in this window.
CPC allows you to view the progress of the upload in real time. During an upload, the following procedure can be used to view a log file that details site information, service and/or fabric information, and upload processes depending on the type of upload being performed. This log file will also report the status of the upload procedure after its completion.
Step 2 Double-click the Upload Request folder to open it.
Step 3 Click the specific upload request folder to open it.
Step 4 Double-click the Upload Request Log folder to open it.
Step 5 Click AuditLog to highlight it and select Log Viewer from the View menu.
The CPC database must be continually updated in order to stay synchronized if changes are being made to nodes in the network. You should re-upload after any of the following:
To re-upload you only need to upload the fabric and Service elements of a particular node. For more information, refer to the sections above titled, "Uploading the Fabric Elements for a Node" and "Uploading Service Elements for a Node."
After uploading new fabric elements and Service elements, you may need to add extra topology information which the upload function is unable to determine (perhaps because the information is not known to the node or subnet manager). Topology information or internetwork links are outside the scope of a single node or subnet manager and must be added manually through the CPC GUI or the FTI.
Step 2 Double-click the Cisco DSL Network folder to open it. You can select objects in the Cisco DSL Network list or you can filter your request for specific criteria. Refer to the section "Filtering" in the chapter titled "GUI Navigation" for more information on filtering in the Tree Viewer.
Step 3 Double-click a Cisco DSL network object folder to open it.
Step 4 Click the Cisco DSL 6400 Node folder to highlight it. Enter search criteria in the appropriate filter fields to find the node you want to upload for and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco 6400 Node folder.
Step 5 Double-click the specific node folder to open it.
Step 6 Click a Cisco DSL logical port folder to highlight it. Enter search criteria in the appropriate filter fields to find a specific logical port and then click the get list button on the toolbar.
Step 7 Double-click the specific logical port folder to open it.
Step 8 Click the Link folder to highlight it.
Step 9 Click the Subset Viewer button on the toolbar.
Step 10 To select a logical port, click it from the Tree Viewer and select copy from the Edit menu.
Step 11 Paste the chosen logical port in the Link Subset Viewer by selecting paste from the Edit menu. The link Subset Viewer has a cell for Local Logical Port and another for Remote Logical Port, representing the two endpoints of the internetwork link. You must choose a logical port for both endpoints.
Step 12 You can create a locked or unlocked link. If you want to create a link, but disallow any provisioning of services across it, select Locked by clicking the empty cell below either of the Lport Status menus. When the cell is clicked, a pull down menu will appear. If you want CPC to use the link, leave the default value Unlocked.
Step 13 If you are not satisfied with a value, click the appropriate field and modify it.
Step 14 Save the Link by clicking the save button on the toolbar.
Step 15 Apply the Transaction by clicking the apply button on the toolbar.
Step 16 Repeat the above procedure for the creation of each internetworking link.
Service element profiles provide you with access to the Cisco 6400-specific attributes for a particular service element. There is a corresponding Service element profile for each service element type that the node supports. Default profiles provide the initial (default) attribute values for the corresponding object class whenever such a new object is created.
For a given service element, more than one profile may be defined. However, for a given object, only one profile may be associated at any one time.
Since profiles themselves are objects which you can create and modify, they provide a means to store and name commonly used sets of attributes and provide a reliable shorthand method of configuring any number of new objects. A profile has most of the same attributes as the corresponding object class. Some attributes of the object class are not included in the profile because they are expected to be unique for each object. For example, the VPI and VCI for a PVC would not be a profile attribute. Similarly, an object's name is not a profile attribute.
The attributes of a profile are referred to as initial value attributes because they are used to assign the initial values to the corresponding object. Once a new object has been created based on a profile, changes to profile attribute values do not cause any changes to the corresponding object. The only time the profile attributes affect the object is when you create a new object or when you reassign an existing object to the same or different profile.
For the Cisco 6400 Equipment Module, you can create service element profiles for the following supported service elements:
This section details the generic procedure for creating, modifying and deleting Service element profiles, and then provides the specific configurable attributes for each Service element profile for this Equipment Module.
If you provide values for these attributes and also provide values in other places when you are creating a service (either during service creation or in a Service object profile) the threader will override the values based on the following scale of priorities:
Step 2 Service object profile--CPC will only use the information provided in the Service object values that are either not available or not specified in the Service object Subset Viewer.
Step 3 Service element profile--CPC uses values from the Service element profile for all attributes that are no present or not specified in the Service object profile or on the Service object Subset Viewer.
All Subset Viewers and Object Viewers for Service Element and Service Element Profiles contain common attributes that can be specified for each object. Specifying the name for an object is mandatory. Table 10-5 shows the common attributes that can be configured for Service Elements and their associated profiles.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Name | This attribute is used to specify a name for the Service Element or Service Element profile | text strong (up to 64 characters) |
|
Domain | This is the management domain that the Service Element or Service Element profile belongs to. | Text strong (up to 16 characters) |
|
Customer | This is the customer that the Service Element or Service Element profile belongs to. This attribute is also labelled as "VPN" in both viewers. | Text string (up to 16 characters) |
|
Profile | This attribute is used to specify a profile for a service element. In the Object Viewer, a pull down menu is used to select from a range of profiles that have been created for a specific Service Element. If no profile is selected, a default profile is used. |
|
|
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco DSL 6400 Equipment Module folder to open it.
Step 4 Click the folder that represents the service element profile you want to create (for example, Cisco DSL 6400 Logical Port Profile) to highlight it.
Step 5 Click the Subset Viewer button on the toolbar.
Step 6 Enter a Name for the profile and enter the appropriate attribute values in the available row of cells.
Step 7 Save the profile by clicking the save button on the toolbar.
Step 8 To specify other attributes, click the row to highlight it and click the Object Viewer button on the toolbar. For more information about the configurable attributes and their values, refer to the attribute tables in this section.
Step 9 Save the profile by clicking the save button on the toolbar.
Step 10 Apply the Transaction by clicking the apply button on the toolbar.
|
Note Attribute fields in the Subset Viewer can be added, modified and deleted if required. Refer to the section "Customization" in the chapter titled "GUI Navigation" for more information on customizing the Subset Viewer. |
To modify a service element profile, complete the following steps"
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco DSL 6400 Equipment Module folder to open it.
Step 4 Click the folder that represents the service element profile you want to modify (for example, Cisco DSL 6400 Logical Port Profile) to highlight it.
Step 5 Click the Subset Viewer button on the toolbar.
Step 6 Click on the get list button on the toolbar to get a list of profiles.
Step 7 Click on the profile and modify the values in the available row of cells.
Step 8 Save the profile by clicking the save button on the toolbar.
Step 9 To specify other attributes, highlight the row and click the Object Viewer button on the toolbar. For more information about the configurable attributes and their values, refer to the attribute tables in this section.
Step 10 Save the profile by clicking the save button on the toolbar.
Step 11 Apply the Transaction by clicking the apply button on the toolbar.
To delete a service element profile, complete the following steps:
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco DSL 6400 Equipment Module folder to open it.
Step 4 Double-click on the type of profile that you want to delete (for example, CIsco DSL 6400 Logical Port Profile).
Step 5 Click specific profile to highlight it.
Step 6 Click on the delete button on the toolbar.
Step 7 Apply the Transaction by clicking the apply button on the toolbar.
The physical port profile provides you with access to the additional attributes that you can configure for a physical port. The information you provide in the physical port profile is communicated back to the Cisco 6400 through the Equipment Module and helps to define the type of service you are provisioning in the network.
Figure 10-1 shows the Physical Port Profile
Subset Viewer.
Table 10-6 below lists the configurable attributes for the physical port profile. Attributes with an asterisk "*" next to their Default value indicates that these fields should not be changed.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
Port Type | Specify the port type. | DS3, OC3, Internal | DS3 |
Bandwidth (kbits/s) | The bandwidth for the physical port. | 0-2147483647 | DS3 |
Max PDU size (bits) | The maximum PDU size. | 0-2147483647 |
|
Subscriber Id | The Subscriber Id. | Text string (up to 32 characters) | 53 |
Class | The object class name. | Text string (up to 4 characters) | C4pp |
Service Object Id | The service object Id. | Text string (up to 44 characters) |
|
6400 Physical Port Parameters | |||
Access Name | The access name. | Text string (up to 32 characters) |
|
Access Password | Specify the Access password. | Text string (up to 32 characters) |
|
Enable Password | Specify the Enable password. | Text string (up to 32 characters) |
|
NRP IP Address | Specify the Node Routing Processor address. | Text string (up to 15 characters) |
|
The logical port profile provides you with access to the attributes that you can configure for a logical port. The information you provide in the logical port profile is communicated back to the Cisco 6400 through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create logical port profiles, the Equipment Module will communicate the values specified in the default logical port profile.
Figure 10-2 shows the Logical Port Profile Object Viewer.
Table 10-7 below lists the configurable attributes for the logical port profile.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
Protocol | Specify the protocol. | ATM | ATM |
Signalling Role | A DCE logical port represents the "network side" equipment. This logical port type supports all types of PVs. A DTE is almost identical to the DCE logical port except for SVC applications. It assumes the role of the "user side" of the UNI signalling interface. | DCE, DTE | DCE |
NNI Enable | You can enable or disable NNI for the logical port. | TRUE, FALSE | FALSE |
Admin Status | Specify the administrative status for the logical port. | ShuttingDown, Unlocked, Locked | Unlocked |
Maximum Connections | Specify the maximum number of connections for the logical port. For internal ports it is 2048. | 0-2147483647 | 0 |
Service Object Id | The service object Id that owns this service element. | Text string (up to 44 characters) |
|
Class | The CPC class for this logical port object. | Text string (up to 4 characters) | C4ip* |
Resource Map | The resource map ATM-ATM is supported | 0-2147483647 | 16 |
Peer Logical Port | Specify the peer logical port (nodename/portname). | Text string (up to 40 characters) |
|
QoS | Specify the Quality of Service |
|
|
Group | Specifies the logical group membership. Allows several logical ports to be put in a common group as a pooled resource. | Text string (up to 32 characters) |
|
Priority | The logical port usage priority. | 0-2147483647 | 0 |
Multiple Ranges | Specify whether or not to enable or disable multiple ranges. | TRUE, FALSE | FALSE |
EMS Name | This is the name of the Element Management System. | Text string (up to 65 characters) |
|
Bandwidth | |||
Incoming Maximum (kbits/s) | The maximum incoming bandwidth for the logical port. | 0-2147483647 |
|
Incoming Nominal Threshold (%) | Specify the incoming committed bandwidth nominal threshold percentage. | 0-100 | 100 |
Incoming Committed (kbits/s) | The incoming committed bandwidth is auto-calculated based on the nominal threshold and bandwidth. | 0-2147483647 | 0* |
Outgoing Maximum (kbits/s) | The maximum outgoing bandwidth for the logical port. | 0-2147483647 |
|
Outgoing Nominal Threshold (%) | Specify the outgoing committed bandwidth nominal threshold percentage | 0-2147483647 | 100 |
Outgoing Committed (kbits/s) | The outgoing committed bandwidth is auto-calculated based on the nominal threshold and bandwidth. | 0-2147483647 | 0 |
6400 NRP Specific | |||
Routing | Specify whether or not to enable or disable routing. | TRUE, FALSE | TRUE |
Tunneling | Specify whether or not to enable or disable tunneling. | TRUE, FALSE | FALSE |
Multihopping | Specify whether or not to enable or disable multihopping. | TRUE, FALSE | FALSE |
IOS Version | Specifies the IOS version being used. | Text string (up to 16 characters) |
|
Maximum Internal Connections | Specifies the maximum number of internal connections for the logical port. | 0-2147483647 | 2048 |
Primary RADIUS Server | Specifies the primary RADIUS server. | Text string (up to 32 characters) |
|
Backup RADIUS Server | Specifies the backup RADIUS server. | Text string (up to 32 characters) |
|
The Cross-Connection service element profile provides you with access to the additional attributes that you can configure for a cross connection through the Cisco 6400. The information you provide in the service element profile is communicated to the Cisco 6400 through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create a profile, the Equipment Module will communicate the values specified in the default profile.
Figure 10-3 shows the Cross-Connection Profile Object Viewer.
Table 10-8 below lists the configurable attributes for the service element profile. Attributes with an asterisk "*" next to their Default value indicates that these fields should not be changed.
| Attributes Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
Recovery Priority | This is the recovery priority for NNI resiliency. | The lower the value, the higher the priority; 0 having indefinitely low priority; (default=5) | 0 |
UNI Recovery Priority | This is the recovery priority for UNI resiliency. | The lower the value, the higher the priority; 0 having infinitely low priority; (default =5) | 0 |
Provider Service | This is the Provider Service. | Text string (up to 32 characters) |
|
Service Object Id | This is the service object Id. | Text string (up to 44 characters) |
|
ATM LPort Associations | |||
A Endpoint VCI | This is the VCI for the A endpoint. If you want to let CPC auto-select the VPI, enter 0. | 0-4096 | 0 |
A Endpoing VPI | This is the VPI for the A endpoint. If you want to let CPC auto-select the VPI, enter -1. | -1-255 | -1 |
Z Endpoing VCI | This is the VPI for the Z endpoint. If you want to let CPC auto-select the VPI, enter 0. | 0-4096 | 0 |
Z Endpoint VPI | This is the VPI for the Z endpoint. If you want to let CPC auto-select the VPI, enter -1. | -1-255 | -1 |
ATM Attributes | |||
Circuit Type | This is the circuit type. | VC, VP | VC |
Class of Service | You can specify the class of service for traffic. The class of service determines which traffic descriptor you can select. | CBR, ABR, UBR, rt_VBR, nrt_VBR | CBR |
Fixed Round-Trip Time | This attribute specifies the round-trip time in milliseconds. | 0-16700000 | 0 |
Bandwidth (kbits/s) | This is the bandwidth. | 0-2147483647 |
|
Primary logical port | The original logical port that is being backed up by UNI resiliency (nodename/portname). | Text string (up to 44 characters) |
|
Susbtainable Cell Rate (cells/s) | SCR is the maximum average cell transmission rate that is allowed over a given period of time on a given circuit. It allows the network to allocate sufficient resources for guaranteeing the network performance objectives are met. | 0-2147483647 | 0 |
Peak Cell Rate (cells/s) | PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell lose ratio) will be met. | 0-2147483647 | 0 |
Minimum Cell Rate (cells/s) | MCR is the minimum cell rate, which is the minimum allocated bandwidth for a connection. | 0-2147483647 | 0 |
Maximum Burst Size (cells) | MBS is the maximum number of cells that can be received at the PCR. This allows a burst of cells to arrive at a rate higher than the SCR. If the burst is larger than anticipated, the additional cells are either tagged or dropped. This parameter applies only to VBR traffic. | 0-2147483647 | 0 |
CDVT (microseconds) | Cell Delay Variation Tolerance establishes the time scale over which the PCR is policed. This is set to allow for jitter (CDV). | 0-2147483647 | 0 |
Traffic Desc | This is the traffic descriptor type which describes the specified traffic parameters for the service (for more information see the chapter titled "Provisioning ATM Services") | None, ABR_FC, ABR_NFC, CBR.1, UBR.1, UBR.2, VBR.1, VBR.2, VBR.3, Other | None |
The NRP Internal PVC profile provides you with access to the additional attributes that you can configure for a service through the Cisco 6400. The information you provide in the Service element profile is communicated back to the Cisco 6400 through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create Service element profiles, the Equipment Module will communicate the values specified in the default Service element profile.
Figure 10-4 shows the NRP Internal PVC Service Element Profile Object Viewer.
Table 10-9 below lists the configurable attributes for the service element profile. Attributes with an asterisk "*" next to their Default value indicates that these fields should not be changed.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
6400 NRP Specific Attributes | |||
Name | This is the Network Connection name. | Text string (up to 30 characters) |
|
CNX Type | Specify the CNX type. | subscriber, service, multihop_inother | other |
Service Name | This is the service name key that associates a subscriber with a tunnel. This attribute is required if static binding is configured. | Text string (up to 32 characters) |
|
Sub-interface Number | Specify the sub-interface number. This value will be generated automatically if -1 is specified. | 0-2147483647 | -1 |
Sub-interface IP Address | Specify the sub-interface IP address. | Text string (up to 15 characters) |
|
Sub-interface Network Mask | Specify the sub-interface network mask. | Text string (up to 15 characters) |
|
Broadcast | Specify whether or not to enable or disable broadcasting. | TRUE, FALSE | TRUE |
Circuit Type | This is the circuit type. | VC | VC |
VPI | The Virtual Path Identifier | 0-2147483647 | 0 |
VCI | The Virtual Channel Identifier | 0-2147483647 | 0 |
PVC Mapping on IP (Only for Service CNX) | |||
Next-Hop IP Address | IP Address of the Next-Hop if broadcast is TRUE. If broadcast if FALSE, it is the ISP IP address. | Text string (up to 15 characters) |
|
VC Class Attributes | |||
QoS Class | Specify the QoS class. | UBR+ | UBR+ |
Peak Cell Rate | PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell loss ratio) will be met. | 0-2147483647 | 140 |
Minimum Cell Rate (cells/s) | MCR is the minimum cell rate, which is the minimum allocated bandwidth for a connection. | 0-2147483647 | 0 |
NRP->NSP Bandwidth | The bandwidth from the NRP to the NSP. | 0-2147483647 | o |
NSP->NRP | The bandwidth from the NSP to the NRP. | 0-2147483647 | 0 |
Encapsulation | Specify the encapsulation type. | aal5ciscopp, aal5snap, aal5mux | aal5ciscoppp |
Virtual Template Attributes | |||
Authentication Type | This is the authentication type. When none is selected, no authentication will be performed. Selecting pap will use Password Authentication Protocol to authenticate the tunnel. Selecting chap will use Challenge Handshake Authentication Protocol to authenticate the tunnel. | none, pap, chap | none |
The virtual template object in CPC corresponds with the IOS Virtual Template object, allowing you to create virtual template interfaces on the NRP. Virtual template interfaces can be uploaded from the 6400 or created and deleted in CPC.
To create a virtual template, perform the following procedure:
Step 2 Double-click the Cisco DSL Network folder and double-click the specific network.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port.
Step 5 Click the Cisco DSL 6400 Virtual Template folder to highlight it and click the Subset Viewer button on the toolbar.
Step 6 Enter the required information in the available row of cells. See Table 10-10 for more information about these attributes.
Step 7 Save the virtual template by clicking the save button the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Virtual Template Index | This is the virtual template index number that is auto assigned by IOS. | 0-2147483647 | 0 |
Authentication Type | This is the authentication type. When none is selected, no authentication will be performed. Selecting pap will use Password Authentication Protocol to authenticate the tunnel. Selecting chap will use Challenge Handshake Authentication Protocol to authenticate the tunnel. | none, pap, chap | none |
Node | This is the node that contains the virtual template. | Text string (up to 32 characters) |
|
LPort | This is the logical port (NRP) that contains the virtual template. | Text string (up to 32 characters) |
|
Virtual Circuit Class (VC Class) assignment is used to associate a set of VC parameters for a particular interface or subinterface. VC classes must be established in order to create NRP internal PVCs. These PVCs use a VC class to determine QoS, encapsulation, and bandwidth parameters. Modification of a VC Class causes modification of the bandwidth and encapsulation information for each cross-connection, therefore you can only create and delete VC classes in CPC.
VC classes can be uploaded directly from the NRP as a part of a node upload or created/deleted in CPC. To create or delete a VC class, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific network.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node.
Step 4 Double-click the Cisco DSL 6400 Node folder and double-click the specific node.
Step 5 Click the Cisco DSL 6400 VC Class folder to highlight it and click the Object Viewer button on the toolbar.
Step 6 Enter the appropriate values under the Common Attributes, VC-Class Parameters, and Contained By tabs. Refer to Table 10-11 for attribute information.
Step 7 Save the VC Class by clicking the save button the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
VC-Class Parameters | |||
VC-Class Name | Specify the VC-Class name. | Text string (up to 16 characters) |
|
Service Name | This is the service name key that associates a subscriber with a tunnel. | Text string (up to 32 characters) |
|
QoS | This is the quality of service. | UBR+ | UBR+ |
Peak Cell Rate (cells/s) | PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell loss ratio) will be met. | 0-2147483647 | 0 |
Minimum Cell Rate (cells/s) | MCR is the minimum cell rate, which is the minimum allocates bandwidth for a connection. | 0-2147483647 | 0 |
NRP-NSP Bandwidth (kbits/s) | This is the bandwidth in cells/s from the NRP to the NSP. | 0-2147483647 | 0 |
NSP-NRP Bandwidth (kbits/s) | This is the bandwidth in cells/s from the NSP to the NRP. | 0-2147483647 | 0 |
Encapsulation | This is the encapsulation type. | aal5ciscoppp,aal5mux, aal5snap | aal5ciscopp |
Virtual Template Parameters | |||
Authentication Type | This is the authentication type. When none is selected, no authentication will be performed. Selecting pap will use Password Authentication Protocol to authenticate the tunnel. Selecting chap will use Challenge Handshake Authentication Protocol to authenticate the tunnel. | none, pap, chap | none |
Contained By | |||
Node | This is the node that contains the VC Class. | Text string (up to 32 characters) |
|
c4vt.vtindex | This is a pointer to the virtual template. | Text string (up to 32 characters) |
|
NRP internal PVCs can be uploaded from an NRP on the 6400 or created, modified, or deleted within CPC. Profiles can be created for cross-connects allowing you to create a custom template in order to use the cross-connect as a subscriber downlink, incoming tunnel for PPP aggregation, or service uplink with tunnel support.
NRP internal PVCs are associated only with the internal logical port on an NRP. This logical port is considered the Z endpoint of a NSP cross-connect. The internal PVC is associated with the corresponding cross-connect on the NSP through the VCI/VPI of the internal logical port.
Internal PVCs are automatically created as a part of binding a subscriber stream to a tunnel (service uplink) during a single hop tunnel provisioning. They can also be created as a part of binding an incoming tunnel to an outgoing tunnel during multihop provisioning and as part of the creation of a service uplink followed by tunnel creation which is configured through the DSL Service Application.
When NRP internal PVD is provisioned as a part of binding a subscriber stream to a tunnel, certain sub-interface attributes and other attributes that are used in the provisioning of a next hop are defaulted to zero or null because these attributes are not needed. If static domain binding is used during the creation of a single hop tunnel, the service name attribute must be supplied for the PVC.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port folder.
Step 5 Click the Cisco DSL 6400 NRP Internal PVC folder to highlight it and click the Object Viewer button on the toolbar.
Step 6 Enter the appropriate values under the Common Attributes, VC-Class Parameters, and Contained/Carried By, and 6400 NRP Specific tabs. Refer to Table 10-12 for attribute information.
Step 7 Save the Internal PVC Class by clicking the save button the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Contained/Carried By | |||
Network | This is the network that contains the NRP internal PVC. | Text string (up to 32 characters) |
|
Node | This is the node that contains the NRP internal PVC. | Text string (up to 32 characters) |
|
c4acl_acl_id | This is the Access Control List Id. An access control list contains Access Control Elements that define packet filtering information in order to limit the accessibility of interfaces or subinterfaces on an NRP. | 100-199, 2000-2699 |
|
6400 NRP Specific | |||
Name | Specify a name for the NRP internal PVC. | Text string (up to 30 characters) |
|
CNX Type | Specify the connection type. This attribute is used to determine what function the internal PVC will have. An NRP internal PVC can serve several roles. It can be a subscriber downlink involved in binding a subscriber stream to a tunnel, an ingress tunnel for multihop PPP aggregation, or a service uplink with tunnel support. | subscriber, service, multihop_in, other | other |
Service Name | This is the service name key that associates a subscriber with a tunnel. This attribute is required if static binding is configured. | Text string (up to 32 characters) |
|
Sub-interface | Specify the sub-interface IP number. | 0-2147483647 | -1 |
Sub-interface IP Address | Specify the sub-interface network mask. | Text string (up to 15 characters) |
|
Sub-interface Network Mask | Specify the sub-interface network mask. | Text string (up to 15 characters) |
|
Broadcast | Specify whether broadcasting should be enabled or disabled. | TRUE, FALSE | TRUE |
Circuit Type | This is the circuit type. | VC, CP |
|
VPI | The Virtual Path Identifier | 0-2147483647 | 0 |
VCI | The Virtual Channel Identifier | 0-2147483647 | 0 |
PVC Mapping on IP (Only for Service CNX) | |||
Next-Hop IP Address | IP Address of the Next-Hop if broadcast is TRUE. If broadcast if FALSE, it is the ISP IP address. | Text string (up to 15 characters) |
|
VC Class Attributes | |||
QoS Class | Specify the QoS class. | UBR+ | UBR+ |
Peak Cell Rate | PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell loss ratio) will be met. | 0-2147483647 | 140 |
Minimum Cell Rate (cells/s) | MCR is the minimum cell rate, which is the minimum allocated bandwidth for a connection. | 0-2147483647 | 0 |
NRP->NSP Bandwidth | The bandwidth from the NRP to the NSP. | 0-2147483647 | o |
NSP->NRP | The bandwidth from the NSP to the NRP. | 0-2147483647 | 0 |
Encapsulation | Specify the encapsulation type. | aal5ciscopp, aal5snap, aal5mux | aal5ciscoppp |
Virtual Template Attributes | |||
Authentication Type | This is the authentication type. When none is selected, no authentication will be performed. Selecting pap will use Password Authentication Protocol to authenticate the tunnel. Selecting chap will use Challenge Handshake Authentication Protocol to authenticate the tunnel. | none, pap, chap | none |
The Cisco DSL 6400 Equipment Module allows you to configure IOS QoS parameters for NSP internal PVCs. QoS and specific PVC traffic parameters can be configured in CPC and translated into IOS commands in the NSP.
The following service categories are supported: Non Real-Time Variable Bit rate (nrt_VBR), Real-Time Variable Bit Rate (rt_VBR), Available Bit Rate (ABR), Unspecified Bit Rate (UBR) and Constant Bit Rate (CBR).
IOS QoS parameters can be created and deleted using CPC. Deletion of an IOS QoS index is permitted only it is not associated with an NSP internal PVC. No modification is allowed once an IOS index is created. Different NSP internal PVCs sharing the same QoS parameters must share the same IOS QoS index.
To configure IOS QoS, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 IOSQoS folder to highlight it and clickObject Viewer button on the toolbar.
Step 5 Enter the appropriate values under the Common Attributes, IOS QoS Parameters, and Contained By tabs. Refer to Table 10-13 for attribute information.
Step 6 Save the QoS by clicking the save button the toolbar.
Step 7 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
IOS QoS Parameters | |||
Quality of Service | This is the quality of service (QoS). | none, nrt_VBR.1, nrt_VBR, rt_VBR, rt_VBR.1, ABR, UBR, CBR | CBR |
SCR (cells/s) | SCR is the maximum average cell transmission rate that is allowed over a given period of time on a given circuit. It allows the network to allocate sufficient resources for guaranteeing the network performance objectives are met. | 0-2147483647 | 0 |
Peak Cell Rate (cells/s) | PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell loss ratio) will be met. | 0-2147483647 | 0 |
Minimum Cell Rate (cells/s) | MCR is the minimum cell rate, which is the minimum allocates bandwidth for a connection. | 0-2147483647 | 500 |
MBS (cells) | MBS is the maximum number of cells that can be received at the PCR. The allows a burst of cells to arrive at a rate higher than the SCR. If the burst is larger than anticipated, the additional cells are either tagged or dropped. This parameter applies only to VBR traffic. | 0-2147483647 | 0 |
CDVT (micro-seconds) | Cell Delay Variation Tolerance establishes the time scale over which the PCR is policed. This is set to allow for jitter (CDV). | 0-2147483647 | 100 |
Contained By | |||
Node | This is the node that you are configuring QoS templates on. This field is autogenerated in the Object Viewer. | Text string (up to 32 characters) |
|
NSP cross connections can be used as conventional PVC cross-connection when both associated physical ports are external (i.e., two QC3 ports) or as a PVC part of a subscriber downlink or service uplink if one of the physical ports is internal. NSP cross-connections can be created, modified or deleted within CPC or uploaded directly from the NSP on the Cisco 6400 UAC.
PVCs must be created on an NSP during the provisioning of a subscriber carrier. A subscriber carrier is a service used during single hope and multihop tunnel provisioning that prohibits data transfer from an external ATM interface on the NSP to an internal logical port on the NRP. If no tunnels are being provisioned, the PVC acts as a typical cross connect between two external physical ports on the NSP.
If a single hop or multihop tunnel is being provisioned, the PVC acts as a link between an external interface on the NSP and an internal physical port on the NRP. This links can be associated with a subscriber downlink that functions as an ingress tunnel for subscriber sessions.
Before a NSP cross-connection is created, QoS traffic, descriptor information must be specified through IOSQOS object. The IOSQOS attribute populates corresponding attributes in the NSP PVC.
To configure an NSP cross-connection, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port folder.
Step 5 Click the Cisco DSL 6400 Cross-Connection folder to highlight it and click the Object Viewer button on the toolbar.
Step 6 Enter the appropriate values under the Common Attributes, ATM LPort Associations, and ATM Attributes tabs. Refer to Table 10-14 for attribute information.
Step 7 Save the cross-connection by clicking the save button on the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
| Attributes Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Network | This is the network that contains the cross connection. | Text string (up to 32 characters) |
|
Recovery Priority | This is the recovery priority for NNI resiliency. | the lower the value, the higher the priority; 0 having infinitely low priority | 0 |
UNI Recovery | This is the recovery priority for UNI resiliency. | integer; same as NNI Recovery Priority | 0 |
Provider Service | This is the provider service associated with this cross connection. | Text string (up to 32 characters) |
|
Service Object Id | This is the service object Id. This field is autogenerated. |
|
|
ATM LPort Associates (A Endpoint) | |||
Local Node | This is the node (6400 chassis) containing the A endpoint. | Text string (up to 32 characters) |
|
Local Port | This is the logical port designated as the A endpoint of the cross-connection. | Text string (up to 32 characters) |
|
A VCI | This is the VCI for the A endpoint. If you want to let CPC auto-select the VPI, enter 0. | 0-4096 | 0 |
A VPI | This is the VPI for the A endpoint. If you want to let CPC auto-select the VPI, enter -1. | -1-255 | -1 |
ATM LPort Associations (Z Endpoint) | |||
Remote Node | This is the node (6400 chassis) containing the Z endpoint. | Text string (up to 32 characters) |
|
Remote LPort | This is the logical port designated as the Z endpoint of the cross-connection. | Text string (up to 32 characters) |
|
Z VCI | This is the VCI for the Z endpoint. If you want to let CPC auto-select the VPI, enter 0. | 0-4096 | 0 |
Z VPI | This is the VPI for the Z endpoint. If you want to let CPC auto-select the VPI, enter -1. | -1-255 | -1 |
An access control list (ACL) is required to limit the accessibility of interfaces or subinterfaces on an NRP.
ACLs are composed of Access Control Elements (ACEs) that define packet filtering information. ACEs will be detailed in the next section.
An ACL must be created before associating it with a particular NRP internal cross connection. To create an ACL for a specific interface or sub-interface, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port folder.
Step 5 Click the Cisco DSL 6400 Access Control List folder to highlight it and click the Object Viewer button on the toolbar.
Step 6 Enter the appropriate values under the Common Attributes, Control List Parameters, and Contained/Carried By tabs. Refer to Table 10-15 for attribute information.
Step 7 Save the ACL by clicking the save button on the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
Once an ACL is created, the only attribute that can be modified is the name that you have assigned it. The name attribute does not get delivered to IOS. To modify the name, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port folder.
Step 5 Click the Cisco DSL 6400 Access Control List folder and click the specific ACL that you want to change the name for.
Step 6 Click the Object Viewer on the toolbar.
Step 7 Click the Control List Parameters tab and click the Description field. Enter the new name.
Step 8 Save the new name by clicking the save button on the toolbar.
Step 9 Apply the Transaction by clicking the apply button on the toolbar.
Deletion of an ACL should not be performed if there are one or more NRP Internal PVCs associated with it. If you delete an ACL, you will delete all ACEs (Access Control Elements) that are associated with it. To delete an ACL, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port folder.
Step 5 Click the Cisco DSL 6400 Access Control List folder to highlight it and click the specific ACL that you want to delete.
Step 6 Click the delete button on the toolbar.
Step 7 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Control List Parameters | |||
Access Control List ID | This is the Access Control List Id. If a value of 0 is specified, the Equipment Module will autogenerate the Id. | 100-199, 2000-2699 | 0 |
Description | This is a name that you can specify for the ACL. This attribute does not get delivered to IOS. | Text string (up to 64 characters) |
|
Contained/Carried By | |||
LPORT | This is the logical port (NRP) which the ACL is provisioned on. | Text string (up to 32 characters) |
|
Node | This is the node (6400 chassis) that contains the NRP. | Text string (up to 32 characters) |
|
Network | This is the network that contains the 6400 UAC. | Text string (up to 32 characters) |
|
Access Control Elements (ACEs) define packed filtering information for ATM interfaces and subinterfaces on the Cisco 6400 NRP. For a particular interface or subinterface, the ACE specifies:
To create an ACE for a particular ACL, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port folder.
Step 5 Click the Cisco DSL 6400 Access Control List folder to highlight it and click the specific access control list.
Step 6 Click the Cisco DSL 6400 Access Control List Element folder and click the Object Viewer button on the toolbar.
Step 7 Enter the appropriate values under the Common Attributes, Access Control Element Parameters, and Contained By tabs. Refer to Table 10-16 for attribute information.
Step 8 Save the ACE by clicking the save button on the toolbar.
Step 9 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Access Control Element Parameters | |||
Service Name | This is the protocol/service that is permitted on the interface or subinterface. You can permit UDP datagrams and the ICMP ping command. | none, udp_1024, icmp_ping | none |
Source Type | This is the type of source of the packets to be filtered. This will be automatically changed to "any" if a mask of 255.255.255.255 is specified, or "host" if a mask of 0.0.0.0 is specified. | host, specific, any | specific |
Source IP | This is the IP address of the source of the packets. | Text string (up to 15 characters) |
|
Source Mask | This is the wildcard for the source IP address. Each subfield of the address can only be set to 255 or 0. | Text string (up to 15 characters) |
|
Destination Type | This is the type of destination of the packets to be filtered. This will be automatically changed to "any" if a mask of 255.255.255.255 is specified, or "host" if a mask of 0.0.0.0 is specified | host, specific, any | specific |
Destination IP | This is the IP address of the destination of the packets. | Text string (up to 15 characters) |
|
Destination Mask | This is the network mask for the destination IP address. Each subfield of the address can only be set to 255 or 0. | Text string (up to 15 characters) |
|
Contained By | |||
Access Control List | This is the Access Control List that contains this ACE. This field is autogenerated. | Text string (up to 32 characters) |
|
NRP Name | This is the NRP on which the ACE is provisioned. This field is autogenerated. | Text string (up to 32 characters) |
|
Node Name | This is the 6400 chassis containing the NRP. This field is autogenerated. | Text string (up to 32 characters) |
|
Network Name | This is the network containing the 6400 UAC. This field is autogenerated. | Text string (up to 32 characters) |
|
When you modify an ACE in CPC, the CL in IOS will be deleted and then recreated with the new element values. To modify an ACE, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port folder.
Step 5 Click the Cisco DSL 6400 Access Control List folder to highlight it and click the specific access control list.
Step 6 Click the Cisco DSL 6400 Access Control List Element folder and click the Object Viewer button on the toolbar.
Step 7 Perform the modifications
Step 8 Save the modified ACE by clicking the save button on the toolbar.
Step 9 Apply the Transaction by clicking the apply button on the toolbar.
Deletion of an access control elements is handled differently according to the number of ACEs in the ACL. If the ACE to be deleted is the only one associated with a particular ACL, CPC will instruct the NIF to delete the ACL from the NRO. If an ACL has more than one associated ACE, CPC will instruct the NIF to delete the ACL from the NRP and then recreate it without the ACE that has been deleted. To delete an ACE from an ACL, perform the following procedure:
Step 2 Double-click the Cisco DSL Network folder and double-click the specific Cisco DSL network folder.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node folder.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port folder.
Step 5 Double-click the Cisco DSL 6400 Access Control List folder t and double-click the specific access control list.
Step 6 Double-click the Cisco DSL 6400 Access Control List Element folder and click the specific ACE that you want to delete.
Step 7 Click the delete button on the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
Subscriber streams can be aggregated into tunnels for more efficient use of backbone PVCs. There are two types of aggregation that can be achieved: single hope and multihop. Single hop aggregation concentrates PPP sessions from a subscriber into a L2TP tunnel for more efficient use of high performance DSL networking hardware. Multihop tunneling enhances this economy by aggregating L2TP tunnels into a larger tunnel.
Tunneling is used to optimize the usage of backbone PVCs by multiplexing PPP sessions within L2TP tunnels. By tunnelling PPP sessions, fewer PVCs are required. Single hop aggregation occurs if a subscriber's PVCs are aggregated once into a tunnel. If PVCs are aggregated more than once into larger tunnels, the aggregation is considered multihop.
A single hop outgoing tunnel is first created on a 6400 which acts as the L2TP Access Concentrator (LAC). The LAC acts as an aggregation point for subscriber PPP sessions. Single hope outgoing tunnels are recorded in the RADIUS server. The tunnels reside on the RADISU server and do not belong to a particular 6400 device. Only dial-out (outgoing) tunnels are recorded on the RADIUS server.
A single hop tunnel is created on the RADIUS server after an L2TP Subscriber Aggregation Point Service has been successfully provisioned using the DSL Service Application.
To create a single hop tunnel, perform the following procedure:
Step 2 Double-click the Cisco DSL 6400 RADIUS Server folder.
Step 3 Double-click the specific RADIUS server.
Step 4 Click the Cisco DSL 6400 Single hop Tunnel folder and click the Object Viewer button on the toolbar.
Step 5 Enter the appropriate values under the Common Attributes, Tunnel Specific Parameters, and Contained/Carried By tabs. Refer to Table 10-17 for attribute information.
Step 6 Save the tunnel by clicking the save button on the toolbar.
Step 7 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Tunnel Specific Parameters | |||
Service Name | This is the service name key that associates a subscriber with a tunnel. | Text string (up to 32 characters) |
|
Dial In/Out | This specifies whether the tunnel is dial in, dial out, or other. Dial in tunnels refer to MHITs. Dial out tunnels refer to multihop egress tunnels (MHETs). Other refers to various VPDN groups that are out of the MHIT provisioning scope. | other, dial_out_s | other |
Tunnel Type | This is the tunnel type. This can be either layer 2 tunneling protocol or layer 2 forwarding. | l2tp, 12f | l1tp |
Tunnel Name | This is the tunnel name that is required for authentication at a remote site. | Text string (up to 64 characters) |
|
Tunnel Password | This is the tunnel password that is required for authentication at a remote site. | Text string (up to 32 characters) |
|
Contained/Carried By | |||
Radius | This is the RADIUS server hostname that contains the single hop tunnel. | Text string (up to 32 characters) |
|
Before multiple subscriber streams can be aggregated, authentication must occur to associate a stream with a tunnel. CPC supports two methods of authentication for single hop tunnels:
Step 2 Dynamic Binding--This subscriber is dynamically bound to the tunnel with service filtration. Dynamic binding supports multi-destination selection.
Static Domain binding uses the Service Name key specified during the creation of a subscriber to bind a subscriber's traffic to a particular tunnel. Within this tunnel, the service name attribute overrides the domain provided in the PPP sessions. The NRP uses this service name to query the RADIUS database for subscriber authorization.
Dynamic binding relies on the analysis of a username and a service name associated with a specific PPP session to authenticate the subscriber. If a subscriber is not statically bound to a tunnel, the 6400 will conduct dynamic tunnel service authorization by performing two steps:
Step 2 Tunnel Service Authorization--The user profile on the RADIUS server contains a list of domains accessible to the user, enabling tunnel service authorization for the client-supplied domain. If successful, the LAC established an L2TP tunnel.
Service Lists for domain preauthorization can be uploaded from the RADIUS server, and additional entries can be created, modified, and deleted using CPC. Performing an upload of the RADIUS server includes the upload of associated Service Lists. To add, modify, or delete a service to the Service List, perform the following procedure.
Step 2 Double-click the Cisco DSL 6400 RADIUS server folder and double-click the specific RADIUS server that contains the Service List that you want to modify.
Step 3 Click the Cisco 6400 DSL Service List folder and click the Subset Viewer button on the toolbar.
Step 4 Click the get list button on the toolbar to populate the Subset Viewer.
Step 5 To create a new entry:
a. Enter the required information in the Subscriber ID and Service Name fields. See Table 10-18 for information on these attributes.
b. Save the new entry by clicking the save button on the toolbar.
c. Apply the Transaction by clicking the apply button on the toolbar.
To modify an entry:
a. Modify the required information in the Subscriber ID and Service Name fields. Repeat for all necessary modifications.
b. Save the new entry by clicking the save button on the toolbar.
c. Apply the Transaction by clicking the apply button on the toolbar.
To delete an entry:
a. Click the entry (row) to highlight it.
b. Click the delete button on the toolbar. Repeat for all entries that you want to delete.
c. Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Subscriber ID | This is the subscriber ID. | Text string (up to 32 characters) |
|
Service Name | This is the service name key that associates a subscriber with a tunnel. | Text string (up to 32 characters) |
|
Radius | This is the RADIUS server. This field is autogenerated in the Object Viewer and the Subset Viewer. | Text string (up to 32 characters) |
|
Once a tunnel has been created, a tunnel destination must be specified. A tunnel can have multiple destinations and each destination is treated as a separate object within the CPC database. A tunnel must have at least one tunnel destination which includes a destination IP address (specifying the L2TP Network Server (LNS) and a session limit that specifies the maximum number of sessions permitted for each tunnel. The priority of the IP address can be optionally specified.
A single hop tunnel destination object will be created as a result of provisioning an L2TP Destination Service using the DSL Service Application.
To configure a single hop tunnel destination, perform the following procedure:
Step 2 Double-click the Cisco DSL 6400 RADIUS Server folder.
Step 3 Double-click the specific RADIUS server.
Step 4 Double-click the Cisco DSL 6400 Single hop Tunnel folder.
Step 5 Double-click the specific tunnel to configure a destination.
Step 6 Click the Cisco DSL 6400 Tunnel Destination folder and click the Object Viewer on the toolbar
Step 7 Enter the appropriate values under the Common Attributes, Authenticator Specific Parameters, and Contained/Carried By tabs. Refer to Table 10-19 for attribute information.
Step 8 Save the tunnel by clicking the save button on the toolbar.
Step 9 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Tunnel Specific Parameters | |||
Destination IP Address | This is the destination IP address (IP address of the LNS server). This is the termination point for the L2TP tunnel where PPP sessions are processed and passed on to higher layer protocols. | Text string (up to 15 characters) |
|
Session Limit | This is the maximum number of PPP sessions that can run over the tunnel. | Text string |
|
Priority | This is the priority of the tunnel destination IP address. 1 is the highest value that can be specified, and 0 is the lowest. | 0-32767 | 100 |
Contained/Carried By | |||
Tunnel | This is the tunnel. | Text string (up to 32 characters) |
|
RADIUS | This is the name of the RADIUS server that acts as the depositor of the tunnel. | Text string (up to 32 characters) |
|
The Cisco DSL 6400 Equipment Module supports the creation of multihop tunnels to aggregate PPP session between several access concentrators. Multihop tunneling improves the economy of ATM PVCs by concentrating traffic across them.
Unlike single hop tunnels that are registered on a RADIUS server, multihop tunnels are configured on the NRP IOS on the 6400.
CPC allows you to create a Multihop Ingress Tunnel (MHIT) and a Multihop Egress Tunnel (MHET) to aggregate subscriber traffic. MHITs are dial-in tunnels on a multihop enabled Cisco 6400 and can be considered the endpoint of the SHT. When a MHIT is created, a logical connection must be established with a corresponding SHT which represents its "other half". The remote tunnel must name on an MHT must be identical to the tunnel name of the SHT to make this connection. An MHIT is created upon successful provisioning of an L2TP Subscriber Aggregation Point Service with the aggregation type L1TP using the DSL Service Application.
The MHET aggregates MHITs by creating aggregation key objects. Aggregation keys can be specified as either a domain or a tunnel name. If multihop aggregation is to be performed by using the tunnel name as the aggregation type, the aggregation key must be identical to the remote tunnel name of the MHIT and the tunnel name of the SHT. An MHET is created upon successful provisioning of an L2TP Subscriber Aggregation Point Service with an aggregation type L2TPTAP using the DSL Service Application.
To create a multihop tunnel, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific network.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port.
Step 5 Click the CISCO DSL 6400 Multihop Tunnel folder and click the Object Viewer on the toolbar.
Step 6 Enter the appropriate values under the Common Attributes, Authenticator Specific Parameters, and Contained/Carried By tabs. Refer to Table 10-20 for attribute information.
Step 7 Save the tunnel by clicking the save button on the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Tunnel Specific Parameters | |||
VPDN GROUP | This is the group number for Virtual Private Dial-Up Networking (VPDN). This value can be specified manually or autogenerated if left blank. | Text string up to (32 characters)
|
|
Tunnel Name | This is the tunnel name that is required for authentication at a remote site. | Text string up to (64 characters)
|
|
Tunnel Password | This is the tunnel password that is required for authentication at remote site. | Text string up to (32 characters)
|
|
Remote Tunnel Name | This is the tunnel name for a counterpart tunnel on the L2TP Access Concentrator (LAC) at the next hop. This attribute is required only for the creation of a multihop ingress tunnel (MHIT) | Text string up to (64 characters)
|
|
Remote Tunnel Password | This is the password used to authenticate the remote tunnel. This is attribute is required only for the creation of a MHIT. | Text string up to (32 characters)
|
|
Authentication Type | This is the authentication type. When none is selected, no authentication will be performed. Selecting pap will use Password Authentication Protocol to authenticate the tunnel. Selecting chap will use Challenge Handshake Authentication Protocol to authenticate the tunnel. For an MHIT, an authentication type must be specified. For an MHET, no authentication must be selected. | none, pap,chap | none |
Dial In/Out | This specifies whether the tunnel is dial in, dial out, or other. Dial in tunnels refer to the MHITs. Dial out tunnels refer to various VPDN groups that are out of the MHIT provisioning scope. | other, dial_out, dial_in | other |
Tunnel Type | This is the tunnel type. | 12tp, 12f | 12tp |
Contained/Carried By | |||
LPORT | This is the parent logical port for the tunnel. This field is autogenerated in the Object Viewer. | Text string up to (32 characters)
|
|
Node | This is the node containing the logical port. | Text string up to (32 characters)
|
|
Network | This is the network containing the node. | Text string up to (32 characters)
|
|
Virtual Template | This is the pointer to a virtual template. This attribute is required only when the tunnel is Dial In. | Text string up to (32 characters) |
|
Multihop tunnel destinations are required for MHETs to establish a termination point. A tunnel can have multiple destinations and each destination is treated as a separate object within the CPC database. A tunnel must have at least one tunnel destination which includes a destination IP address of the next hop (specifying the L2TP Network Server (LNS)). Optionally, a session limit can specify the maximum number of sessions permitted for each tunnel. If no session limit is defined, the NRP tunnel will try to carry as many session as possible, depending on the firmware of the NRP. The priority of the IP address can be optionally specified.
A multihop tunnel destination object will be created as a result of provisioning an L2TP Destination Service using the DSL Service Application.
To configure a multihop tunnel destination, perform the following procedure:
Step 2 Double-click the Cisco DSL Network folder and double-click the specific network.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port.
Step 5 Double-click the CISCO DSL 6400 Multihop Tunnel folder and double- click the specific multihop tunnel that you want to configure a destination for.
Step 6 Enter the appropriate values under the Common Attributes, Tunnel Destination Specific Parameters, and Contained/Carried By tabs. Refer to Table 10-21 for attribute information.
Step 7 Save the tunnel by clicking the save button on the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
MHETs use an associated key to identify which MHITs it will aggregate. The key used depends on the type of aggregation chosen. If you chose aggregation based on domain name, the key is a domain name and all tunnels originating from that domain will be aggregated into the tunnel. If tunnel name aggregation is chosen, the MHET will use MHITs with the tunnel name specified in the aggregation key. An MHET can have many keys for the aggregation of ingress tunnels based on multiple domain names or tunnel names. Aggregation keys provide a flexible way to configure the aggregation of a number of HMITs into an MHET.
MHET aggregation keys can be uploaded from the NRP for existing tunnels or created and downloaded.
MHET aggregation keys will be created in the 6400 as a result of provisioning an L2TP Tunnel Aggregation Point Service using the DSL Service Application.
To create an aggregation key for an MHET, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific network.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port.
Step 5 Double-click the CISCO DSL 6400 Multihop Tunnel folder and double-click the specific multihop tunnel that you want to create an aggregation key for.
Step 6 Click the Cisco DSL 6400 Aggregation Key folder to highlight it and click the Subset Viewer button on the toolbar.
Step 7 Enter the required information in the available row of cells. Refer to Table 10-22 for attribute information.
Step 8 Save the aggregation key by clicking the save button on the toolbar.
Step 9 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Aggregation Type Type | Specify the aggregation type. | TunnelName, Domain | TunnelName |
Aggregation Key | Specify an aggregation key. | Text string (up to 64 characters) |
|
MHET | This is the multihop egress tunnel that you are configuring an aggregation key for. This field is autogenerated. | Text string (up to 32 characters) |
|
NRP | This is the NRP on which the MHET exists. This field is autogenerated. | Text string (up to 32 characters) |
|
Node | This is the node that contains the NRP. This field is autogenerated. | Text string (up to 32 characters) |
|
Once PVCs have been configured and tunnels have been established on the NRP, static route entries can be created for IP traffic engineering purposes. A route entry is associated with a sub-interface on the NRP. A route entry will be added to the static routing table on the NRP when an IP Route Service Object is provisioned using the DSL Service Application.
To configure a route entry, perform the following procedure.
Step 2 Double-click the Cisco DSL Network folder and double-click the specific network.
Step 3 Double-click the Cisco DSL 6400 Node folder and double-click the specific node.
Step 4 Double-click the Cisco DSL 6400 Logical Port folder and double-click the specific logical port.
Step 5 Double-click the CISCO DSL 6400 Route Entry folder and double- click the Subset Viewer on the toolbar.
Step 6 Enter the required information in the available row of cells. Refer to Table 10-22 for more information about these attributes.
Step 7 Save the aggregation key by clicking the save button on the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
IP Address | Specify an IP address to be mapped. This address corresponds with the destination IP address of the tunnel. | TunnelName, Domain | TunnelName |
Netmask | Specify the network mask. | Text string (up to 15 characters) |
|
Mapping Target | Specify the target to map the IP address to. You can specify either an AUM interface or an IP address. | Text string (up to 44 characters) |
|
LPort | This is the logical port that contains the subinterface. This field is autogenerated. | Text string (up to 32 characters) |
|
Node | This is the node that contains the logical port. This field is autogenerated. | Text string (up to 32 characters) |
|
Posted: Thu Aug 3 16:40:18 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.