260-668080-001 Rev 002 March 2013 55
Eclipse Edge User Manual
Networking Configuration
The Networking configuration screen provides view and change settings for NMS IP
addressing and routing, trap destinations, and a DHCP server option. Refer to:
• Static or Dynamic Routing on page 55
• Networking Screens on page 58
• DHCP Server Function on page 66
• XP4 Compatibility on page 70
For additional (advanced) information on Eclipse NMS networking,
including network dimensioning for ProVision, connectivity options,
addressing and routing basics, and an introduction to OSPF, refer to
the Aviat Networks white paper: Management of Eclipse Networks.
Most screens support context sensitive help. To view, click on Help
in the tool bar, or select Context Help under Help in the menu bar.
Static or Dynamic Routing
Each Eclipse Edge terminal functions as a router to manage the NMS IP routing
between terminals, and from terminals to other management connected devices.
Static routing requires manual configuration of the routing table and any
subsequent reconfiguration. It is suitable for simple networks and for networks
where no significant change in routing is expected. A default gateway option is
provided.
Dynamic routing makes use of a routing protocol such as RIP (Routing Internet
Protocol) or OSPF (Open Shortest Path First), which dynamically updates the
routing tables held within each router through a mutual exchange of messages. In
most instances it should only be necessary to enter the IP address for the terminal
and select RIP or OSPF. For Eclipse, the dynamic routing options are RIP1, RIP2,
or OSPF. Compared to static routing, dynamic requires much less configuration
management by a network administrator.
For large networks using OSPF with segmented OSPF areas, the OSPF area
(network group) for the terminal must be enabled along with entry of the OSPF area
number.
Dynamic routing must be used in Eclipse ring-network configurations.
Refer to Eclipse Address and Routing Options on page 56.