Allied Telesis C613-16164-00 REV E manual Configure VRF-lite

Page 47

Configuring a complex inter-VRF solution

Local interfaces can be utilised by a number of protocols for various purposes. They can be used as a reliable address via which to access a device - an address that is always accessible, irrespective of the link status of any individual external interface.

Within each VRF, configure optional route distinguisher (RD), route-targets and VRF import and export maps. The RD, route-targets and VRF import and export maps are used when leaking routes via BGP. They are not required when inter-VRF communication is achieved via static inter-VRF routes. BGP is used to facilitate inter-VRF communication in this example.

The RD is a BGP ASN (xxx:). The VRF RD is also used by MPLS to facilitate VRF VPNs, which are currently not supported, and thus serves little purpose in the context of VRF-lite. However the RD command is required if using BGP to facilitate inter-VRF communications. Each RD references a unique VRF instance (:xxx). A complete VRF ASN uses the syntax xxx:xxx. For example 100:1 denotes BGP ASN 100, VRF instance1.

The command route-target export xxx:xxx enables routes in the VRF domain with a matching VRF ASN tag to be exported via BGP to be subsequently leaked to other VRFs.

The command route-target import xxx:xxx enables routes from other VRF domains with a matching VRF ASN tag to be imported via BGP into the VRF domain.

The command export map name references a route map, which in turn references the ACLs previously configured. This command ensures (via the associated ACLs) that only selected routes are exported from the VRF domain to BGP.

In this example VRF orange has a static route to network 192.168.20.0/24. This same IP subnet is assigned to vlan 2, which is a part of VRF green. Therefore there is an export map (orange 140) and associated ACL orangeBlock20Export140 deny 192.168.20.0/24 to ensure the network 192.168.20.0 is not exported into BGP, whilst still allowing the export of other networks that do not match the ACL.

The command import map name references a route map, which in turn references the ACLs previously configured. This commands ensures (via the associated ACLs) that only selected routes are imported into the VRF domain from BGP.

There is no route leakage to or from VRF overlap. VRF overlap (and its associated VLANs) remain completely isolated from all other VRF domains. VRF overlap contains network 192.168.10.0/24 associated with vlan6. This same subnet is also contained in VRF red vlan1. This is OK, as VRF overlap has no associated route-target import and route-target export commands.

Configure VRF-lite Page 47

Page 46 Page 48
Image 47
Page 46 Page 48
Contents What is VRF-lite? How To Configure VRF-lite IntroductionWhich products and software version does it apply to? Software feature licensesCommand summary Who should read this document?Contents VRF GlossaryUnderstanding VRF-lite Vlan5 VRF-lite security domainsRoute table and interface management with VRF-lite Interface management with VRFAdding a VRF-aware static ARP Route management with VRFInter-VRF communication Static and dynamic inter-VRF routing For example VRF-lite features in AW+ Ping VRF aware services includeRoute limiting per VRF instance VRF-aware utilities within AW+ 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 Can be replaced with Using the route-target commandRoute-target import ASNVRFinstance For example Route-target both ASNVRFinstance For exampleVia BGP IVR, VRF shared will end up with the routes Also, if VRF shared configuration includesIf VRF red initially includes If VRF shared initially includesThen 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 Grey Other features used in this configurationVCStack and VRF-lite Stack provisioningVirtual Chassis ID X610 VCStack configurationX900 configuration 74 Configure VRF-lite Port Sharing VRF routing and double tagging on the same portCommunication plan GreenX610 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.
Top Page Image Contents