|
|
Table Of Contents
Shutdown Through V Commands for Cisco DSLAMs with NI-2
tag-switching request-tags for
Shutdown Through V Commands for Cisco DSLAMs with NI-2
This chapter documents commands that you use to configure Cisco DSLAMs with NI-2. Commands in this chapter are listed alphabetically. For information on how to configure DSL features, refer to the Configuration Guide for Cisco DSLAMs with NI-2.
Note
Commands that are identical to those documented in the Cisco IOS Configuration Fundamentals Command Reference and the ATM and Layer 3 Switch Router Command Reference have been removed from this chapter.
This chapter discusses the following commands:
tag-switching request-tags for
shutdown
To disable a port, use the shutdown command. To enable a port, use the no form of the command.
shutdown
no shutdown
Syntax Description
This command has no keywords or arguments.
Defaults
Enabled (no shutdown)
Command Modes
Interface configuration
Command History
Usage Guidelines
Use shutdown to disable a port. Use no shutdown to enable a disabled port.
Examples
In this example, the command enables slot 20, port 1:
DSLAM# configure terminalDSLAM(config)# interface atm 20/1DSLAM(config-if)# no shutdownRelated Commands
None.
slot
To provision a slot for a specific card type, or to change the line coding for a flexi line card, use the slot command.
slot slot# cardtype
Syntax Description
Defaults
There is no default value for this command.
Command Modes
Global configuration
Command History
12.0(5)DA
This command was introduced.
12.1(1)DA
New card types were added.
12.1(6)DA
New card types were added.
Usage Guidelines
Use the slot command to provision a slot for a line card, and to provision a flexi line card for CAP or DMT line coding.
A card mismatch error condition can occur if the specified slot contains one type of card but is provisioned for another type.
If you attempt to provision an empty slot, the major alarm PROVISIONED SLOT IS EMPTY appears.
Note
The 4xflexi line card and the 8xDMT line card are spectrally incompatible with both the 8xIDSL line card and the 4xSDSL (STU-C) line card. If you install spectrally incompatible cards in the same side of the chassis, the lines served by those cards can suffer reduced performance. For best performance in a chassis with a mixture of line card types, always install flexi or DMT cards on one side of the chassis and install IDSL and SDSL cards on the opposite side.
Examples
The command in this example provisions slot 30 for a 4xflexi DMT line card.
DSLAM# configure terminalDSLAM(config)# slot 30 ATUC-4FLEXIDMTRelated Commands
snmp-server community
To set up the community access string to permit access to the SNMP, use the snmp-server community global configuration command. The no form of this command removes the specified community string.
snmp-server community string [view view-name] [ro | rw] [number]
no snmp-server community string
Syntax Description
Defaults
By default, an SNMP community string permits read-only access to all objects.
Note
Command Modes
Global configuration
Command History
Usage Guidelines
The no snmp-server command disables all versions of SNMP (SNMPv1, SNMPv2C, SNMPv3).
The first snmp-server command that you enter enables all versions of SNMP.
Examples
The following example assigns the string comaccess to SNMP, allowing read-only access, and specifies that IP access list 4 can use the community string:
DSLAM(config)# snmp-server community comaccess ro 4The following example assigns the string mgr to SNMP allowing read-write access to the objects in the restricted view:
DSLAM(config)# snmp-server community mgr view restricted rwThe following example removes the community comaccess:
DSLAM(config)# no snmp-server community comaccessThe following example disables all versions of SNMP:
DSLAM(config)# no snmp-serverRelated Commands
access-list
Configures the access list mechanism to filter frames by protocol type or vendor code.
snmp-server contact
To set the system contact (sysContact) string, use the snmp-server contact global configuration command. Use the no form of the command to remove the system contact information.
snmp-server contact text
no snmp-server contact
Syntax Description
Defaults
No system contact string is set.
Command Modes
Global configuration
Command History
Examples
The following example shows a system contact string:
DSLAM(config)# snmp-server contact Dial System Operator at beeper # 27345Related Commands
snmp-server enable traps
To enable the DSLAM to send SNMP traps or informs (SNMP notifications), use the snmp-server enable traps global configuration command. Use the no form of this command to disable SNMP notifications.
snmp-server enable traps [notification-type] [notification-option]
no snmp-server enable traps [notification-type] [notification-option]
Syntax Description
Defaults
This command is disabled by default. Most notification types are disabled. However, you cannot control some notification types with this command.
If you enter this command with no notification-type keywords, the default is to enable all notification types that are controlled by this command.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications are sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. To specify whether the notifications should be sent as traps or informs, use the snmp-server host [traps | informs] command.
If you do not enter an snmp-server enable traps command, no notifications controlled by this command are sent. In order to configure the DSLAM to send these SNMP notifications, enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. To enable multiple types of notifications, issue a separate snmp-server enable traps command for each notification type and notification option.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send notifications, configure at least one snmp-server host command.
For a host to receive a notification controlled by this command, both the snmp-server enable traps command and the snmp-server host command for that host must be enabled. If the notification type is not controlled by this command, only the appropriate snmp-server host command must be enabled.
The notification types used in this command all have associated MIB objects that allow them to be globally enabled or disabled. Not all of the notification types available in the snmp-server host command have notificationEnable MIB objects, so some of these notification types cannot be controlled with the snmp-server enable command.
Examples
The following example enables the DSLAM to send all traps to the host specified by the name myhost.cisco.com, using the community string defined as public:
DSLAM(config)# snmp-server enable trapsDSLAM(config)# snmp-server host myhost.cisco.com publicThe following example enables the DSLAM to send Frame Relay and environmental monitor traps to the host myhost.cisco.com using the community string public:
DSLAM(config)# snmp-server enable traps frame-relayDSLAM(config)# snmp-server enable traps envmon temperatureDSLAM(config)# snmp-server host myhost.cisco.com publicThe following example does not send traps to any host. The BGP traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps (which are not enabled in this example).
DSLAM(config)# snmp-server enable traps bgpDSLAM(config)# snmp-server host bob public isdnThe following example enables the DSLAM to send all inform requests to the host at the address myhost.cisco.com, using the community string defined as public:
DSLAM(config)# snmp-server enable trapsDSLAM(config)# snmp-server host myhost.cisco.com informs version 2c publicThe following example sends HSRP MIB traps to the host myhost.cisco.com using the community string public.
DSLAM(config)# snmp-server enable hsrpDSLAM(config)# snmp-server host myhost.cisco.com traps version 2c public hsrpRelated Commands
snmp-server host
To specify the recipient of an SNMP notification operation, use the snmp-server host global configuration command. To remove the specified host, use the no form of this command.
snmp-server host host-addr [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}] community-string [udp-port port] [notification-type]
no snmp-server host host [traps | informs]
Syntax Description
Defaults
This command is disabled by default. No notifications are sent.
If you enter this command with no keywords, the default is to send all trap types to the host. No informs are sent to this host.
If no version keyword is present, the default is version 1. The no snmp-server host command with no keywords disables traps, but not informs, to the host. To disable informs, use the no snmp-server host informs command.
Note
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send acknowledgments when it receives traps. The sender cannot determine if the traps were received. However, an SNMP entity that receives an inform request acknowledges the message with an SNMP response protocol data unit (PDU). If the sender never receives the response, the inform request can be sent again. Thus, informs are more likely to reach their intended destination.
However, informs consume more resources in the agent and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in memory until a response is received or the request times out. Also, traps are sent only once, but an inform can be retried several times. The retries increase traffic and contribute to a higher overhead on the network.
If you do not enter an snmp-server host command, no notifications are sent. In order to configure the DSLAM to send SNMP notifications, enter at least one snmp-server host command. If you enter the command with no keywords, all trap types are enabled for the host.
To enable multiple hosts, issue a separate snmp-server host command for each host. You can specify multiple notification types in the command for each host.
When you issue multiple snmp-server host commands for the same host and kind of notification (trap or inform), each succeeding command overwrites the previous command. Only the last snmp-server host command is in effect. For example, if you enter an snmp-server host inform command for a host and then enter another snmp-server host inform command for the same host, the second command replaces the first.
The snmp-server host command is used with the snmp-server enable command. Use the snmp-server enable command to specify which SNMP notifications are sent globally. For a host to receive most notifications, enable at least one snmp-server enable command and the snmp-server host command for that host.
However, some notification types cannot be controlled with the snmp-server enable command. Some notification types are always enabled. Other notification types are enabled by a different command. For example, the linkUpDown notifications are controlled by the snmp trap link-status command. These notification types do not require an snmp-server enable command.
The availability of a notification-type option depends on the DSLAM type and Cisco IOS software features supported on the DSLAM. For example, the envmon notification-type is available only if the environmental monitor is part of the system.
Examples
If you want to configure a unique SNMP community string for traps, but you want to prevent SNMP polling access with this string, the configuration should include an access-list. In the following example, the community string is named "comaccess" and the access list is numbered 10:
DSLAM(config)# snmp-server community comaccess ro 10DSLAM(config)# snmp-server host 172.20.2.160 comaccessDSLAM(config)# access-list 10 deny anyThe following example sends the SNMP traps to the host specified by the name myhost.cisco.com. The community string is defined as comaccess.
DSLAM(config)# snmp-server enable trapsDSLAM(config)# snmp-server host myhost.cisco.com comaccess snmpThe following example sends the SNMP and Cisco environmental monitor enterprise-specific traps to address 172.30.2.160:
DSLAM(config)# snmp-server enable trapsDSLAM(config)# snmp-server host 172.30.2.160 public snmp envmonThe following example enables the DSLAM to send all traps to the host myhost.cisco.com using the community string public:
DSLAM(config)# snmp-server enable trapsDSLAM(config)# snmp-server host myhost.cisco.com publicThe following example will not send traps to any host. The BGP traps are enabled for all hosts, but only the ISDN traps are enabled to be sent to a host.
DSLAM(config)# snmp-server enable traps bgpDSLAM(config)# snmp-server host bob public isdnThe following example enables the DSLAM to send all inform requests to the host myhost.cisco.com using the community string public:
DSLAM(config)# snmp-server enable trapsDSLAM(config)# snmp-server host myhost.cisco.com informs version 2c publicThe following example sends HSRP MIB traps to the host specified by the name myhost.cisco.com. The community string is defined as public.
DSLAM(config)# snmp-server enable hsrpDSLAM(config)# snmp-server host myhost.cisco.com traps version 2c public hsrpRelated Commands
snmp-server ifindex persist
To globally enable ifIndex values to remain constant across reboots for use by SNMP, use the snmp-server ifindex persist command in global configuration mode. To globally disable ifIndex persistence, use the no form of this command in global configuration mode.
snmp-server ifindex persist
no snmp-server ifindex persist
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Global configuration mode
Command History
Usage Guidelines
Interface Index Persistence means that ifIndex values in the IF-MIB persist across reboots, allowing for consistent identification of specific interfaces that use SNMP.
The snmp-server ifindex persist global configuration command does not override an interface-specific configuration. Interface-specific configuration of ifIndex persistence is performed with the [no] snmp ifindex persist and snmp ifindex clear interface configuration commands.
The [no] snmp-server ifindex persist global configuration command enables and disables ifIndex persistence for all interfaces on the DSLAM using ifDescr and ifIndex entries in the ifIndex table of the IF-MIB.
Examples
In the following example, ifIndex persistence is enabled for all interfaces:
DSLAM(config)# snmp-server ifindex persistIn this example, if ifIndex persistence was previously disabled for a specific interface through the use of the no snmp ifindex persist interface configuration mode command, ifIndex persistence remains disabled for that interface. The global ifIndex command does not override the interface-specific commands.
Related Commands
snmp-server location
To set the system location string, use the snmp-server location global configuration command. Use the no form of this command to remove the location string.
snmp-server location text
no snmp-server location
Syntax Description
Defaults
No system location string is set.
Command Modes
Global configuration
Command History
Examples
The following example shows a system location string:
DSLAM(config)# snmp-server location Building 3/Room 214Related Commands
snmp-server queue-length
To establish the message queue length for each trap host, use the snmp-server queue-length global configuration command.
snmp-server queue-length length
Syntax Description
length
Integer that specifies the number of trap events that can be held before the queue must be emptied.
Defaults
10 events
Command Modes
Global configuration
Command History
Usage Guidelines
This command defines the length of the message queue for each trap host. Once a trap message is successfully transmitted, the software continues to empty the queue, but never faster than at a rate of 4 trap messages per second.
Examples
The following example establishes a message queue that traps four events before it must be emptied:
DSLAM(config)# snmp-server queue-length 4Related Commands
None.
snmp trap link-status
To enable SNMP link trap generation, use the snmp trap link-status interface configuration command. To disable SNMP link traps, use the no form of this command.
snmp trap link-status
no snmp trap link-status
Syntax Description
This command has no arguments or keywords.
Defaults
SNMP link traps are sent when an interface goes up or down.
Command Modes
Interface and profile configuration
Command History
Usage Guidelines
By default, SNMP link traps are sent when an interface goes up or down. For interfaces that are expected to go up and down during normal usage, such as ISDN interfaces, the output that these traps generate might not be useful. The no form of this command disables these traps.
Examples
The following example disables the sending of SNMP link traps related to the atm 0/1 interface:
DSLAM(config)# interface atm 0/1DSLAM(config)# no snmp trap link-statusRelated Commands
None.
sonet
To modify the framing mode for the interface, use the sonet interface configuration command.
sonet [stm-1 | sts-3c] [protection | working | <cr>]
Syntax Description
Defaults
Default value is sts-3c.
Command Modes
Interface configuration
Command History
Examples
The following example sets the framing mode to stm-1 on both the working and protection fibers:
DSLAM> enableDSLAM# configure terminalDSLAM(config)# interface atm 0/1DSLAM(config-if)# sonet stm-1Related Commands
source-ip
To specify an alternate IP address for a VPDN tunnel that is different from the physical IP address used to open the tunnel, use the source-ip VPDN group command. To remove the alternate IP address, use the no form of this command.
source-ip ip-address
no source-ip
Syntax Description
ip-address
Alternate IP address (that is, different from the physical IP address used to open the VPDN tunnel) that the DSLAM uses to identify the tunnel.
Defaults
Disabled
Command Modes
VPDN group mode
Command History
Usage Guidelines
You can configure each VPDN group on a DSLAM with a unique source-ip command.
Examples
The following example configures an L2TP access concentrator (LAC) to accept L2TP dial-out calls using the alternate IP address 172.23.33.7, which is different from the physical IP address used to open the L2TP tunnel.
DSLAM(config)# vpdn-group 3DSLAM(config-vpdn)# accept-dialoutDSLAM(config-vpdn-acc-out)# protocol l2tpDSLAM(config-vpdn-acc-out)# exitDSLAM(config-vpdn)# source-ip 172.23.33.7Related Commands
split-mode
To enter the redundancy submode to specify redundancy on NI-2s, use the redundancy global configuration command.
redundancy split-mode
Syntax Description
Defaults
The default is no split-mode.
Command Modes
Redundancy submode
Command History
Usage Guidelines
If you use the redundancy command, you enter redundancy privileged EXEC submode (config-red). Within this submode, you can configure the redundancy-specific parameter for putting the system in split mode. To exit redundancy privileged EXEC submode, type exit.
If you disable split mode, the standby card is reloaded.
Examples
The following example puts the system into simplex mode:
DSLAM> enableDSLAM# configure terminalDSLAM(config)# redundancyDSLAM(config-red)# split-modeThis command will place the system in SIMPLEX mode. [confirm] ySecondary auto-sync disabled due to split-modeRelated Commands
show redundancy states
Display the state of the primary and secondary NI-2s, and identify which NI-2 is active.
subtend-id
To set the subtend node identifier, use the subtend-id command.
subtend-id node#
Syntax Description
node#
The identifier that you assign to this subtend node or to the specified subtend interface. The range is 0 to 12.
Defaults
The default subtend ID is 0 (zero).
Command Modes
Global configuration or interface configuration. See the Usage Guidelines below for details.
Command History
12.0(5)DA
This command was introduced.
12.0(8)DA
The ability to assign a subtend ID to an interface was added.
Usage Guidelines
Assign to each subtended node a subtend identifier that is unique within its local subtend tree. If this condition is not met, some subscribers might not have fair access to the network.
The node at the top of the subtend tree—that is, the node that is connected to the trunk—must have the subtend ID 0. (Subtend ID 0 is the default.)
You can use the subtend-id command in global configuration mode or in interface configuration mode:
•
•
Examples
The command in this example sets the subtend node identifier of this chassis to 12:
DSLAM# configure terminalDSLAM(config)# subtend-id 12The command in this example sets the subtend node identifier to 6 on port 0/2:
DSLAM# configure terminalDSLAM(config)# interface atm 0/2DSLAM(config-if)# subtend-id 6Related Commands
None.
tag-switching request-tags for
To restrict the creation of LVCs through the use of access lists on the LSC or label edge router, use the tag-switching request-tags for global configuration command. Use the no form of this command to disable this feature.
tag-switching request-tags for access list
no tag-switching request-tags for
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
This command includes the following usage guidelines:
•
•
•
Examples
This example shows how to prevent headend LVCs from being established from the LSC to all 198.x.x.x destinations. Add the following commands to the LSC configuration:
DSLAM(config)# tag-switching request-tags for 1DSLAM(config)# access-list 1 deny 198.0.0.0 0.255.255.255DSLAM(config)# access-list 1 permit anyRelated Commands
access list
Creates access lists.
ip access-list
Permits or denies access to IP addresses.
virtual-template
To specify which virtual template to use to clone virtual-access interfaces, use the virtual-template accept-dialin command. To remove the virtual template from an accept-dialin VPDN subgroup, use the no form of this command.
virtual-template template-number
no virtual-template
Syntax Description
Defaults
Disabled
Command Modes
Accept-dialin mode
Command History
Usage Guidelines
Each accept-dialin group can clone virtual-access interfaces using only one virtual template. If you enter a second virtual-template command on an accept-dialin subgroup, it replaces the first virtual-template command.
You must first enable a tunneling protocol on the accept-dialin VPDN subgroup (using the protocol command) before you can enable the virtual-template command. If you remove or modify the protocol command, the virtual-template command is removed from the request-dialin subgroup.
Examples
The following example enables the LNS to accept an L2TP tunnel from a LAC named "mugsy." A virtual-access interface will be cloned from virtual template 1:
DSLAM(config)# vpdn enableDSLAM(config)# vpdn-group 1(config-vpdn)# accept-dialin(config-vpdn-acc-in)# protocol l2tp(config-vpdn-acc-in)# virtual-template 1Related Commands
accept-dialin
Accepts requests to create either L2F or L2TP tunnels for dial-in.
vpdn domain-delimiter
To specify the characters to be used to delimit the domain prefix or domain suffix, use the vpdn domain-delimiter global configuration command.
vpdn domain-delimiter delimiter-characters [suffix | prefix]
Syntax Description
Defaults
Disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You can enter one vpdn domain-delimiter command to list the suffix delimiters and another vpdn domain-delimiter command to list the prefix delimiters. However, no character can be both a suffix delimiter and a prefix delimiter.
This command allows the network access server to parse a list of home gateway DNS domain names and addresses sent by an AAA server. The AAA server can store domain names or IP addresses in the following AV pair:
cisco-avpair = "lcp:interface-config=ip address 1.1.1.1 255.255.255.255.0",cisco-avpair = "lcp:interface-config=ip address bigrouter@excellentinc.com,Examples
The following example lists three suffix delimiters and three prefix delimiters:
DSLAM(config)# vpdn domain-delimiter %-@ suffixDSLAM(config)# vpdn domain-delimiter #/\\ prefixRelated Commands
vpdn enable
To enable VPDN on the DSLAM and inform the DSLAM to look for tunnel definitions in a local database, use the vpdn enable global configuration command. To disable VPDN, use the no form of this command.
vpdn enable
no vpdn enable
Syntax Description
This command has no keywords or arguments.
Defaults
Disabled
Command Modes
Global configuration.
Command History
Examples
The following example enables VPDN on the router:
DSLAM(config)# vpdn enableRelated Commands
None.
vpdn-group
To define a local, unique group number identifier, use the vpdn-group global configuration command. To remove a group number, use the no form of this command.
vpdn-group group-number
no vpdn-group group-number
Syntax Description
Defaults
VPDN group number assignments are not defined.
Command Modes
Global configuration
Command History
Usage Guidelines
The vpdn-group command defines a local, unique identifier for each VPDN group.
Examples
The following example establishes local VPDN group number 1 for which other variables, such as force-local chap, can be assigned:
DSLAM(config)# vpdn enableDSLAM(config)# vpdn group-number 1Related Commands
None.
vpdn outgoing
To specify use of a domain name when selecting a tunnel for forwarding traffic to the remote host (the home gateway) on a virtual private dialup network, use the vpdn outgoing global configuration command.
vpdn outgoing {domain-name} local-name ip ip-address
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The request-dialin command replaces this command.
The domain-name and local-name arguments are case sensitive.
This command is usually used on a network access server, not on a home gateway.
You can use the domain name to choose a tunnel destination. For example, if a user dials in as joe@company-a.com, where joe is the username and company-a.com is the domain name, you can select a tunnel destination based on the domain (company-a.com).
Note
Examples
The following example selects a tunnel destination based on the domain name:
DSLAM(config)# vpdn enableDSLAM(config)# vpdn outgoing chicago-main go-blue ip 172.17.33.125Related Commands
vpdn source-ip
To set the source IP address of the network access server, use the vpdn source-ip global configuration command.
vpdn source-ip address
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
One source IP address is configured on the network access server. The source IP address is configured per network access server, not per domain.
Examples
The following example enables VPDN on the network access server and sets an IP source address of 171.4.48.3.
DSLAM(config)# vpdn enableDSLAM(config)# vpdn source-ip 171.4.48.3Related Commands
None.
Posted: Mon May 10 22:15:22 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
