![[Top]](../../images/home.jpg){kind=small}
![[Contents]](../../images/contents.jpg){kind=small}
![[Prev]](../../images/previous.jpg){kind=small}
![[Next]](../../images/next.jpg){kind=small}
![[Last]](../../images/index.jpg){kind=small}
This chapter covers these topics:
The MAX acts as an OSPF internal router with limited border router capability. At this release, we do not recommend an area border router (ABR) configuration for the MAX, so the Ethernet interface and all of the MAX WAN links should be configured in the same area.
The MAX does not function as a full AS border router (ASBR) at this release. However, ASBR calculations are performed for external routes such as WAN links that do not support OSPF. The MAX imports external routes into its OSPF database and flags them as ASE (autonomous system external). It redistributes those routes via OSPF ASE advertisements, and propagates its OSPF routes to remote WAN routers running RIP.
The MAX supports null and simple password authentication.
An AS (autonomous system) is a group of OSPF routers exchanging information, typically under the control of one company. An AS can include a large number of networks, all of which are assigned the same AS number. All information exchanged within the AS is interior.
Exterior protocols are used to exchange routing information between autonomous systems. They are referred to by the acronym EGP (exterior gateway protocol). The AS number may be used by border routers to filter out certain EGP routing information. OSPF can make use of EGP data generated by other border routers and added into the OSPF system as ASEs, as well as static routes configured in the MAX or RADIUS.
An AS border router (ASBR) is required to communicate with other autonomous systems by using an external gateway protocol (EGP), as shown in Figure 11-1. An EGP acts as a shuttle service between autonomous systems.
Figure 11-1. Autonomous system border routers
ASBRs perform calculations related to external routes. The MAX imports external routes from RIP-for example, when it establishes a WAN link with a caller that does not support OSPF-and the ASBR calculations are always performed.
If you must prevent the MAX from performing ASBR calculations, you can disable them in Ethernet > Mod Config > OSPF Global Options.
Figure 11-2. Adjacency between neighboring routers
An OSPF router dynamically detects its neighboring routers by sending its Hello packets to the multicast address All SPFRouters. It attempts to form adjacencies with some of its newly acquired neighbors.
Adjacency is a relationship formed between selected neighboring routers for the purpose of exchanging routing information. Not every pair of neighboring routers become adjacent. Adjacencies are established during network initialization in pairs, between two neighbors. As the adjacency is established, the neighbors exchange databases and build a consistent, synchronized database between them.
When an OSPF router detects a change on one of its interfaces, it modifies its topological database and multicasts the change to its adjacent neighbor, which in turn propagates the change to its adjacent neighbor until all routers within an area have synchronized topological databases. This results in quick convergence among routers. OSPF routes can also be summarized in link-state advertisements (LSAs).
Figure 11-3. Designated and backup designated routers
The MAX can function as a designated router (DR) or backup designated router (BDR). However, many sites choose to assign a LAN-based router for these roles in order to dedicate the MAX to WAN processing. The administrator chooses a DR and BDR based on the device's processing power and reliability.
To reduce the number of adjacencies each router must form, OSPF calls one of the routers the designated router. A designated router is elected as routers are forming adjacencies, and then all other routers establish adjacencies only with the designated router. This simplifies the routing table update procedure and reduces the number of link-state records in the database. The designated router plays other important roles as well to reduce the overhead of a OSPF link-state procedures. For example, other routers send link-state advertisements it to the designated router only by using the all-designated-routers multicast address of 224.0.0.6.
To prevent the designated router from becoming a serious liability to the network if it fails, OSPF also elects a backup designated router at the same time. Other routers maintain adjacencies with both the designated router and its backup router, but the backup router leaves as many of the processing tasks as possible to the designated router. If the designated router fails, the backup immediately becomes the designated router and a new backup is elected.
The administrator chooses which router is to be the designated router based on the processing power, speed, and memory of the system, and then assigns priorities to other routers on the network in case the backup designated router is also down at the same time.
The OSPF cost can also be used for preferred path selection. If two paths to a destination have equal costs, you can assign a higher cost to one of the paths to configure it as a backup to be used only when the primary path is not available.
Figure 11-4 shows how costs are used to direct traffic over high-speed links. For example, if Router-2 in Figure 11-4 receives packets destined for Host B, it will route them through Router-1 across two T1 links (Cost=20) rather than across one 56kbps B-channel to Router-3 (Cost=240).
Figure 11-4. OSPF costs for different types of links
The MAX has a default cost of 1 for a connected route (Ethernet) and 10 for a WAN link. If you have two paths to the same destination, the one with the lower cost will be used. You may want to reflect the bandwidth of a connection when assigning costs; for example, for a single B-channel connection, the cost would be 24 times greater than a T1 link.
The backbone area is special and always has the area number 0.0.0.0. Other areas are assigned area numbers that are unique within the autonomous system.
Each areas acts like its own network: all area-specific routing information stays within the area, and all routers within an area must have a synchronized topological database. To tie the areas together, some routers belong to an area and to the backbone area. These routers are area border routers (ABRs). In Figure 11-5, all of the routers are ABRs.If the ABRs and area boundaries are set up correctly, link-state databases are unique to an area.
Figure 11-5. Dividing an AS into areas
To prevent flooding of external routes throughout the AS, you can configure an area as a stub when there is a single exit point from the area, or when the choice of exit point need not be made on a per-external-destination basis. You might need to specify a stub area with no default cost (StubNoDefault) if the area has more than one exit point.
In a stub area, routing to AS-external destinations is based on a per-area default cost. The per-area default cost is advertised to all routers within the stub area by a border router, and is used for all external destinations.
If the MAX supports external routes across its WAN links, you should not configure it in a stub area. Because an ABR configuration is not currently recommended for the MAX, the area in which it resides should not be a stub area if any of its links are AS-external.
You must also specify whether these type-7 LSAs should be advertised outside the NSSA. If you choose to advertise a type-7 LSA, the NSSA Area Border Router (ABR) converts it to a type-5 LSA, which can then be flooded throughout the AS. If you choose not to advertise a type-7 LSA, it is not advertised beyond the NSSA.
Refer to RFC 1587 for complete information on NSSAs.
OSPF routers exchange routing information and build Link-state databases. Link-state databases are synchronized between pairs of adjacent routers (as described in Exchange of routing information). In addition, each OSPF router uses its link-state database to calculate a self-rooted tree of shortest paths to all destinations, as shown in Figure 11-6.
Figure 11-6. Sample network topology
The routers then use the trees to build their routing tables, as shown in Table 11-1.
Table 11-1. Link state databases for network topology in Figure 11-6
Router-1 |
Router-2 |
Router-3 |
|---|---|---|
| Network-1/Cost 0 | Network-2/Cost0 | Network-3/Cost 0 |
| Network-2/Cost 0 | Network-3/Cost0 | Network-4/Cost 0 |
| Router-2/Cost 20 | Router-1/Cost 20 | Router-2/Cost 30 |
| Router-3/Cost 30 |
Table 11-2, Table 11-3, and Table 11-4 show another example of self-rooted shortest-path trees calculated from link-state databases, and the resulting routing tables. Actual routing tables also contain externally derived routing data, which is advertised throughout the AS but kept separate from the Link-state data. Also, each external route can be tagged by the advertising router, enabling the passing of additional information between routers on the boundary of the AS.
Table 11-2. Shortest-path tree and resulting routing table for Router-1
 | Destination | Next Hop | Metric |
| Network-1 | Direct | 0 | |
| Network-2 | Direct | 0 | |
| Network-3 | Router-2 | 20 | |
| Network-4 | Router-2 | 50 | |
Table 11-3. Shortest-path tree and resulting routing table for Router-2
 | Destination | Next Hop | Metric |
| Network-1 | Router-1 | 20 | |
| Network-2 | Direct | 0 | |
| Network-3 | Direct | 0 | |
| Network-4 | Router-2 | 30 |
Table 11-4. Shortest-path tree and resulting routing table for Router-3
 | Destination | Next Hop | Metric |
| Network-1 | Router-2 | 50 | |
| Network-2 | Router-2 | 30 | |
| Network-3 | Direct | 0 | |
| Network-4 | Direct | 0 | |
Ethernet
Mod Config
OSPF options...
RunOSPF=Yes
Area=0.0.0.0
AreaType=Normal
HelloInterval=10
DeadInterval=40
Priority=5
AuthType=Simple
AuthKey=ascend0
Cost=1
LSA-type=N/A
ASE-tag=N/A
TransitDelay=1
RetransmitInterval=5
OSPF global options...
Enable ASBR=Yes
EthernetFor more information on each parameter, see the MAX Reference Guide.
Connections
OSPF options
RunOSPF=Yes
Area=0.0.0.0
AreaType=Normal
HelloInterval=40
DeadInterval=120
Priority=5
AuthType=Simple
AuthKey=ascend0
Cost=10
LSA-type=N/A
ASE-tag=N/A
TransitDelay=5
RetransmitInterval=20
Figure 11-7. An example OSPF setup
In Figure 11-7, all OSPF routers are in the same area (the backbone area), so the units will all form adjacencies and synchronize their databases together.
Another way to configure the same units would be to create a second area (such as 0.0.0.1) in one of the existing OSPF routers, and add the MAX to that area. You can then assign the same area number (0.0.0.1) to all OSPF routers reached through the MAX across a WAN link.
After you configure the MAX as an IP host on that interface, you can configure it as an OSPF router in the backbone area in the Ethernet profile. To configure the MAX as an OSPF router on Ethernet:
EthernetNote that RIP is turned off. It is not necessary to run both RIP and OSPF, and it reduces processor overhead to turn RIP off. OSPF can learn routes from RIP, incorporate them in the routing table, assign them an external metric, and tag them as external routes. See Chapter 10, Configuring IP Routing.
Mod Config
Ether options...
IP Adrs=10.168.8.17/24
2nd Adrs=0.0.0.0
RIP=Off
Ignore Def Rt=Yes
Proxy Mode=Always
Filter=0
IPX Frame=N/A
OSPF options...
RunOSPF=Yes
Area=0.0.0.0In this case, the Ethernet is in the backbone area. (The backbone area number is always 0.0.0.0.) The backbone area is not a stub area, so leave the setting at its default. See Stub areas for background information.
AreaType=Normal
HelloInterval=10
DeadInterval=40
Priority=5
AuthType=SimpleIf authentication is not required, set AuthType=None.
AuthKey=ascend0
Cost=1Then type a number greater than zero and less than 16777215. By default the cost of a Ethernet connected route is 1.
TransitDelay=1
RetransmitInterval=5This specifies the number of seconds between retransmissions of Link-State Advertisements, Database Description and Link State Request Packets.
An OSPF WAN link has a default cost of 10. You can assign higher costs to reflect a slower connection or lower costs to set up a preferred route to a certain destination. If the cost of one route is lower than another to the same destination, the higher-cost route will not be used unless route preferences change that equation (see Route preferences).
OSPF on the WAN link is configured in a Connection profile. In this example, the MAX is connecting to another MAX unit across a T1 link (see Figure 11-7 on page 11-13). To configure this interface:
EthernetSee Chapter 10, Configuring IP Routing.
Connections
IP options
LAN Adrs=10.2.3.4/24
WAN Alias=0.0.0.0
IF Adrs=0.0.0.0
Metric=7
Preference=N/A
Private=No
RIP=Off
Pool=0
OSPF options
RunOSPF=Yes
Area=0.0.0.0At this release, we recommend that you use the same area number for the Ethernet interface of the MAX and each of its WAN links. In this example, the Ethernet interface is in the backbone area (0.0.0.0). You can use any area numbering scheme that is consistent throughout the AS and uses this format.
AreaType=Normal
HelloInterval=40The Priority value is used to configure the MAX as a DR or BDR.
DeadInterval=120
Priority=5
AuthType=SimpleIf authentication is not required, set AuthType=None.
AuthKey=ascend0
For example, for a T1 link the cost should be at least 10.
Cost=10
In this example, RIP is turned off on the link and ASE information is configured explicitly.
EthernetSee Chapter 10, Configuring IP Routing. Note that Connections > OSPF Options includes two ASE parameters that are active only when OSPF is not running on a link. When you configure these parameters, the Connection profile route will be advertised whenever the MAX is up.
Connections
IP options
LAN Adrs=10.2.3.4/24
WAN Alias=0.0.0.0
IF Adrs=0.0.0.0
Metric=7
Preference=N/A
Private=No
RIP=Off
Pool=0
OSPF options
RunOSPF=No
Cost=240
LSA-type=Type 2
LSA-type=Type 2This specifies the type of metric to be advertised for an external route.
A Type 1 external metric is expressed in the same units as the link state metric (the same units as interface cost). Type 1 is the default.
A Type 2 external metric is considered larger than any link state path. Use of Type 2 external metrics assumes that routing outside the AS is the major cost of routing a packet, and eliminates the need for conversion of external costs to internal link state metrics.
ASE-tag=cfff8000
To invoke the terminal-server interface, select System > Sys Diag > Term Serv and press Enter.
ascend% iproute show -lIn addition to the standard routing-table fields, which are described in Chapter 10, Configuring IP Routing, the following three columns are specific to OSPF and are displayed only when you use the -l option. These OSPF-specific columns are displayed on the far right of each entry in the routing table:
... Cost T Tag
... 1 0 0xc0000000
... 9 1 0xc8000000
... 10 0 0xc0000000
... 9 1 0xc8000000
... 1 1 0xc0000000
... 3 1 0xc8000000
... 9 1 0xc8000000
... 4 1 0xc8000000
... 5 1 0xc8000000
... 3 1 0xc8000000
... 3 1 0xc8000000
... 3 1 0xc8000000
For example, if a router A has two equal-cost routes to example.com, one via router B and the other via router C, the routing table could look like this:
Destination Gateway IF Flg Pref Met Use Age
10.174.88.0/25 10.174.88.12 wan2 OGM 10 10 52 19Note that the "M" in the Flags column indicates an equal-cost multipath. A Traceroute from A to example.com would look like this:
10.174.88.0/25 10.174.88.13 wan3 OGM 10 10 52 19
10.174.88.12/32 10.174.88.12 wan2 OG 10 10 0 28
10.174.88.13/32 10.174.88.13 wan3 OG 10 10 0 28
192.168.253.0/24 - ie0 C 0 0 1 49
192.168.253.6/32 - lo0 CP 0 0 53 49
223.1.1.0/24 10.174.88.12 wan2 OG 10 10 0 19
223.5.1.0/24 10.174.88.12 wan2 OG 10 10 0 19
223.12.9.0/24 10.174.88.12 wan2 OG 10 10 0 19
255.255.255.255/32 - ie0 CP 0 0 0 49
ascend% traceroute -q 10 example.com
traceroute to example.com (10.174.88.1), 30 hops max, 0 byte packets
1 C.example.com (10.174.88.13) 20 ms B .example.com (10.174.88.12) 20 ms C.example.com (10.174.88.13) 20 ms B .example.com (10.174.88.12) 20 ms 20 ms C.example.com (10.174.88.13) 60 ms 20 ms B .example.com (10.174.88.12) 20 ms C.example.com (10.174.88.13) 20 ms B .example.com (10.174.88.12) 20 ms
2 example.com (10.174.88.1) 20 ms 20 ms 20 ms 20 ms 30 ms 20 ms 20 ms 30 ms 20 ms 30 ms
Third-party routing requires that all OSPF routers know how to route to the forwarding address. This will usually mean that the forwarding address must be on an Ethernet that has an OSPF router acting as the forwarding router, or that designated router is sending LSAs for that Ethernet to any area that sees the static route's forwarding address LSAs. To configure a static route for OSPF to advertise a third-party gateway:
Ethernet
Static Rtes
Name=third-party
Silent=No
Active=Yes
Dest=10.212.65.0/24
Gateway=101.2.3.4
Metric=3
Preference=100
Private=No
Ospf-Cost=1
LSA-Type=Type1
ASE-tag=c00000000
Third-Party=Yes
To enable OSPF to add the RIP-v2 routes to its routing table, configure RIP-v2 normally in this Connection profile. OSPF will import all RIP routes as Type-2 ASEs. The reason why RIP routes are imported with Type-2 metrics by default is that RIP metrics are not directly comparable to OSPF metrics. To prevent OSPF from interpreting RIP metrics, we assign the imported ASE route a Type-2 metric, which means that it is so large compared to OSPF costs that the metric can be ignored.
For each IP address and netmask pair, the routing table holds one route per protocol, where the protocols are defined as follows:
You can modify the default in Ethernet > Mod Config > Route Pref.
You can modify the default in Ethernet > Mod Config > Route Pref.
You can modify the default in the Connection or IP Route profile.
If multiple routes exist for a given address and netmask pair, the route with the lower Preference is better. If two routes have the same Preference, then the lower Metric is better. The best route by these criteria is actually used by the router. The others remain latent or hidden, and are used in case the best route was removed.
To assign a WAN link the same preference as a route learned from OSPF:
Ethernet
Connections
IP options
LAN Adrs=10.9.8.10/22
WAN Alias=0.0.0.0
IF Adrs=0.0.0.0
Metric=5
Preference=10
Private=No
RIP=Off
Pool=0
EthernetOr, to change RIP metrics to Type 1:
Mod Config
Route prefs...
Static Preference=10
Rip Preference=100
RipAseType=Type2
Rip Tag=c8000000
OSPF Preference=10
Ethernet
Mod Config
Route prefs...
Static Preference=100
Rip Preference=100
RipAseType=Type1
Rip Tag=c8000000
OSPF Preference=10
ascend% show ospf ?
show ospf ? Display help information
show ospf errors Display OSPF errors
show ospf areas Display OSPF areas
show ospf general Display OSPF general info
show ospf interfaces Display OSPF interfaces
show ospf lsdb Display OSPF link-state DB
show ospf lsa Display OSPF link-state advertisements
show ospf nbrs Display OSPF neighbors
show ospf rtab Display OSPF routing tab
show ospf io Display OSPF io
ascend% show ospf errors
ERRORS from: bootThe output lists all error messages related to OSPF, with each message preceded by the number of times it has been generated since the MAX powered up. Immediately following the number is a field indicating the packet type:
0: IP: Bad OSPF pkt type 0: IP: Bad IP Dest
0: IP: Bad IP proto id 1: IP: Pkt src = my IP addr
0: OSPF: Bad OSPF version 0: OSPF: Bad OSPF checksum
0: OSPF: Bad intf area id 0: OSPF: Area mismatch
0: OSPF: Bad virt link info 0: OSPF: Auth type != area type
0: OSPF: Auth key != area key 0: OSPF: Packet is too small
0: OSPF: Packet size > IP length 0: OSPF: Transmit bad
0: OSPF: Received on down IF 0: Hello: IF mask mismatch
0: Hello: IF hello timer mismatch 0: Hello: IF dead timer mismatch
0: Hello: Extern option mismatch 0: Hello: Nbr Id/IP addr confusion
0: Hello: Unknown Virt nbr 0: Hello: Unknown NBMA nbr
0: DD: Unknown nbr 0: DD: Nbr state low
0: DD: Nbr's rtr = my rtrid 0: DD: Extern option mismatch
0: Ack: Unknown nbr 0: Ack: Nbr state low
0: Ls Req: Nbr state low 0: Ls Req: Unknown nbr
0: Ls Req: Empty request 0: LS Req: Bad pkt
0: LS Update: Nbr state low 0: Ls Update: Unknown nbr
0: Ls Update: Newer self-gen LSA 0: Ls Update: Bad LS chksum
0: Ls Update: less recent rx 0: Ls Update: Unknown type
ascend% show ospf areas
Area ID: 0.0.0.0
Auth Type: Simple Passwd Import ASE: On Spf Runs: 23
Local ABRs: 0 Local ASBRs: 5 Inter LSAs: 7 Inter Cksum sum: 0x2ee0e
ascend% show ospf general
Rtr ID: 10.5.2.154
Status: Enabled Version: 2 ABR: Off ASBR: On
LS ASE Count: 8 ASE Cksum sum: Ox4c303 Tos Support: TOS 0 Only
New LSA Originate Count: 13 Rx New LSA Count: 498
ascend% show ospf interfaces
Area IP Address Type State Cost Pri DR BDR
---------------------------------------------------------------------- -----
0.0.0.0 10.5.2.154 Bcast BackupDR 1 5 10.5.2.155 10.5.2.154
0.0.0.0 10.5.2.154 PtoP P To P 10 5 None None
0.0.0.0 10.5.2.154 PtoP P To P 10 5 None None
ascend% show ospf lsdb
LS Data Base:
Area LS Type Link ID Adv Rtr Age Len Seq # Metric
---------------------------------------------------------------------- -
0.0.0.0 STUB 10.5.2.146 10.5.2.146 3600 24 0 0
0.0.0.0 STUB 10.5.2.154 10.5.2.154 3600 24 0 0
0.0.0.0 STUB 10.5.2.155 10.5.2.155 3600 24 0 0
0.0.0.0 STUB 10.5.2.162 10.5.2.162 3600 24 0 0
0.0.0.0 STUB 10.5.2.163 10.5.2.163 3600 24 0 0
0.0.0.0 RTR 10.5.2.146 10.5.2.146 659 72 8000003e 0
0.0.0.0 RTR 10.5.2.154 10.5.2.154 950 84 8000000a 0
0.0.0.0 RTR 10.5.2.155 10.5.2.155 940 60 80000005 0
0.0.0.0 RTR 10.5.2.162 10.5.2.162 980 84 8000003b 0
0.0.0.0 RTR 10.5.2.163 10.5.2.163 961 60 80000005 0
0.0.0.0 NET 10.5.2.155 10.5.2.155 940 32 80000003 0
0.0.0.0 NET 10.5.2.163 10.5.2.163 961 32 80000003 0
0.0.0.0 ASE 10.5.2.16 10.5.2.163 18 36 80000098 3
0.0.0.0 ASE 10.5.2.18 10.5.2.163 546 36 80000004 10
0.0.0.0 ASE 10.5.2.144 10.5.2.146 245 36 80000037 1
0.0.0.0 ASE 10.5.2.152 10.5.2.154 536 36 80000006 1
0.0.0.0 ASE 10.5.2.152 10.5.2.155 526 36 80000004 1
0.0.0.0 ASE 10.5.2.152 10.5.2.163 18 36 80000097 9
0.0.0.0 ASE 10.5.2.155 10.5.2.163 17 36 80000097 9
0.0.0.0 ASE 10.5.2.160 10.5.2.162 568 36 80000037 1
Type 1 (RTR) are router-LSAs that describe the collected states of the router's interfaces.
Type 2 (NET) are network-LSAs that describe the set of routers attached to the network.
Types 3 and 4 (STUB) are summary-LSAs that describe point-to-point routes to networks or AS boundary routers.
Type 5 (ASE) are AS-external-LSAs that describe routes to destinations external to the Autonomous System. A default route for the Autonomous System can also be described by an AS-external-LSA.
show ospf lsa area ls-type ls-id adv-rtrThis command requires that you include the first four fields of the LSA as listed in the database. You can select the first four fields and paste them in after typing the command, for example, to see an expanded view of the last entry in the link-state database shown in the previous section:
ascend% show ospf lsa 0.0.0.0 ase 10.5.2.160 10.5.2.162
LSA type: ASE ls id: 10.5.2.160 adv rtr: 110.5.2.162 age: 568
len: 36 seq #: 80000037 cksum: 0xfffa
Net mask: 255.255.255.255 Tos 0 metric: 10 E type: 1
Forwarding Address: 0.0.0.0 Tag: c0000000
ascend% show ospf nbrs
Area Interface Router Id Nbr IP Addr State Mode Pri
---------------------------------------------------------------------- -----
0.0.0.0 10.5.2.154 10.5.2.155 10.5.2.155 Full Slave 5
0.0.0.0 10.5.2.154 10.5.2.146 10.5.2.146 Full Master 5
0.0.0.0 10.5.2.154 10.5.2.162 10.5.2.162 Full Slave 5
ascend% show ospf rtab
SPF algorithm run 24 times since boot
Dest D_mask Area Cost E Path Nexthop AdvRtr L
---------------------------------------------------------------------- -----
Nets:
10.5.2.163 255.255.255.248 0.0.0.0 10 3 EXT 10.5.2.163 10.5.2.163 0
10.5.2.163 255.255.255.255 0.0.0.0 20 0 EXT 10.5.2.163 10.5.2.163 0
10.5.2.146 255.255.255.248 0.0.0.0 20 1 EXT 10.5.2.154 10.5.2.146 0
10.5.2.146 255.255.255.255 0.0.0.0 20 0 STUB 10.5.2.154 10.5.2.146 0
10.5.2.155 255.255.255.248 0.0.0.0 10 0 INT 10.5.2.154 10.5.2.155 1
10.5.2.154 255.255.255.255 0.0.0.0 21 0 STUB 10.5.2.163 10.5.2.154 0
10.5.2.155 255.255.255.255 0.0.0.0 20 9 STUB 10.5.2.155 10.5.2.155 1
10.5.2.163 255.255.255.248 0.0.0.0 11 1 INT 10.5.2.163 10.5.2.163 0
10.5.2.162 255.255.255.255 0.0.0.0 20 0 STUB 10.5.2.163 10.5.2.162 0
10.5.2.163 255.255.255.255 0.0.0.0 10 0 STUB 10.5.2.163 10.5.2.163 0
ascend% show ospf io
IO stats from: boot
>> RECEIVED:
0: Monitor request
785: Hello
13: DB Description
6: Link-State Req
1387: Link-State Update
64: Link-State Ack
>> SENT:
794: Hello
15: DB Description
6: Link-State Req
1017: Link-State Update
212: Link-State Ack
Copyright © 1998, Ascend Communications, Inc. All rights reserved.
