juniper device how to find what port a bgp ip is on
BGP Peering Sessions
Understanding External BGP Peering Sessions
To plant point-to-point connections betwixt peer autonomous systems (Ass), you configure a BGP session on each interface of a point-to-point link. Mostly, such sessions are fabricated at network exit points with neighboring hosts outside the Equally. Figure one shows an example of a BGP peering session.
Figure ane: BGP Peering Session 
In Effigy 1, Router A is a gateway router for Every bit 3, and Router B is a gateway router for Every bit 10. For traffic internal to either AS, an interior gateway protocol (IGP) is used (OSPF, for case). To route traffic betwixt peer Ass, a BGP session is used.
You arrange BGP routing devices into groups of peers. Unlike peer groups tin have different group types, AS numbers, and route reflector cluster identifiers.
To define a BGP group that recognizes only the specified BGP systems as peers, statically configure all the organisation'south peers by including one or more neighbor statements. The peer neighbour's address can be either an IPv6 or IPv4 address.
As the number of external BGP (EBGP) groups increases, the power to support a big number of BGP sessions might become a scaling issue. The preferred style to configure a large number of BGP neighbors is to configure a few groups consisting of multiple neighbors per group. Supporting fewer EBGP groups generally scales better than supporting a big number of EBGP groups. This becomes more evident in the case of hundreds of EBGP groups when compared with a few EBGP groups with multiple peers in each group.
Afterward the BGP peers are established, non-BGP routes are not automatically advertised past the BGP peers. At each BGP-enabled device, policy configuration is required to export the local, static, or IGP-learned routes into the BGP RIB so advertise them every bit BGP routes to the other peers. BGP'southward advertisement policy, by default, does not advertise any non-BGP routes (such as local routes) to peers.
Note:
On SRX Series devices, you must enable the expected host-inbound traffic on the specified interfaces or all interfaces of the zone. Otherwise entering traffic destined to this device is dropped by default.
For example, to allow BGP traffic on a specific zone of your SRX Serial device, use the following footstep:
[edit] user@host# set security zones security-zone trust host-inbound-traffic protocols bgp
(All interfaces)
[edit] user@host# gear up security zones security-zone trust interfaces ge-0/0/1.0 host-inbound-traffic protocols bgp
(Specified interface)
Example: Configuring External BGP Point-to-Betoken Peer Sessions
This example shows how to configure BGP signal-to-bespeak peer sessions.
- Requirements
- Overview
- Configuration
- Verification
Requirements
Before you lot begin, if the default BGP policy is non acceptable for your network, configure routing policies to filter incoming BGP routes and to advertise BGP routes.
Overview
Figure 2 shows a network with BGP peer sessions. In the sample network, Device East in AS 17 has BGP peer sessions to a group of peers chosen external-peers. Peers A, B, and C reside in Every bit 22 and have IP addresses ten.10.ten.ii, ten.ten.x.6, and 10.ten.ten.ten. Peer D resides in AS 79, at IP address 10.21.7.ii. This instance shows the configuration on Device E.
Topology
Figure 2: Typical Network with BGP Peer Sessions 
Configuration
Procedure
- CLI Quick Configuration
- Stride-by-Step Process
- Results
CLI Quick Configuration
To quickly configure this example, copy the post-obit commands, paste them into a text file, remove any line breaks, change whatever details necessary to friction match your network configuration, and and so copy and paste the commands into the CLI at the [edit] hierarchy level.
set interfaces ge-ane/2/0 unit of measurement 0 clarification to-A fix interfaces ge-1/2/0 unit 0 family inet accost ten.x.10.ane/30 set interfaces ge-0/0/1 unit of measurement v clarification to-B set interfaces ge-0/0/1 unit 5 family inet address 10.10.x.5/30 prepare interfaces ge-0/ane/0 unit of measurement ix description to-C set interfaces ge-0/1/0 unit of measurement 9 family inet accost 10.x.x.ix/30 set interfaces ge-1/ii/one unit 21 description to-D set interfaces ge-1/2/1 unit 21 family inet address 10.21.vii.1/30 set protocols bgp group external-peers blazon external set protocols bgp group external-peers peer-as 22 prepare protocols bgp grouping external-peers neighbour x.10.10.2 set protocols bgp group external-peers neighbour 10.x.10.6 set protocols bgp group external-peers neighbor 10.x.10.ten set protocols bgp grouping external-peers neighbor 10.21.vii.two peer-as 79 fix routing-options autonomous-system 17
Pace-by-Pace Procedure
The following example requires yous to navigate various levels in the configuration hierarchy. For data almost navigating the CLI, see Using the CLI Editor in Configuration Mode in the Junos Bone CLI User Guide.
To configure the BGP peer sessions:
-
Configure the interfaces to Peers A, B, C, and D.
[edit interfaces] user@E# ready ge-1/2/0 unit of measurement 0 description to-A user@Eastward# set up ge-1/2/0 unit 0 family inet address 10.ten.10.1/xxx user@East# set ge-0/0/1 unit of measurement v description to-B user@E# set ge-0/0/1 unit five family inet address 10.x.10.5/thirty user@E# set up ge-0/1/0 unit ix description to-C user@Eastward# prepare ge-0/1/0 unit 9 family unit inet accost 10.ten.10.nine/30 user@E# set ge-1/two/1 unit of measurement 21 description to-D user@E# set ge-i/two/1 unit 21 family inet address 10.21.7.1/xxx
-
Ready the democratic system (AS) number.
[edit routing-options] user@Eastward# set autonomous-arrangement 17
-
Create the BGP group, and add the external neighbor addresses.
[edit protocols bgp group external-peers] user@East# set neighbor 10.x.10.2 user@E# set neighbor 10.10.x.6 user@E# set neighbour x.10.10.10
-
Specify the democratic organization (AS) number of the external AS.
[edit protocols bgp group external-peers] user@E# set peer-as 22
-
Add together Peer D, and fix the As number at the individual neighbor level.
The neighbour configuration overrides the group configuration. And then, while
peer-as 22is gear up for all the other neighbors in the group,peer-as 79is set for neighbor ten.21.seven.two.[edit protocols bgp grouping external-peers] user@E# set neighbor 10.21.7.two peer-as 79
-
Set the peer type to external BGP (EBGP).
[edit protocols bgp grouping external-peers] user@E# set type external
Results
From configuration style, confirm your configuration past entering the bear witness interfaces, show protocols, and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
[edit] user@E# bear witness interfaces ge-1/2/0 { unit 0 { description to-A; family unit inet { address ten.10.ten.ane/xxx; } } } ge-0/0/ane { unit 5 { description to-B; family unit inet { address 10.10.10.5/30; } } } ge-0/1/0 { unit 9 { description to-C; family inet { address 10.10.10.ix/30; } } } ge-1/ii/one { unit of measurement 21 { description to-D; family inet { address 10.21.seven.1/thirty; } } } [edit] user@E# testify protocols bgp { group external-peers { blazon external; peer-equally 22; neighbour 10.ten.10.2; neighbor 10.10.x.6; neighbor 10.10.10.10; neighbor ten.21.seven.two { peer-equally 79; } } } [edit] user@E# show routing-options democratic-organization 17; If you are washed configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
- Verifying BGP Neighbors
- Verifying BGP Groups
- Verifying BGP Summary Information
Verifying BGP Neighbors
- Purpose
- Action
Purpose
Verify that BGP is running on configured interfaces and that the BGP session is active for each neighbor address.
Action
From operational way, run the show bgp neighbor command.
user@E> show bgp neighbor Peer: ten.10.x.ii+179 AS 22 Local: 10.x.10.one+65406 AS 17 Blazon: External Land: Established Flags: <Sync> Final State: OpenConfirm Last Event: RecvKeepAlive Last Error: None Options: <Preference PeerAS Refresh> Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 10.10.10.2 Local ID: x.ten.10.ane Active Holdtime: 90 Keepalive Interval: 30 Peer index: 0 BFD: disabled, downwards Local Interface: ge-1/2/0.0 NLRI for restart configured on peer: inet-unicast NLRI advertised by peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh adequacy (2) Restart time configured on the peer: 120 Stale routes from peer are kept for: 300 Restart fourth dimension requested by this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received end-of-rib markers: inet-unicast NLRI of all end-of-rib markers sent: inet-unicast Peer supports 4 byte Every bit extension (peer-as 22) Peer does not support Addpath Table inet.0 Fleck: 10000 RIB State: BGP restart is consummate Send land: in sync Agile prefixes: 0 Received prefixes: 0 Accustomed prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Last traffic (seconds): Received 10 Sent half-dozen Checked 1 Input messages: Total 8522 Updates 1 Refreshes 0 Octets 161922 Output messages: Total 8433 Updates 0 Refreshes 0 Octets 160290 Output Queue[0]: 0 Peer: 10.ten.10.6+54781 AS 22 Local: 10.ten.x.5+179 AS 17 Blazon: External State: Established Flags: <Sync> Last Land: OpenConfirm Last Outcome: RecvKeepAlive Concluding Fault: None Options: <Preference PeerAS Refresh> Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 10.x.10.6 Local ID: ten.10.10.1 Agile Holdtime: 90 Keepalive Interval: 30 Peer index: 1 BFD: disabled, downward Local Interface: ge-0/0/1.5 NLRI for restart configured on peer: inet-unicast NLRI advertised by peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh capability (2) Restart fourth dimension configured on the peer: 120 Stale routes from peer are kept for: 300 Restart time requested past this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received end-of-rib markers: inet-unicast NLRI of all end-of-rib markers sent: inet-unicast Peer supports 4 byte AS extension (peer-as 22) Peer does non support Addpath Table inet.0 Bit: 10000 RIB Country: BGP restart is complete Send state: in sync Active prefixes: 0 Received prefixes: 0 Accepted prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Last traffic (seconds): Received 12 Sent 6 Checked 33 Input messages: Total 8527 Updates 1 Refreshes 0 Octets 162057 Output letters: Total 8430 Updates 0 Refreshes 0 Octets 160233 Output Queue[0]: 0 Peer: 10.10.10.x+55012 AS 22 Local: x.10.10.9+179 AS 17 Type: External State: Established Flags: <Sync> Last State: OpenConfirm Last Outcome: RecvKeepAlive Last Error: None Options: <Preference PeerAS Refresh> Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 10.ten.10.ten Local ID: 10.10.10.1 Agile Holdtime: 90 Keepalive Interval: 30 Peer alphabetize: 2 BFD: disabled, down Local Interface: atomic number 26-0/one/0.ix NLRI for restart configured on peer: inet-unicast NLRI advertised past peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh capability (2) Restart time configured on the peer: 120 Stale routes from peer are kept for: 300 Restart time requested by this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received end-of-rib markers: inet-unicast NLRI of all end-of-rib markers sent: inet-unicast Peer supports 4 byte Equally extension (peer-equally 22) Peer does non support Addpath Table inet.0 Bit: 10000 RIB Country: BGP restart is complete Send state: in sync Active prefixes: 0 Received prefixes: 0 Accepted prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Terminal traffic (seconds): Received xv Sent 6 Checked 37 Input letters: Total 8527 Updates 1 Refreshes 0 Octets 162057 Output messages: Total 8429 Updates 0 Refreshes 0 Octets 160214 Output Queue[0]: 0 Peer: 10.21.7.ii+61867 AS 79 Local: x.21.7.1+179 Every bit 17 Type: External State: Established Flags: <ImportEval Sync> Last Country: OpenConfirm Last Event: RecvKeepAlive Last Mistake: None Options: <Preference PeerAS Refresh> Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 10.21.7.2 Local ID: 10.10.10.i Active Holdtime: 90 Keepalive Interval: 30 Peer index: 3 BFD: disabled, down Local Interface: ge-1/ii/1.21 NLRI for restart configured on peer: inet-unicast NLRI advertised by peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh capability (2) Restart time configured on the peer: 120 Dried routes from peer are kept for: 300 Restart time requested by this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received end-of-rib markers: inet-unicast NLRI of all finish-of-rib markers sent: inet-unicast Peer supports iv byte Every bit extension (peer-as 79) Peer does not support Addpath Table inet.0 Bit: 10000 RIB State: BGP restart is complete Send state: in sync Agile prefixes: 0 Received prefixes: 0 Accustomed prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Final traffic (seconds): Received 28 Sent 24 Checked 47 Input letters: Total 8521 Updates 1 Refreshes 0 Octets 161943 Output messages: Total 8427 Updates 0 Refreshes 0 Octets 160176 Output Queue[0]: 0
Verifying BGP Groups
- Purpose
- Activeness
Purpose
Verify that the BGP groups are configured correctly.
Action
From operational manner, run the prove bgp grouping command.
user@E> show bgp group Grouping Type: External Local AS: 17 Name: external-peers Index: 0 Flags: <> Holdtime: 0 Total peers: four Established: four x.10.x.2+179 10.ten.10.6+54781 10.x.10.10+55012 ten.21.7.two+61867 inet.0: 0/0/0/0 Groups: 1 Peers: four External: iv Internal: 0 Downwards peers: 0 Flaps: 0 Table Tot Paths Deed Paths Suppressed History Damp Country Pending inet.0 0 0 0 0 0 0
Verifying BGP Summary Information
- Purpose
- Activity
Purpose
Verify that the BGP configuration is correct.
Activity
From operational mode, run the evidence bgp summary command.
user@E> show bgp summary Groups: 1 Peers: 4 Down peers: 0 Table Tot Paths Act Paths Suppressed History Clammy Land Pending inet.0 0 0 0 0 0 0 Peer Every bit InPkt OutPkt OutQ Flaps Concluding Upwardly/Dwn State|#Active/Received/Accepted/Damped... x.10.10.2 22 8559 8470 0 0 2nd 16:12:56 0/0/0/0 0/0/0/0 ten.10.ten.six 22 8566 8468 0 0 second 16:12:12 0/0/0/0 0/0/0/0 10.x.10.10 22 8565 8466 0 0 second sixteen:11:31 0/0/0/0 0/0/0/0 10.21.vii.two 79 8560 8465 0 0 2d xvi:10:58 0/0/0/0 0/0/0/0
Instance: Configuring External BGP on Logical Systems with IPv6 Interfaces
This instance shows how to configure external BGP (EBGP) point-to-point peer sessions on logical systems with IPv6 interfaces.
- Requirements
- Overview
- Configuration
- Verification
Requirements
In this example, no special configuration beyond device initialization is required.
Overview
Junos OS supports EBGP peer sessions by ways of IPv6 addresses. An IPv6 peer session can be configured when an IPv6 accost is specified in the neighbour argument. This example uses EUI-64 to generate IPv6 addresses that are automatically applied to the interfaces. An EUI-64 accost is an IPv6 address that uses the IEEE EUI-64 format for the interface identifier portion of the accost (the last 64 bits).
Note:
Alternatively, you can configure EBGP sessions using manually assigned 128-scrap IPv6 addresses.
If you utilize 128-fleck link-local addresses for the interfaces, you must include the local-interface argument. This statement is valid simply for 128-scrap IPv6 link-local addresses and is mandatory for configuring an IPv6 EBGP link-local peer session.
Configuring EBGP peering using link-local addresses is only applicable for direct connected interfaces. There is no support for multihop peering.
After your interfaces are up, yous tin use the prove interfaces terse command to view the EUI-64-generated IPv6 addresses on the interfaces. Y'all must use these generated addresses in the BGP neighbor statements. This example demonstrates the full stop-to-finish procedure.
In this example, Frame Relay interface encapsulation is applied to the logical tunnel (lt) interfaces. This is a requirement considering merely Frame Relay encapsulation is supported when IPv6 addresses are configured on the lt interfaces.
Figure three shows a network with BGP peer sessions. In the sample network, Router R1 has v logical systems configured. Device Due east in autonomous organisation (AS) 17 has BGP peer sessions to a group of peers called external-peers. Peers A, B, and C reside in Every bit 22. This case shows the stride-by-step configuration on Logical Organization A and Logical System E.
Topology
Figure 3: Typical Network with BGP Peer Sessions 
Configuration
- Procedure
- Configuring the External BGP Sessions
Procedure
- CLI Quick Configuration
- Footstep-by-Step Procedure
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to lucifer your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and so enter commit from configuration mode.
Device A
ready logical-systems A interfaces lt-0/i/0 unit 1 description to-E set logical-systems A interfaces lt-0/i/0 unit 1 encapsulation frame-relay set logical-systems A interfaces lt-0/1/0 unit 1 dlci one set logical-systems A interfaces lt-0/1/0 unit 1 peer-unit of measurement 25 set logical-systems A interfaces lt-0/1/0 unit 1 family inet6 address 2001:db8:0:one::/64 eui-64 set logical-systems A interfaces lo0 unit 1 family inet6 address 2001:db8::1/128 set logical-systems A protocols bgp group external-peers type external prepare logical-systems A protocols bgp group external-peers peer-as 17 gear up logical-systems A protocols bgp group external-peers neighbor 2001:db8:0:1:2a0:a502:0:19da prepare logical-systems A routing-options router-id 172.sixteen.1.one gear up logical-systems A routing-options autonomous-system 22
Device B
set logical-systems B interfaces lt-0/1/0 unit six description to-E set logical-systems B interfaces lt-0/i/0 unit of measurement vi encapsulation frame-relay set logical-systems B interfaces lt-0/ane/0 unit 6 dlci half dozen set logical-systems B interfaces lt-0/1/0 unit 6 peer-unit of measurement 5 set logical-systems B interfaces lt-0/1/0 unit 6 family inet6 accost 2001:db8:0:two::/64 eui-64 fix logical-systems B interfaces lo0 unit of measurement 2 family unit inet6 address 2001:db8::2/128 set up logical-systems B protocols bgp grouping external-peers type external set logical-systems B protocols bgp grouping external-peers peer-every bit 17 prepare logical-systems B protocols bgp grouping external-peers neighbor 2001:db8:0:2:2a0:a502:0:5da fix logical-systems B routing-options router-id 172.16.2.2 set logical-systems B routing-options democratic-system 22
Device C
gear up logical-systems C interfaces lt-0/1/0 unit x description to-East set logical-systems C interfaces lt-0/i/0 unit 10 encapsulation frame-relay set logical-systems C interfaces lt-0/1/0 unit 10 dlci x set logical-systems C interfaces lt-0/1/0 unit of measurement ten peer-unit ix set logical-systems C interfaces lt-0/ane/0 unit of measurement ten family inet6 accost 2001:db8:0:three::/64 eui-64 prepare logical-systems C interfaces lo0 unit of measurement iii family unit inet6 address 2001:db8::three/128 set logical-systems C protocols bgp grouping external-peers blazon external set logical-systems C protocols bgp grouping external-peers peer-as 17 gear up logical-systems C protocols bgp grouping external-peers neighbor 2001:db8:0:3:2a0:a502:0:9da set up logical-systems C routing-options router-id 172.sixteen.three.iii gear up logical-systems C routing-options autonomous-organization 22
Device D
set logical-systems D interfaces lt-0/1/0 unit 7 description to-Due east prepare logical-systems D interfaces lt-0/1/0 unit 7 encapsulation frame-relay set logical-systems D interfaces lt-0/one/0 unit of measurement 7 dlci vii set logical-systems D interfaces lt-0/ane/0 unit 7 peer-unit 21 fix logical-systems D interfaces lt-0/ane/0 unit of measurement 7 family inet6 accost 2001:db8:0:4::/64 eui-64 set logical-systems D interfaces lo0 unit 4 family inet6 accost 2001:db8::4/128 set logical-systems D protocols bgp group external-peers type external gear up logical-systems D protocols bgp group external-peers peer-every bit 17 set logical-systems D protocols bgp group external-peers neighbor 2001:db8:0:four:2a0:a502:0:15da set logical-systems D routing-options router-id 172.16.iv.4 set up logical-systems D routing-options autonomous-system 79
Device East
set logical-systems Eastward interfaces lt-0/one/0 unit 5 description to-B set logical-systems E interfaces lt-0/1/0 unit five encapsulation frame-relay set up logical-systems E interfaces lt-0/1/0 unit 5 dlci vi set up logical-systems E interfaces lt-0/1/0 unit 5 peer-unit six set logical-systems E interfaces lt-0/ane/0 unit 5 family inet6 address 2001:db8:0:2::/64 eui-64 prepare logical-systems E interfaces lt-0/i/0 unit of measurement ix clarification to-C set logical-systems E interfaces lt-0/1/0 unit 9 encapsulation frame-relay set logical-systems E interfaces lt-0/1/0 unit 9 dlci 10 set logical-systems E interfaces lt-0/1/0 unit 9 peer-unit 10 set logical-systems Eastward interfaces lt-0/1/0 unit 9 family inet6 accost 2001:db8:0:3::/64 eui-64 prepare logical-systems Eastward interfaces lt-0/one/0 unit 21 description to-D gear up logical-systems E interfaces lt-0/1/0 unit of measurement 21 encapsulation frame-relay set logical-systems E interfaces lt-0/i/0 unit 21 dlci 7 set logical-systems E interfaces lt-0/1/0 unit of measurement 21 peer-unit 7 ready logical-systems Due east interfaces lt-0/1/0 unit 21 family unit inet6 address 2001:db8:0:four::/64 eui-64 set logical-systems E interfaces lt-0/i/0 unit 25 description to-A set up logical-systems Due east interfaces lt-0/one/0 unit 25 encapsulation frame-relay fix logical-systems East interfaces lt-0/1/0 unit 25 dlci one ready logical-systems Eastward interfaces lt-0/ane/0 unit 25 peer-unit ane set logical-systems E interfaces lt-0/1/0 unit of measurement 25 family unit inet6 address 2001:db8:0:one::/64 eui-64 set logical-systems E interfaces lo0 unit v family unit inet6 address 2001:db8::5/128 gear up logical-systems Due east protocols bgp group external-peers blazon external set logical-systems East protocols bgp group external-peers peer-as 22 set up logical-systems E protocols bgp group external-peers neighbor 2001:db8:0:ane:2a0:a502:0:1da set up logical-systems East protocols bgp group external-peers neighbor 2001:db8:0:2:2a0:a502:0:6da set logical-systems Due east protocols bgp group external-peers neighbor 2001:db8:0:3:2a0:a502:0:ada set logical-systems E protocols bgp grouping external-peers neighbor 2001:db8:0:4:2a0:a502:0:7da peer-as 79 set logical-systems Eastward routing-options router-id 172.sixteen.5.5 set logical-systems East routing-options autonomous-system 17
Step-by-Step Procedure
The post-obit case requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Fashion in the CLI User Guide.
To configure the BGP peer sessions:
-
Run the
testify interfaces tersecontrol to verify that the physical router has a logical tunnel (lt) interface.user@R1> show interfaces terse Interface Admin Link Proto Local Remote ... lt-0/ane/0 upward up ...
-
On Logical Arrangement A, configure the interface encapsulation, peer-unit of measurement number, and DLCI to accomplish Logical System E.
user@R1> set cli logical-system A Logical system: A [edit] user@R1:A> edit Entering configuration way [edit] user@R1:A# edit interfaces [edit interfaces] user@R1:A# ready lt-0/1/0 unit of measurement 1 encapsulation frame-relay user@R1:A# set lt-0/ane/0 unit of measurement ane dlci 1 user@R1:A# prepare lt-0/i/0 unit 1 peer-unit 25
-
On Logical Organization A, configure the network address for the link to Peer E, and configure a loopback interface.
[edit interfaces] user@R1:A# set lt-0/1/0 unit 1 description to-Eastward user@R1:A# set lt-0/one/0 unit one family inet6 accost 2001:db8:0:1::/64 eui-64 user@R1:A# set up lo0 unit one family inet6 accost 2001:db8::ane/128
-
On Logical Arrangement East, configure the interface encapsulation, peer-unit of measurement number, and DLCI to attain Logical System A.
user@R1> gear up cli logical-system East Logical system: E [edit] user@R1:Eastward> edit Entering configuration mode [edit] user@R1:E# edit interfaces [edit interfaces] user@R1:E# set lt-0/1/0 unit 25 encapsulation frame-relay user@R1:E# set lt-0/one/0 unit of measurement 25 dlci 1 user@R1:E# set lt-0/1/0 unit 25 peer-unit i
-
On Logical System E, configure the network address for the link to Peer A, and configure a loopback interface.
[edit interfaces] user@R1:East# gear up lt-0/one/0 unit 25 clarification to-A user@R1:E# set lt-0/1/0 unit 25 family inet6 address 2001:db8:0:1::/64 eui-64 user@R1:E# set lo0 unit 5 family inet6 address 2001:db8::five/128
-
Run the
show interfaces tersecommand to see the IPv6 addresses that are generated by EUI-64.The 2001 addresses are used in this case in the BGP
neighborstatements.Annotation:
The fe80 addresses are link-local addresses and are not used in this case.
user@R1:A> show interfaces terse Interface Admin Link Proto Local Remote Logical organisation: A betsy@tp8:A> show interfaces terse Interface Admin Link Proto Local Remote lt-0/one/0 lt-0/1/0.1 upwardly up inet6 2001:db8:0:1:2a0:a502:0:1da/64 fe80::2a0:a502:0:1da/64 lo0 lo0.1 up up inet6 2001:db8::1 fe80::2a0:a50f:fc56:1da
user@R1:E> evidence interfaces terse Interface Admin Link Proto Local Remote lt-0/1/0 lt-0/1/0.25 upwards upwardly inet6 2001:db8:0:1:2a0:a502:0:19da/64 fe80::2a0:a502:0:19da/64 lo0 lo0.5 up up inet6 2001:db8::v fe80::2a0:a50f:fc56:1da
-
Repeat the interface configuration on the other logical systems.
Configuring the External BGP Sessions
- Footstep-past-Step Procedure
- Results
Step-by-Step Process
The following instance requires you to navigate diverse levels in the configuration hierarchy. For data most navigating the CLI, see Using the CLI Editor in Configuration Style in the CLI User Guide.
To configure the BGP peer sessions:
-
On Logical Arrangement A, create the BGP group, and add the external neighbor address.
[edit protocols bgp grouping external-peers] user@R1:A# ready neighbor 2001:db8:0:1:2a0:a502:0:19da
-
On Logical System Due east, create the BGP group, and add the external neighbor address.
[edit protocols bgp group external-peers] user@R1:E# set neighbor 2001:db8:0:1:2a0:a502:0:1da
-
On Logical Organisation A, specify the autonomous system (AS) number of the external As.
[edit protocols bgp grouping external-peers] user@R1:A# set peer-as 17
-
On Logical System E, specify the democratic system (As) number of the external Equally.
[edit protocols bgp group external-peers] user@R1:E# set peer-as 22
-
On Logical System A, set the peer type to EBGP.
[edit protocols bgp group external-peers] user@R1:A# set blazon external
-
On Logical Arrangement E, fix the peer type to EBGP.
[edit protocols bgp grouping external-peers] user@R1:Due east# gear up type external
-
On Logical System A, set the autonomous arrangement (Every bit) number and router ID.
[edit routing-options] user@R1:A# set up router-id 172.16.1.1 user@R1:A# fix autonomous-system 22
-
On Logical System E, set up the AS number and router ID.
[edit routing-options] user@R1:East# ready router-id 172.16.5.5 user@R1:E# prepare autonomous-organisation 17
-
Repeat these steps for Peers A, B, C, and D.
Results
From configuration style, ostend your configuration by entering the show logical-systems command. If the output does not display the intended configuration, echo the instructions in this case to correct the configuration.
[edit] user@R1# prove logical-systems A { interfaces { lt-0/i/0 { unit one { description to-East; encapsulation frame-relay; dlci ane; peer-unit 25; family unit inet6 { address 2001:db8:0:1::/64 { eui-64; } } } } lo0 { unit of measurement 1 { family inet6 { address 2001:db8::1/128; } } } } protocols { bgp { group external-peers { type external; peer-every bit 17; neighbour 2001:db8:0:ane:2a0:a502:0:19da; } } routing-options { router-id 172.xvi.one.ane; autonomous-system 22; } } B { interfaces { lt-0/1/0 { unit of measurement half dozen { description to-E; encapsulation frame-relay; dlci half dozen; peer-unit 5; family inet6 { address 2001:db8:0:ii::/64 { eui-64; } } } } lo0 { unit 2 { family inet6 { address 2001:db8::two/128; } } } } protocols { bgp { grouping external-peers { type external; peer-as 17; neighbor 2001:db8:0:ii:2a0:a502:0:5da; } } routing-options { router-id 172.16.2.ii; autonomous-system 22; } } C { interfaces { lt-0/1/0 { unit 10 { description to-E; encapsulation frame-relay; dlci 10; peer-unit 9; family inet6 { address 2001:db8:0:iii::/64 { eui-64; } } } } lo0 { unit 3 { family inet6 { address 2001:db8::3/128; } } } } protocols { bgp { group external-peers { type external; peer-as 17; neighbor 2001:db8:0:3:2a0:a502:0:9da; } } } routing-options { router-id 172.xvi.three.3; democratic-system 22; } } D { interfaces { lt-0/ane/0 { unit 7 { description to-E; encapsulation frame-relay; dlci 7; peer-unit 21; family inet6 { address 2001:db8:0:4::/64 { eui-64; } } } } lo0 { unit iv { family inet6 { accost 2001:db8::4/128; } } } } protocols { bgp { group external-peers { type external; peer-as 17; neighbor 2001:db8:0:four:2a0:a502:0:15da; } } routing-options { router-id 172.16.iv.4; autonomous-system 79; } } Due east { interfaces { lt-0/i/0 { unit of measurement 5 { clarification to-B; encapsulation frame-relay; dlci 6; peer-unit 6; family inet6 { address 2001:db8:0:ii::/64 { eui-64; } } } unit 9 { description to-C; encapsulation frame-relay; dlci 10; peer-unit of measurement 10; family inet6 { address 2001:db8:0:three::/64 { eui-64; } } } unit of measurement 21 { clarification to-D; encapsulation frame-relay; dlci seven; peer-unit of measurement 7; family inet6 { address 2001:db8:0:4::/64 { eui-64; } } } unit 25 { description to-A; encapsulation frame-relay; dlci 1; peer-unit i; family inet6 { address 2001:db8:0:ane::/64 { eui-64; } } } } lo0 { unit 5 { family inet6 { address 2001:db8::5/128; } } } } protocols { bgp { group external-peers { type external; peer-as 22; neighbor 2001:db8:0:i:2a0:a502:0:1da; neighbor 2001:db8:0:ii:2a0:a502:0:6da; neighbor 2001:db8:0:three:2a0:a502:0:ada; neighbour 2001:db8:0:4:2a0:a502:0:7da { peer-as 79; } } } } routing-options { router-id 172.xvi.5.5; democratic-organisation 17; } } If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
- Verifying BGP Neighbors
- Verifying BGP Groups
- Verifying BGP Summary Data
- Checking the Routing Table
Verifying BGP Neighbors
- Purpose
- Action
- Pregnant
Purpose
Verify that BGP is running on configured interfaces and that the BGP session is active for each neighbour address.
Activeness
From operational mode, run the show bgp neighbor command.
user@R1:E> testify bgp neighbor Peer: 2001:db8:0:1:2a0:a502:0:1da+54987 AS 22 Local: 2001:db8:0:i:2a0:a502:0:19da+179 AS 17 Type: External State: Established Flags: <Sync> Last State: OpenConfirm Last Event: RecvKeepAlive Terminal Fault: Open Message Error Options: <Preference PeerAS Refresh> Holdtime: 90 Preference: 170 Number of flaps: 0 Mistake: 'Open up Message Error' Sent: xx Recv: 0 Peer ID: 172.16.1.1 Local ID: 172.sixteen.five.5 Active Holdtime: 90 Keepalive Interval: 30 Peer index: 0 BFD: disabled, down Local Interface: lt-0/1/0.25 NLRI for restart configured on peer: inet6-unicast NLRI advertised by peer: inet6-unicast NLRI for this session: inet6-unicast Peer supports Refresh capability (2) Stale routes from peer are kept for: 300 Peer does not back up Restarter functionality NLRI that restart is negotiated for: inet6-unicast NLRI of received end-of-rib markers: inet6-unicast NLRI of all terminate-of-rib markers sent: inet6-unicast Peer supports four byte As extension (peer-equally 22) Peer does not back up Addpath Table inet6.0 Bit: 10000 RIB State: BGP restart is complete Ship state: in sync Active prefixes: 0 Received prefixes: 0 Accepted prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Last traffic (seconds): Received 7 Sent 18 Checked 81 Input letters: Full 1611 Updates 1 Refreshes 0 Octets 30660 Output letters: Total 1594 Updates 0 Refreshes 0 Octets 30356 Output Queue[0]: 0 Peer: 2001:db8:0:two:2a0:a502:0:6da+179 AS 22 Local: 2001:db8:0:2:2a0:a502:0:5da+55502 AS 17 Blazon: External Land: Established Flags: <Sync> Concluding Land: OpenConfirm Last Event: RecvKeepAlive Concluding Error: Open Message Error Options: <Preference PeerAS Refresh> Holdtime: 90 Preference: 170 Number of flaps: 0 Error: 'Open up Message Fault' Sent: 26 Recv: 0 Peer ID: 172.16.2.2 Local ID: 172.sixteen.five.5 Agile Holdtime: 90 Keepalive Interval: xxx Peer index: 2 BFD: disabled, down Local Interface: lt-0/1/0.five NLRI for restart configured on peer: inet6-unicast NLRI advertised by peer: inet6-unicast NLRI for this session: inet6-unicast Peer supports Refresh adequacy (2) Stale routes from peer are kept for: 300 Peer does not back up Restarter functionality NLRI that restart is negotiated for: inet6-unicast NLRI of received end-of-rib markers: inet6-unicast NLRI of all end-of-rib markers sent: inet6-unicast Peer supports iv byte As extension (peer-equally 22) Peer does non back up Addpath Table inet6.0 Scrap: 10000 RIB Land: BGP restart is complete Ship country: in sync Active prefixes: 0 Received prefixes: 0 Accustomed prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Terminal traffic (seconds): Received 15 Sent eight Checked eight Input messages: Total 1610 Updates 1 Refreshes 0 Octets 30601 Output messages: Full 1645 Updates 0 Refreshes 0 Octets 32417 Output Queue[0]: 0 Peer: 2001:db8:0:3:2a0:a502:0:ada+55983 AS 22 Local: 2001:db8:0:3:2a0:a502:0:9da+179 AS 17 Type: External Land: Established Flags: <Sync> Final State: OpenConfirm Last Event: RecvKeepAlive Last Error: None Options: <Preference PeerAS Refresh> Holdtime: xc Preference: 170 Number of flaps: 0 Peer ID: 172.16.3.3 Local ID: 172.sixteen.5.5 Active Holdtime: 90 Keepalive Interval: 30 Peer index: 3 BFD: disabled, down Local Interface: lt-0/1/0.ix NLRI for restart configured on peer: inet6-unicast NLRI advertised by peer: inet6-unicast NLRI for this session: inet6-unicast Peer supports Refresh capability (2) Stale routes from peer are kept for: 300 Peer does non support Restarter functionality NLRI that restart is negotiated for: inet6-unicast NLRI of received finish-of-rib markers: inet6-unicast NLRI of all end-of-rib markers sent: inet6-unicast Peer supports iv byte Every bit extension (peer-as 22) Peer does not support Addpath Table inet6.0 Bit: 10000 RIB State: BGP restart is complete Send state: in sync Active prefixes: 0 Received prefixes: 0 Accepted prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Last traffic (seconds): Received 21 Sent 21 Checked 67 Input letters: Total 1610 Updates 1 Refreshes 0 Octets 30641 Output messages: Total 1587 Updates 0 Refreshes 0 Octets 30223 Output Queue[0]: 0 Peer: 2001:db8:0:4:2a0:a502:0:7da+49255 AS 79 Local: 2001:db8:0:four:2a0:a502:0:15da+179 AS 17 Type: External State: Established Flags: <Sync> Last State: OpenConfirm Terminal Issue: RecvKeepAlive Terminal Fault: None Options: <Preference PeerAS Refresh> Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 172.16.4.iv Local ID: 172.xvi.5.5 Agile Holdtime: 90 Keepalive Interval: 30 Peer alphabetize: 1 BFD: disabled, down Local Interface: lt-0/i/0.21 NLRI for restart configured on peer: inet6-unicast NLRI advertised by peer: inet6-unicast NLRI for this session: inet6-unicast Peer supports Refresh adequacy (2) Stale routes from peer are kept for: 300 Peer does not support Restarter functionality NLRI that restart is negotiated for: inet6-unicast NLRI of received end-of-rib markers: inet6-unicast NLRI of all end-of-rib markers sent: inet6-unicast Peer supports four byte Every bit extension (peer-as 79) Peer does not support Addpath Table inet6.0 Bit: 10000 RIB State: BGP restart is complete Send state: in sync Active prefixes: 0 Received prefixes: 0 Accepted prefixes: 0 Suppressed due to damping: 0 Advertised prefixes: 0 Last traffic (seconds): Received 6 Sent 17 Checked 25 Input letters: Total 1615 Updates one Refreshes 0 Octets 30736 Output letters: Total 1593 Updates 0 Refreshes 0 Octets 30337 Output Queue[0]: 0
Meaning
IPv6 unicast network layer reachability information (NLRI) is beingness exchanged betwixt the neighbors.
Verifying BGP Groups
- Purpose
- Action
- Meaning
Purpose
Verify that the BGP groups are configured correctly.
Action
From operational mode, run the prove bgp group command.
user@R1:Due east> show bgp grouping Group Type: External Local AS: 17 Name: external-peers Index: 0 Flags: <> Holdtime: 0 Total peers: 4 Established: four 2001:db8:0:1:2a0:a502:0:1da+54987 2001:db8:0:2:2a0:a502:0:6da+179 2001:db8:0:3:2a0:a502:0:ada+55983 2001:db8:0:4:2a0:a502:0:7da+49255 inet6.0: 0/0/0/0 Groups: i Peers: 4 External: four Internal: 0 Down peers: 0 Flaps: 0 Table Tot Paths Human activity Paths Suppressed History Clammy State Pending inet6.0 0 0 0 0 0 0 inet6.2 0 0 0 0 0 0
Meaning
The group type is external, and the group has iv peers.
Verifying BGP Summary Information
- Purpose
- Action
- Meaning
Purpose
Verify that the BGP peer relationships are established.
Action
From operational mode, run the show bgp summary control.
user@R1:E> show bgp summary Groups: i Peers: four Downwardly peers: 0 Table Tot Paths Act Paths Suppressed History Clammy Land Pending inet6.0 0 0 0 0 0 0 inet6.2 0 0 0 0 0 0 Peer Every bit InPkt OutPkt OutQ Flaps Last Upward/Dwn State|#Active/Received/Accustomed/Damped... 2001:db8:0:1:2a0:a502:0:1da 22 1617 1600 0 0 12:07:00 Establ inet6.0: 0/0/0/0 2001:db8:0:2:2a0:a502:0:6da 22 1616 1651 0 0 12:06:56 Establ inet6.0: 0/0/0/0 2001:db8:0:three:2a0:a502:0:ada 22 1617 1594 0 0 12:04:32 Establ inet6.0: 0/0/0/0 2001:db8:0:4:2a0:a502:0:7da 79 1621 1599 0 0 12:07:00 Establ inet6.0: 0/0/0/0
Meaning
The Down peers: 0 output shows that the BGP peers are in the established state.
Checking the Routing Table
- Purpose
- Action
- Significant
Purpose
Verify that the inet6.0 routing table is populated with local and direct routes.
Action
From operational mode, run the show route command.
user@R1:E> evidence route inet6.0: xv destinations, 18 routes (xv active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 2001:db8::v/128 *[Straight/0] 12:41:18 > via lo0.5 2001:db8:0:ane::/64 *[Straight/0] 14:twoscore:01 > via lt-0/1/0.25 2001:db8:0:1:2a0:a502:0:19da/128 *[Local/0] fourteen:twoscore:01 Local via lt-0/1/0.25 2001:db8:0:2::/64 *[Directly/0] xiv:40:02 > via lt-0/i/0.v 2001:db8:0:ii:2a0:a502:0:5da/128 *[Local/0] 14:40:02 Local via lt-0/1/0.5 2001:db8:0:iii::/64 *[Directly/0] 14:40:02 > via lt-0/1/0.nine 2001:db8:0:three:2a0:a502:0:9da/128 *[Local/0] 14:40:02 Local via lt-0/1/0.9 2001:db8:0:4::/64 *[Direct/0] 14:40:01 > via lt-0/1/0.21 2001:db8:0:4:2a0:a502:0:15da/128 *[Local/0] 14:40:01 Local via lt-0/1/0.21 fe80::/64 *[Directly/0] 14:40:02 > via lt-0/1/0.five [Direct/0] 14:40:02 > via lt-0/1/0.9 [Directly/0] xiv:40:01 > via lt-0/ane/0.21 [Directly/0] 14:40:01 > via lt-0/i/0.25 fe80::2a0:a502:0:5da/128 *[Local/0] 14:xl:02 Local via lt-0/ane/0.v fe80::2a0:a502:0:9da/128 *[Local/0] xiv:xl:02 Local via lt-0/1/0.9 fe80::2a0:a502:0:15da/128 *[Local/0] 14:40:01 Local via lt-0/1/0.21 fe80::2a0:a502:0:19da/128 *[Local/0] fourteen:40:01 Local via lt-0/1/0.25 fe80::2a0:a50f:fc56:1da/128 *[Direct/0] 12:41:18 > via lo0.five
Meaning
The inet6.0 routing table contains local and straight routes. To populate the routing table with other types of routes, you must configure routing policies.
Understanding Internal BGP Peering Sessions
When two BGP-enabled devices are in the aforementioned autonomous arrangement (AS), the BGP session is called an internal BGP session, or IBGP session. BGP uses the same message types on IBGP and external BGP (EBGP) sessions, merely the rules for when to send each message and how to interpret each message differ slightly. For this reason, some people refer to IBGP and EBGP equally 2 separate protocols.
Figure 4: Internal and External BGP 
In Figure 4, Device Jackson, Device Memphis, and Device Biloxi have IBGP peer sessions with each other. Likewise, Device Miami and Device Atlanta have IBGP peer sessions betwixt each other.
The purpose of IBGP is to provide a means by which EBGP route advertisements tin be forwarded throughout the network. In theory, to attain this job y'all could redistribute all of your EBGP routes into an interior gateway protocol (IGP), such as OSPF or IS-IS. This, nevertheless, is not recommended in a production environs considering of the big number of EBGP routes in the Cyberspace and considering of the way that IGPs operate. In short, with that many routes the IGP churns or crashes.
Generally, the loopback interface (lo0) is used to establish connections between IBGP peers. The loopback interface is e'er up as long as the device is operating. If at that place is a route to the loopback accost, the IBGP peering session stays up. If a physical interface address is used instead and that interface goes up and down, the IBGP peering session also goes up and downwardly. Thus the loopback interface provides fault tolerance in case the physical interface or the link goes down, if the device has link redundancy.
While IBGP neighbors exercise not need to be straight connected, they do demand to be fully meshed. In this case, fully meshed means that each device is logically continued to every other device through neighbor peer relationships. The neighbor statement creates the mesh. Considering of the full mesh requirement of IBGP, you must configure private peering sessions between all IBGP devices in the Equally. The full mesh demand not be physical links. Rather, the configuration on each routing device must create a full mesh of peer sessions (using multiple neighbor statements).
Annotation:
The requirement for a full mesh is waived if you configure a confederation or route reflection.
To sympathize the full-mesh requirement, consider that an IBGP-learned route cannot exist readvertised to another IBGP peer. The reason for preventing the readvertisement of IBGP routes and requiring the total mesh is to avert routing loops within an As. The Every bit path attribute is the means by which BGP routing devices avoid loops. The path information is examined for the local As number but when the route is received from an EBGP peer. Because the aspect is only modified across Every bit boundaries, this system works well. Withal, the fact that the attribute is only modified across As boundaries presents an event inside the AS. For case, suppose that routing devices A, B, and C are all in the aforementioned Equally. Device A receives a route from an EBGP peer and sends the route to Device B, which installs it as the active route. The route is then sent to Device C, which installs information technology locally and sends information technology back to Device A. If Device A installs the route, a loop is formed within the AS. The routing devices are not able to observe the loop considering the AS path aspect is non modified during these advertisements. Therefore, the BGP protocol designers decided that the only assurance of never forming a routing loop was to preclude an IBGP peer from advert an IBGP-learned route within the AS. For route reachability, the IBGP peers are fully meshed.
IBGP supports multihop connections, then IBGP neighbors can be located anywhere within the Equally and often do not share a link. A recursive route lookup resolves the loopback peering accost to an IP forwarding adjacent hop. The lookup service is provided by static routes or an IGP such as OSPF, or BGP routes.
Example: Configuring Internal BGP Peer Sessions
This example shows how to configure internal BGP peer sessions.
- Requirements
- Overview
- Configuration
- Verification
Requirements
No special configuration beyond device initialization is required before you lot configure this example.
Overview
In this example, y'all configure internal BGP (IBGP) peer sessions. The loopback interface (lo0) is used to establish connections between IBGP peers. The loopback interface is always upwards every bit long as the device is operating. If there is a route to the loopback address, the IBGP peer session stays up. If a physical interface address is used instead and that interface goes up and down, the IBGP peer session besides goes up and down. Thus, if the device has link back-up, the loopback interface provides fault tolerance in instance the physical interface or 1 of the links goes downward.
When a device peers with a remote device's loopback interface accost, the local device expects BGP update messages to come from (exist sourced by) the remote device'due south loopback interface accost. The local-address statement enables you to specify the source information in BGP update letters. If you omit the local-address statement, the expected source of BGP update messages is based on the device's source accost pick rules, which normally results in the egress interface accost being the expected source of update messages. When this happens, the peer session is not established considering a mismatch exists between the expected source address (the egress interface of the peer) and the actual source (the loopback interface of the peer). To make sure that the expected source address matches the bodily source accost, specify the loopback interface address in the local-accost statement.
Because IBGP supports multihop connections, IBGP neighbors can be located anywhere inside the autonomous system (As) and oft practise non share a link. A recursive road lookup resolves the loopback peer address to an IP forwarding next hop. In this case, this service is provided past OSPF. Although interior gateway protocol (IGP) neighbors do non need to be direct continued, they do need to be fully meshed. In this case, fully meshed ways that each device is logically connected to every other device through neighbour peer relationships. The neighbor statement creates the mesh.
Notation:
The requirement for a full mesh is waived if you lot configure a confederation or route reflection.
Later the BGP peers are established, local routes are not automatically advertised by the BGP peers. At each BGP-enabled device, policy configuration is required to consign the local, static, or IGP-learned routes into the BGP routing information base (RIB) and then advertise them every bit BGP routes to the other peers. BGP'southward advertisement policy, past default, does not annunciate any non-BGP routes (such as local routes) to peers.
In the sample network, the devices in As 17 are fully meshed in the group internal-peers. The devices have loopback addresses 192.168.6.v, 192.163.6.4, and 192.168.twoscore.4.
Effigy 5 shows a typical network with internal peer sessions.
Figure v: Typical Network with IBGP Sessions 
Configuration
- CLI Quick Configuration
- Configuring Device A
- Configuring Device B
- Configuring Device C
CLI Quick Configuration
To apace configure this example, copy the following commands, paste them into a text file, remove any line breaks, change whatsoever details necessary to match your network configuration, and and so copy and paste the commands into the CLI at the [edit] hierarchy level.
Device A
set interfaces ge-0/one/0 unit of measurement 1 clarification to-B prepare interfaces ge-0/1/0 unit i family inet address x.ten.ten.one/thirty set interfaces lo0 unit 1 family unit inet address 192.168.six.5/32 set protocols bgp group internal-peers type internal set up protocols bgp group internal-peers description "connections to B and C" set protocols bgp group internal-peers local-address 192.168.6.5 set up protocols bgp group internal-peers export transport-direct gear up protocols bgp grouping internal-peers neighbor 192.163.6.iv set protocols bgp group internal-peers neighbour 192.168.40.four set protocols ospf area 0.0.0.0 interface lo0.1 passive set up protocols ospf area 0.0.0.0 interface ge-0/i/0.1 set up policy-options policy-statement transport-direct term 2 from protocol direct set policy-options policy-statement send-direct term 2 then accept set routing-options router-id 192.168.half dozen.5 fix routing-options autonomous-system 17
Device B
ready interfaces ge-0/1/0 unit 2 clarification to-A ready interfaces ge-0/1/0 unit 2 family unit inet address ten.10.10.two/xxx set interfaces ge-0/1/i unit v clarification to-C set interfaces ge-0/1/ane unit v family unit inet address 10.10.10.five/30 set interfaces lo0 unit 2 family inet accost 192.163.6.4/32 prepare protocols bgp grouping internal-peers blazon internal set protocols bgp grouping internal-peers clarification "connections to A and C" prepare protocols bgp group internal-peers local-address 192.163.half dozen.iv set protocols bgp grouping internal-peers export ship-directly set protocols bgp grouping internal-peers neighbor 192.168.40.4 ready protocols bgp grouping internal-peers neighbor 192.168.half-dozen.5 set up protocols ospf area 0.0.0.0 interface lo0.2 passive gear up protocols ospf area 0.0.0.0 interface ge-0/1/0.2 set protocols ospf area 0.0.0.0 interface ge-0/1/ane.five set policy-options policy-statement send-direct term 2 from protocol direct prepare policy-options policy-statement send-direct term 2 and then accept set routing-options router-id 192.163.6.4 set routing-options autonomous-system 17
Device C
ready interfaces ge-0/1/0 unit half dozen description to-B set interfaces ge-0/1/0 unit half-dozen family inet address 10.10.ten.6/30 set interfaces lo0 unit 3 family unit inet address 192.168.40.4/32 set protocols bgp group internal-peers type internal set protocols bgp grouping internal-peers description "connections to A and B" set protocols bgp group internal-peers local-address 192.168.40.4 ready protocols bgp grouping internal-peers export send-directly fix protocols bgp group internal-peers neighbor 192.163.6.4 set protocols bgp group internal-peers neighbor 192.168.6.v fix protocols ospf area 0.0.0.0 interface lo0.three passive gear up protocols ospf area 0.0.0.0 interface ge-0/i/0.6 set policy-options policy-statement send-direct term ii from protocol direct set policy-options policy-argument ship-straight term 2 and then accept set routing-options router-id 192.168.xl.iv set routing-options autonomous-arrangement 17
Configuring Device A
- Step-by-Step Procedure
- Results
Step-by-Step Procedure
The post-obit example requires y'all to navigate diverse levels in the configuration bureaucracy. For information nigh navigating the CLI, see Using the CLI Editor in Configuration Way in the Junos Os CLI User Guide.
To configure internal BGP peer sessions on Device A:
-
Configure the interfaces.
[edit interfaces ge-0/1/0 unit 1] user@A# gear up description to-B user@A# set family inet accost 10.10.10.1/30 [edit interfaces] user@A# set lo0 unit 1 family inet address 192.168.six.v/32
-
Configure BGP.
The
neighborstatements are included for both Device B and Device C, fifty-fifty though Device A is non directly connected to Device C.[edit protocols bgp group internal-peers] user@A# set blazon internal user@A# set description "connections to B and C" user@A# set local-address 192.168.6.5 user@A# fix export send-direct user@A# set neighbor 192.163.6.four user@A# gear up neighbor 192.168.40.iv
-
Configure OSPF.
[edit protocols ospf expanse 0.0.0.0] user@A# set up interface lo0.ane passive user@A# prepare interface ge-0/1/0.1
-
Configure a policy that accepts direct routes.
Other useful options for this scenario might exist to have routes learned through OSPF or local routes.
[edit policy-options policy-statement send-direct term 2] user@A# set from protocol direct user@A# fix and then take
-
Configure the router ID and the Equally number.
[edit routing-options] user@A# set router-id 192.168.6.five user@A# set autonomous-arrangement 17
Results
From configuration fashion, ostend your configuration by entering the testify interfaces, show policy-options, prove protocols, and testify routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
user@A# show interfaces ge-0/i/0 { unit 1 { clarification to-B; family inet { address 10.10.x.ane/30; } } } lo0 { unit of measurement 1 { family unit inet { address 192.168.six.5/32; } } } user@A# show policy-options policy-statement transport-straight { term two { from protocol straight; and so accept; } } user@A# show protocols bgp { group internal-peers { type internal; clarification "connections to B and C"; local-accost 192.168.6.5; export send-straight; neighbour 192.163.six.4; neighbor 192.168.40.4; } } ospf { area 0.0.0.0 { interface lo0.1 { passive; } interface ge-0/1/0.one; } } user@A# show routing-options router-id 192.168.6.5; autonomous-arrangement 17;
If you are done configuring the device, enter commit from configuration mode.
Configuring Device B
- Step-past-Stride Procedure
- Results
Step-by-Step Procedure
The following example requires that you navigate diverse levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Manner.
To configure internal BGP peer sessions on Device B:
-
Configure the interfaces.
[edit interfaces ge-0/1/0 unit ii] user@B# set up description to-A user@B# gear up family unit inet accost 10.10.x.2/30 [edit interfaces ge-0/1/ane] user@B# ready unit 5 description to-C user@B# set unit 5 family inet address x.10.x.5/30 [edit interfaces] user@B# set lo0 unit 2 family unit inet address 192.163.6.4/32
-
Configure BGP.
The
neighborstatements are included for both Device B and Device C, even though Device A is not direct continued to Device C.[edit protocols bgp group internal-peers] user@B# set blazon internal user@B# set description "connections to A and C" user@B# set local-address 192.163.vi.4 user@B# set consign send-direct user@B# set up neighbour 192.168.40.4 user@B# set neighbor 192.168.6.5
-
Configure OSPF.
[edit protocols ospf area 0.0.0.0] user@B# set interface lo0.2 passive user@B# set interface ge-0/1/0.2 user@B# set interface ge-0/1/1.five
-
Configure a policy that accepts direct routes.
Other useful options for this scenario might be to accept routes learned through OSPF or local routes.
[edit policy-options policy-argument ship-direct term ii] user@B# set from protocol direct user@B# set then accept
-
Configure the router ID and the Every bit number.
[edit routing-options] user@B# gear up router-id 192.163.6.4 user@B# set autonomous-system 17
Results
From configuration mode, ostend your configuration by entering the show interfaces, show policy-options, show protocols, and show routing-options commands. If the output does not display the intended configuration, echo the instructions in this instance to correct the configuration.
user@B# bear witness interfaces ge-0/1/0 { unit 2 { clarification to-A; family inet { address x.ten.10.ii/thirty; } } } ge-0/1/1 { unit 5 { description to-C; family inet { accost 10.10.x.v/30; } } } lo0 { unit 2 { family inet { address 192.163.vi.four/32; } } } user@B# testify policy-options policy-argument send-direct { term ii { from protocol directly; and then accept; } } user@B# evidence protocols bgp { group internal-peers { blazon internal; clarification "connections to A and C"; local-address 192.163.6.4; export send-direct; neighbor 192.168.40.4; neighbor 192.168.half-dozen.five; } } ospf { expanse 0.0.0.0 { interface lo0.2 { passive; } interface ge-0/1/0.2; interface ge-0/1/ane.5; } } user@B# evidence routing-options router-id 192.163.6.4; democratic-system 17;
If you are washed configuring the device, enter commit from configuration style.
Configuring Device C
- Pace-by-Step Procedure
- Results
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information almost navigating the CLI, see Using the CLI Editor in Configuration Mode in the Junos Os CLI User Guide.
To configure internal BGP peer sessions on Device C:
-
Configure the interfaces.
[edit interfaces ge-0/one/0 unit 6] user@C# set clarification to-B user@C# gear up family inet accost 10.10.10.6/thirty [edit interfaces] user@C# set lo0 unit 3 family inet address 192.168.40.4/32
-
Configure BGP.
The
neighborstatements are included for both Device B and Device C, even though Device A is not directly continued to Device C.[edit protocols bgp group internal-peers] user@C# gear up type internal user@C# prepare clarification "connections to A and B" user@C# set local-address 192.168.40.4 user@C# ready consign send-straight user@C# set neighbour 192.163.6.iv user@C# set up neighbor 192.168.six.5
-
Configure OSPF.
[edit protocols ospf surface area 0.0.0.0] user@C# set interface lo0.three passive user@C# prepare interface ge-0/1/0.six
-
Configure a policy that accepts direct routes.
Other useful options for this scenario might be to accept routes learned through OSPF or local routes.
[edit policy-options policy-statement send-straight term ii] user@C# gear up from protocol direct user@C# set up and so accept
-
Configure the router ID and the Equally number.
[edit routing-options] user@C# set router-id 192.168.40.4 user@C# gear up democratic-system 17
Results
From configuration style, confirm your configuration by entering the show interfaces, show policy-options, show protocols, and prove routing-options commands. If the output does not brandish the intended configuration, repeat the instructions in this example to correct the configuration.
user@C# show interfaces ge-0/ane/0 { unit 6 { description to-B; family inet { address 10.x.10.vi/thirty; } } } lo0 { unit 3 { family unit inet { address 192.168.forty.four/32; } } } user@C# show policy-options policy-statement send-straight { term 2 { from protocol direct; and so accept; } } user@C# show protocols bgp { group internal-peers { type internal; description "connections to A and B"; local-address 192.168.40.4; consign send-direct; neighbour 192.163.6.iv; neighbour 192.168.half dozen.v; } } ospf { expanse 0.0.0.0 { interface lo0.3 { passive; } interface ge-0/1/0.6; } } user@C# prove routing-options router-id 192.168.40.4; autonomous-organisation 17;
If you are done configuring the device, enter commit from configuration manner.
Verification
Confirm that the configuration is working properly.
- Verifying BGP Neighbors
- Verifying BGP Groups
- Verifying BGP Summary Information
- Verifying That BGP Routes Are Installed in the Routing Table
Verifying BGP Neighbors
- Purpose
- Action
Purpose
Verify that BGP is running on configured interfaces and that the BGP session is active for each neighbor address.
Action
From operational fashion, enter the evidence bgp neighbor command.
user@A> show bgp neighbor Peer: 192.163.6.4+179 Equally 17 Local: 192.168.six.5+58852 AS 17 Type: Internal State: Established Flags: Sync Concluding Country: OpenConfirm Last Event: RecvKeepAlive Last Error: None Export: [ transport-direct ] Options: Preference LocalAddress Refresh Local Address: 192.168.6.5 Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 192.163.vi.four Local ID: 192.168.vi.5 Active Holdtime: xc Keepalive Interval: 30 Peer alphabetize: 0 BFD: disabled, down NLRI for restart configured on peer: inet-unicast NLRI advertised by peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh adequacy (2) Restart time configured on the peer: 120 Dried routes from peer are kept for: 300 Restart time requested by this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received terminate-of-rib markers: inet-unicast NLRI of all end-of-rib markers sent: inet-unicast Peer supports iv byte AS extension (peer-as 17) Peer does non back up Addpath Table inet.0 Bit: 10000 RIB State: BGP restart is consummate Send state: in sync Active prefixes: 0 Received prefixes: 3 Accepted prefixes: iii Suppressed due to damping: 0 Advertised prefixes: 2 Last traffic (seconds): Received 25 Sent 19 Checked 67 Input letters: Total 2420 Updates iv Refreshes 0 Octets 46055 Output messages: Full 2411 Updates two Refreshes 0 Octets 45921 Output Queue[0]: 0 Peer: 192.168.forty.4+179 Every bit 17 Local: 192.168.half-dozen.five+56466 AS 17 Type: Internal Country: Established Flags: Sync Terminal State: OpenConfirm Last Event: RecvKeepAlive Final Error: None Export: [ send-direct ] Options: Preference LocalAddress Refresh Local Address: 192.168.6.5 Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 192.168.twoscore.4 Local ID: 192.168.6.5 Active Holdtime: ninety Keepalive Interval: xxx Peer index: 1 BFD: disabled, downward NLRI for restart configured on peer: inet-unicast NLRI advertised by peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh adequacy (two) Restart time configured on the peer: 120 Stale routes from peer are kept for: 300 Restart fourth dimension requested by this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received end-of-rib markers: inet-unicast NLRI of all end-of-rib markers sent: inet-unicast Peer supports 4 byte AS extension (peer-as 17) Peer does non support Addpath Table inet.0 Flake: 10000 RIB Land: BGP restart is complete Transport state: in sync Active prefixes: 0 Received prefixes: 2 Accepted prefixes: 2 Suppressed due to damping: 0 Advertised prefixes: 2 Concluding traffic (seconds): Received 7 Sent 21 Checked 24 Input messages: Full 2412 Updates two Refreshes 0 Octets 45867 Output messages: Full 2409 Updates 2 Refreshes 0 Octets 45883 Output Queue[0]: 0
Verifying BGP Groups
- Purpose
- Action
Purpose
Verify that the BGP groups are configured correctly.
Action
From operational mode, enter the show bgp group command.
user@A> prove bgp group Group Type: Internal As: 17 Local AS: 17 Proper noun: internal-peers Index: 0 Flags: <Export Eval> Export: [ send-direct ] Holdtime: 0 Total peers: 2 Established: 2 192.163.6.4+179 192.168.40.4+179 inet.0: 0/v/five/0 Groups: 1 Peers: 2 External: 0 Internal: two Downward peers: 0 Flaps: 0 Table Tot Paths Act Paths Suppressed History Clammy State Pending inet.0 5 0 0 0 0 0
Verifying BGP Summary Information
- Purpose
- Activity
Purpose
Verify that the BGP configuration is right.
Activeness
From operational way, enter the show bgp summary command.
user@A> show bgp summary Groups: one Peers: 2 Downwardly peers: 0 Table Tot Paths Human activity Paths Suppressed History Damp Land Pending inet.0 5 0 0 0 0 0 Peer As InPkt OutPkt OutQ Flaps Last Up/Dwn Country|#Active/Received/Accepted/Damped... 192.163.six.iv 17 2441 2432 0 0 xviii:18:52 0/3/3/0 0/0/0/0 192.168.xl.four 17 2432 2430 0 0 18:18:48 0/two/two/0 0/0/0/0
Verifying That BGP Routes Are Installed in the Routing Table
- Purpose
- Action
Purpose
Verify that the consign policy configuration is causing the BGP routes to exist installed in the routing tables of the peers.
Activity
From operational fashion, enter the show route protocol bgp command.
user@A> bear witness route protocol bgp inet.0: 7 destinations, 12 routes (seven active, 0 holddown, 0 hidden) + = Active Road, - = Last Active, * = Both 10.x.10.0/30 [BGP/170] 07:09:57, localpref 100, from 192.163.vi.4 Every bit path: I > to 10.10.ten.2 via ge-0/i/0.1 ten.10.10.4/30 [BGP/170] 07:09:57, localpref 100, from 192.163.6.four Every bit path: I > to 10.10.x.2 via ge-0/1/0.1 [BGP/170] 07:07:12, localpref 100, from 192.168.40.four Equally path: I > to 10.10.10.two via ge-0/1/0.1 192.163.half-dozen.4/32 [BGP/170] 07:09:57, localpref 100, from 192.163.half-dozen.4 Equally path: I > to 10.ten.10.2 via ge-0/1/0.ane 192.168.40.iv/32 [BGP/170] 07:07:12, localpref 100, from 192.168.forty.four AS path: I > to x.x.10.2 via ge-0/1/0.1
Example: Configuring Internal BGP Peering Sessions on Logical Systems
This example shows how to configure internal BGP peer sessions on logical systems.
- Requirements
- Overview
- Configuration
- Verification
Requirements
In this example, no special configuration beyond device initialization is required.
Overview
In this example, yous configure internal BGP (IBGP) peering sessions.
In the sample network, the devices in AS 17 are fully meshed in the grouping internal-peers. The devices have loopback addresses 192.168.half dozen.5, 192.163.half-dozen.four, and 192.168.40.4.
Effigy six shows a typical network with internal peer sessions.
Effigy 6: Typical Network with IBGP Sessions 
Configuration
- CLI Quick Configuration
- Device A
CLI Quick Configuration
To quickly configure this example, re-create the post-obit commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.
fix logical-systems A interfaces lt-0/1/0 unit of measurement 1 description to-B gear up logical-systems A interfaces lt-0/1/0 unit of measurement 1 encapsulation ethernet prepare logical-systems A interfaces lt-0/ane/0 unit 1 peer-unit 2 gear up logical-systems A interfaces lt-0/1/0 unit ane family unit inet address 10.10.10.1/30 ready logical-systems A interfaces lo0 unit 1 family inet address 192.168.6.v/32 set up logical-systems A protocols bgp grouping internal-peers blazon internal gear up logical-systems A protocols bgp group internal-peers local-address 192.168.vi.five set logical-systems A protocols bgp group internal-peers export send-direct set logical-systems A protocols bgp group internal-peers neighbor 192.163.6.4 set logical-systems A protocols bgp group internal-peers neighbour 192.168.forty.iv set logical-systems A protocols ospf area 0.0.0.0 interface lo0.one passive set logical-systems A protocols ospf surface area 0.0.0.0 interface lt-0/1/0.ane set logical-systems A policy-options policy-statement send-direct term 2 from protocol directly set logical-systems A policy-options policy-argument ship-directly term two then take prepare logical-systems A routing-options router-id 192.168.6.5 prepare logical-systems A routing-options autonomous-system 17 fix logical-systems B interfaces lt-0/i/0 unit 2 clarification to-A gear up logical-systems B interfaces lt-0/ane/0 unit 2 encapsulation ethernet fix logical-systems B interfaces lt-0/ane/0 unit ii peer-unit of measurement i set up logical-systems B interfaces lt-0/1/0 unit 2 family inet address ten.ten.x.2/30 set logical-systems B interfaces lt-0/1/0 unit of measurement 5 description to-C set logical-systems B interfaces lt-0/1/0 unit of measurement v encapsulation ethernet gear up logical-systems B interfaces lt-0/1/0 unit of measurement 5 peer-unit 6 set logical-systems B interfaces lt-0/ane/0 unit 5 family inet address ten.10.x.5/30 fix logical-systems B interfaces lo0 unit two family inet address 192.163.6.4/32 ready logical-systems B protocols bgp group internal-peers type internal set logical-systems B protocols bgp grouping internal-peers local-address 192.163.6.4 set logical-systems B protocols bgp group internal-peers export transport-direct gear up logical-systems B protocols bgp group internal-peers neighbor 192.168.twoscore.four set logical-systems B protocols bgp group internal-peers neighbor 192.168.half-dozen.5 set logical-systems B protocols ospf area 0.0.0.0 interface lo0.2 passive set logical-systems B protocols ospf area 0.0.0.0 interface lt-0/1/0.2 set logical-systems B protocols ospf area 0.0.0.0 interface lt-0/one/0.5 set logical-systems B policy-options policy-argument send-directly term ii from protocol direct prepare logical-systems B policy-options policy-argument send-direct term 2 and so accept set logical-systems B routing-options router-id 192.163.6.iv set logical-systems B routing-options autonomous-system 17 fix logical-systems C interfaces lt-0/1/0 unit 6 description to-B set logical-systems C interfaces lt-0/i/0 unit of measurement 6 encapsulation ethernet set up logical-systems C interfaces lt-0/1/0 unit vi peer-unit five set logical-systems C interfaces lt-0/1/0 unit 6 family inet accost 10.10.10.6/30 set logical-systems C interfaces lo0 unit 3 family inet accost 192.168.40.4/32 set logical-systems C protocols bgp group internal-peers blazon internal set logical-systems C protocols bgp grouping internal-peers local-accost 192.168.twoscore.4 set logical-systems C protocols bgp group internal-peers export send-direct fix logical-systems C protocols bgp grouping internal-peers neighbour 192.163.six.iv fix logical-systems C protocols bgp grouping internal-peers neighbor 192.168.6.5 ready logical-systems C protocols ospf area 0.0.0.0 interface lo0.3 passive prepare logical-systems C protocols ospf area 0.0.0.0 interface lt-0/1/0.6 set up logical-systems C policy-options policy-statement send-direct term 2 from protocol direct set logical-systems C policy-options policy-statement send-straight term two so accept gear up logical-systems C routing-options router-id 192.168.xl.iv prepare logical-systems C routing-options autonomous-system 17
Device A
- Step-by-Pace Procedure
- Results
Step-by-Stride Process
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.
To configure internal BGP peer sessions on Device A:
-
Configure the interfaces.
[edit logical-systems A interfaces lt-0/ane/0 unit 1] user@R1# set description to-B user@R1# prepare encapsulation ethernet user@R1# gear up peer-unit ii user@R1# fix family inet address ten.10.10.1/xxx user@R1# set family unit inet address 192.168.6.5/32 user@R1# upward user@R1# upwardly [edit logical-systems A interfaces] user@R1# set lo0 unit one family inet address 192.168.half dozen.5/32 user@R1# leave [edit] user@R1# edit logical-systems B interfaces lt-0/1/0 [edit logical-systems B interfaces lt-0/one/0] user@R1# set unit 2 description to-A user@R1# set unit of measurement 2 encapsulation ethernet user@R1# set unit 2 peer-unit 1 user@R1# gear up unit of measurement 2 family unit inet address x.x.x.ii/30 user@R1# set unit 5 description to-C user@R1# set unit 5 encapsulation ethernet user@R1# set unit 5 peer-unit half dozen user@R1# set family inet address 10.10.x.5/30 user@R1# upwardly [edit logical-systems B interfaces] user@R1# set lo0 unit ii family inet accost 192.163.6.4/32 user@R1# exit [edit] user@R1# edit logical-systems C interfaces lt-0/1/0 unit of measurement 6 [edit logical-systems C interfaces lt-0/1/0 unit of measurement half dozen] set description to-B ready encapsulation ethernet ready peer-unit 5 set family unit inet accost 10.10.10.vi/30 user@R1# up user@R1# upwardly [edit logical-systems C interfaces] gear up lo0 unit of measurement 3 family inet accost 192.168.twoscore.four/32
-
Configure BGP.
On Logical Organization A, the
neighborstatements are included for both Device B and Device C, even though Logical System A is not directly connected to Device C.[edit logical-systems A protocols bgp group internal-peers] user@R1# set type internal user@R1# fix local-address 192.168.half dozen.5 user@R1# ready export send-direct user@R1# set neighbor 192.163.vi.4 user@R1# set neighbor 192.168.40.4 [edit logical-systems B protocols bgp grouping internal-peers] user@R1# ready blazon internal user@R1# set local-address 192.163.half dozen.4 user@R1# ready export send-direct user@R1# set neighbor 192.168.twoscore.4 user@R1# set neighbor 192.168.six.5 [edit logical-systems C protocols bgp group internal-peers] user@R1# ready type internal user@R1# set local-address 192.168.forty.4 user@R1# set export ship-direct user@R1# prepare neighbor 192.163.six.4 user@R1# gear up neighbor 192.168.6.5
-
Configure OSPF.
[edit logical-systems A protocols ospf area 0.0.0.0] user@R1# set interface lo0.1 passive user@R1# set interface lt-0/1/0.ane [edit logical-systems A protocols ospf area 0.0.0.0] user@R1# set interface lo0.2 passive user@R1# fix interface lt-0/one/0.2 user@R1# fix interface lt-0/1/0.five [edit logical-systems A protocols ospf expanse 0.0.0.0] user@R1# fix interface lo0.iii passive user@R1# set interface lt-0/ane/0.6
-
Configure a policy that accepts direct routes.
Other useful options for this scenario might be to have routes learned through OSPF or local routes.
[edit logical-systems A policy-options policy-statement ship-direct term two] user@R1# set from protocol directly user@R1# ready then take [edit logical-systems B policy-options policy-statement ship-straight term 2] user@R1# set from protocol direct user@R1# gear up then accept [edit logical-systems C policy-options policy-statement ship-straight term ii] user@R1# set from protocol direct user@R1# fix and then have
-
Configure the router ID and the democratic system (AS) number.
[edit logical-systems A routing-options] user@R1# set router-id 192.168.6.5 user@R1# set democratic-system 17 [edit logical-systems B routing-options] user@R1# set router-id 192.163.6.iv user@R1# set autonomous-system 17 [edit logical-systems C routing-options] user@R1# set router-id 192.168.40.4 user@R1# set democratic-system 17
Results
From configuration mode, ostend your configuration past entering the bear witness logical-systems command. If the output does non display the intended configuration, repeat the configuration instructions in this example to correct it.
user@R1# testify logical-systems A { interfaces { lt-0/1/0 { unit i { clarification to-B; encapsulation ethernet; peer-unit 2; family inet { address ten.10.10.1/30; } } } lo0 { unit 1 { family inet { address 192.168.6.5/32; } } } } protocols { bgp { group internal-peers { type internal; local-accost 192.168.6.5; consign send-straight; neighbour 192.163.6.iv; neighbor 192.168.forty.4; } } ospf { area 0.0.0.0 { interface lo0.ane { passive; } interface lt-0/1/0.1; } } } policy-options { policy-statement send-direct { term two { from protocol directly; then accept; } } } routing-options { router-id 192.168.6.5; democratic-system 17; } } B { interfaces { lt-0/1/0 { unit ii { description to-A; encapsulation ethernet; peer-unit 1; family inet { accost 10.x.ten.2/30; } } unit of measurement 5 { description to-C; encapsulation ethernet; peer-unit vi; family inet { address 10.10.ten.five/30; } } } lo0 { unit 2 { family inet { address 192.163.6.4/32; } } } } protocols { bgp { group internal-peers { blazon internal; local-address 192.163.half dozen.4; export send-directly; neighbor 192.168.twoscore.four; neighbor 192.168.vi.5; } } ospf { expanse 0.0.0.0 { interface lo0.2 { passive; } interface lt-0/1/0.2; interface lt-0/1/0.v; } } } policy-options { policy-argument send-direct { term 2 { from protocol directly; and so accept; } } } routing-options { router-id 192.163.half-dozen.4; autonomous-system 17; } } C { interfaces { lt-0/1/0 { unit 6 { clarification to-B; encapsulation ethernet; peer-unit of measurement 5; family inet { address 10.10.x.6/xxx; } } } lo0 { unit 3 { family inet { accost 192.168.40.four/32; } } } } protocols { bgp { group internal-peers { type internal; local-address 192.168.40.4; export send-directly; neighbor 192.163.6.4; neighbor 192.168.6.five; } } ospf { area 0.0.0.0 { interface lo0.3 { passive; } interface lt-0/1/0.6; } } } policy-options { policy-statement send-directly { term ii { from protocol directly; so accept; } } } routing-options { router-id 192.168.forty.4; democratic-system 17; } } If you lot are done configuring the device, enter commit from configuration style.
Verification
Ostend that the configuration is working properly.
- Verifying BGP Neighbors
- Verifying BGP Groups
- Verifying BGP Summary Information
- Verifying That BGP Routes Are Installed in the Routing Table
Verifying BGP Neighbors
- Purpose
- Action
Purpose
Verify that BGP is running on configured interfaces and that the BGP session is active for each neighbour address.
Action
From the operational mode, enter the evidence bgp neighbor control.
user@R1> prove bgp neighbor logical-system A Peer: 192.163.half dozen.four+179 As 17 Local: 192.168.6.5+58852 Equally 17 Type: Internal Country: Established Flags: <Sync> Last State: OpenConfirm Last Outcome: RecvKeepAlive Last Error: None Consign: [ send-direct ] Options: <Preference LocalAddress Refresh> Local Address: 192.168.6.5 Holdtime: 90 Preference: 170 Number of flaps: 0 Peer ID: 192.163.6.4 Local ID: 192.168.half dozen.5 Active Holdtime: 90 Keepalive Interval: 30 Peer index: 0 BFD: disabled, down NLRI for restart configured on peer: inet-unicast NLRI advertised by peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh capability (2) Restart time configured on the peer: 120 Dried routes from peer are kept for: 300 Restart time requested by this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received cease-of-rib markers: inet-unicast NLRI of all end-of-rib markers sent: inet-unicast Peer supports 4 byte Equally extension (peer-as 17) Peer does not support Addpath Tabular array inet.0 Bit: 10000 RIB State: BGP restart is complete Ship country: in sync Active prefixes: 0 Received prefixes: 3 Accustomed prefixes: 3 Suppressed due to damping: 0 Advertised prefixes: 2 Last traffic (seconds): Received 16 Sent 1 Checked 63 Input messages: Total 15713 Updates iv Refreshes 0 Octets 298622 Output messages: Total 15690 Updates two Refreshes 0 Octets 298222 Output Queue[0]: 0 Peer: 192.168.forty.four+179 AS 17 Local: 192.168.six.5+56466 Every bit 17 Blazon: Internal State: Established Flags: <Sync> Last Country: OpenConfirm Last Event: RecvKeepAlive Last Fault: None Export: [ ship-direct ] Options: <Preference LocalAddress Refresh> Local Address: 192.168.6.v Holdtime: ninety Preference: 170 Number of flaps: 0 Peer ID: 192.168.40.four Local ID: 192.168.half-dozen.5 Active Holdtime: ninety Keepalive Interval: 30 Peer alphabetize: i BFD: disabled, down NLRI for restart configured on peer: inet-unicast NLRI advertised by peer: inet-unicast NLRI for this session: inet-unicast Peer supports Refresh adequacy (2) Restart time configured on the peer: 120 Stale routes from peer are kept for: 300 Restart time requested by this peer: 120 NLRI that peer supports restart for: inet-unicast NLRI that restart is negotiated for: inet-unicast NLRI of received stop-of-rib markers: inet-unicast NLRI of all finish-of-rib markers sent: inet-unicast Peer supports 4 byte AS extension (peer-as 17) Peer does not support Addpath Tabular array inet.0 Bit: 10000 RIB State: BGP restart is complete Send country: in sync Agile prefixes: 0 Received prefixes: two Accepted prefixes: 2 Suppressed due to damping: 0 Advertised prefixes: two Final traffic (seconds): Received 15 Sent 22 Checked 68 Input letters: Full 15688 Updates 2 Refreshes 0 Octets 298111 Output messages: Total 15688 Updates ii Refreshes 0 Octets 298184 Output Queue[0]: 0
Verifying BGP Groups
- Purpose
- Action
Purpose
Verify that the BGP groups are configured correctly.
Action
From the operational fashion, enter the evidence bgp group command.
user@A> show bgp group logical-system A Group Type: Internal AS: 17 Local AS: 17 Proper noun: internal-peers Index: 0 Flags: <Export Eval> Export: [ send-direct ] Holdtime: 0 Total peers: 2 Established: 2 192.163.six.4+179 192.168.twoscore.4+179 inet.0: 0/5/5/0 Groups: 1 Peers: ii External: 0 Internal: ii Downward peers: 0 Flaps: 0 Table Tot Paths Human action Paths Suppressed History Damp Country Pending inet.0 5 0 0 0 0 0
Verifying BGP Summary Information
- Purpose
- Action
Purpose
Verify that the BGP configuration is correct.
Action
From the operational style, enter the testify bgp summary command.
user@A> prove bgp summary logical-system A Groups: 1 Peers: 2 Downward peers: 0 Table Tot Paths Act Paths Suppressed History Damp Land Pending inet.0 five 0 0 0 0 0 Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Agile/Received/Accustomed/Damped... 192.163.6.4 17 15723 15700 0 0 4d 22:13:15 0/3/3/0 0/0/0/0 192.168.40.iv 17 15698 15699 0 0 4d 22:13:11 0/2/2/0 0/0/0/0
Verifying That BGP Routes Are Installed in the Routing Tabular array
- Purpose
- Activity
Purpose
Verify that the export policy configuration is working.
Activity
From the operational manner, enter the show route protocol bgp control.
user@A> show road protocol bgp logical-system A inet.0: 7 destinations, 12 routes (7 active, 0 holddown, 0 hidden) + = Active Road, - = Terminal Active, * = Both 10.10.10.0/xxx [BGP/170] 4d xi:05:55, localpref 100, from 192.163.vi.4 AS path: I > to x.10.ten.2 via lt-0/i/0.1 10.x.x.4/30 [BGP/170] 4d eleven:05:55, localpref 100, from 192.163.6.4 AS path: I > to 10.10.ten.2 via lt-0/1/0.1 [BGP/170] 4d 11:03:10, localpref 100, from 192.168.forty.iv AS path: I > to 10.ten.10.2 via lt-0/i/0.1 192.163.6.4/32 [BGP/170] 4d xi:05:55, localpref 100, from 192.163.vi.iv Every bit path: I > to x.10.10.2 via lt-0/1/0.1 192.168.40.4/32 [BGP/170] 4d 11:03:10, localpref 100, from 192.168.xl.4 As path: I > to x.10.10.two via lt-0/one/0.one
Overview: Configure Multiple Single-Hop EBGP Sessions on Unlike Links Using the Same Link-Local Accost (IPv6)
In circuitous networks such as Data Center or Cloud, link-local addresses are widely used due to the loftier number of links and nodes. Being able to deploy multiple single-hop BGP sessions for Juniper devices using link-local addresses is a significant advantage.
Starting in Junos Os Release 20.4R1, you tin enable single-hop EBGP sessions on different links over multiple directly connected peers that employ the same IPv6 link-local address. You are no longer required to have unique peer addresses for Juniper devices for every EBGP session.
Example: Configure Multiple Unmarried-Hop EBGP Sessions on Different Links Using the Same IPv6 Link-Local Address
This example shows how to configure multiple single-hop EBGP sessions on unlike links using the same IPv6 link-local address.
- Requirements
- Overview
- Configuration
- Verification
Requirements
This example uses the following hardware and software components:
-
2 MX Serial routers
-
Junos Os Release 20.4R1 or afterwards version
Overview
Prior to Junos OS Release 20.4R1, you could configure BGP peers with link-local addresses but you could not configure multiple BGP peers to use the aforementioned link-local address on different interfaces. Starting in Junos OS xx.4R1, you can enable multiple single-hop EBGP sessions on unlike links using the same link-local address.
Topology
Configuration
In this example, you configure multiple single-hop EBGP sessions on two different links using the same IPv6 link-local address.
- CLI Quick Configuration
- Configure Single-Hop EBGP Sessions on Multiple Links Using the Same IPv6 Link-Local Address
- Results
CLI Quick Configuration
R1
set interfaces ge-0/0/1set interfaces ge-0/0/1 description R1-to-R2-Linkfix interfaces ge-0/0/1 vlan-taggingset interfaces ge-0/0/1 unit 1 vlan-id 1set interfaces ge-0/0/1 unit ane family inet6 address fe80::10/64fix interfaces ge-0/0/1 unit of measurement 2 vlan-id 2set interfaces ge-0/0/1 unit 2 family unit inet6 address fe80::x/64set interfaces lo0 unit 0 family unit inet address 198.51.100.1/24 mainset routing-options router-id 198.51.100.1set routing-options democratic-organisation 65541set protocols bgp grouping external peer-equally 65542gear up protocols bgp group external local-as 65541set up protocols bgp group external neighbor fe80::twenty%ge-0/0/1.1set protocols bgp grouping external neighbor "fe80::20%ge-0/0/1.2
R2
gear up interfaces ge-0/0/1gear up interfaces ge-0/0/1 description R2-to-R1-Linkready interfaces ge-0/0/1 vlan-taggingfix interfaces ge-0/0/one unit i vlan-id 1set interfaces ge-0/0/1 unit 1 family inet6 address fe80::xx/64set interfaces ge-0/0/one unit 2 vlan-id iiset interfaces ge-0/0/1 unit 2 family inet6 accost fe80::xx/64set interfaces lo0 unit 0 family inet address 198.51.100.2/24 principalset routing-options router-id 198.51.100.2set routing-options autonomous-system 65542ready protocols bgp group external peer-equally 65541fix protocols bgp group external local-as 65542set protocols bgp group external neighbor fe80::10%ge-0/0/one.1ready protocols bgp group external neighbor fe80::10%ge-0/0/1.2
Configure Single-Hop EBGP Sessions on Multiple Links Using the Same IPv6 Link-Local Address
Step-by-Step Procedure
-
Configure basic gear up, including vlan-tagging, vlan-id, loopback and IPv6 link-local addresses for R1 and R2.
You can configure multiple units on a unmarried interface as follows:
R1
set interfaces ge-0/0/iprepare interfaces ge-0/0/ane description R1-to-R2-Linkfix interfaces ge-0/0/one vlan-taggingset interfaces ge-0/0/1 unit 1 vlan-id oneset interfaces ge-0/0/ane unit i family inet6 address fe80::10/64set interfaces ge-0/0/1 unit 2 vlan-id 2fix interfaces ge-0/0/1 unit 2 family inet6 address fe80::10/64set up interfaces lo0 unit of measurement 0 family unit inet address 198.51.100.1/24 principalR2
prepare interfaces ge-0/0/oneset interfaces ge-0/0/1 description R2-to-R1-Linkset interfaces ge-0/0/1 vlan-taggingready interfaces ge-0/0/1 unit of measurement i vlan-id 1set interfaces ge-0/0/1 unit i family inet6 accost fe80::20/64set interfaces ge-0/0/ane unit two vlan-id twoset up interfaces ge-0/0/ane unit of measurement 2 family unit inet6 accost fe80::twenty/64prepare interfaces lo0 unit 0 family unit inet address 198.51.100.ii/24 principal -
Configure routing options to enable BGP on R1 and R2.
R1
prepare routing-options router-id 198.51.100.oneset routing-options democratic-system 65541R2
ready routing-options router-id 198.51.100.2set routing-options democratic-arrangement 65542 -
Configure EBGP on the multiple links on R1 and R2 using the aforementioned link-local IPv6 addresses in the
set protocols bgp group group neighbor peeraddress%localinterface.unitformat:R1
set protocols bgp group external peer-as 65542prepare protocols bgp group external local-every bit 65541prepare protocols bgp group external neighbor fe80::20%ge-0/0/one.1ready protocols bgp group external neighbor "fe80::twenty%ge-0/0/one.2R2
set protocols bgp group external peer-equally 65541fix protocols bgp group external local-as 65542set protocols bgp grouping external neighbor fe80::10%ge-0/0/ane.1set protocols bgp grouping external neighbor fe80::10%ge-0/0/ane.2 -
Enter
commitfrom the configuration mode.
Results
Verify your configuration by checking the below configurations from devices as follows:
Hither'south how you can verify configurations on R1 device:
user@R1# evidence interfaces
ge-0/0/ane { description R1-to-R2-Link; vlan-tagging; unit of measurement 1 { vlan-id ane; family inet6 { address fe80::10/64; } } unit 2 { vlan-id 2; family inet6 { address fe80::10/64; } } } lo0 { unit of measurement 0 { family inet { address 198.51.100.i/24 { main; } } } } user@R1# testify protocols
bgp { grouping external { peer-every bit 65542; local-as 65541; neighbor "fe80::twenty%ge-0/0/i.1"; neighbour "fe80::20%ge-0/0/1.2"; } } user@R1# prove routing-options
router-id 198.51.100.ane; democratic-organization 65541;
Verification
Verify EBGP Link-local Support
- Purpose
- Action
- Meaning
Purpose
Apply the show bgp summary command to verify the EBGP sessions created on the devices with the same link-local accost through different interfaces.
Action
user@R1> evidence bgp summary Threading mode: BGP I/O Default eBGP mode: advertise - accept, receive - accept Groups: 1 Peers: two Downwards peers: 0 Table Tot Paths Human activity Paths Suppressed History Damp State Pending inet6.0 0 0 0 0 0 0 Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Agile/Received/Accepted/Damped... fe80::20%ge-0/0/one.1 65542 115 114 0 0 l:59 Establ inet6.0: 0/0/0/0 fe80::20%ge-0/0/i.2 65542 114 114 0 0 fifty:58 Establ inet6.0: 0/0/0/0 Meaning
The output indicates that two EBGP sessions are established with the aforementioned IPv6 link-local address (fe80::20) of R2 through the 2 configured local-interfaces of R1 (ge-0/0/1.1 and ge-0/0/i.2).
Source: https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/bgp-peering-sessions.html
0 Response to "juniper device how to find what port a bgp ip is on"
Post a Comment