-
CSS Basic Configuration Guide (Software Version 5.00)
-
Content Services Switch Basic Configuration Guide Index (Software Version 5.00)
-
About This Guide
-
Logging in and Getting Started
-
Configuring User Profiles and CSS Parameters
-
Configuring CSS Network Protocols
-
Configuring Interfaces and Circuits
-
Configuring Services
-
Configuring Owners
-
Configuring Content Rules
-
Using the CSS Logging Features
-
Configuring Simple Network Management Protocol (SNMP)
-
Configuring Remote Monitoring (RMON)
-
Upgrading Your CSS Software
-
Table Of Contents
Configuring Interfaces and Circuits
Interface and Circuit Overview
Interface and Circuit Configuration Quick Start
Entering a Description for the Interface
Configuring Interface Duplex and Speed
Setting the Interface Maximum Idle Time
Showing Interface Duplex and Speed
Bridging an Interface to a VLAN
Specifying VLAN Trunking to an Interface
Selecting a Default VLAN in a Trunk
Configuring Bridge Pathcost for a Trunked Interface/VLAN Pair
Configuring Bridge Priority for a Trunked Interface/VLAN Pair
Configuring Bridge State for a Trunked Interface/VLAN Pair
Configuring the Low-Water Mark of Flow Control Blocks on an Interface
Smoothing Bursty Network Traffic on the CSS 11800 Gigabit Ethernet Module
Showing Trunking Configurations
Showing Ethernet Interface Errors
Configuring Router-Discovery Lifetime
Configuring Router-Discovery Limited-Broadcast
Configuring Router-Discovery Max-Advertisement-Interval
Configuring Router-Discovery Min-Advertisement-Interval
Configuring a Circuit IP Interface
Configuring a Circuit IP Address
Configuring a Circuit-IP Broadcast Address
Configuring Circuit-IP Redirects
Configuring Circuit-IP Unreachables
Configuring Router-Discovery Preference
Configuring RIP for an IP Interface
Configuring RIP Packet Logging
Configuring Interfaces and Circuits
This chapter describes how to configure the CSS interfaces and circuits, and bridge interfaces to VLANs. Information in this chapter applies to all CSS models except where noted.
This chapter contains the following sections:
•
Interface and Circuit Overview
•
•
Interface and Circuit Overview
The CSS provides ethernet interfaces (ports) that enable you to connect servers, PCs, routers, and other devices to the CSS.
Using the bridge command, you bridge (assign) the interfaces to a specific Virtual LAN (VLAN). Each VLAN circuit requires an IP address. Assigning an IP address to each VLAN circuit allows the CSS to route Ethernet interfaces from VLAN to VLAN.
Using the trunk command, you can assign multiple VLANs to a CSS interface port (Gigabit Ethernet ports only). A trunk is a point-to-point link carrying the traffic of several VLANs (as illustrated in Figure 4-2). The advantage of a trunk is to save ports when creating a link between two devices implementing VLANs, typically two switches. A trunk bundles virtual links over one physical link. The unique physical link between the two CSSs is able to carry traffic for the specified VLANs.
Note
The CSS forwards VLAN circuit traffic to the IP interface. The IP interface passes the traffic to the IP forwarding function where the CSS compares the destination of each packet to information contained in the routing table. Once the CSS resolves the packet addresses, it forwards the packet to the appropriate VLAN and destination port.
When trunking is enabled, the CSS automatically inserts a tag in every frame transmitted over the trunk link to identify the originating VLAN. When the VLAN-aware device receives the frame the device reviews the VLAN-tagged packet to identify the transmitting VLAN. If the VLAN is recognized, the frame is routed to the proper port and VLAN destination. If the frame is from a VLAN that is not assigned to the trunk port, the packet is ignored. By default, the CSS discards untagged packets.
Note
Note that on an 802.1Q trunk, you may configure one VLAN (using the optional default-vlan command) to:
•
•
By this method, the CSS can determine which VLAN transmitted an untagged frame. This capability allows VLAN-aware devices and VLAN-unaware devices to transmit and receive information on the same cable.
illustrates the interfaces, circuits, and VLANs in a CSS and Figure 4-2 illustrates trunking between VLANs.
Figure 4-1 Content Services Switch Interfaces and Circuits
Figure 4-2 Interface Trunking Between VLANs
Interface and Circuit Configuration Quick Start
Table 4-1 provides a quick overview of the steps required to configure interfaces and circuits. Each step includes the CLI command required to complete the task. For a complete description of each feature and all the options associated with the CLI command, refer to the sections following Table 4-1.
Configuring Interfaces
Interfaces are ports that enable you to connect devices to the CSS and connect the CSS to the Internet. The commands to configure interfaces on the CSS 11050 and CSS 11150 differ slightly from the commands to configure interfaces on the CSS 11800 because the CSS 11800 requires a slot/port designation. The CSS 11050 and CSS 11150 do not use the slot/port designation.
Configuring an interface requires you to:
•
•
•
•
•
•
•
Note
Configuring an Interface
To configure an interface, enter the interface command and a valid interface name. To use the interface command for a:
•
•
For example, to configure interface e1 on a CSS 11050 or CSS 11150, access interface mode for e1 by entering:
(config)# interface e1The CSS changes from config mode to the specific interface mode.
(config-if[e1])#Entering a Description for the Interface
To help you to identify the interface, use the description command to describe the interface. Enter a quoted text string from 1 to 255 characters in length including spaces.
For example:
(config-if[e1])# description "Connects to server17"To display an interface description, use the show running-config interface command. For example:
(config-if[e1])# show running-config interface e11!************************ INTERFACE ************************interface e11description "Connects to server17"bridge vlan 2To remove an interface description, enter:
(config-if[e1])# no descriptionConfiguring Interface Duplex and Speed
Use the phy command to configure the speed or flow control (pause) method and duplex for a CSS Fast Ethernet or Gigabit Ethernet interface (port), respectively. By default, the port is configured to auto-negotiate. Auto-negotiate enables the port to detect the speed or pause method, and duplex of incoming signals and synchronize with them automatically.
For Fast Ethernet modules (FEM), when older equipment cannot transmit the duplex and speed with its signals, you can configure the speed and duplex on the port to match the transmitting equipment.
For Gigabit Ethernet modules (GEM), if the link does not come up and you need to force the module and its link partner into a specific mode, you can set the duplex and flow control (pause) method. The pause methods of communications between modules determines how the module sends pause frames. The module sends pause frames when it becomes overwhelmed with data. The CSS module and its link partner must be configured with the same pause method.
Use the phy command to manually configure the interface (port) duplex and speed to one of the following settings:
•
•
•
•
•
•
•
•
•
For example, to set interface e1 to 100 Mbps and half-duplex, enter:
(config-if[e1])# phy 100Mbits-HDSetting the Interface Maximum Idle Time
Use the max-idle command as a troubleshooting tool to verify an interface's ability to receive traffic. If the interface does not receive traffic within the configured idle time, the CSS reinitializes it automatically.
Set the idle time to a value greater than the interval over which the interface is not receiving traffic. For example, if the interface receives traffic every 90 seconds, set the idle time to a value greater than 90 seconds. If you set the idle time to less than 90 seconds, the CSS would continuously reinitialize the interface before the interface was able to receive traffic.
Enter the idle time from 15 to 65535 seconds. The default is 0, which disables the idle timer. For example, to set the maximum idle time for interface e7 to 180 seconds, enter:
(config-if[e7])# max-idle 180To reset the idle time for an interface to its default value of 0, enter:
(config-if[e7])# no max-idleShowing Interface Duplex and Speed
To show duplex and speed values for all interfaces, enter the show phy command. For example:
(config)# show phyTo show duplex and speed value for a specific interface, enter the show phy command and the interface name. For example:
(config)# show phy e3Table 4-2 describes the fields in the show phy output.
Bridging an Interface to a VLAN
To bridge a interface to a VLAN, use the bridge vlan command to specify a virtual local area network (VLAN) and associate it with the specified interface port. Enter an integer from 1 to 4094 as the VLAN identifier. The default is 1. All interfaces are assigned to VLAN1 by default.
Note
For example, to configure e1 to VLAN2, enter:
(config-if[e1])# bridge vlan 2
Note
Note
To restore the default VLAN1, enter:
(config-if[e7])# no bridge vlanTo display all interfaces and the VLANs to which they are configured, enter the show circuit command. Refer to "Showing Circuits" in this chapter for information about the show circuits command.
In the show circuit display, VLANs appear as VLAN (uppercase, with no space before the VLAN number).
Configuring Bridge Pathcost
To set the path cost for an interface, use the bridge pathcost command. The cost is the contribution of the interface to the vast path cost towards spanning-tree root. Enter an integer from 1 to 65535. The default is dynamically configured based on the interface speed.
For example, to set a path cost of 9 for e7, enter:
(config-if[e7])# bridge pathcost 9To restore the default path cost, enter:
(config-if[e7])# no bridge pathcostConfiguring Bridge Priority
To set the bridge priority for a port, use the bridge priority command. Enter an integer from 0 to 255. The default is 128.
For example, to set a bridge priority of 100 for e7, enter:
(config-if[e7])# bridge priority 100To restore the default priority of 128, enter:
(config-if[e7])# no bridge priorityConfiguring Bridge State
To set the bridge state to enable or disable for an interface, use the bridge state command. An interface is set to bridge state enable by default.
For example, to enable the bridge state for e7, enter:
(config-if[e7])# bridge state enableTo disable the bridge state for e7, enter:
(config-if[e7])# bridge state disableSpecifying VLAN Trunking to an Interface
To activate VLAN trunking for a CSS Gigabit Interface, use the trunk command and specify all VLANs that are to include the specified port as part of the VLAN. The trunk command also converts the link into a trunk link. To specify the number of each VLAN that is to be associated with the Gigabit Interface, use the vlan command. Enter an integer from 1 to 4094 as the VLAN identifier.
Note
Note
Note
For example, to configure gigabit ethernet port 1 in slot 1 for use in VLAN2, VLAN3, and VLAN9, enter:
CSS11800(config-if[1/1])# trunkCSS11800(config-if[1/1])# vlan 2Create VLAN<2>, [y/n]:yCSS11800(config-if-vlan[1/1-2])# vlan 3Create VLAN<3>, [y/n]:yCSS11800(config-if-vlan[1/1-3])# vlan 9Create VLAN<9>, [y/n]:yCSS11800(config-if-vlan[1/1-9])#Every time you enter a vlan command for a new VLAN, the software automatically prompts you to create the specified VLAN (where y instructs the software to create the VLAN and n cancels the VLAN creation).
To disable trunking on the specified Gigabit Interface and associated VLANs, enter:
(config-trunkif[2/3])# no trunkThe no trunk command turns off all trunking, removes all specified vlan commands associated with the interface, and deletes this information from the running configuration. The interface is returned to VLAN1 by default.
To display all interfaces and the VLANs to which they are configured, enter the show circuit command. Refer to Table 4-9 for information about the show circuits command.
Note
Selecting a Default VLAN in a Trunk
To define a default VLAN that has the capability to accept packets that arrive untagged on the interface, include the default-vlan command as part of the trunk/VLAN definition. The command also specifies that the packets transmitted from this VLAN will be untagged. The default VLAN must be explicitly set if you want untagged packets to be processed by the CSS. Otherwise these packets will be discarded.
The default-vlan command can only be specified for a single VLAN. If you attempt to use this command for another VLAN, the software instructs you to disable the current default VLAN (using the no default-vlan command).
For example, enter:
CSS11800(config-if[1/1])# trunkCSS11800(config-if[1/1])# vlan 2Create VLAN<2>, [y/n]:yCSS11800(config-if-vlan[1/1-2])# vlan 3Create VLAN<3>, [y/n]:yCSS11800(config-if-vlan[1/1-3])# default-vlanTo remove the default VLAN selection, enter:
CSS11800(config-if-vlan[1/1-3])# no default-vlanConfiguring Bridge Pathcost for a Trunked Interface/VLAN Pair
To set the spanning-tree port path cost for a given interface/VLAN pair, use the bridge pathcost command. The cost is the contribution of the given interface/VLAN pair to the vast path cost towards spanning-tree root. Enter an integer from 1 to 65535. The default is dynamically configured based on the link speed.
For example, to set a path cost of 2 for slot 1, port 1, VLAN3, enter:
CSS11800(config-if-vlan[1/1-3])# bridge pathcost 2To restore the default path cost, enter:
CSS11800(config-if-vlan[1/1-3])# no bridge pathcostConfiguring Bridge Priority for a Trunked Interface/VLAN Pair
To set the spanning-tree bridge priority for a given interface/VLAN pair, use the bridge priority command. Enter an integer from 0 to 255. The default is 128.
For example, to set a bridge priority of 100 for slot 1, port 1, VLAN3, enter:
CSS11800(config-if-vlan[1/1-3])# bridge priority 100To restore the default priority of 128, enter:
CSS11800(config-if-vlan[1/1-3])# no bridge priorityConfiguring Bridge State for a Trunked Interface/VLAN Pair
To set the bridge state to enable or disable for a given interface/VLAN pair, use the bridge state command. An interface is set to bridge state enable by default.
For example, to enable the bridge state for slot 1, port 1,VLAN3, enter:
CSS11800(config-if-vlan[1/1-3])# bridge state enableTo disable the bridge state for slot 1, port 1, located in VLAN3, enter:
CSS11800(config-if-vlan[1/1-3])# bridge state disableConfiguring the Low-Water Mark of Flow Control Blocks on an Interface
Use the fcb-lowwater command to configure the low-water mark of flow control blocks (FCBs) on the interface. The low-water mark is the percentage of the total number of FCBs available. If the number of FCBs available on a port goes below the low-water mark, then aggressive flow recovery occurs.
The syntax for this interface mode command is:
fcb-lowwater percentage
Enter the percentage as the total number of available FCBs. Enter a number from 1 to 100. The default is 25%.
To reset the percentage of available FCBs to its default of 25, enter:
(config-if[e7])# no fcb-lowwaterSmoothing Bursty Network Traffic on the CSS 11800 Gigabit Ethernet Module
Use the gem-traffic-bursty global configuration mode command to smooth bursty traffic on Gigabit Ethernet Modules (GEMs) in the CSS 11800 for applications sensitive to packet loss. Traffic burstiness is the occurrence of extreme amounts of traffic for a short period of time (when traffic bursts over a rate of 16 Gbps for short intervals). During extremely heavy traffic loads, when a single GEM port has greater than one gigabit per second of incoming network traffic, substantial packet loss can occur. This condition can easily occur when a group of servers attached to multiple ports send traffic simultaneously to a single client uplink port.
If the traffic load at the client uplink port is at a rate close to a gigabit per second with occasional bursts of greater than one gigabit per second, you can use the gem-traffic-bursty command to reduce overall packet loss. This command can greatly reduce packet loss for applications sensitive to this condition, for example, video and audio streaming applications.
If the traffic load at the client uplink port remains at a constant rate greater than one gigabit per second, you may need to perform a network reconfiguration, for example, configure an additional client uplink port. You should not use the gem-traffic-bursty command to solve the problem.
Note
To smooth bursty traffic on the GEMs in a CSS 11800, enter:
(config)# gem-traffic-burstyTo reset the default traffic handling behavior on the GEM, enter:
(config)# no gem-traffic-burstyShowing Bridge Configurations
The CSS enables you to show bridging information. To display this information, use the show bridge command.
The syntax for this interface mode command is:
show bridge [forwarding|status] {vlan_number}
The options and variables are:
•
•
•
Table 4-3 describes the fields in the show bridge forwarding output.
To display bridge status information, use the show bridge status command.
Note
Table 4-4 describes the fields in the show bridge status output.
Showing Trunking Configurations
The CSS enables you to show VLAN trunk status information for a Gigabit Ethernet port. To display this information, use the show trunk command.
Table 4-5 describes the fields in the show trunk output.
Showing Interfaces
To display a list of valid interfaces for the CSS, use the show interface command. For example:
(config)# show interfaceTo only display information for a specific interface, enter the show interface command and the interface name.
(config)# show interface e7Table 4-6 describes the fields in the show interface output.
Showing Interface Statistics
To display the extended 64-bit MIB-II statistics for a specific interface or all interfaces in the CSS, use the show mibii command. The Enterprise ap64Stats MIB defines these statistics. To display the RFC1213 32-bit statistics, include the -32 suffix.
To display extended MIB-II statistics for a specific interface in the CSS, enter the show mibii command with the interface name. To see a list of interfaces in the CSS, enter show mibii ?.
Table 4-7 describes the fields in the show mibii output.
To clear interface statistics, use the clear statistics command in SuperUser mode. For example:
# clear statisticsShowing Ethernet Interface Errors
To list the errors on an Ethernet interface, use the show ether-errors command and options. When required, enter the interface name as a case-sensitive unquoted text string. To see a list of interfaces, enter show ether-errors ?.
The command provides the following options:
•
•
•
•
•
•
Table 4-8 describes the fields in the show ether-errors output.
Shutting Down an Interface
To shutdown an interface, use the admin-shutdown command in interface mode.
Caution
For example, to shut down interface e3, enter:
(config-if[e3]) admin-shutdown physical
Note
Restarting the Interface
To restart the interface, enter the no admin-shutdown command. For example, to restart interface e3, enter:
(config-if[e3])# no admin-shutdown physicalShutting Down All Interfaces
To shut down all interfaces simultaneously, use the admin-shutdown command at the SuperUser prompt. This command provides a quick way to shut down all physical devices in the CSS except the Console and Management ports.
Caution
To shut down all interfaces, enter:
# admin-shutdown
Note
Restarting All Interfaces
To restart all interfaces, enter:
# no admin-shutdownConfiguring Circuits
A circuit on the CSS is a logical entity that maps IP interfaces to a logical port or group of logical ports (for example, a VLAN). Each VLAN circuit requires an IP address. Assigning an IP address to each VLAN circuit allows the CSS to route Ethernet interfaces from VLAN to VLAN.
To enter a specific circuit configuration mode, enter the circuit command and VLAN as shown in the following example:
(config)# circuit VLAN7(config-circuit[VLAN7])#
Note
You can configure the following settings for a circuit:
•
•
•
•
Note
Configuring Router-Discovery Lifetime
To configure the maximum age in seconds that hosts remember router advertisements, use the router-discovery lifetime command with an integer between 0 and 9000 seconds. The default is 3 x the max-advertisement-interval.
For example:
(config-circuit[VLAN7])# router-discovery lifetime 600To reset the time to the default of 3 x the max-advertisement-interval, enter:
(config-circuit[VLAN7)# no router-discovery lifetimeConfiguring Router-Discovery Limited-Broadcast
To transmit router discovery packets using the broadcast address 255.255.255.255, use the router-discovery limited-broadcast command. The default is 224.0.0.1. For example:
(config-circuit[VLAN7])# router-discovery limited-broadcastTo revert to the default of 224.0.0.1, enter:
(config-circuit[VLAN7)# no router-discovery limited-broadcastConfiguring Router-Discovery Max-Advertisement-Interval
To configure router discovery maximum advertisement interval, use the router-discovery max-advertisement-interval command. The maximum value defines the interval between advertisements in seconds. Enter an integer from 4 to 1800. The default is 600 (10 minutes). For example:
(config-circuit[VLAN7])# router-discovery max-advertisement-interval 300To restore router discovery maximum advertisement interval to the default of 600, enter:
(config-circuit[VLAN7])# no router-discovery max-advertisement-intervalConfiguring Router-Discovery Min-Advertisement-Interval
To configure router discovery minimum advertisement interval timers, use the router-discovery min-advertisement-interval command. The minimum value defines the minimum interval between advertisements in seconds. Enter an integer from 0 to 1800.
The default is 0.75 x the max-advertisement-interval. If this value is greater than 0, it must be less than the maximum value.
For example:
(config-circuit[VLAN7])# router-discovery min-advertisement-interval 100To reset the minimum router advertisement interval to the default of 0.75 x the maximum advertisement value, enter:
(config-circuit[VLAN7])# no router-discovery min-advertisement-intervalShowing Circuits
To show circuit information, use the show circuits command. A circuit on the CSS is a logical entity that maps IP interfaces to a logical port or group of logical ports.
This command provides the following options:
•
•
•
To list all circuits and their interfaces in the Up state, enter:
# show circuitsTo list all circuits and their interfaces regardless of their state, enter:
# show circuits allTo list an individual circuit, enter:
# show circuits name VLAN5Table 4-9 describes the fields in the show circuits output.
Configuring a Circuit IP Interface
A circuit on the CSS is a logical entity that maps IP interfaces to a logical port or group of logical ports (for example, a VLAN). Each VLAN circuit requires an IP address. Assigning an IP address to each VLAN circuit allows the CSS to route Ethernet interfaces from VLAN to VLAN.
To enter a specific circuit configuration mode, enter the circuit command and VLAN as shown in the following example:
(config)# circuit VLAN7(config-circuit[VLAN7])#
Note
The following sections describe how to define a a circuit IP address.
•
•
•
•
•
Configuring a Circuit IP Address
To assign an IP address to a circuit, use the ip address command from the specific circuit mode. Enter the IP address and a subnet mask in CIDR bitcount notation or a mask in dot-decimal notation. The subnet mask range is 8 to 31.
For example, to configure an IP address and subnet mask for VLAN7, enter:
(config-circuit[VLAN7])# ip address 173.3.6.58/8When you specify an IP address, the mode changes to the specific circuit-ip-VLAN-IP address as shown:
(config-circuit-ip[VLAN7-173.3.6.58])#To remove a local IP address from a circuit, enter the following command from the circuit mode:
(config-circuit[VLAN7])# no ip addressConfiguring a Circuit-IP Broadcast Address
To change the broadcast address associated with a circuit, use the broadcast command. If you leave the broadcast address at zero, the all-ones host is used for numbered interfaces.
The default broadcast address is an all-ones host address (for example, an IP address 173.3.6.58/24 has a broadcast address of 173.3.6.58/255). This command is available in IP configuration mode.
For example, to change the broadcast address on circuit VLAN7, enter:
(config-circuit-ip[VLAN7-173.3.6.58])# broadcast 0.0.0.0To reset the broadcast IP address to the default all-ones host address, enter:
(config-circuit[VLAN7-173.3.6.58])# no broadcastConfiguring Circuit-IP Redirects
To enable the transmission of Internet Control Message Protocol (ICMP) redirect messages, use the redirects command. The default state is enabled.
For example:
(config-circuit-ip[VLAN7-173.3.6.58])# redirectsTo disable the transmission of ICMP redirect messages, enter:
(config-circuit-ip[VLAN7-173.3.6.58])# no redirectsConfiguring Circuit-IP Unreachables
To enable the transmission of ICMP "destination unreachable" messages, use the unreachables command. The default state is enabled.
For example:
(config-circuit-ip[VLAN7-173.3.6.58])# unreachablesTo disable the transmission of ICMP "destination unreachable" messages, enter:
(config-circuit-ip[VLAN7-173.3.6.58])# no unreachablesEnabling Router-Discovery
To enable router discovery for an interface, use the router-discovery command. When enabled, router discovery transmits packets with a multicast address of 244.0.0.1. To enable an interface to transmit packets with a multicast address of 255.255.255.255, use the router-discovery limited-broadcast command in circuit mode (see "Configuring Router-Discovery Limited-Broadcast", earlier in this chapter). Router discovery is disabled by default.
For example:
(config-circuit-ip[VLAN7-192.168.1.58])# router-discoveryTo disable router discovery, enter:
(config-circuit-ip[VLAN7-192.168.1.58])# no router-discoveryConfiguring Router-Discovery Preference
To configure the router discovery preference value, use the router-discovery preference command and a value to define the router preference value to advertise. The value is an integer from 0 (default) to 65535. If you use the default value, you do not need to use this command.
For example:
(config-circuit-ip[VLAN7-192.168.1.58])# router-discovery preference 100To restore the router discovery preference value to the default of 0, enter:
(config-circuit-ip[VLAN7-192.168.1.58])# no router-discovery preferenceEnabling a Circuit IP
To enable the IP interface on a circuit, use the enable command. The default is enable.
For example:
(config-circuit-ip[VLAN7-173.3.6.58])# enableDisabling a Circuit IP
To disable the IP interfaces on a circuit, enter:
(config-circuit-ip[VLAN7-173.3.6.58])# no enableShowing IP Interfaces
Use the show ip interfaces command to display configured IP interfaces on the CSS. The display includes the circuit state, IP address, broadcast address, Internet Control Message Protocol (ICMP) settings, and Router Discovery Program (RDP) settings.
Table 4-10 describes the fields in the show ip interfaces output.
Configuring RIP for an IP Interface
The CSS enables you to configure Routing Information Protocol (RIP) attributes on each IP interface. To configure Routing Information Protocol (RIP) parameters and run RIP on an IP interface, use the following routing commands within the specific circuit IP mode. The default mode is to send RIP version 2 (v2) and receive either RIP or RIP2.
You can configure the following routing options for each IP interface:
•
•
•
•
•
To start running RIP on an IP interface, enter:
(config-circuit-ip[VLAN7-192.168.1.58)# ripTo stop running the RIP on the interface, enter:
(config-circuit-ip[VLAN7-192.168.1.58])# no ripConfiguring RIP Default-Route
To advertise a default route on an IP interface with a specific metric, use the
rip default-route command.You can also specify an optional metric in the command line. The CSS uses this metric when advertising a route. Enter a number from 1 to 15. The default is 1.
For example:
(config-circuit-ip[VLAN7-192.168.1.58])# ripdefault-route 9Configuring RIP Receive
To specify the RIP version that the interface receives, use the rip receive command. The rip receive options are:
•
•
•
•
For example:
(config-circuit-ip[VLAN7-192.168.1.58])# rip receive bothConfiguring RIP Send
To specify the RIP version that the interface sends, use the rip send command. The rip send options are:
•
•
•
For example:
(config-circuit-ip[VLAN7-192.168.1.58])# rip send v1Configuring RIP Packet Logging
To enable the logging of received or transmitted RIP packets on the interface, use the rip log command. Use the no form of this command to disable logging (default setting). The rip log options are:
•
•
For example:
(config-circuit-ip[VLAN7-192.168.1.58])# rip log rxShowing RIP Configurations
To show a RIP configuration for one IP address or all IP addresses configured in the CSS, use the show rip command. The command provides the following options:
•
•
•
•
•
Table 4-11 describes the fields in the show rip output.
To display global RIP statistics, enter:
# show rip globalsTable 4-12 describes the fields in the show rip globals output.
To display the RIP interface statistics for all RIP interface entries, enter:
# show rip statisticsTable 4-13 describes the fields in the show rip statistics output.
Where to Go Next
For information on creating and configuring services, refer to <Xref_Color>Chapter 5, Configuring Services.
