Tracing IS-IS Protocol Traffic
Problem
You are setting up IS-IS on your network and want to keep a running log of IS-IS protocol packets that the router is sending to help you track any problems that might occur during the configuration process.
Solution
Set up a tracing file that captures information about IS-IS protocol operations:
[edit protocols isis] aviva@RouterJ# set traceoptions file isis-logs aviva@RouterJ# set traceoptions flag error aviva@RouterJ# set traceoptions flag general aviva@RouterJ# set traceoptions flag normal
To stop the tracing, remove the traceoptions statement from the configuration:
[edit protocols isis] aviva@RouterJ# delete traceoptions
Discussion
To debug IS-IS operations, use the JUNOS tracing facility to track the packets that IS-IS is sending and receiving. You specify the name of the file to which you want to collect the information and the type of information you want to trace. In this example, we set three flags to track normal operations and errors in the file isis-logs, which is on the routers hard disk in the directory /var/log (on M-series and T-series routers) and /cf/var/log (on J-series routers).
When you are first bringing up an IS-IS network, you may find that an adjacency is not establishing between two Level 1 routers:
aviva@RouterJ> show isis adjacency Interface System L State Hold (secs) SNPA fe-0/0/1.0 RouterF 1 Down 0 0:5:85:c1:86:31 fe-1/0/0.0 RouterH 2 Up 22 0:5:85:c1:d1:f4 fe-1/0/1.0 RouterG 2 Up 24 0:5:85:c2:2e:f5
The logfile shows where the problem is:
aviva@RouterJ> show log isis-logs | last Jun 25 12:47:15 ERROR: IIH from RouterG with no matching areas, interface fe-1/0/1.0 Jun 25 12:47:15 local area 49.0050 Jun 25 12:47:15 remote area 49.0020 (3 bytes) Jun 25 12:47:15 ERROR: IIH from RouterF with no matching areas, interface fe-0/0/1.0 Jun 25 12:47:15 local area 49.0050 Jun 25 12:47:15 remote area 49.0051 (3 bytes)
The second error shows that the adjacency to the Level 1 router RouterF is down because RouterJ is in Area 50, while RouterF has been accidentally misconfigured to be in Area 51. You might wonder why we are not concerned with the first error in the file, which also reports an area mismatch. We don care about this because RouterG is another Level 2 router and is in a different area (Area 20), so its fine for it to have a different area number.
Over time, the IS-IS logfiles can become very large and fill up the routers hard disk. To save the logfile for future analysis, you can copy the file to a server:
aviva@RouterJ> file copy /cf/var/log/isis-logs server1:isis-logs-20050625
If you no longer need the information in the file, you can delete the contents:
aviva@RouterJ> clear log isis-logs
Deleting the files contents does not turn off tracing.
To stop the tracing altogether, you can remove the traceoptions statement from the configuration with the delete traceoptions command or you can leave the statements in the configuration and simply deactivate them so that they do not take effect when you commit the configuration:
[edit protocols isis] aviva@RouterJ# deactivate traceoptions
To delete the logfiles and the rolled-over version of the file, use the file delete command:
aviva@RouterJ> file delete isis-logs*
When debugging IS-IS, you can set one or more of the following trace flags to capture IS-IS information:
[edit protocols isis traceoptions] aviva@RouterA# set flag ? Possible completions: all Trace everything csn Trace complete sequence number (CSN) packets error Trace errored packets general Trace general events graceful-restart Trace graceful restart events hello Trace hello packets lsp Trace link-state packets lsp-generation Trace LSP generation normal Trace normal events packets Trace IS-IS packets policy Trace policy processing psn Trace partial sequence number (PSN) packets route Trace routing information spf Trace SPF events state Trace state transitions task Trace routing protocol task processing timer Trace routing protocol timer processing
Using some of the other flags, you can see IS-IS protocol packet exchanges:
Jun 25 13:06:31 Sending L2 CSN on interface fe-1/0/0.0 Jun 25 13:06:31 LSP range 0000.0000.0000.00-00 to ffff.ffff.ffff.ff-ff Jun 25 13:06:31 packet length 131 Jun 25 13:06:31 Received L1 LAN IIH, source id RouterH on fe-1/0/0.0 Jun 25 13:06:31 ERROR: IIH from RouterH with no matching areas, interface fe-1/0/0.0 Jun 25 13:06:31 local area 49.0050 Jun 25 13:06:31 remote area 49.0030 (3 bytes) Jun 25 13:06:31 ISIS L2 periodic xmit to 01:80:c2:00:00:15 interface fe-1/0/1.0 Jun 25 13:06:31 ISIS L2 periodic xmit to 01:80:c2:00:00:15 interface fe-1/0/0.0 Jun 25 13:06:31 ISIS L2 hello from RouterH interface fe-1/0/0.0 absorbed Jun 25 13:06:32 Sending L2 CSN on interface fe-1/0/1.0 Jun 25 13:06:32 LSP range 0000.0000.0000.00-00 to ffff.ffff.ffff.ff-ff Jun 25 13:06:32 packet length 131 Jun 25 13:06:32 Sending L1 CSN on interface fe-0/0/1.0 Jun 25 13:06:32 LSP range 0000.0000.0000.00-00 to ffff.ffff.ffff.ff-ff Jun 25 13:06:32 packet length 83 Jun 25 13:06:32 Received L1 LAN IIH, source id RouterG on fe-1/0/1.0 Jun 25 13:06:32 ERROR: IIH from RouterG with no matching areas, interface fe-1/0/1.0 Jun 25 13:06:32 local area 49.0050 Jun 25 13:06:32 remote area 49.0020 (3 bytes) Jun 25 13:06:33 ISIS L1 hello from RouterF interface fe-0/0/1.0 absorbed Jun 25 13:06:33 ISIS L1 periodic xmit to 01:80:c2:00:00:14 interface fe-0/0/1.0 Jun 25 13:06:33 ISIS L2 hello from RouterG interface fe-1/0/1.0 absorbed
This logfile snippet shows that IS-IS exchanges complete sequence number (CSN) LSPs with one of its Level 2 and one of its Level 1 neighbors. You also see the periodic transmission of IS-IS Hello packets.
See Also
Recipe 5.10
Router Configuration and File Management
- Introduction
- Configuring the Router for the First Time
- Configuring the Router from the CLI
- Getting Exclusive Access to Configure the Router
- Displaying the Commands to Recreate a Configuration
- Including Comments in the Configuration
- Checking the Syntax of the Configuration
- Activating the Router Configuration
- Debugging a Failed Commit
- Exiting Configuration Mode
- Keeping a Record of Configuration Changes
- Determining What Changes You Have Made to the Configuration
- Configuring the Router by Copying a File from a Server
- Configuring the Router by Copying Text from a Terminal Window
- Backing Up the Routers Configuration
- Scheduling the Activation of a Configuration
- Provisionally Activating a Configuration
- Loading a Previous Router Configuration
- Creating an Emergency Rescue Configuration
- Backing Up Filesystems on M-Series and T-Series Routers
- Backing Up Filesystems on J-Series Routers
- Restoring a Backed-Up Filesystem
- Installing a Different Software Release on M-Series and T-Series Routers
- Installing a Different Software Release on J-Series Routers
- Creating an Emergency Boot Disk
- Gathering Software Version Information
- Gathering Hardware Inventory Information
- Finding Out How Long the Router Has Been Up
- Gathering Information Before Contacting Support
- Managing Routers with Similar Configurations
- Managing Redundant Routing Engines
- Using the Second Routing Engine to Upgrade to a New Software Version
Basic Router Security and Access Control
- Basic Router Security and Access Control
- Introduction
- Allowing Access to the Router
- Controlling Root Authentication
- Logging In to the Routers Console
- Setting the Login Authentication Methods
- Setting Up Login Accounts on the Router
- Changing the Format of Plain-Text Passwords
- Changing the Plain-Text Password Encryption Method
- Creating a Login Account for Remote Authentication
- Creating a Group Login Account
- Customizing Account Privileges
- Creating a Privilege Class that Hides Encrypted Passwords
- Setting Up RADIUS User Authentication
- Setting Up TACACS+ User Authentication
- Restricting Inbound SSH and Telnet Access
- Setting the Source Address for Telnet Connections
- Creating a Login Banner
- Finding Out Who Is Logged In to the Router
- Logging Out of the Router
- Forcibly Logging a User Out
IPSec
- IPSec
- Introduction
- Configuring IPSec
- Configuring IPSec Dynamic SAs
- Creating IPSec Dynamic SAs on J-Series Routers or Routers with AS PICs
- Using Digital Certificates to Create Dynamic IPSec SAs
SNMP
- SNMP
- Introduction
- Configuring SNMP
- Setting Router Information for the MIB-II System Group
- Setting Up SNMP Traps
- Controlling SNMP Access to the Router
- Using a Firewall Filter to Protect SNMP Access
- Controlling Access to Router MIBs
- Extracting Software Inventory Information with SNMP
- Extracting Hardware Inventory Information with SNMP
- Collecting Router Operational Information with SNMP
- Logging SNMP Access to the Router
- Logging Enterprise-Specific Traps
- Using RMON Traps to Monitor the Routers Temperature
- Configuring SNMPv3
- Tracking Router Configuration Changes
- Setting Up SNMPv3 Traps
Logging
- Logging
- Introduction
- Turning On Logging
- Limiting the Messages Collected
- Including the Facility and Severity in Messages
- Changing the Size of a Logging File
- Clearing the Routers Logfiles
- Sending Log Messages to Your Screen
- Sending Logging Messages to a Log Server
- Saving Logging Messages to the Other Routing Engine
- Turning Off Logging
- Turning On Basic Tracing
- Monitoring Interface Traffic
NTP
- NTP
- Introduction
- Setting the Date and Time on the Router Manually
- Setting the Time Zone
- Synchronizing Time When the Router Boots
- Synchronizing Time Periodically
- Authenticating NTP
- Checking NTP Status
Router Interfaces
- Router Interfaces
- Introduction
- Viewing Interface Status
- Viewing Traffic Statistics on an Interface
- Setting an IP Address for the Router
- Setting the Routers Source Address
- Configuring an IPv4 Address on an Interface
- Configuring an IPv6 Address on an Interface
- Configuring an ISO Address on an Interface
- Creating an MPLS Protocol Family on a Logical Interface
- Configuring an Interface Description
- Choosing Primary and Preferred Interface Addresses
- Using the Management Interface
- Finding Out What IP Addresses Are Used on the Router
- Configuring Ethernet Interfaces
- Using VRRP on Ethernet Interfaces
- Connecting to an Ethernet Switch
- Configuring T1 Interfaces
- Performing a Loopback Test on a T1 Interface
- Setting Up a BERT Test on a T1 Interface
- Configuring Frame Relay on a T1 Interface
- Configuring a SONET Interface
- Using APS to Protect Against SONET Circuit Failures
- Configuring an ATM Interface
- Dealing with Nonconfigurable Interfaces
- Configuring Interfaces Before the PICs Are Installed
IP Routing
- IP Routing
- Introduction
- Viewing the Routes in the Routing Table
- Viewing Routes to a Particular Prefix
- Viewing Routes Learned from a Specific Protocol
- Displaying the Routes in the Forwarding Table
- Creating Static Routes
- Blackholing Routes
- Filtering Traffic Using Unicast Reverse-Path Forwarding
- Aggregating Routes
- Load-Balancing Traffic Flows
- Adding Martian Addresses
- Changing Route Preferences to Migrate to Another IGP
- Configuring Routing Protocols to Restart Without Losing Adjacencies
Routing Policy and Firewall Filters
- Routing Policy and Firewall Filters
- Introduction
- Creating a Simple Routing Policy
- Changing a Routes Routing Information
- Filtering Routes by IP Address
- Filtering Long Prefixes
- Filtering Unallocated Prefix Blocks
- Creating a Chain of Routing Policies
- Making Sure a Routing Policy Is Functioning Properly
- Creating a Simple Firewall Filter that Matches Packet Contents
- Creating a Firewall Filter that Negates a Match
- Reordering Firewall Terms
- Filtering Traffic Transiting the Router
- Using a Firewall Filter to Count Traffic on an Interface
- Logging the Traffic on an Interface
- Limiting Traffic on an Interface
- Protecting the Local Routing Engine
- Rate-Limiting Traffic Flow to the Routing Engine
- Using Counters to Determine Whether a Router Is Under Attack
RIP
- RIP
- Introduction
- Configuring RIP
- Having RIP Advertise Its Routes
- Configuring RIP for IPv6
- Enabling RIP Authentication
- Routing RIP Traffic over Faster Interfaces
- Sending Version 1 Update Messages
- Tracing RIP Protocol Traffic
IS-IS
- IS-IS
- Introduction
- Configuring IS-IS
- Viewing the IS-IS Link-State Database
- Viewing Routes Learned by IS-IS
- Configuring IS-IS for IPv6
- Configuring a Level 1Only Router
- Controlling DIS Election
- Enabling IS-IS Authentication
- Redistributing Static Routes into IS-IS
- Leaking IS-IS Level 2 Routes into Level 1
- Adjusting IS-IS Link Costs
- Improving IS-IS Convergence Times
- Moving IS-IS Traffic off a Router
- Disabling IS-IS on an Interface
- Tracing IS-IS Protocol Traffic
OSPF
- Introduction
- Configuring OSPF
- Viewing Routes Learned by OSPF
- Viewing the OSPF Link-State Database
- Configuring OSPF for IPv6
- Configuring a Multiarea OSPF Network
- Setting Up Stub Areas
- Creating a Not-So-Stubby Area
- Summarizing Routes in OSPF
- Enabling OSPF Authentication
- Redistributing Static Routes into OSPF
- Adjusting OSPF Link Costs
- Improving OSPF Convergence Times
- Moving OSPF Traffic off a Router
- Disabling OSPF on an Interface
- Tracing OSPF Protocol Traffic
BGP
- Introduction
- Configuring a BGP Session Between Routers in Two ASs
- Configuring BGP on Routers Within an AS
- Diagnosing TCP Session Problems
- Adjusting the Next-Hop Attribute
- Adjusting Local Preference Values
- Removing Private AS Numbers from the AS Path
- Prepending AS Numbers to the AS Path
- Filtering BGP Routes Based on AS Paths
- Restricting the Number of Routes Advertised to a BGP Peer
- Authenticating BGP Peers
- Setting Up Route Reflectors
- Mitigating Route Instabilities with Route Flap Damping
- Adding a BGP Community to Routes
- Load-Balancing BGP Traffic
- Tracing BGP Protocol Traffic
MPLS
- Introduction
- Configuring LSPs Using LDP as the Signaling Protocol
- Viewing Information and LDP-Signaled LSPs in the Routing Tables
- Verifying that an LDP-Signaled LSP Is Carrying Traffic
- Enabling LDP Authentication
- Tracing LDP Operations
- Setting Up RSVP-Signaled LSPs
- Viewing Information About RSVP-Signaled LSPs in the Routing Tables
- Verifying Packet Labels
- Verifying that the RSVP-Signaled LSP Is Carrying Traffic
- Configuring RSVP Authentication
- Protecting an LSPs Path
- Using Fast Reroute to Reduce Packet Loss Following a Link Failure
- Automatically Allocating Bandwidth
- Prioritizing LSPs
- Allowing IGP Traffic to Use an LSP
- Installing LSPs into the Unicast Routing Table
- Tracing RSVP Operations
VPNs
- Introduction
- Setting Up a Simple Layer 3 VPN
- Viewing the VPN Routing Tables
- Adding a VPN for a Second Customer
IP Multicast
- Introduction
- Configuring PIM-SM
- Manually Establishing a PIM-SM RP
- Using Auto-RP to Dynamically Map RPs
- Setting Up a PIM-SM Bootstrap Router
- Filtering PIM-SM Bootstrap Messages
- Configuring Multiple RPs in a PIM-SM Domain with Anycast RP
- Configuring Multiple RPs in a PIM-SM Domain Anycast PIM
- Limiting the Group Ranges an RP Services
- Viewing Multicast Routes
- Checking the Groups for Which a PIM-SM Router Maintains Join State
- Manually Configuring IGMP
- Using SSM
- Connecting PIM-SM Domains Using MSDP and MBGP
- Configuring PIM-DM
- Tracing PIM Packets
Junos Cookbook (Cookbooks (OReilly))
ISBN: 0596100140
EAN: 2147483647
EAN: 2147483647
Year: 2007
Pages: 290
Pages: 290
Authors: Aviva Garrett
