AMF 110 Dokumentacja Pobierz pdf (Strona 132)

AMF Introduction and Configuration

126 New and Enhanced Features in AlliedWare Plus 5.4.4 Major and Minor Versions

Configuring a virtual link

The Layer 2 tunnel created by the command atmf virtual-link id ip remote-id remote-ip

command on page 208 enables a local AMF session to appear to pass transparently

across a Wide Area Network (WAN) such as the Internet. The addresses configured as the

local and remote tunnel IP addresses must have IP connectivity to each other. If the tunnel

is configured to connect a head office and branch office over the Internet, typically this

would involve using some type of managed WAN service such as a site-to-site VPN.

Tunnels are only supported using IPv4.

Configuration involves creating the following:

■ local tunnel ID

■ local IP address

■ remote tunnel ID

■ remote IP address

A reciprocal configuration is also required on the corresponding remote device. The local

tunnel ID must be unique to the device on which it is configured.

The tunneled link may operate via external (non AlliedWare Plus) routers in order to

provide wide area network connectivity. However, in this configuration, these devices

perform a conventional router-to-router connection. The protocol tunneling function is

accomplished by the AMF nodes.

Note that the requirement to preconfigure the local IP address and tunnel ID on a device

located at the far end of an AMF virtual-link tunnel means that zero touch device

replacement cannot be achieved on a remote device that terminates the tunnel.

Example Use the following command to create the tunnel shown in figure Figure 5 on page 125.

Prioritizing the tunneled traffic

On the switch that interfaces to the wide area network router, we advise that you prioritize

the tunneled traffic directed to the CPU over other CPU-bound user data. You can achieve

this by allocating a higher Class of Service (CoS) tag to tunnel traffic than other traffic. The

following configuration example shows an appropriate method. In the following

configuration example, the virtual link traffic is between IP addresses 192.168.1.1 (on

Host-A) and 192.168.2.1 (on Host-B). This connection is mapped to VLAN 10.

Note that the following process will prioritize the AMF traffic only within Switch 1 and

Switch 2. To prioritize the tunneled AMF data across the IP network would require

applying Layer 3 QoS by applying a DSCP (Differentiated Services Code Point) priority at

the network boundary (Router 1 and Router 2) and ensuring that these priority levels are

managed throughout the wide area network. Applying and managing QoS through the

wide area network is outside the scope of this document.

Host-A(config)#

atmf virtual-link id 1 ip 192.168.1.1

remote-id 2 remote-ip 192.168.2.1

Host-B(config)#

atmf virtual-link id 2 ip 192.168.2.1

remote-id 1 remote-ip 192.168.1.1

Caution

On an IP interface that is carrying ATMF virtual link traffic, do not set the

MTU (Maximum Transmission Unit) below its default value of 1500 bytes.

1 2 ... 127 128 129 130 131 132 133 134 135 136 137 ... 301 302

Komentarze do niniejszej Instrukcji

Brak uwag

AMF 110 Dokumentacja Strona 132

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Rowery AMF 110