|
|
Table Of Contents
Configuring the Line Interface
How to Configure the Line Interfaces
How to Configure the Gigabit Ethernet Line Interfaces
How to Configure the Fast Ethernet Line Interfaces
How to Configure Tunneling Protocols
How to Select the Tunneling Mode
How to Display the Tunneling Configuration
How to Configure VLAN Translation
VLAN Translation Features and Limitations
How to Set the VLAN Translation Constant
How to Disable VLAN Translation
How to Monitor VLAN Translation
How to Configure Traffic Rules and Counters
Information About Traffic Rules and Counters
How to Configure Traffic Counters
How to Configure Traffic Rules
How to Manage Traffic Rules and Counters
How to Enable and Disable TOS Marking
About Counting Dropped Packets
How to Disable the Hardware Packet Drop
Configuring the Line Interface
This module describes how to configure the physical line interfaces (ports) as well how to configure those interfaces for tunneling, VLAN translation, TOS marking, and traffic rules.
•
How to Configure the Line Interfaces
•
•
•
•
•
How to Configure the Line Interfaces
•
•
Line Interfaces
The Line Interfaces (Subscriber and Network) are used to connect the SCE platform to the network. See the description of network topologies in the Topology section of the Cisco SCE 2000/SCE 1000 Installation and Configuration Guides .
The SCE 1000 2xGBE and the SCE 2000 4xGBE have Gigabit Ethernet line interfaces. You should configure auto-negotiatefor these interfaces.
The SCE 2000 4/8x FE has Fast Ethernet line interfaces. You should configure the speedand duplexfor these interfaces.
How to Configure the Gigabit Ethernet Line Interfaces
Note
SUMMARY STEPS
1.
configure, and press Enter.2.
interface GigabitEthernet 0/portnumber, and press Enter3.
4.
auto-negotiate, and press press EnterAt the SCE(config if)# prompt, typeexitand press Enter.5.
DETAILED STEPS
Step 1
configure, and press Enter.Enters Global Configuration mode.
Step 2
interface GigabitEthernet 0/portnumber, and press EnterStep 3
Enters Interface Configuration mode for the selected GBE interface.
Step 4
auto-negotiate, and press press EnterEnables auto-negotiation.Step 5
exitand press Enter.Exits to global configuration mode, from which you can access a different Gigabit Ethernet interface.
Step 6
Auto-negotiation must enabled separately and explicitly for each Gigabit Ethernet interface.
How to Configure the Fast Ethernet Line Interfaces
Note that both sides of the FE link (both the SCE 2000 4/8xFE and the remote device) should have the same configuration. Use either of the following two configuration options:
•
•
SUMMARY STEPS
1.
configure, and press Enter.2.
interface FastEthernet 0/portnumber, and press Enter, where portnumberis the number of the selected port (1-4).3.
duplexauto|full|half, and press Enter,4.
speedauto|100, and press Enter,5.
exitand press Enter.6.
DETAILED STEPS
Step 1
configure, and press Enter.Enters Global Configuration mode.
Step 2
interface FastEthernet 0/portnumber, and press Enter, where portnumberis the number of the selected port (1-4).Enters Interface Configuration mode for the selected FE interface.
Step 3
duplexauto|full|half, and press press EnterConfigures the duplex mode for the selected FE interface.Step 4
speedauto|100, and press press EnterConfigures the speed for the selected FE interface.Step 5
exitand press Enter.Exits to global configuration mode, from which you can access a different Fast Ethernet interface.
Step 6
Speed and duplex mode must enabled separately and explicitly for each Fast Ethernet interface.
How to Configure Tunneling Protocols
•
•
About Tunneling Protocols
Tunneling technology is used across various telecommunications segments to solve a wide variety of networking problems. The SCE platform is designed to recognize and process various tunneling protocols in several ways. The SCE platform is able to either ignore the tunneling protocols ("skip" the header) or treat the tunneling information as subscriber information ("classify"). A special case of classification by tunneling information is MPLS/VPN with private IP support .
The following table shows the support for the various tunneling protocols (the default behavior for each protocol is in bold):
When the tunneling information is ignored, the subscriber identification is the subscriber IP of the IP packet carried inside the tunnel.
L2TP is an IP-based tunneling protocol, therefore the system must be specifically configured to recognize the L2TP flows, given the UDP port used for L2TP. The SCE platform can then skip the external IP, UDP, and L2TP headers, reaching the internal IP, which is the actual subscriber traffic. If L2TP is not configured, the system treats the external IP header as the subscriber traffic, thus all the flows in the tunnel are seen as a single flow.
A single VLAN tag is supported per packet (no QinQ support). MPLS labels are supported up to a maximum of 15 labels per packet.
Subscriber classification by VLAN tag is supported only in symmetric VLAN environments - i.e. where the upstream and downstream tags are identical.
Note
Use these commands to configure tunneling:
•
•
•
•
How to Select the Tunneling Mode
•
•
•
How to Configure IP Tunnels
By default, IP tunnel recognition is disabled. Use this command to configure recognition of L2TP tunnels and skipping into the internal IP packet.
An IP tunnel is mutually exclusive with tunnel-based classification.
Step 1
ip tunnel L2TP skipand press Enter.Enables IP tunnel mode
•
no ip tunnel
How to Configure the VLAN Environment
Use this command to configure the VLAN environment.
•
•
Options
There are three options:
•
•
•
Symmetric environment refers to an environment in which the same VLAN tags are used for carrying a transaction in the upstream and downstream directions.
Setting the mode to classify means that subscriber and flow classification will use the VLAN tag. Using VLAN classification is mutually exclusive with other tunnel-based classification or IP tunnels.
An a-symmetric environment is an environment in which the VLAN tags might not be the same in the upstream and downstream directions.
The SCE platform is configured by default to work in symmetric environments. A specific command should be used to allow correct operation of the SCE platform in asymmetric environments and instruct it to take into consideration that the upstream and downstream of each flow has potentially different VLAN tags.
Note
Step 1
vlan {symmetric classify | symmetric skip |a-symmetric skip}and press Enter.Specify the desired VLAN mode.
Configuring the VLAN Environment: Example
The following example selects symmetric skip VLAN tunnel environment.
SCE(config if)#vlan symmetric skipHow to Configure the MPLS Environment
Use this command to set the MPLS environment.
•
•
Options
The following options are available:
•
•
•
When this option is configured, both ip-tunneland VLANmust be set to their default values.
Use the VPN keyword when the labels are mandatory in the traffic, otherwise use traffic-engineering (default).
Note that using the VPN value incurs a performance penalty.
The MPLS VPN auto-learn option is required in an MPLS/VPN environment.
Step 1
Specify the desired MPLS mode.
Configuring the MPLS Environment: Example
The following example selects the MPLS/VPN tunnel environment.
SCE(config if)#mpls vpn auto-learnHow to Configure the L2TP Environment
Use this command to set the port number that the LNS and LAC use for L2TP tunnels.
Options
The following option is available:
•
Default port# = 1701
Step 1
L2TP identify-by port-numberportnumberand press Enter.Enables privileged EXEC mode.
Note
How to Display the Tunneling Configuration
Step 1
show interface linecard 0 MPLS|VLAN|L2TP|IP-tunneland press Enter.Displays the current configuration for the specified tunnel option.
How to Configure VLAN Translation
•
•
•
•
About VLAN Translation
Some topologies require the SCE platform to be able to translate between different VLAN tags.
The following drawing illustrates an example of such a system, in which one router acts as a dispatcher, forwarding traffic and performing load balancing between two SCE 2000 platforms.
Figure 6-1 VLAN Translation
In this example, traffic enters the router via the access ports; it is forwarded to an EtherChannel, which is configured as a trunk, and enters the SCE 2000 platforms.
As can be seen from this drawing, the subscriber side VLAN tags must be different from those on the network side, or the router will simply forward the traffic to the opposite port. This can be supported very simply by having the SCE platform replace the VLAN tags according to a preset configuration.
VLAN Translation Features and Limitations
Features
•
•
•
•
•
•
•
Limitations
•
This means that in general, installations using the VLAN translation feature should rely on cutoff on failure and at upgrade (use redundant SCE platform).
•
•
How to Set the VLAN Translation Constant
Use this command to define the VLAN translation constant. Make sure that the same VLAN translation constant is configured for all SCE platforms in the system.
•
•
Options
The following options are available:
•
•
The configured translation is applied to the network port side. The reverse operation is performed at the subscriber side.
For example, if "increment 5" is defined, at the network port the VLAN is incremented by 5, and at the subscriber port the VLAN is decremented by 5.
In this case, the network side VLAN tags might be 105, 205, 305, and the subscriber side the VLAN tags would then be 100, 200, 300.
Default = 0
Maximum = 2047 (Note that there is no protection for wraparound of the VLAN value.)
Step 1
vlan translation increment|decrement valuevalueand press Enter.Sets the VLAN translation constant.
Setting the VLAN Translation Constant: Example
The following example sets the translation constant to 10, decremented at the network side.
SCE(config if)#vlan translation decrement value 10How to Disable VLAN Translation
Step 1
no vlan translationand press EnterDisables VLAN translation.
How to Monitor VLAN Translation
Step 1
Displays current VLAN translation configuration.
How to Configure Traffic Rules and Counters
•
•
•
•
Information About Traffic Rules and Counters
•
What are Traffic Rules and Counters?
Traffic rules and counters may be configured by the user. This functionality enables the user to define specific operations on the traffic flowing through the SCE Platform, such as blocking or ignoring certain flows or counting certain packets. The configuration of traffic rules and counters is independent of the application loaded by the SCE platform, and thus is preserved when the application being run by the SCE platform is changed.
Possible uses for traffic rules and counters include:
•
•
Possible examples include ignoring traffic from a certain IP range known to require no service, or traffic from a certain protocol.
•
Possible examples include performing ingress source address filtering (dropping packets originating from a subscriber port whose IP address does not belong to any defined subscriber-side subnet), or blocking specific ports.
It should be noted that using traffic rules and counters does not affect performance. It is possible to define the maximum number of both traffic rules and counters without causing any degradation in the SCE platform performance.
Traffic Rules
A traffic rule specifies that a defined action should be taken on packets processed by the SCE Platform that meet certain criteria. The maximum number of rules is 128, which includes not only traffic rules configured via the SCE platform CLI, but also any additional rules configured by external management systems, such as SCA BB. Each rule is given a name when it is defined, which is then used when referring to the rule.
Packets are selected according to user-defined criteria, which may be any combination of the following:
•
•
•
•
The possible actions are:
•
•
•
•
•
Block and Ignore actions affect only packets that are not part of an existing flow.
Note that Block and Ignore are mutually exclusive. However, blocked or ignored packets can also be counted.
It is possible for a single packet to match more that one rule (The simplest way to cause this is to configure two identical rules with different names). When this happens, the system operates as follows:
•
–
–
•
Traffic Counters
Traffic counters count the traffic as specified by the traffic rules. The maximum number of counters is 32. Each counter is given a name when it is defined, which is then used when referring to the counter.
A traffic counter can be configured in one of two ways:
•
•
How to Configure Traffic Counters
A traffic counter must be created before it can be referenced in a traffic rule. Use the following commands to create and delete traffic counters.
•
•
•
How to Create a Traffic Counter
Options
The following options are available:
•
•
•
Step 1
traffic-counter namenamecount-bytes|count-packets and press Enter.Adds a traffic counter with the specified name and counting mode..
How to Delete a Traffic Counter
Step 1
no traffic-counter namenameand press Enter.Note that a traffic counter cannot be deleted if it is used by any existing traffic rule.
How to Delete all Existing Traffic Counters
Step 1
no traffic-counter alland press Enter.Removes all traffic counters.
Note that a traffic counter cannot be deleted if it is used by any existing traffic rule.
How to Configure Traffic Rules
Use the following commands to create and delete traffic rules.
•
•
•
How to Create a Traffic Rule
•
•
Options
The following options are available:
IP specification:
all|([all-but] (ip-address|ip-range))•
•
•
protocol:
Any one of the following protocols:
TCP/UCP/ICMP/IGRP/EIGRP/IS-IS/OSPF/Othertunnel id specification:
all|([all-but] tunnel id)•
•
Use the traffic-rule tunnel-id-modecommand.
Note that the VLAN tag itself is a 12-bit value, and therefore aliasing of the lower 8 bits can occur, depending on the VLAN tags used.
direction:
Any of the following:
upstream/downstream/bothtraffic-counter:
Either of the following:
•
•
action: (not required if the action is count only)
One of the following:
•
•
•
•
Step 1
directiondirectiontraffic-counter <traffic-counter> [action action]Enables privileged EXEC mode.
Configuring Traffic Rules: Examples
Example 1
This example creates the following traffic rule:
•
•
•
•
•
•
SCE(config if)# traffic-rule rule1 IP-addresses subscriber-side all network-side 10.10.10.10 protocol other direction both traffic-counter name counter1Example 2
This example creates the following traffic rule:
•
•
•
•
•
•
•
•
The first command enables tunnel id mode.
SCE(config if)#traffic-rule tunnel-id-mode SCE(config if)# traffic-rule rule2 IP-addresses subscriber-side all network-side all-but 10.10.10.0/24 protocol tcp tunnel-id all direction downstream traffic-counter name counter2 action blockExample 3
This example creates the following traffic rule:
•
•
•
•
•
•
•
SCE(config if)# traffic-rule rule3 IP-addresses all protocol IS-IS direction upstream traffic-counter none action ignoreHow to Delete a Traffic Rule
Step 1
no traffic-rule namenameand press Enter.Removes the specified traffic rule.
How to Delete all Traffic Rules
Step 1
no traffic-rule alland press Enter.Removes all existing traffic rules.
How to Manage Traffic Rules and Counters
Use these commands to display existing traffic rule configuration, as well as traffic counter configuration (packets/bytes and the name of the rule using the counter) and traffic counter value.
You can also reset a specific counter or all counters.
•
•
•
•
•
•
How to View a Specified Traffic Rule
Step 1
show interface linecard 0 traffic-rule namerule-nameand press Enter.Displays the configuration of the specified traffic rule.
How to View all Traffic Rules
Step 1
show interface linecard 0 traffic-rule alland press Enter.Displays the configuration of all existing traffic rules.
How to View a Specified Traffic Counter
•
Step 1
show interface linecard 0 traffic-counter namecounter-nameand press Enter.Displays the value of the specified counter and lists the traffic rules that use it.
Viewing a Traffic Counter: Example
The following example displays information for the traffic counter "cnt".
SCE# show interface linecard 0 traffic-counter name cnt Counter 'cnt' value: 0 packets. Rules using it: None.How to View all Traffic Counters
Step 1
show interface linecard 0 traffic-counter alland press Enter.Displays the value of the each counter and lists the traffic rules that use it.
Viewing the Traffic Counters: Example
The following example displays information for all existing traffic counters.
SCE# show interface linecard 0 traffic-counter all Counter 'cnt' value: 0 packets. Rules using it: None. Counter 'cnt2' value: 0 packets. Rules using it: Rule2. 2 counters listed out of 32 available.How to Reset a Specified Traffic Counter
Step 1
clear interface linecard 0 traffic-counter namecounter-nameand press Enter.Displays the value of the specified counter and lists the traffic rules that use it.
How to Reset all Traffic Counters
Step 1
clear interface linecard 0 traffic-counter alland press Enter.Displays the value of the each counter and lists the traffic rules that use it.
How to Configure TOS Marking
•
About TOS Marking
The SCE platform TOS marking feature enables marking the TOS field in the IP header of each packet according to two applicative attributes of the packet: its Class (class of service) and its Color (reflects the packet's level of compliance to its relevant bandwidth limitations, where applicable). The actual TOS value set in the IP header is determined according to the configurable TOS table, based on the Class and Color. The default values in the TOS table are based on the Diffserv standard.
Note
How to Enable and Disable TOS Marking
How to Enable TOS Marking
Step 1
ToS-marking mode diffservand press Enter.Enables TOS marking.
How to Disable TOS Marking
Step 1
no ToS-marking mode diffservand press Enter.Disables TOS marking.
How to Modify the TOS Table
•
•
Options
The following options are available:
•
•
•
The value parameter must be in hexadecimal format in the range 0x0 to 0x3f .
Step 1
ToS-marking set-table-entry classclasscolor colorvalue value and press Enter.Modify the TOS Table: Example
The following example sets a TOS marking table entry.
SCE(config if)#ToS-marking set-table-entry class AF3 color green value 0x24How to Count Dropped Packets
•
•
About Counting Dropped Packets
By default, the SCE platform hardware drops red packets (packets that are marked to be dropped due to BW control criteria). However, this presents a problem for the user who needs to know the number of dropped packets per service. To be able to count dropped packets per service, the traffic processor must see all dropped packets for all flows. However, if the hardware is dropping red packets, the traffic processor will not be able to count all dropped packets and the user will not get proper values on the relevant MIB counters.
The user can disable the drop-red-packets-by-hardware mode. This allows the application to access existing per-flow counters. The application can then retrieve the number of dropped packets for every flow and provide the user with better visibility into the exact number of dropped packets and their distribution.
Note that counting all dropped packets has a considerable effect on system performance, and therefore, by default, the drop-red-packets-by-hardware mode is enabled.
How to Disable the Hardware Packet Drop
Use this command to disable the drop-red-packets-by-hardware mode, enabling the software to count all dropped packets.
By default hardware packet drop is enabled.
Note
Step 1
no accelerate-packet-dropsand press Enter.Disables hardware packet drop.
•
accelerate-packet-drops
Posted: Wed May 30 08:43:51 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
