Users Guide

Table Of Contents
456 | OSPFv2 Dell PowerConnect ArubaOS 5.0 | [User Guide
OSPF monitoring is available from an IP Routing sub-section (see Figure 102). Both Static and OSPF routes are
available in table format.
Figure 102 Monitoring OSPF
OSPF Interfaces and Neighboring information is available from the OSPF tab (see Figure 102). The Interface
information includes transmit (TX) and receive (RX) statistics.
Deployment Best Practices
Below are some guidelines regarding deployment and topology for this release of OSPFv2.
z In WLAN scenario, configure the Dell controller and all upstream routers in totally stub area; in Branch
Office scenario, configure as stub area so that the Branch Office controller can receive corporate subnets.
z In the WLAN scenario upstream router, only configure the interface connected to the controller in the same
area as the controller. This will minimize the number of local subnet addresses advertised by the upstream
router to the controller.
z Use the upstream router as the designated router (DR) for the link/interface between the controller and the
upstream router.
z The GRE tunnel must be in Layer 2 mode to support Multicast over IPsec tunnel. The Corporate VLAN and
the Remote Office VLAN must be the same VLAN ID.
z The default MTU value for a Layer 3 GRE tunnel in an Dell controller is 1100. When running OSPF over a
GRE tunnel between an Dell controller and another vendor’s router, the MTU values must be the same on
both sides of the GRE tunnel.
z The controllers do not support ABR/ASBR; designate the upstream router (or some other router) as a ABR.
z Do not enable OSPF on any uplink/WAN interfaces on the Branch Office Controller. Enable OSPF only on
the Layer 3 GRE tunnel connecting the master controller.
z Use only one physical port in the uplink VLAN interface that is connecting to the upstream router. This will
prevent broadcasting the protocol PDUs to other ports and hence limit the number of adjacencies on the
uplink interface to only one.