- play_arrow Overview
- play_arrow Overview
- J-Web User Interface for EX Series Switches Overview
- J-Web Interface—Application Package
- Understanding J-Web User Interface Sessions
- Dashboard for EX Series Switches
- Understanding J-Web Configuration Tools
- Understand Alarm Types and Severity Levels on EX Series Switches
- Using the Commit Options to Commit Configuration Changes (J-Web Procedure)
-
- play_arrow Configuration
- play_arrow Starting J-Web
- play_arrow J-Web Configuration Tools
- play_arrow System Basics Configuration
- Connecting and Configuring an EX Series Switch (J-Web Procedure)
- Configuring Date and Time for the EX Series Switch (J-Web Procedure)
- Configuring System Identity for an EX Series Switch (J-Web Procedure)
- Configuring Management Access for the EX Series Switch (J-Web Procedure)
- Generating SSL Certificates to Be Used for Secure Web Access (EX Series Switch)
- Rebooting or Halting the EX Series Switch (J-Web Procedure)
- play_arrow Class of Service Configuration
- Defining CoS Drop Profiles (J-Web Procedure)
- Defining CoS Classifiers (J-Web Procedure)
- Defining CoS Code-Point Aliases (J-Web Procedure)
- Assigning CoS Components to Interfaces (J-Web Procedure)
- Defining CoS Forwarding Classes (J-Web Procedure)
- Defining CoS Rewrite Rules (J-Web Procedure)
- Defining CoS Schedulers (J-Web Procedure)
- Defining CoS Scheduler Maps (J-Web Procedure)
- play_arrow Security and Management Configuration
- play_arrow Routing Policies and Packet Filtering Configuration
- play_arrow Ethernet Switching Configuration
- play_arrow Interfaces
- play_arrow Configuring Services
- play_arrow Configuring Layer 3 Protocols
- play_arrow Configuring Real-Time Performance Monitoring
- play_arrow Software Installation and Upgrades
- play_arrow Configuration, Files, Users, Licenses, and Product Registration
- Managing Configuration Files Through the Configuration History (J-Web Procedure)
- Setting or Deleting the Rescue Configuration (J-Web Procedure)
- Uploading a Configuration File (J-Web Procedure)
- Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure)
- Managing Users (J-Web Procedure)
- Managing Licenses for the EX Series Switch (J-Web Procedure)
- Registering the EX Series Switch with the J-Web Interface
- Generating Support Information Reports for EX Series Switches Using the J-Web Interface
- play_arrow Virtual Chassis Configuration
-
- play_arrow Administration
- play_arrow Software, Files, Licenses, Logs
- Uploading a Configuration File (J-Web Procedure)
- Managing Configuration Files Through the Configuration History (J-Web Procedure)
- Setting or Deleting the Rescue Configuration (J-Web Procedure)
- Updating J-Web Interface on EX Series Switches (J-Web Procedure)
- Upgrading Junos OS on EX Series Switches (J-Web Procedure)
- Managing Licenses for the EX Series Switch (J-Web Procedure)
- Rebooting or Halting the EX Series Switch (J-Web Procedure)
- Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure)
- Registering the EX Series Switch with the J-Web Interface
- Generating Support Information Reports for EX Series Switches Using the J-Web Interface
-
- play_arrow Troubleshooting
- play_arrow Troubleshooting Task
- play_arrow FAQ
-
Monitoring OSPF Routing Information
Purpose
This topic applies only to the J-Web Application package.
Use the monitoring functionality to monitor OSPF routing information on routing devices.
Action
To view OSPF routing information in the J-Web interface, select Monitor > Routing > OSPF Information.
To view OSPF routing information in the CLI, enter the following CLI commands:
show ospf neighbor
show ospf interface
show ospf statistics
Meaning
Table 1 summarizes key output fields in the OSPF routing display in the J-Web interface.
Field | Values | Additional Information |
---|---|---|
OSPF Interfaces | ||
Interface | Name of the interface running OSPF. | |
State | State of the interface: BDR, Down, DR, DRother, Loop, PtToPt, or Waiting. | The Down state, indicating that the interface is not functioning, and PtToPt state, indicating that a point-to-point connection has been established, are the most common states. |
Area | Number of the area that the interface is in. | |
DR ID | Address of the area's designated device. | |
BDR ID | Address of the area's backup designated device. | |
Neighbors | Number of neighbors on this interface. | |
Adjacency Count | Number of devices in the area using the same area identifier. | |
Stub Type | The areas into which OSPF does not flood AS external advertisements | |
Passive Mode | In this mode the interface is present on the network but does not transmit or receive packets. | |
Authentication Type | The authentication scheme for the backbone or area. | |
Interface Address | The IP address of the interface. | |
Address Mask | The subnet mask or address prefix. | |
MTU | The maximum transmission unit size. | |
Interface Cost | The path cost used to calculate the root path cost from any given LAN segment is determined by the total cost of each link in the path. | |
Hello Interval | How often the routing device sends hello packets out of the interface. | |
Dead Interval | The interval during which the routing device receives no hello packets from the neighbor. | |
Retransmit Interval | The interval for which the routing device waits to receive a link-state acknowledgment packet before retransmitting link-state advertisements to an interface’s neighbors. | |
OSPF Statistics | ||
Packets tab | ||
Sent | Displays the total number of packets sent. | |
Received | Displays the total number of packets received. | |
Details tab | ||
Flood Queue Depth | Number of entries in the extended queue. | |
Total Retransmits | Number of retransmission entries enqueued. | |
Total Database Summaries | Total number of database description packets. | |
OSPF Neighbors | ||
Address | Address of the neighbor. | |
Interface | Interface through which the neighbor is reachable. | |
State | State of the neighbor: Attempt, Down, Exchange, ExStart, Full, Init, Loading, or 2way. | Generally, only the Down state, indicating a failed OSPF adjacency, and the Full state, indicating a functional adjacency, are maintained for more than a few seconds. The other states are transitional states that a neighbor is in only briefly while an OSPF adjacency is being established. |
ID | ID of the neighbor. | |
Priority | Priority of the neighbor to become the designated router. | |
Activity Time | The activity time. | |
Area | Area that the neighbor is in. | |
Options | Option bits received in the hello packets from the neighbor. | |
DR Address | Address of the designated router. | |
BDR Address | Address of the backup designated router. | |
Uptime | Length of time since the neighbor came up. | |
Adjacency | Length of time since the adjacency with the neighbor was established. |