Allied Telesis C613-16164-00 REV E manual Static inter-VRF routing

Page 17

Configuring VRF-lite

Static inter-VRF routing

Static inter-VRF routing involves creating static routes in one VRF instance whose egress VLAN is in a different egress VLAN. These static routes must specify both the egress VLAN and next hop IP address.

The following diagram illustrates use of static routing to achieve inter- VRF communication in VRF-lite.

 

 

 

 

1 9 2 . 1 6 8 . 2 0 . 0/2 4

1 9 2 . 1 6 8 . 2 0 . 0/2 4

 

 

 

 

 

1 9 2 . 1 6 8 . 1 . 0/2 4 global default VRF domain

 

VRF green

1 9 2 . 1 6 8 . 5 0 . 0/2 4

 

 

 

 

VRF red

 

 

 

 

 

VRF blue

 

 

 

 

 

 

 

 

192.168.20.6

 

 

 

192.168.50.10

 

 

 

 

VLAN20

VLAN10

 

VLAN10

 

VLAN30

 

192.168.1.5

 

 

192.168.20.5

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Device A

 

Device B

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DEVICE A STATIC ROUTES CONFIGURATION

DEVICE B STATIC ROUTES CONFIGURATION

 

 

ip route vrf red 192.168.20.0/24 vlan10

ip route vrf blue 192.168.20.0/24 vlan10

From source vrf red, create a static route to

From source vrf blue, create a static route to 192.168.20.0/24

192.168.20.0/24 to access target vlan10. Target vlan is

to access target vlan10. Target vlan is required when

required when performing static IVR.

performing static IVR.

ip route 192.168.1.0/24 vlan20

ip route vrf green 192.168.50.0/24 vlan30

From the source global VRF domain, create a static route to

From the source vrf green, create a static route to

192.168.1.0/24 to access target vlan20. Target vlan is

192.168.50.0/24 to access target vlan30. Target vlan is required

when performing static IVR.

required when performing static IVR.

 

 

 

ip route vrf red 192.168.50.0/24 192.168.20.6 vlan10

ip route vrf blue 192.168.1.0/24 192.168.20.5 vlan10

From source vrf red, create a static route to

From source vrf blue, create a static route to 192.168.1.0/24

192.168.50.0/24 with a next hop of 192.168.20.6

with a next hop of 192.168.20.5 egressing target vlan10.

 

egressing target vlan10. Target vlan is required when

Target vlan is required when performing static IVR.

 

performing static IVR.

 

ip route 192.168.50.0/24 192.168.20.6

ip route vrf green 192.168.1.0/24 192.168.20.5

From the global VRF domain, create a static route to

From the source vrf green, create a static route to 192.168.1.0/

192.168.50.0/24 with a next hop of 192.168.20.6.

24 with a next hop of 192.168.20.5. Static routes to networks

within a VRF instance do not require the target vlan.

Static routes to networks within a VRF instance do

 

not require target vlan.

 

 

 

Configure VRF-lite Page 17

Image 17
Contents What is VRF-lite? How To Configure VRF-lite IntroductionCommand summary Software feature licensesWho should read this document? Which products and software version does it apply to?Contents VRF GlossaryUnderstanding VRF-lite Route table and interface management with VRF-lite VRF-lite security domainsInterface management with VRF Vlan5Adding a VRF-aware static ARP Route management with VRFInter-VRF communication Static and dynamic inter-VRF routing For example VRF-lite features in AW+Route limiting per VRF instance VRF aware services includeVRF-aware utilities within AW+  Ping TCP dump  Telnet client SSH client Awplusconfig# access-list standard Configuring VRF-liteAwplusconfig-if#switchportaccess vlanx Family Awplusconfig-route-map#match ip Ip route 192.168.50.0/24 Ip route vrf green 192.168.1.0/24 Static inter-VRF routingForwarding Information Base FIB and routing protocols Dynamic inter-VRF communication explainedBGP Inter-VRF communication via BGP Route-target import ASNVRFinstance For example Using the route-target commandRoute-target both ASNVRFinstance For example Can be replaced withIf VRF red initially includes Also, if VRF shared configuration includesIf VRF shared initially includes Via BGP IVR, VRF shared will end up with the routesThen via BGP IVR, VRF red will end up with the routes If VRF shared configuration includesViewing source VRF and attribute information for a prefix How VRF-lite security is maintainedMultiple VRFs without inter-VRF communication Simple VRF-lite configuration examples26 Configure VRF-lite Vlan 28 Configure VRF-lite Configure VRF-lite 30 Configure VRF-lite Configure VRF-lite 32 Configure VRF-lite Inter-VRF configuration examples with Internet access Configuration Configure VRF-lite Example B Configuration 38 Configure VRF-lite Configure VRF-lite Example C Configuration 42 Configure VRF-lite Configure VRF-lite  Each VLANs is associated with a VRF instance Configuring a complex inter-VRF solutionNetwork description VRF communication plan Configuration breakdown Configure VRF-lite Configure Vrfs Configure the hardware ACLs 192.168.43.0/24 via the shared VRF This example, three access groups are attached to portWithin the same IP subnet that the switch port is a member Configure Vlan Database Configure IP Addresses Configure VRF-lite Configure Dynamic Routing Configure VRF-lite 56 Configure VRF-lite Configure Static Routing Complete show run output from VRF device is below Configure VRF-lite 60 Configure VRF-lite Configure VRF-lite IP route table from VRF device is below VRF blue Hostname Internetrouter Hostname sharedrouter N1 Ospf Nssa Hostname redospfpeerHostname greeniBGPpeer Hostname bluerippeer Hostname orangerouter Hostname orangeospfpeer VCStack and VRF-lite Other features used in this configurationStack provisioning GreyVirtual Chassis ID X610 VCStack configurationX900 configuration 74 Configure VRF-lite Communication plan Sharing VRF routing and double tagging on the same portGreen PortX610 B ConfigurationsX610 a Configure VRF-lite Additional notes BGP configuration tips 80 Configure VRF-lite VRF device Red router vlan database Red router Route Limits Configuring static route limits100 Configuring Dynamic route limitsAllowed number of fib routes excluding Connect and Static Syntax No max-fib-routesVRF-lite usage guidelines Routing general Useful VRF-related diagnostics command listGeneral Routing protocols IP prefix network, e.g TCPdump HW platform table commands

C613-16164-00 REV E specifications

The Allied Telesis C613-16164-00 REV E is a robust networking device designed to enhance connectivity and communication within enterprise environments. Renowned for its reliability and efficiency, this device serves as an ideal choice for organizations seeking to improve their network infrastructure.

At its core, the C613-16164-00 REV E is a part of Allied Telesis' suite of products that adhere to high-performance standards. One of the main features is its support for both Layer 2 and Layer 3 networking, making it versatile enough to handle a variety of network configurations. This capability allows for seamless integration into different network architectures, whether for simple local area networks (LANs) or more advanced setups with routing capabilities.

Another significant characteristic of the C613-16164-00 REV E is its high-speed data transfer capabilities. With support for Gigabit Ethernet, the device ensures that data can be transmitted quickly and efficiently across the network. This is particularly important for businesses that rely on heavy data usage and need to maintain performance standards even during peak hours.

Additionally, the C613-16164-00 REV E features advanced security measures, including VLAN support and port security configurations, which help protect sensitive information and prevent unauthorized access. This is essential for businesses that handle confidential data and must comply with industry regulations.

In terms of manageability, the device supports SNMP (Simple Network Management Protocol), allowing for easy monitoring and management of network resources. Network administrators can efficiently manage the device and optimize performance with minimal effort, improving overall productivity.

The design of the C613-16164-00 REV E is also noteworthy; it is built for durability, often featuring a compact form factor that makes installation straightforward without compromising on performance. Its compatibility with various Allied Telesis products ensures that organizations can build a cohesive network ecosystem.

In conclusion, the Allied Telesis C613-16164-00 REV E stands out as an excellent networking solution characterized by its support for multiple networking layers, high-speed data transfer, and robust security features. Ideal for both small to medium enterprises and larger organizations, it helps ensure that businesses can maintain efficient and secure operations in a constantly evolving digital landscape.