Configuring the LAN
As a second step, configure the Data Center LAN which includes one physical interface.
Refer to "Use Case 1" diagram where the LAN information is displayed in blue.
|
1
|
Click the Interfaces tab. |
|
2
|
Enter the ip|engine Management IP address (10.1.4.2), Prefix Length (24). |
The Management IP address is used for communicating with other ip|engines, the ZTP Server and the Orchestrator.
|
3
|
Use the default Auto Generated option (creation window only) to let the system allocate LAN addresses automatically to the Routers (Router X IP = Management IP + X) linked to the WANs in Router mode that you will configure for this ip|engine. Also refer to "IP Address allocation". |
In this example, only Router 2 IP address will be automatically defined as it corresponds to WAN2 in Router mode.
|
4
|
Do not activate the DHCP Relay function since the Data Center hosts can directly access the DHCP Server. The ip|engine does not need to relay host requests. |
|
5
|
Do not enter any VLAN ID. Note that the grey values appearing in some fields of the interface are only given as examples and are not taken into account in the configuration. |
|
6
|
Do not activate the MultiPath function. |
|
7
|
Enable the Copy LAN to WAN function to copy the state of the LAN to its related WAN. This LAN/WAN state synchronization is useful when the LAN interface breaks down. |
|
8
|
Leave the Speed parameter to Auto to let the system define the speed of the interface, or you can force the speed to 100FD or 1000FD. The full duplex speed is expressed in megabits per second. |
|
9
|
Define this Data Center hub ip|engine as a Backhauling Site. This means it can receive Internet traffic through the overlay and route it to a firewall in the LAN: specify the LAN Internet Gateway IP address as 10.1.4.40 |
The following window displays the validated settings.
Defining additional Subnets
In Use Case 1, there is one additional subnet you must specify because the system is unable to detect it automatically. Subnets enable you to classify, measure and control the traffic coming from and going to specific hosts and servers.
|
10
|
Click the Subnets tab and the Add subnet icon  . |
|
11
|
Define the additional subnet by entering its prefix (10.1.5.0), prefix length (24) and next hop (10.1.4.249). |
Note: The Next Hop field is optional and you can leave it empty if you enable BGP or OSPF.
|
12
|
The Data Center ip|engine exchanges its routing tables with the local router using either BGP or OSPF. Refer to the following procedures which are mutually exclusive. |
Configuring BGP
|
1
|
In the Interfaces window, select BGP as the LAN Routing Protocol. |
|
2
|
Click the BGP tab and the Add peering icon . |
|
3
|
Enter the IP address of the BGP local peers (10.1.4.249 and 10.1.4.254). |
|
4
|
Activate AS Path Prepending and enter 2 in the Value field. The authorized range is [1-10]. |
An AS Path is a BGP route attribute and corresponds to the list of autonomous systems that routing information passes through to get to a specified router. AS path length represents the sequence of AS hops that a BGP route follows from a particular AS (the traffic sender) towards the origin AS (the traffic receiver).
Since BGP prefers the shortest AS path to get to the destination, the MPLS CE router (10.1.4.254) will probably re-route the traffic to the hybrid Data Center ip|engine router (10.1.4.4) and use the Internet route towards B02 instead of using the MPLS route towards the same ip|engine (see "Use Case 4C" and "Use Case 1" diagrams). To avoid this behavior and enable the DWS Service to operate correctly, you can manipulate AS path length by extending the AS path with multiple copies of the AS number of the first AS path hop.
By entering 2 as AS Path Prepending value, you define three AS path hops (2 + the initial one) from the Data Center to B02 for the Internet route. It corresponds to AS_PATH=[65002, 65002, 65002] and is not shorter than AS_PATH=[65500,65002] for the MPLS route (where 65500 represents the MPLS hop).
Configuring OSPF
|
1
|
In the Interfaces window, select OSPF as the LAN Routing Protocol. |
|
2
|
Click the Add subinterface icon . Enter 10 as VLAN ID, 10.10.4.4 as the sub-interface IP address for Router 2 and 24 as Prefix Length. Each VLAN corresponds to an OSPF network area. |
|
4
|
Configure Router 2 as follows: |
|
•
|
VLAN: select VLAN ID 10 you defined in the previous step. You can also select the 'None' option to take into account the ip address of the router. |
|
•
|
Area ID: by default, Area 0 which is the backbone area or the core of the OSPF network. It corresponds to the area including the CE router. All other areas are connected to it and all the traffic between areas must traverse it. |
In this example, enter 1 as Area 1 ID.
|
•
|
Cost: use the 10 default value which corresponds to the interface cost of Router 2 (10.1.4.4). |
|
•
|
Authentication: select one authentication method among MD5, SHA1, HMAC SHA256, HMAC SHA384 and HMAC SHA512. By default, there is no authentication (NONE option). |
|
•
|
Key: enter your authentication password. Use the  icon different statuses to either display or hide the key. |
|
•
|
Key ID: enter 1 as the password identifier. This value must match the key ID of the Core Router password. |
|
5
|
Specify OSPF Advanced Configuration parameters which are common to all the routers: |
|
•
|
Hello Timer: time between each Hello packet sent by the router to the interface(s). Hello packets enable the system to establish adjacencies and router keepalive messages to notify neighbors that links are up and active. |
|
•
|
Dead Timer: time after the last Hello packet is sent by a router and before the router is considered as dead. Dead Timer cannot be smaller than Hello Timer x 3. |
|
•
|
Priority: with the Broadcast network type (only network type supported), the network elects one Designated Router (DR) and one Backup Designated Router (BDR). They are in charge of transferring topology modifications to all the routers of the area. The priority mechanism determines which router is DR and which one is BDR. |
The router with the highest priority value is the DR router which is the main router for distributing the routes. If both DR and BDR routers have the same priority value, the router with the highest IP address is selected as the DR. In the current example, keep the 0 default value, i.e. this router is neither DR nor BDR (it does not participate in the election).
|
•
|
Default Originate: only check this option if you want to redistribute a default route through OSPF. |
|
•
|
Instance ID: set this field to 0 to ensure this parameter is not currently used by routers. |
Note: The 
button in the LAN Routing Protocol area of the LAN window enables you to delete BGP or OSPF configurations and restore the default values. When you click this button and confirm the operation, either BGP local peers are deleted or OSPF authentication data are cleared.
Also see how to configure:
a Branch Office ip|engine LAN