10.2.5. Special Routes 
The usual demands made on the routing between access points and HG
3500 modules in the central OpenScape 4000 switch are fully met by the
administration described above. A default router (AMO SIPCO, parameter
DEFRT) serves the HiPath 3500 processors as an access to the IP
world beyond the OpenScape 4000 LAN segment. One default router per LAN
segment in which access points are located serves the access points as
a bridge to other network segments.
However, additional demands may be imposed by the specific network
architecture of the customer.
A distinction is to be made between 2 basic scenarios in this context:
- Links between LAN segments containing access points which do not lead to the respective LAN segments via the default router.
- Links from the OpenScape 4000 LAN segment to LAN segments containing access points which do not lead to the OpenScape 4000 LAN segment via the default router.
The difference is that, in the first case, only HG 3575 routing tables
are affected, while in the second case, the routing tables of all HG
3500 modules, as well as the CC computer and the OpenScape 4000 Assistant,
are also affected.
The routing tables of the HG 3500 and HG 3575 allow the configuration
of 8 routes (in addition to default routes which do not appear in the
routing table). These are configured by specifying a target (IP) address,
the netmask of the target network and the IP address of the router port
to be accessed by the source module.
It must be ensured that:
- no duplicate routes are entered, e.g.
|
192.168.23.99
|
,
|
255.255.255.0
|
,
|
192.168.22.2
|
|
192.168.23.98
|
,
|
255.255.255.0
|
,
|
192.168.22.2
|
-
The first entry already leads the route into the entire network segment 192.168.23.X via the router port 192.168.22.2. The second entry would achieve precisely the same and, therefore, must be suppressed.
- the configuration of the route from A to B remains in place without influencing the route from B to A. In other words, a route back to the source must generally also be configured in the target module, e.g.
|
192.168.22.43
|
,
|
255.255.255.0
|
,
|
192.168.23.2
|