Configuring Peer Groups - Avaya 1000 Series Configuration Manual

Configuring BGP Features
BGP route table, local router ID is 100.1.1.3 Status codes: * valid, > best, i -
internal Origin codes: i - IGP, e - EGP, ? - incomplete
Network
15.1.1.0/24
15.1.2.0/24
18.1.3.0/24
18.1.0.0/21
18.1.5.0/24
18.1.6.0/24
18.1.7.0/24
Apply a filter_list out to Avaya2 using group ToAvaya2 in Avaya1.
Avaya1/configure> policy as_path 1 1 deny ".* 200"
Avaya1/configure> policy as_path 1 2 permit ".*"
The above commands configures a AS_PATH filter which denies all routes originating from
AS200 and permitting other routes. Apply that AS_PATH 1 filter OUTBOUND to group
ToAvaya2.
Avaya1/configure> router bgp 100
Avaya1/configure/router/bgp 100> group ToAvaya2
external
Avaya1/configure/router/bgp 100/group ToAvaya2
external> filter_list 1 out
Avaya1 should have filtered all the routes that originated from AS200 while sending bgp
updates to Avaya2.
Avaya2> show ip bgp table

Configuring Peer Groups

Peer Groups are used in Avaya to apply common policies to a set of neighbors. OUTBOUND
policies can only be applied to peer groups. INBOUND policies are neighbor based.In Avaya
BGP Implementation the policy can be applied in different ways. Avaya supports 3 types of
Peer Groups.
By default Avaya has 3 peer groups configured on the system once BGP is configured:
• BgpInternal
• BgpExternal
• BgpExternal_rt
330 Avaya Secure Router 1000 Series Configuration Guide
Orig Next Hop Next Hop
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
Metric LocPrf Path
100 200 ?
100 200 ?
100 200 ?
100 i
100 200 ?
100 200 ?
100 200 ?
December 2010