Table des Matières
Publicité
Les langues disponibles
Les langues disponibles
ANNEX A - BUILDING A MANAGEMENT NETWORK
The static routes, as implemented in the ADR155c, have the following characteristics:
• each route is assigned a metric.
• each route is assigned a preference. The preference is used to settle conflicts when routes of
different types (static and dynamic) have the same destination.
• preference is given to the static routes with respect to the dynamic routes.
• the static routes are always exported by the routing protocols to the other equipment.
Depending on whether the interface which the routes take is in the operational state or not, the
static routes are set up or removed to avoid assignment of non-valid routes.
A maximum of twenty static routes is supported by each ADR
Configuration of static routes
In the static tables context, each network node must have its routing table filled in order to
correctly route the packets received.
All IP routes of a routing table of a given equipment comprise the following fields:
• «destination @IP» : corresponds to the IP address of the equipment or sub-network (or
network) to be reached from the given equipment,
• «subnet mask» : this is the sub-network mask associated to the IP address defined in the
«destination @IP» ; all equipment with the IP address part defined by the "1" bits of this field
which corresponds to the same value as the «destination @IP» part defined by this same
mask can be reached through this route,
• «next hop @IP» : IP address of next equipment (connected directly with given equipment) to
which the packet will be sent,
• «metric» (also referred to as "cost" or distance): value from 1 to 15 indicating the number of
hops to reach the corresponding equipment at the «destination @IP» address. 16
corresponds to infinity for the RIP routing daemon. This field is only used by a possible
routing daemon to select a preferential route if several different routes exist for the same
destination. It is always possible to configure this field for 1 to simplify if use of the field is not
indispensable.
• «interf.» : interface number used to reach the next equipment (whose IP address is «next
hop @IP»).
Note:
Declaration of the interface IP addresses results in setting up implicit static routes to the
associated SUBNETs. It is therefore not necessary to define static routes to join two
equipments on a single SUBNET.
Note:
The IP addresses of an equipment are the addresses of its interfaces (or ports) which
have been configured. The manager only knows one IP address per equipment. This is
why reference is often made to the IP address of an equipment to designate the address
configured in the manager database. This is the address of the port by which the
equipment normally dialogues with the manager.
Note:
To operate an equipment via a PC and an Ethernet interface, the IP address of the
operation PC must be modified so that it belongs to the same SUBNET as the Ethernet
interface used to connect to the network.
The HOST 1 number on each SUBNET should be left free, i.e. begin to number the
equipment starting with the HOST 2 number. The PC will thus always take an IP
address such as : NET.SUBNET.1
Note:
A default router can be defined (option sometimes available) to which all packets which
cannot be routed by the routing table are transmitted.
The figure below gives an example of an IP network and routing tables associated to two typical
equipments. Note that each port of the on-board routing function corresponds to a different
SUBNET.
Installation and User Guide - N56717020104
Page AA-2
No reproduction or communication without the written consent of SAGEM SA
Publicité
Chapitres
Table des Matières
