Allied Telesis C613-16164-00 REV E manual BGP configuration tips

Page 79

Dynamic inter-VRF routing between the global VRF domain and a VRF instance

For both these examples all BGP neighbor relationships involve peering between IP local addresses, not to VLAN interface IP addresses within the same subnet.

BGP configuration tips

The following BGP configuration tips are included to explain the use of some BGP specific commands used in the i-BGP and e-BGP example configuration files below.

neighbor x.x.x.x update-source lo

The command neighbor x.x.x.x update-source lo is used to ensure the lo is used as the update source when establishing the BGP neighbor relationship instead of the egress VLAN interface IP.

neighbor x.x.x.x ebgp-multihop 2

The command neighbor x.x.x.x ebgp-multihop 2 is not applicable for an i-BGP connection, but is required for e-BGP when peering to an IP address in a remote network. For example, when forming an e-BGP neighbor relationship to the IP local address configured in a remote peer, the command is required.

This command above, is automatically generated when using e-BGP peering in conjunction with the neighbor x.x.x.x update-source command. The command defaults to hop count of 2 when automatically generated, but it can be explicitly configured to allow e-BGP peering to devices up to 255 hops away.

I-BGP doesn't default to peers being in the same subnet, as it supports multi-hop automatically. This is because the default configuration of i-BGP is a full mesh of all the routers in the AS and there’s no expectation that all i-BGP peers within the mesh will be in the same subnet. So, unlike e-BGP it can be quite common for an i-BGP TCP connection to be formed to IP address in a remote network, instead of peering to an IP address in same subnet.

In the case of e-BGP, it is uncommon to peer to a local loopback address, and similarly, the connection is not typically via a multi-hop L3 routed path - and the concept of a full mesh between all peers doesn’t apply. Hence e-BGP defaults to not allowing peering beyond a single hop.

neighbor x.x.x.x next-hop-self

I-BGP does not change the next hop address contained in BGP routes. To get i-BGP to change the nexthop IP, you need to use the neighbor x.x.x.x next-hop-self command.

neighbor x.x.x.x route-map <xx> out

The command neighbor x.x.x.x route-map <xx> out is used to reference and apply a route map. The route map in turn references an access-list. The out parameter in the command neighbor x.x.x.x route-map <xx> out specifies that the access list (used to filter routes), applies to outgoing advertisements.

Configure VRF-lite Page 79

Page 78 Page 80
Image 79
Page 78 Page 80
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+ SSH client  Telnet client TCP dump 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 Network description Configuring a complex inter-VRF solution Each VLANs is associated with a VRF instance VRF communication plan Configuration breakdown Configure VRF-lite Configure Vrfs Configure the hardware ACLs Within the same IP subnet that the switch port is a member This example, three access groups are attached to port192.168.43.0/24 via the shared VRF 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 a ConfigurationsX610 B 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 limitsAllowed number of fib routes excluding Connect and Static Configuring Dynamic route limits100 Syntax No max-fib-routesVRF-lite usage guidelines General Useful VRF-related diagnostics command listRouting general 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