This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg] Multi home BGP reestablishment.
- Previous message (by thread): [routing-wg] Towards cleaning up RPKI INVALIDs
- Next message (by thread): [routing-wg] /24 prefix "hijackability" metric (defining "better than avg AS")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Masud Akhtar Ahmed
m.ahmed at londontelecom.net
Tue Sep 18 17:36:22 CEST 2018
I received a complaint from one of our important client is having issues for their BGP peer connectivity with their one upstream ANSs (AS 3xxx I. e Level 3 ) network.
My research and development was as following details:
• Run BGP protocol • configure BGP peering sessions against one of unestablished edge,(i. e Level 3 ) using peer groups • and then advertise networks.
[N. B I used some dummy character here in this example to hide real network IPs ANSs info.]
Info: The max number of VTY users is 10, and the number
of current VTY users on line is 1.
The current login time is 2018-02-08 11:09:51.
<XYG_NE40_H01> system-view
Enter system view, return user view with Ctrl+Z.
[XYG_NE40_H01]
[XYG_NE40_H01] dis bgp peer
BGP local router ID : 31.2x.xxx.xx
Local AS number: 56XXX
Total number of peers: 2 Peers in established state : 1
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre fRcv
4.69.249.28 4 3xxx 31061725 361482 0 01h13m Unestablished 0
149.14.146.113 4 17x 6842050 56912 0 0948h28m Established 0942
[XYG_NE40_H01] bgp 56XXX
[XYG_NE40_H01] undo synchronization
[XYG_NE40_H01] undo summary automatic
[XYG_NE40_H01-bgp] peer 4.69.249.28 as-number 3xxx
[XYG_NE40_H01-bgp] peer 4.69.249.28 description Level3_BXXXXXXX_10GE
[XYG_NE40_H01-bgp] network 31.2x.xxx.0 255.255.248.0
[XYG_NE40_H01-bgp] network 31.2x.xxx.0 255.255.255.0
[XYG_NE40_H01-bgp] network 31.2x.xxx.0 255.255.255.0
[XYG_NE40_H01-bgp] network 31.2x.xxx.0 255.255.255.0
[XYG_NE40_H01-bgp] network 31.2x.xxx.0 255.255.255.0
[XYG_NE40_H01-bgp] network 31.2x.xxx.0 255.255.255.0
[XYG_NE40_H01-bgp] dis this
#
bgp 56XXX
router-id 31.2x.xxx.20
peer 4.69.249.28 as-number 3xxx
peer 4.69.249.28 description Level3_ BXXXXXXX_10GE
peer 4.69.249.28 ebgp-max-hop 255
peer 149.14.146.113 as-number 17x
peer 149.14.146.113 description Cogentco
#
ipv4-family unicast
undo synchronization
default local-preference 200
undo ebgp-interface-sensitive
preference 200 200 200
network 31.2x.xxx.0 255.255.248.0
network 31.2x.xxx.0 255.255.255.0
network 31.2x.xxx.0 255.255.255.0
network 31.2x.xxx.0 255.255.255.0
network 31.2x.xxx.0 255.255.255.0
network 31.2x.xxx.0 255.255.255.0
network 149.14.146.112 255.255.255.248
peer 4.69.249.28 enable
peer 149.14.146.113 enable
peer 149.14.146.113 ip-prefix Cogentco-in import
peer 149.14.146.113 ip-prefix Cogentco-out export
#
Return
< XYG_NE40_H01>
< XYG_NE40_H01> system-view
Enter system view, return user view with Ctrl+Z.
[XYG_NE40_H01] dis bgp peer
BGP local router ID : 31.2x.xxx.xx
Local AS number : 56XXX
Total number of peers : 2 Peers in established state : 2
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre fRcv
4.69.249.28 4 3xxx 31061725 361482 0h13m Established 140
149.14.146.113 4 17x 6842050 56912 0 0948h28m Established 1
< XYG_NE40_H01> quite
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
- Previous message (by thread): [routing-wg] Towards cleaning up RPKI INVALIDs
- Next message (by thread): [routing-wg] /24 prefix "hijackability" metric (defining "better than avg AS")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]