JunOS BGP - Revision history

Admin: /* Goal 1 */

2019-03-04T02:06:56Z

Goal 1

Admin: /* Goal 2 */

2019-03-04T02:04:13Z

Goal 2

Admin at 02:03, 4 March 2019

2019-03-04T02:03:16Z

Admin: /* Verification */

2019-03-02T04:58:36Z

Verification

Admin: /* BGP verification commands */

2019-03-02T04:58:24Z

BGP verification commands

Admin: /* Checking */

2019-03-02T04:40:29Z

Checking

Admin: /* Checking */

2019-03-02T04:37:20Z

Checking

Admin: /* EBGP Setup */

2019-03-02T04:28:24Z

EBGP Setup

Admin: /* EBGP Setup */

2019-03-02T04:22:02Z

EBGP Setup

Admin: /* On cr1-sfo */

2019-03-02T04:21:19Z

On cr1-sfo

@@ Line 11: / Line 11: @@
 =Goal 1=
-[[file:bgp1.png]]
+[[file:bgp2.png]]
 Our goal is to setup the network like in the above image.

@@ Line 297: / Line 297: @@
 =Goal 2=
 [[file:lag.png]]
 =Goal 3=

@@ Line 9: / Line 9: @@
   sudo apt-get install screen
-=The Goal=
+=Goal 1=
 [[file:bgp1.png]]
@@ Line 288: / Line 288: @@
 =BGP verification commands=
   show bgp neighbor
@@ Line 293: / Line 294: @@
   show bgp summary

← Older revision		Revision as of 04:58, 2 March 2019
Line 288:		Line 288:

	=BGP verification commands=		=BGP verification commands=
−
	show bgp neighbor		show bgp neighbor

← Older revision		Revision as of 04:58, 2 March 2019
Line 284:		Line 284:
	Output messages: Total 16 Updates 0 Refreshes 0 Octets 367		Output messages: Total 16 Updates 0 Refreshes 0 Octets 367
	Output Queue[0]: 0		Output Queue[0]: 0
		+
		+	We have setup peering between cr1-tx and cr1-sfo.
		+
		+	=BGP verification commands=
		+
		+	show bgp neighbor
		+
		+	show bgp group
		+
		+	show bgp summary

@@ Line 211: / Line 211: @@
 Now that we have cr1-sfo setup let us go back to cr1-tx and run again "show bgp neighbor"
+==Verification==
 * On cr1-tx
   root@cr1-tx> show bgp neighbor
@@ Line 247: / Line 247: @@
    Input messages:  Total 5      Updates 1       Refreshes 0     Octets 139
    Output messages: Total 5      Updates 0       Refreshes 0     Octets 158
    Output Queue[0]: 0

← Older revision		Revision as of 04:37, 2 March 2019
Line 209:		Line 209:
	root@cr1-sfo# show routing-options		root@cr1-sfo# show routing-options
	autonomous-system 29;		autonomous-system 29;
		+
		+	Now that we have cr1-sfo setup let us go back to cr1-tx and run again "show bgp neighbor"
		+
		+	* On cr1-tx
		+	root@cr1-tx> show bgp neighbor
		+	Peer: 10.10.10.2+55085 AS 29 Local: 10.10.10.1+179 AS 17
		+	Type: External State: Established Flags: <Sync>
		+	Last 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: 10.10.10.1 Active Holdtime: 90
		+	Keepalive Interval: 30 Group index: 0 Peer index: 0
		+	BFD: disabled, down
		+	Local Interface: xe-0/0/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 capability (2)
		+	Stale routes from peer are kept for: 300
		+	Peer does not support Restarter functionality
		+	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 29)
		+	Peer does not support Addpath
		+	Table inet.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 10 Sent 6 Checked 65
		+	Input messages: Total 5 Updates 1 Refreshes 0 Octets 139
		+	Output messages: Total 5 Updates 0 Refreshes 0 Octets 158
		+	Output Queue[0]: 0

@@ Line 140: / Line 140: @@
 Step 1: Set interface description
   [edit]
-  root@cr1-sfo# set interfaces xe-0/0/0 description to-cr1-tx
+  root@cr1-sfo# set interfaces xe-0/0/0 description to-cr1-sfo
 Step 2: Assign an IP address to the interface
@@ Line 149: / Line 149: @@
   [edit interfaces]
   +   xe-0/0/0 {
-  +       description to-cr1-tx;
+  +       description to-cr1-sfo;
   +       unit 0 {
   +           family inet {
@@ Line 183: / Line 183: @@
   root@cr1-tx# set type external
 Type " exit"

← Older revision		Revision as of 04:22, 2 March 2019
Line 161:		Line 161:
	To set the AS number we need to be in the routing-options level for that type in		To set the AS number we need to be in the routing-options level for that type in
	edit routing-options		edit routing-options
		+
		+	[edit routing-options]
		+	root@cr1-tx# set autonomous-system 29
		+	step 4 : Create the BGP group/ add external neighbor address
		+
		+	To do this we need to be in the protocols bgp group external-peers level
		+
		+	Type "exit" to leave the routing-options level and then type in
		+	[edit]
		+	root@cr1-tx# edit protocols bgp group external-peers
		+
		+	[edit protocols bgp group external-peers]
		+	root@cr1-tx# set neighbor 10.10.10.1
		+
		+	Step 5: Specify external AS number
		+	[edit protocols bgp group external-peers]
		+	root@cr1-tx# set peer-as 17
		+
		+	Step 6: Set the peer type
		+	[edit protocols bgp group external-peers]
		+	root@cr1-tx# set type external
		+	Type " exit"

← Older revision		Revision as of 04:21, 2 March 2019
Line 136:		Line 136:

	== On cr1-sfo ==		== On cr1-sfo ==
		+	We are going to use the interface xe-0/0/0 which is a 10Gbs interfaces.
		+
		+	Step 1: Set interface description
		+	[edit]
		+	root@cr1-sfo# set interfaces xe-0/0/0 description to-cr1-tx
		+
		+	Step 2: Assign an IP address to the interface
		+	set interfaces xe-0/0/0 unit 0 family inet address 10.10.10.2/30
		+
		+	* Check before committing
		+	root@cr1-sfo# show \| compare
		+	[edit interfaces]
		+	+ xe-0/0/0 {
		+	+ description to-cr1-tx;
		+	+ unit 0 {
		+	+ family inet {
		+	+ address 10.10.10.2/30;
		+	+ }
		+	+ }
		+	+ }
		+
		+	Step 3: Set the Autonomous system (AS) number
		+
		+	To set the AS number we need to be in the routing-options level for that type in
		+	edit routing-options