MPLS Traffic Engineering with Autoroute
Problem
You want to use the Autoroute feature to automatically maintain traffic-engineered paths through your MPLS network.
Solution
This recipe uses Cisco's Autoroute feature for managing Traffic Engineering (TE) with OSPF in an MPLS network. For this method, we must explicitly define all of the traffic paths and associate them with Tunnels on the PE routers:
Router-PE1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router-PE1(config)#mpls traffic-eng tunnels Router-PE1(config)#interface Loopback0 Router-PE1(config-if)#ip address 10.0.0.2 255.255.255.255 Router-PE1(config-if)#exit Router-PE1(config)#interface Tunnel11 Router-PE1(config-if)#ip unnumbered Loopback0 Router-PE1(config-if)#tunnel destination 10.0.0.3 Router-PE1(config-if)#tunnel mode mpls traffic-eng Router-PE1(config-if)#tunnel mpls traffic-eng autoroute announce Router-PE1(config-if)#tunnel mpls traffic-eng priority 7 7 Router-PE1(config-if)#tunnel mpls traffic-eng bandwidth 256 Router-PE1(config-if)#tunnel mpls traffic-eng path-option 1 explicit name def-PE3 Router-PE1(config-if)#exit Router-PE1(config)#interface Tunnel12 Router-PE1(config-if)#ip unnumbered Loopback0 Router-PE1(config-if)#tunnel destination 10.0.0.3 Router-PE1(config-if)#tunnel mode mpls traffic-eng Router-PE1(config-if)#tunnel mpls traffic-eng autoroute announce Router-PE1(config-if)#tunnel mpls traffic-eng priority 7 7 Router-PE1(config-if)#tunnel mpls traffic-eng bandwidth 256 Router-PE1(config-if)#tunnel mpls traffic-eng path-option 1 explicit name hi-PE3 Router-PE1(config-if)#exit Router-PE1(config)#interface Serial0/0 Router-PE1(config-if)#ip address 10.1.1.13 255.255.255.252 Router-PE1(config-if)#mpls traffic-eng tunnels Router-PE1(config-if)#tag-switching ip Router-PE1(config-if)#ip rsvp bandwidth 512 Router-PE1(config-if)#exit Router-PE1(config)#interface ATM1/0.1 tag-switching Router-PE1(config-subif)#ip address 10.1.1.2 255.255.255.252 Router-PE1(config-subif)#mpls traffic-eng tunnels Router-PE1(config-subif)#tag-switching ip Router-PE1(config-subif)#ip rsvp bandwidth 4000 Router-PE1(config-subif)#exit Router-PE1(config)#router ospf 99 Router-PE1(config-router)#router-id 10.0.0.2 Router-PE1(config-router)#log-adjacency-changes Router-PE1(config-router)#network 10.0.0.0 0.255.255.255 area 0 Router-PE1(config-router)#mpls traffic-eng router-id Loopback0 Router-PE1(config-router)#mpls traffic-eng area 0 Router-PE1(config-router)#exit Router-PE1(config)#ip explicit-path name def-PE3 enable Router-PE1(cfg-ip-expl-path)#next-address 10.1.1.14 Explicit Path name def-PE3: 1: next-address 10.1.1.14 Router-PE1(cfg-ip-expl-path)#next-address 10.1.1.9 Explicit Path name def-PE3: 1: next-address 10.1.1.14 2: next-address 10.1.1.9 Router-PE1(cfg-ip-expl-path)#exit Router-PE1(config)#ip explicit-path name hi-PE3 enable Router-PE1(cfg-ip-expl-path)#next-address 10.1.1.1 Explicit Path name hi-PE3: 1: next-address 10.1.1.1 Router-PE1(cfg-ip-expl-path)#next-address 10.1.1.6 Explicit Path name hi-PE3: 1: next-address 10.1.1.1 2: next-address 10.1.1.6 Router-PE1(cfg-ip-expl-path)#exit Router-PE1(config)#end Router-PE1#
The other PE router has a similar configuration:
Router-PE3#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router-PE3(config)#mpls traffic-eng tunnels Router-PE3(config)#interface Loopback0 Router-PE3(config-if)#ip address 10.0.0.3 255.255.255.255 Router-PE3(config-if)#exit Router-PE3(config)#interface Tunnel11 Router-PE3(config-if)#ip unnumbered Loopback0 Router-PE3(config-if)#tunnel destination 10.0.0.2 Router-PE3(config-if)#tunnel mode mpls traffic-eng Router-PE3(config-if)#tunnel mpls traffic-eng autoroute announce Router-PE3(config-if)#tunnel mpls traffic-eng priority 7 7 Router-PE3(config-if)#tunnel mpls traffic-eng bandwidth 256 Router-PE3(config-if)#tunnel mpls traffic-eng path-option 1 explicit name def-PE1 Router-PE3(config-if)#exit Router-PE3(config)#interface Tunnel12 Router-PE3(config-if)#ip unnumbered Loopback0 Router-PE3(config-if)#tunnel destination 10.0.0.2 Router-PE3(config-if)#tunnel mode mpls traffic-eng Router-PE3(config-if)#tunnel mpls traffic-eng autoroute announce Router-PE3(config-if)#tunnel mpls traffic-eng priority 7 7 Router-PE3(config-if)#tunnel mpls traffic-eng bandwidth 256 Router-PE3(config-if)#tunnel mpls traffic-eng path-option 1 explicit name hi-PE1 Router-PE3(config-if)#exit Router-PE3(config)#interface Serial0/0 Router-PE3(config-if)#ip address 10.1.1.9 255.255.255.252 Router-PE3(config-if)#mpls traffic-eng tunnels Router-PE3(config-if)#tag-switching ip Router-PE3(config-if)#ip rsvp bandwidth 512 Router-PE3(config-if)#exit Router-PE3(config)#interface ATM1/0.1 tag-switching Router-PE3(config-subif)#ip address 10.1.1.6 255.255.255.252 Router-PE3(config-subif)#mpls traffic-eng tunnels Router-PE3(config-subif)#tag-switching ip Router-PE3(config-subif)#ip rsvp bandwidth 4000 Router-PE3(config-subif)#exit Router-PE3(config)#router ospf 99 Router-PE3(config-router)#router-id 10.0.0.3 Router-PE3(config-router)#log-adjacency-changes Router-PE3(config-router)#network 10.0.0.0 0.255.255.255 area 0 Router-PE3(config-router)#mpls traffic-eng router-id Loopback0 Router-PE3(config-router)#mpls traffic-eng area 0 Router-PE3(config-router)#exit Router-PE3(config)#ip explicit-path name def-PE1 enable Router-PE3(cfg-ip-expl-path)#next-address 10.1.1.10 Explicit Path name def-PE1: 1: next-address 10.1.1.10 Router-PE3(cfg-ip-expl-path)#next-address 10.1.1.13 Explicit Path name def-PE1: 1: next-address 10.1.1.10 2: next-address 10.1.1.13 Router-PE3(cfg-ip-expl-path)#exit Router-PE3(config)#ip explicit-path name hi-PE1 enable Router-PE3(cfg-ip-expl-path)#next-address 10.1.1.5 Explicit Path name hi-PE1: 1: next-address 10.1.1.5 Router-PE3(cfg-ip-expl-path)#next-address 10.1.1.2 Explicit Path name hi-PE1: 1: next-address 10.1.1.5 2: next-address 10.1.1.2 Router-PE3(cfg-ip-expl-path)#exit Router-PE3(config)#end Router-PE3#
Then we have to configure the P routers, which are somewhat simpler because they don't require tunnels or explicit path definitions. We will show only one P router because they are all essentially the same:
Router-P1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router-P1(config)#mpls traffic-eng tunnels Router-P1(config)#interface Loopback0 Router-P1(config-if)#ip address 10.0.0.11 255.255.255.255 Router-P1(config-if)#exit Router-P1(config)#interface Serial0/0 Router-P1(config-if)#ip address 10.1.1.14 255.255.255.252 Router-P1(config-if)#tag-switching ip Router-P1(config-if)#mpls traffic-eng tunnels Router-P1(config-if)#ip rsvp bandwidth 512 Router-P1(config-if)#exit Router-P1(config)#interface Serial0/1 Router-P1(config-if)#ip address 10.1.1.10 255.255.255.252 Router-P1(config-if)#tag-switching ip Router-P1(config-if)#mpls traffic-eng tunnels Router-P1(config-if)#ip rsvp bandwidth 512 Router-P1(config-if)#exit Router-P1(config)#router ospf 99 Router-P1(config-router)#router-id 10.0.0.11 Router-P1(config-router)#log-adjacency-changes Router-P1(config-router)#network 10.0.0.0 0.255.255.255 area 0 Router-P1(config-router)#mpls traffic-eng router-id Loopback0 Router-P1(config-router)#mpls traffic-eng area 0 Router-P1(config-router)#exit Router-P1(config)#end Router-P1#
Discussion
Traffic Engineering (TE) is a large and complicated topic in itself, and a detailed discussion is out of the scope of this book. For more information, we encourage the reader to refer to one of the many books dedicated to MPLS networking.
In this example, we take advantage of OSPF to distribute information about resource utilization within the MPLS cloud. OSPF uses LSP number 10, the so-called Opaque LSP, to flood this information throughout the area. We enable this feature by using the mpls traffic-eng OSPF configuration commands:
Router-PE3(config)#router ospf 99 Router-PE3(config-router)#router-id 10.0.0.3 Router-PE3(config-router)#log-adjacency-changes Router-PE3(config-router)#network 10.0.0.0 0.255.255.255 area 0 Router-PE3(config-router)#mpls traffic-eng router-id Loopback0 Router-PE3(config-router)#mpls traffic-eng area 0
Since these TE LSPs are only flooded within the area, we have to specify the area to be used. In this case, everything is in Area 0. We have also specified a stable Loopback interface as the source for all TE LSPs to ensure that the information contained in these updates is consistent. Note that although the TE router-id is the same as the main OSPF router ID in this case, this is not always true. Recall from Chapter 8 that the main OSPF router ID is an arbitrary 32-bit value that does not need to be associated with any interfaces on the router.
The bandwidth resource information that the routers send using this method comes from RSVP, which we discuss in greater detail in Chapter 11. We enable RSVP on each MPLS interface and associate with it a maximum reservable bandwidth512 Kbps, in this case:
Router-PE1(config)#interface Serial0/0 Router-PE1(config-if)#ip address 10.1.1.13 255.255.255.252 Router-PE1(config-if)#mpls traffic-eng tunnels Router-PE1(config-if)#tag-switching ip Router-PE1(config-if)#ip rsvp bandwidth 512
This underscores one of the important features of TE tunnels. You can think of them as bandwidth reserved point-to-point virtual circuits between PE routers, across the MPLS cloud. RSVP handles the bandwidth reservation.
But the big trick to this particular type of MPLS TE is the use of special tunnels between the PE routers:
Router-PE1(config)#interface Tunnel11 Router-PE1(config-if)#ip unnumbered Loopback0 Router-PE1(config-if)#tunnel destination 10.0.0.3 Router-PE1(config-if)#tunnel mode mpls traffic-eng Router-PE1(config-if)#tunnel mpls traffic-eng autoroute announce Router-PE1(config-if)#tunnel mpls traffic-eng priority 7 7 Router-PE1(config-if)#tunnel mpls traffic-eng bandwidth 256 Router-PE1(config-if)#tunnel mpls traffic-eng path-option 1 explicit name def-PE3
In this case, we have defined a tunnel from Router-PE1 to Router-PE3. The tunnel mode command specifies that this is to be an MPLS TE tunnel. Recall that in Chapter 12 we looked at other tunnel types such as GRE. This is similar to those tunnels in that it can carry a wide variety of protocols. However it is dynamically generated by the MPLS TE process whenever it is required. The priority and bandwidth options define parameters that the TE process can use to determine which tunnels and which pathways may be used.
The most interesting command in this tunnel configuration is the last one, which associates this tunnel with an explicit path through the MPLS cloud. In this case, the path is named def-PE3, and it is defined using the ip explicit-path command:
Router-PE1(config)#ip explicit-path name def-PE3 enable Router-PE1(cfg-ip-expl-path)#next-address 10.1.1.14 Router-PE1(cfg-ip-expl-path)#next-address 10.1.1.9
Usually in IP networking we don't want to explicitly define paths through the network for two main reasons. First, it doesn't scale well, and second, we usually want the routing protocol to select the best path for us. With TE, however, we do want to exercise control over which of many possible paths a particular conversation might take.
In this example, we have defined two flows, one through each of the two available paths, and have named them "def" and "hi" for default and high priority, respectively. You could use this in conjunction with the MPLS QoS functionality discussed in Recipe 26.9 to make sure that high priority traffic is sent through a different physical path through the network than low priority traffic.
The big advantage to using an IGP like OSPF to control these TE tunnels is that we can still have all of the fault tolerance afforded by multiple paths through the network. And, at the same time, we can ensure that all of the available paths are used appropriately to maximize throughput or to balance the internal loading of the network.
You can see which tunnels are in use with the show mpls traffic-eng tunnels command:
Router-PE1#show mpls traffic-eng tunnels Name: Router-PE1_t11 (Tunnel11) Destination: 10.0.0.3 Status: Admin: up Oper: up Path: valid Signalling: connected path option 1, type explicit def-PE3 (Basis for Setup, path weight 128) Config Parameters: Bandwidth: 256 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) AutoRoute: enabled LockDown: disabled Loadshare: 256 bw-based auto-bw: disabled InLabel : - OutLabel : Serial0/0, 18 RSVP Signalling Info: Src 10.0.0.2, Dst 10.0.0.3, Tun_Id 11, Tun_Instance 16 RSVP Path Info: My Address: 10.0.0.2 Explicit Route: 10.1.1.14 10.1.1.9 10.0.0.3 Record Route: NONE Tspec: ave rate=256 kbits, burst=1000 bytes, peak rate=256 kbits RSVP Resv Info: Record Route: NONE Fspec: ave rate=256 kbits, burst=1000 bytes, peak rate=256 kbits History: Tunnel: Time since created: 2 hours, 14 minutes Time since path change: 2 hours, 12 minutes Current LSP: Uptime: 2 hours, 12 minutes Name: Router-PE1_t12 (Tunnel12) Destination: 10.0.0.3 Status: Admin: up Oper: down Path: not valid Signalling: Down path option 1, type explicit hi-PE3 Config Parameters: Bandwidth: 256 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) AutoRoute: enabled LockDown: disabled Loadshare: 256 bw-based auto-bw: disabled History: Tunnel: Time since created: 2 hours, 14 minutes Path Option 1: Last Error: PCALC:: Explicit path has unknown address, 10.1.1.1 LSP Tunnel Router-PE3_t11 is signalled, connection is up InLabel : Serial0/0, implicit-null OutLabel : - RSVP Signalling Info: Src 10.0.0.3, Dst 10.0.0.2, Tun_Id 11, Tun_Instance 30 RSVP Path Info: My Address: 10.0.0.2 Explicit Route: NONE Record Route: NONE Tspec: ave rate=256 kbits, burst=1000 bytes, peak rate=256 kbits RSVP Resv Info: Record Route: NONE Fspec: ave rate=256 kbits, burst=1000 bytes, peak rate=256 kbits Router-PE1#
See Also
Chapters 8, 11, and 12; Recipe 26.9
Router Configuration and File Management
- Configuring the Router via TFTP
- Saving Router Configuration to Server
- Booting the Router Using a Remote Configuration File
- Storing Configuration Files Larger Than NVRAM
- Clearing the Startup Configuration
- Loading a New IOS Image
- Booting a Different IOS Image
- Booting over the Network
- Copying an IOS Image to a Server
- Copying an IOS Image Through the Console
- Deleting Files from Flash
- Partitioning Flash
- Using the Router as a TFTP Server
- Using FTP from the Router
- Generating Large Numbers of Router Configurations
- Changing the Configurations of Many Routers at Once
- Extracting Hardware Inventory Information
- Backing Up Router Configurations
- Warm Reload
- Warm Upgrade
- Configuration Archiving
- Locking Configuration Access
Router Management
- Creating Command Aliases
- Managing the Routers ARP Cache
- Tuning Router Buffers
- Auto Tuning Buffers
- Using the Cisco Discovery Protocol
- Disabling the Cisco Discovery Protocol
- Using the Small Servers
- Enabling HTTP Access to a Router
- Enabling Secure HTTP (HTTPS) Access to a Router
- Using Static Hostname Tables
- Enabling Domain Name Services
- Disabling Domain Name Lookups
- Specifying a Router Reload Time
- Scheduling of Router Commands
- Displaying Historical CPU Values
- Creating Exception Dump Files
- Generating a Report of Interface Information
- Generating a Report of Routing Table Information
- Generating a Report of ARP Table Information
- Generating a Server Host Table File
User Access and Privilege Levels
- Setting Up User IDs
- Encrypting Passwords
- Using Better Password-Encryption Techniques
- Removing Passwords from a Router Configuration File
- Deciphering Ciscos Weak Password Encryption
- Displaying Active Users
- Sending Messages to Other Users
- Changing the Number of VTYs
- Changing VTY Timeouts
- Restricting VTY Access by Protocol
- Enabling Absolute Timeouts on VTY Lines
- Implementing Banners
- Disabling Banners on a Port
- Disabling Router Lines
- Reserving a VTY Port for Administrative Access
- Restricting Inbound Telnet Access
- Logging Telnet Access
- Setting the Source Address for Telnet
- Automating the Login Sequence
- Using SSH for Secure Access
- Changing Privilege Level of IOS Commands
- Defining Per User Privileges
- Defining Per Port Privileges
TACACS+
- Authenticating Login IDs from a Central System
- Restricting Command Access
- Losing Access to the TACACS+ Server
- Disabling TACACS+ Authentication on a Particular Line
- Capturing User Keystrokes
- Logging System Events
- Setting the IP Source Address for TACACS+ Messages
- Sample Server Configuration Files
IP Routing
- Finding an IP Route
- Finding Types of IP Routes
- Converting Different Mask Formats
- Using Static Routing
- Floating Static Routes
- Using Policy-Based Routing to Route Based on Source Address
- Using Policy-Based Routing to Route Based on Application Type
- Examining Policy-Based Routing
- Changing Administrative Distances
- Routing Over Multiple Paths with Equal Costs
- Static Routes That Track Interfaces or Other Routes
- Keeping Statistics on Routing Table Changes
RIP
- Configuring RIP Version 1
- Filtering Routes with RIP
- Redistributing Static Routes into RIP
- Redistributing Routes Using Route Maps
- Creating a Default Route in RIP
- Disabling RIP on an Interface
- Default Passive Interface
- Unicast Updates for RIP
- Applying Offsets to Routes
- Adjusting Timers
- Configuring Interpacket Delay
- Enabling Nonperiodic Updates
- Increasing the RIP Input Queue
- Configuring RIP Version 2
- Enabling RIP Authentication
- RIP Route Summarization
- Route Tagging
EIGRP
- Configuring EIGRP
- Filtering Routes with EIGRP
- Redistributing Routes into EIGRP
- Redistributing Routes into EIGRP Using Route Maps
- Disabling EIGRP on an Interface
- Adjusting EIGRP Metrics
- Adjusting Timers
- Enabling EIGRP Authentication
- EIGRP Route Summarization
- Logging EIGRP Neighbor State Changes
- Limiting EIGRPs Bandwidth Utilization
- EIGRP Stub Routing
- Route Tagging
- Viewing EIGRP Status
OSPF
- Configuring OSPF
- Filtering Routes in OSPF
- Adjusting OSPF Costs
- Creating a Default Route in OSPF
- Redistributing Static Routes into OSPF
- Redistributing External Routes into OSPF
- Manipulating DR Selection
- Setting the OSPF RID
- Enabling OSPF Authentication
- Selecting the Appropriate Area Types
- Using OSPF on Dial Interfaces
- Summarizing Routes in OSPF
- Disabling OSPF on Certain Interfaces
- Changing the Network Type on an Interface
- OSPF Route Tagging
- Logging OSPF Adjacency Changes
- Adjusting OSPF Timers
- Reducing OSPF Traffic in Stable Networks
- OSPF Virtual Links
- Viewing OSPF Status with Domain Names
- Debugging OSPF
BGP
- Configuring BGP
- Using eBGP Multihop
- Adjusting the Next-Hop Attribute
- Connecting to Two ISPs
- Connecting to Two ISPs with Redundant Routers
- Restricting Networks Advertised to a BGP Peer
- Adjusting Local Preference Values
- Load-Balancing
- Removing Private ASNs from the AS Path
- Filtering BGP Routes Based on AS Paths
- Reducing the Size of the Received Routing Table
- Summarizing Outbound Routing Information
- Prepending ASNs to the AS Path
- Redistributing Routes with BGP
- Using Peer Groups
- Authenticating BGP Peers
- Using BGP Communities
- Using BGP Route Reflectors
- Putting It All Together
Frame Relay
- Setting Up Frame Relay with Point-to-Point Subinterfaces
- Adjusting LMI Options
- Setting Up Frame Relay with Map Statements
- Using Multipoint Subinterfaces
- Configuring Frame Relay SVCs
- Simulating a Frame Relay Cloud
- Compressing Frame Relay Data on a Subinterface
- Compressing Frame Relay Data with Maps
- PPP over Frame Relay
- Viewing Frame Relay Status Information
Handling Queuing and Congestion
- Fast Switching and CEF
- Setting the DSCP or TOS Field
- Using Priority Queuing
- Using Custom Queuing
- Using Custom Queues with Priority Queues
- Using Weighted Fair Queuing
- Using Class-Based Weighted Fair Queuing
- Using NBAR Classification
- Controlling Congestion with WRED
- Using RSVP
- Manual RSVP Reservations
- Aggregating RSVP Reservations
- Using Generic Traffic Shaping
- Using Frame-Relay Traffic Shaping
- Using Committed Access Rate
- Implementing Standards-Based Per-Hop Behavior
- AutoQoS
- Viewing Queue Parameters
Tunnels and VPNs
- Creating a Tunnel
- Tunneling Foreign Protocols in IP
- Tunneling with Dynamic Routing Protocols
- Viewing Tunnel Status
- Creating an Encrypted Router-to-Router VPN in a GRE Tunnel
- Creating an Encrypted VPN Between the LAN Interfaces of Two Routers
- Generating RSA Keys
- Creating a Router-to-Router VPN with RSA Keys
- Creating a VPN Between a Workstation and a Router
- Creating an SSL VPN
- Checking IPSec Protocol Status
Dial Backup
- Automating Dial Backup
- Using Dialer Interfaces
- Using an Async Modem on the AUX Port
- Using Backup Interfaces
- Using Dialer Watch
- Using Virtual Templates
- Ensuring Proper Disconnection
- View Dial Backup Status
- Debugging Dial Backup
NTP and Time
- Time-Stamping Router Logs
- Setting the Time
- Setting the Time Zone
- Adjusting for Daylight Saving Time
- Synchronizing the Time on All Routers (NTP)
- Configuring NTP Redundancy
- Setting the Router As the NTP Master for the Network
- Changing NTP Synchronization Periods
- Using NTP to Send Periodic Broadcast Time Updates
- Using NTP to Send Periodic Multicast Time Updates
- Enabling and Disabling NTP Per Interface
- NTP Authentication
- Limiting the Number of Peers
- Restricting Peers
- Setting the Clock Period
- Checking the NTP Status
- Debugging NTP
- NTP Logging
- Extended Daylight Saving Time
- NTP Server Configuration
DLSw
- Simple Bridging
- Configuring DLSw
- Using DLSw to Bridge Between Ethernet and Token Ring
- Converting Ethernet and Token Ring MAC Addresses
- Configuring SDLC
- Configuring SDLC for Multidrop Connections
- Using STUN
- Using BSTUN
- Controlling DLSw Packet Fragmentation
- Tagging DLSw Packets for QoS
- Supporting SNA Priorities
- DLSw+ Redundancy and Fault Tolerance
- Viewing DLSw Status Information
- Viewing SDLC Status Information
- Debugging DSLw
Router Interfaces and Media
- Viewing Interface Status
- Configuring Serial Interfaces
- Using an Internal T1 CSU/DSU
- Using an Internal ISDN PRI Module
- Using an Internal 56 Kbps CSU/DSU
- Configuring an Async Serial Interface
- Configuring ATM Subinterfaces
- Setting Payload Scrambling on an ATM Circuit
- Classical IP Over ATM
- Configuring Ethernet Interface Features
- Configuring Token Ring Interface Features
- Connecting VLAN Trunks with ISL
- Connecting VLAN Trunks with 802.1Q
- LPD Printer Support
Simple Network Management Protocol
- Configuring SNMP
- Extracting Router Information via SNMP Tools
- Recording Important Router Information for SNMP Access
- Using SNMP to Extract Inventory Information from a List of Routers
- Using Access Lists to Protect SNMP Access
- Logging Unauthorized SNMP Attempts
- Limiting MIB Access
- Using SNMP to Modify a Routers Running Configuration
- Using SNMP to Copy a New IOS Image
- Using SNMP to Perform Mass Configuration Changes
- Preventing Unauthorized Configuration Modifications
- Making Interface Table Numbers Permanent
- Enabling SNMP Traps and Informs
- Sending Syslog Messages As SNMP Traps and Informs
- Setting SNMP Packet Size
- Setting SNMP Queue Size
- Setting SNMP Timeout Values
- Disabling Link Up/Down Traps per Interface
- Setting the IP Source Address for SNMP Traps
- Using RMON to Send Traps
- Enabling SNMPv3
- Strong SNMPv3 Encryption
- Using SAA
Logging
- Enabling Local Router Logging
- Setting the Log Size
- Clearing the Routers Log
- Sending Log Messages to Your Screen
- Using a Remote Log Server
- Enabling Syslog on a Unix Server
- Changing the Default Log Facility
- Restricting What Log Messages Are Sent to the Server
- Setting the IP Source Address for Syslog Messages
- Logging Router Syslog Messages in Different Files
- Maintaining Syslog Files on the Server
- Testing the Syslog Sever Configuration
- Preventing the Most Common Messages from Being Logged
- Rate-Limiting Syslog Traffic
- Enabling Error Log Counting
- XML-Formatted Log Messages
- Modifying Log Messages
Access-Lists
- Filtering by Source or Destination IP Address
- Adding a Comment to an ACL
- Filtering by Application
- Filtering Based on TCP Header Flags
- Restricting TCP Session Direction
- Filtering Multiport Applications
- Filtering Based on DSCP and TOS
- Logging When an Access-List Is Used
- Logging TCP Sessions
- Analyzing ACL Log Entries
- Using Named and Reflexive Access-Lists
- Dealing with Passive Mode FTP
- Using Time-Based Access-Lists
- Filtering Based on Noncontiguous Ports
- Advanced Access-List Editing
- Filtering IPv6
DHCP
- Using IP Helper Addresses for DHCP
- Limiting the Impact of IP Helper Addresses
- Using DHCP to Dynamically Configure Router IP Addresses
- Dynamically Allocating Client IP Addresses via DHCP
- Defining DHCP Configuration Options
- Defining DHCP Lease Periods
- Allocating Static IP Addresses with DHCP
- Configuring a DHCP Database Client
- Configuring Multiple DHCP Servers per Subnet
- DHCP Static Mapping
- DHCP-Secured IP Address Assignment
- Showing DHCP Status
- Debugging DHCP
NAT
- Configuring Basic NAT Functionality
- Allocating External Addresses Dynamically
- Allocating External Addresses Statically
- Translating Some Addresses Statically and Others Dynamically
- Using Route Maps to Refine Static Translation Rules
- Translating in Both Directions Simultaneously
- Rewriting the Network Prefix
- Using NAT for Server Load Distribution
- Stateful NAT Failover
- Adjusting NAT Timers
- Changing TCP Ports for FTP
- Checking NAT Status
- Debugging NAT
First Hop Redundancy Protocols
- Configuring Basic HSRP Functionality
- Using HSRP Preempt
- Making HSRP React to Problems on Other Interfaces
- Load-Balancing with HSRP
- Redirecting ICMP with HSRP
- Manipulating HSRP Timers
- Using HSRP on Token Ring
- HSRP SNMP Support
- Increasing HSRP Security
- Showing HSRP State Information
- Debugging HSRP
- HSRP Version 2
- VRRP
- Gateway Load-Balancing Protocol
IP Multicast
- Configuring Basic Multicast Functionality with PIM-DM
- Routing Multicast Traffic with PIM-SM and BSR
- Routing Multicast Traffic with PIM-SM and Auto-RP
- Filtering PIM Neighbors
- Configuring Routing for a Low-Frequency Multicast Application
- Multicast over Frame Relay or ATM WANs
- Configuring CGMP
- Using IGMP Version 3
- Static Multicast Routes and Group Memberships
- Routing Multicast Traffic with MOSPF
- Routing Multicast Traffic with DVMRP
- DVMRP Tunnels
- Configuring Bidirectional PIM
- Controlling Multicast Scope with TTL
- Controlling Multicast Scope with Administratively Scoped Addressing
- Exchanging Multicast Routing Information with MBGP
- Using MSDP to Discover External Sources
- Configuring Anycast RP
- Converting Broadcasts to Multicasts
- Showing Multicast Status
- Debugging Multicast Routing
IP Mobility
- Local Area Mobility
- Home Agent Configuration
- Foreign Agent Configuration
- Making a Router a Mobile Node
- Reverse-Tunnel Forwarding
- Using HSRP for Home Agent Redundancy
IPv6
- Automatically Generating IPv6 Addresses for an Interface
- Manually Configuring IPv6 Addresses on an Interface
- Configuring DHCP for IPv6
- Dynamic Routing with RIP
- Modifying the Default RIP Parameters
- IPv6 Route Filtering and Metric Manipulation in RIP
- Using OSPF for IPv6
- IPv6 Route Filtering and Metric Manipulation in OSPF
- Route Redistribution
- Dynamic Routing with MBGP
- Tunneling IPv6 Through an Existing IPv4 Network
- Translating Between IPv6 and IPv4
MPLS
- Configuring a Basic MPLS P Router
- Configuring a Basic MPLS PE Router
- Configuring Basic MPLS CE Routers
- Configuring MPLS over ATM
- PE-CE Communication via RIP
- PE-CE Communication via OSPF
- PE-CE Communication via EIGRP
- PE-CE Communication via BGP
- QoS over MPLS
- MPLS Traffic Engineering with Autoroute
- Multicast Over MPLS
- Your Service Provider Doesnt Do What You Want
Security
- Using AutoSecure
- Using Context-Based Access-Lists
- Transparent Cisco IOS Firewall
- Stopping Denial of Service Attacks
- Inspecting Applications on Different Port Numbers
- Intrusion Detection and Prevention
- Login Password Retry Lockout
- Authentication Proxy
Appendix 1. External Software Packages
Appendix 2. IP Precedence, TOS, and DSCP Classifications
- IP Precedence, TOS, and DSCP Classifications
- Queueing Algorithms
- Dropping Packets and Congestion Avoidance
Index
Cisco IOS Cookbook (Cookbooks (OReilly))
ISBN: 0596527225
EAN: 2147483647
EAN: 2147483647
Year: 2004
Pages: 505
Pages: 505
Authors: Kevin Dooley, Ian Brown
