Tracing OSPF Protocol Traffic
Problem
You are setting up OSPF on your network and want to keep a running log of OSPF protocol packets that the router is sending to help track any problems that might occur during the configuration process.
Solution
Set up a tracing file that captures information about OSPF protocol operations:
[edit protocols ospf] aviva@RouterG# set traceoptions file ospf-log aviva@RouterG# set traceoptions flag hello aviva@RouterG# set traceoptions flag error aviva@RouterG# set traceoptions flag general
To stop the tracing, remove the traceoptions statement from the configuration:
[edit protocols ospf] aviva@RouterG# delete traceoptions
Discussion
To debug OSPF operations, use the JUNOS tracing facility to track the packets that OSPF is sending. 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 are logging general OSPF traffic information as well as Hello packets and errors in the ospf-log file, which is on the routers hard disk in the directories /var/log (on M-series and T-series routers) and /cf/var/log (on J-series routers).
Some things you see in the logfile are Hello packets sent to and received from neighbors:
Jun 14 21:49:36 OSPF rcvd Hello 10.0.16.2 -> 224.0.0.5 (fe-0/0/0.0, IFL 0x42) Jun 14 21:49:36 Version 2, length 48, ID 192.168.19.1, area 0.0.0.1 Jun 14 21:49:36 checksum 0x0, authtype 0 Jun 14 21:49:36 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128 Jun 14 21:49:36 dead_ivl 40, DR 10.0.16.1, BDR 10.0.16.2 Jun 14 21:49:36 OSPF sent Hello 10.0.16.1 -> 224.0.0.5 (fe-0/0/0.0, IFL 0x42) Jun 14 21:49:36 Version 2, length 48, ID 192.168.42.1, area 0.0.0.1 Jun 14 21:49:36 checksum 0x0, authtype 0 Jun 14 21:49:36 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128 Jun 14 21:49:36 dead_ivl 40, DR 10.0.16.1, BDR 10.0.16.2
This log shows the values for two of the OSPF timers, the hello interval of 10 seconds (hello_ivl 10) and the dead interval of 40 seconds (dead_ivl 40), as well as the address of the DR and BDR and the priority to become the DR (128).
You also see changes to the adjacency changes when neighbors come up:
Jun 14 21:49:36 RPD_ OSPF_NBRUP: OSPF neighbor 10.0.16.2 (fe-0/0/0.0) state changed from Loading to Full due to OSPF loading done Jun 14 21:49:36 CHANGE 10.0.0.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 2/0 fe-0/0/0.0 <Active Int> Jun 14 21:49:36 ADD 10.0.0.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 2/0 fe-0/0/0.0 <Active Int> Jun 14 21:49:36 CHANGE 10.0.1.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 2/0 fe-0/0/0.0 <Active Int> Jun 14 21:49:36 ADD 10.0.1.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 2/0 fe-0/0/0.0 <Active Int> Jun 14 21:49:36 CHANGE 10.0.2.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 4/0 fe-0/0/0.0 <Active Int> Jun 14 21:49:36 ADD 10.0.2.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 4/0 fe-0/0/0.0 <Active Int>
Here are the adjacency changes when neighbors go down:
Jun 14 22:00:26 RPD_OSPF_NBRDOWN: OSPF neighbor 10.0.16.2 (fe-0/0/0.0) state changed from Full to Down due to Kill all neighbors Jun 14 22:00:26 RPD_OSPF_NBRDOWN: OSPF neighbor 10.0.21.2 (se-0/0/3.0) state changed from Full to Down due to Kill all neighbors Jun 14 22:00:26 OSPF: multicast address 224.0.0.5/32, route ignored Jun 14 22:00:26 OSPF: multicast address 224.0.0.5/32, route ignored Jun 14 22:00:26 CHANGE 10.0.0.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 2/0 fe-0/0/0.0Jun 14 22:00:26 CHANGE 10.0.1.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 2/0 fe-0/0/0.0 Jun 14 22:00:26 CHANGE 10.0.2.0/24 gw 10.0.16.2 OSPF pref 10/0 metric 4/0 fe-0/0/0.0 Jun 14 22:00:26 RELEASE 10.0.21.0/24 gw (null) OSPF pref 10/0 metric 12/0 se-0/0/3.0 Jun 14 22:00:26 CHANGE 10.0.22.0/24 gw (null) OSPF pref 10/0 metric 24/0 se-0/0/3.0 Jun 14 22:00:26 CHANGE 192.168.12.1/32 gw (null) OSPF pref 10/0 metric 12/0 se-0/0/3.0 Jun 14 22:00:26 CHANGE 192.168.17.1/32 gw 10.0.16.2 OSPF pref 10/0 metric 2/0 fe-0/0/0.0 Jun 14 22:00:26 CHANGE 192.168.18.1/32 gw 10.0.16.2 OSPF pref 10/0 metric 2/0 fe-0/0/0.0 Jun 14 22:00:26 rt_close: 8/11 routes proto OSPF Jun 14 22:00:26 Jun 14 22:00:26 CHANGE 224.0.0.5/32 OSPF pref 10/0 metric 1/0 Jun 14 22:00:26 rt_close: 1/1 route proto OSPF Jun 14 22:00:26 Jun 14 22:00:26 Terminating OSPFv2 I/0
Over time, the OSPF logfiles can become very large and fill the routers hard disk. To save a logfile for future analysis, you can copy the file to a server:
aviva@RouterG> file copy /cf/var/log/ospf-log server1:ospf-log-20050614
If you no longer need the information in the file, you can delete the contents:
aviva@RouterG> clear log ospf-log
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 leave the statements in the configuration and simply deactivate them so that they do not take effect when you commit the configuration:
[edit protocols ospf] aviva@RouterG# deactivate traceoptions
To delete the logfiles and the rolled-over version of the file, use the file delete command:
aviva@RouterG> file delete ospf-log*
When debugging OSPF, you can set one or more of the following trace flags to capture OSPF information:
[edit protocols ospf traceoptions] aviva@RouterG# set flag ? Possible completions: all Trace everything database-description Trace database description packets error Trace errored packets event Trace OSPF state machine events flooding Trace LSA flooding general Trace general events hello Trace hello packets lsa-ack Trace LSA acknowledgement packets lsa-request Trace LSA request packets lsa-update Trace LSA update packets normal Trace normal events packet-dump Dump the contents of selected packet types packets Trace all OSPF packets policy Trace policy processing route Trace routing information spf Trace SPF calculations state Trace state transitions task Trace routing protocol task processing timer Trace routing protocol timer processing
Using some of these other flags, you can debug adjacencies to see whether they come up:
Jun 14 22:22:02 OSPF rcvd LSUpdate 10.0.16.1 -> 224.0.0.5 (fe-1/0/0.0, IFL 0x44) Jun 14 22:22:02 Version 2, length 124, ID 192.168.42.1, area 0.0.0.1 Jun 14 22:22:02 checksum 0x0, authtype 0 Jun 14 22:22:02 adv count 1 Jun 14 22:22:02 id 192.168.42.1, type Router (0x1), age 3 Jun 14 22:22:02 options 0x2 Jun 14 22:22:02 adv rtr 192.168.42.1, seq 0x80000015, cksum 0x8c54, len 96 Jun 14 22:22:02 bits 0x0, link count 6 Jun 14 22:22:02 id 10.0.16.2, data 10.0.16.1, type Transit (2) Jun 14 22:22:02 TOS count 0, TOS 0 metric 1 Jun 14 22:22:02 id 172.19.121.0, data 255.255.255.0, type Stub (3) Jun 14 22:22:02 TOS count 0, TOS 0 metric 1 Jun 14 22:22:02 id 172.100.1.0, data 255.255.255.0, type Stub (3) Jun 14 22:22:02 TOS count 0, TOS 0 metric 1 Jun 14 22:22:02 id 192.168.12.1, data 10.0.21.1, type PointToPoint (1) Jun 14 22:22:02 TOS count 0, TOS 0 metric 12 Jun 14 22:22:02 id 10.0.21.0, data 255.255.255.0, type Stub (3) Jun 14 22:22:02 TOS count 0, TOS 0 metric 12 Jun 14 22:22:02 id 192.168.42.1, data 255.255.255.255, type Stub (3) Jun 14 22:22:02 TOS count 0, TOS 0 metric 0
You can also check that the SPF calculation is performed:
Jun 13 16:55:20 OSPF SPF start, area 0.0.0.0 Jun 13 16:55:20 OSPF add LSA Router (192.168.19.1, 192.168.19.1) distance 0 to SPF list Jun 13 16:55:20 Considering router link Transit 10.0.1.2 10.0.1.2 Jun 13 16:55:20 Examining network link 192.168.19.1 Jun 13 16:55:20 Back link found Jun 13 16:55:20 Added to candidate list at distance 1 Jun 13 16:55:20 No nexthops, parent is root Jun 13 16:55:20 Network LSA, adding interface nexthop Jun 13 16:55:20 IP Nexthop #1 (null):0.0.0.0 (fe-0/0/1.0) added Jun 13 16:55:20 Considering router link Transit 10.0.0.1 10.0.0.1 Jun 13 16:55:20 Examining network link 192.168.19.1 Jun 13 16:55:20 Back link found Jun 13 16:55:20 Added to candidate list at distance 1 Jun 13 16:55:20 No nexthops, parent is root Jun 13 16:55:20 Network LSA, adding interface nexthop Jun 13 16:55:20 IP Nexthop #1 (null):0.0.0.0 (fe-1/0/1.0) added Jun 13 16:55:20 Adding SPF route 10.0.1.0/24 Jun 13 16:55:20 IP Nexthop #1 (null):0.0.0.0 (fe-0/0/1.0) added Jun 13 16:55:20 IP Route added with cost 1 (fresh) … Jun 13 16:55:20 SPF elapsed time 0.002172s Jun 13 16:55:20 Adding stub route 192.168.19.1/32 Jun 13 16:55:20 IP Route added with cost 0 Jun 13 16:55:20 IP Nexthop #1 10.0.1.1:0.0.0.0 (fe-0/0/1.0) added … Jun 13 16:55:20 Stub elapsed time 0.000567s Jun 13 16:55:20 Interarea elapsed time 0.000007s Jun 13 16:55:20 External elapsed time 0.000003s Jun 13 16:55:20 NSSA elapsed time 0.000002s Jun 13 16:55:20 Route 10.0.0.0/24 is unchanged Jun 13 16:55:20 Route 10.0.1.0/24 is unchanged Jun 13 16:55:20 CHANGE 10.0.2.0/24 gw 10.0.1.1 OSPF pref 10/0 metric 10001/0 fe-0/0/1.0Jun 13 16:55:20 CHANGE 10.0.2.0/24 gw 10.0.0.2 OSPF pref 10/0 metric 2/0 fe-1/0/1.0 <Active Int> Jun 13 16:55:20 ADD 10.0.2.0/24 gw 10.0.0.2 OSPF pref 10/0 metric 2/0 fe-1/0/1.0 <Active Int> Jun 13 16:55:20 Route 10.0.2.0/24 has changed Jun 13 16:55:20 Considering autosummary for 10.0.2.0/24, summary possible=1 Jun 13 16:55:20 Considering NSSA autosummary for 10.0.2.0/24 Jun 13 16:55:20 CHANGE 192.168.17.1/32 gw 10.0.1.1 OSPF pref 10/0 metric 10001/0 fe-0/0/1.0 Jun 13 16:55:20 CHANGE 192.168.17.1/32 gw 10.0.0.2 OSPF pref 10/0 metric 1/0 fe-1/0/1.0 <Active Int> Jun 13 16:55:20 ADD 192.168.17.1/32 gw 10.0.0.2 OSPF pref 10/0 metric 1/0 fe-1/0/1.0 <Active Int> Jun 13 16:55:20 Route 192.168.17.1/32 has changed Jun 13 16:55:20 Considering autosummary for 192.168.17.1/32, summary possible=1 Jun 13 16:55:20 Considering NSSA autosummary for 192.168.17.1/32 Jun 13 16:55:20 Route 192.168.18.1/32 is unchanged Jun 13 16:55:20 Route 192.168.19.1/32 has been deleted Jun 13 16:55:20 Considering autosummary for 192.168.19.1/32, summary possible=0 Jun 13 16:55:20 All autosummaries deleted Jun 13 16:55:20 Considering NSSA autosummary for 192.168.19.1/32 Jun 13 16:55:20 Route 192.168.17.1 has changed Jun 13 16:55:20 Considering autosummary for 192.168.17.1, summary possible=0 Jun 13 16:55:20 All autosummaries deleted Jun 13 16:55:20 Considering NSSA autosummary for 192.168.17.1 Jun 13 16:55:20 Route 192.168.18.1 is unchanged Jun 13 16:55:20 rt_close: 4/3 routes proto OSPF Jun 13 16:55:20 Jun 13 16:55:20 Cleanup elapsed time 0.001236s Jun 13 16:55:20 Total elapsed time 0.004206s
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
