...
| Tip | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
InfiLINK XG, InfiLINK XG 1000 families of devices
...
Routing configuration for the management traffic
...
Let's look at the task of performing the routing configuration for the management traffic (Figure 4). Within this task, the Slave's device management interface should be accessible to the engineer working at the PC, while the PC and the Slave devices belong to different subnets.
| Center |
|---|
Figure 4 - Scheme of management traffic routing configuration configuration for the InfiLINK XG , / InfiLINK XG 1000 families of devices families |
Let's perform step by step configuration of the Master and Slave devices using the Web interface:
...
| Description | Add the IP addresses to the devices interfaces in accordance with interfaces of the devices according to the scheme. Unlike the devices of the InfiLINK 2x2 , / InfiMAN 2x2 families, the IP address is not assigned to the physical interfaces, but to the virtual management interface (see the Switch section). |
|---|---|
| Master |
|
| Slave |
|
...
| Description | Analyze the routing table: after adding IP addresses to the device's interfaces, the routing table was filled up with entries about specifying the directly connected networks (mark flag C). |
|---|---|
| Master |
|
| Slave |
|
Step 3
| Description | Add static routes for establishing the communication between the PC and the Slave device connectivitydevices. |
|---|---|
| Master | The Master device is intermediate on the path of the packets between the PC and the Slave. Routes to towards the PC and to towards the Slave have been added to the Master's device routing table during the previous steps using the directly connected networks (see step 2), so there is no need to add static entries. |
| Slave | Configure a static route on the Slave device towards the PC's network:
|
Step 3a
| Description | A default route can be configured on the slave device instead of a route to towards the PC's network. |
|---|---|
| Master | Changes are not required. |
| Slave |
|
...
| Description | Analyze the routing table: a static entry (mark flag S) has been added to the Slave's routing table. |
|---|---|
| Master | See step 2 |
| Slave |
|
...
| Description | If a default route has been added in step 3a, a corresponding entry (mark flag S) will be added to the routing table. |
|---|---|
| Master | See step 2 |
| Slave |
|
...
| Description | The task has been solved: an engineer working at on the PC has access to the Slave's device management interface. |
|---|
| Tip | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
Quanta 5, Quanta 70 families of devices
Configuration of management traffic routing
Let's look at the task of routing configuration for management traffic (Figure 5). Within this task, the Slave device management interface should be accessible to the engineer working at the PC, the PC and Slave devices belong to different subnets.
...