mpls实验

于 2024-01-27 21:50:43 发布
阅读量942 收藏 19
点赞数 15
文章标签： 网络 运维
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Michael_LDZ/article/details/135886225
版权

ip地址配置

[r1]int g 0/0/0
[r1-GigabitEthernet0/0/0]ip add    
[r1-GigabitEthernet0/0/0]ip address 12.1.1.1 24
[r1-GigabitEthernet0/0/0]
Jan 27 2024 20:51:07-08:00 r1 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r1-GigabitEthernet0/0/0]int l0
[r1-LoopBack0]ip add    
[r1-LoopBack0]ip address 1.1.1.1 32
[r2]int g 0/0/0
[r2-GigabitEthernet0/0/0]ip add    
[r2-GigabitEthernet0/0/0]ip address 23.1.1.1 24
Jan 27 2024 20:52:53-08:00 r2 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r2-GigabitEthernet0/0/0]int g 0/0/1
[r2-GigabitEthernet0/0/1]int g 0/0/0
[r2-GigabitEthernet0/0/0]undo 23.1.1.1 24
                              ^
Error: Unrecognized command found at '^' position.
[r2-GigabitEthernet0/0/0]undo ip add               
[r2-GigabitEthernet0/0/0]undo ip address 23.1.1.1 24
[r2-GigabitEthernet0/0/0]
Jan 27 2024 20:53:30-08:00 r2 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the DOWN state. 
[r2-GigabitEthernet0/0/0]q
[r2]int g 0/0/0
[r2-GigabitEthernet0/0/0]ip add    
[r2-GigabitEthernet0/0/0]ip address 12.1.1.2 24
Jan 27 2024 20:53:44-08:00 r2 %%01IFNET/4/LINK_STATE(l)[2]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r2-GigabitEthernet0/0/0]int g 0/0/1
[r2-GigabitEthernet0/0/1]ip add    
[r2-GigabitEthernet0/0/1]ip address 23.1.1.1 24
Jan 27 2024 20:53:59-08:00 r2 %%01IFNET/4/LINK_STATE(l)[3]:The line protocol IP 
on the interface GigabitEthernet0/0/1 has entered the UP state. 
[r2-GigabitEthernet0/0/1]int g 0/0/2
[r2-GigabitEthernet0/0/2]ip add    
[r2-GigabitEthernet0/0/2]ip address 24.1.1.1 24
[r2-GigabitEthernet0/0/2]
Jan 27 2024 20:54:19-08:00 r2 %%01IFNET/4/LINK_STATE(l)[4]:The line protocol IP 
on the interface GigabitEthernet0/0/2 has entered the UP state. 
[r2-GigabitEthernet0/0/2]int l0
[r2-LoopBack0]ip ad    
[r2-LoopBack0]ip address 2.2.2.2 32
[r2-LoopBack0]q
[r3]int g 0/0/0
[r3-GigabitEthernet0/0/0]ip add    
[r3-GigabitEthernet0/0/0]ip address 23.1.1.2 24
Jan 27 2024 20:55:41-08:00 r3 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r3-GigabitEthernet0/0/0]int g 0/0/1
[r3-GigabitEthernet0/0/1]ip add    
[r3-GigabitEthernet0/0/1]ip address 36.1.1.1 24
Jan 27 2024 20:56:05-08:00 r3 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol IP 
on the interface GigabitEthernet0/0/1 has entered the UP state. 
[r3-GigabitEthernet0/0/1]int g 0/0/2
[r3-GigabitEthernet0/0/2]ip add    
[r3-GigabitEthernet0/0/2]ip address 35.1.1.1 24
Jan 27 2024 20:56:21-08:00 r3 %%01IFNET/4/LINK_STATE(l)[2]:The line protocol IP 
on the interface GigabitEthernet0/0/2 has entered the UP state. 
[r3-GigabitEthernet0/0/2]int l0
[r3-LoopBack0]ip add    
[r3-LoopBack0]ip address 3.3.3.3 32

[r4]int g 0/0/0
[r4-GigabitEthernet0/0/0]ip add    
[r4-GigabitEthernet0/0/0]ip address 24.1.1.2 24
[r4-GigabitEthernet0/0/0]
Jan 27 2024 20:57:14-08:00 r4 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r4-GigabitEthernet0/0/0]int g 0/0/1
[r4-GigabitEthernet0/0/1]ip add    
[r4-GigabitEthernet0/0/1]ip address 45.1.1.1 24
[r4-GigabitEthernet0/0/1]
Jan 27 2024 20:57:36-08:00 r4 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol IP 
on the interface GigabitEthernet0/0/1 has entered the UP state. 
[r4-GigabitEthernet0/0/1]int g 0/0/2
[r4-GigabitEthernet0/0/2]ip aff    
[r4-GigabitEthernet0/0/2]ip add    
[r4-GigabitEthernet0/0/2]ip address 46.1.1.1 24
[r4-GigabitEthernet0/0/2]
Jan 27 2024 20:57:54-08:00 r4 %%01IFNET/4/LINK_STATE(l)[2]:The line protocol IP 
on the interface GigabitEthernet0/0/2 has entered the UP state. 
[r4-GigabitEthernet0/0/2]int l0
[r4-LoopBack0]ip add    
[r4-LoopBack0]ip address 4.4.4.4 32
[r5]int g 0/0/0
[r5-GigabitEthernet0/0/0]ip add    
[r5-GigabitEthernet0/0/0]ip address 45.1.1.2 24
Jan 27 2024 21:00:37-08:00 r5 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r5-GigabitEthernet0/0/0]int g 0/0/1
[r5-GigabitEthernet0/0/1]ip add    
[r5-GigabitEthernet0/0/1]ip address 35.1.1.2 24
[r5-GigabitEthernet0/0/1]
Jan 27 2024 21:01:02-08:00 r5 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol IP 
on the interface GigabitEthernet0/0/1 has entered the UP state. 
[r5-GigabitEthernet0/0/1]in g 0/0/2
[r5-GigabitEthernet0/0/2]ip add    
[r5-GigabitEthernet0/0/2]ip address 57.1.1.1 24
Jan 27 2024 21:01:20-08:00 r5 %%01IFNET/4/LINK_STATE(l)[2]:The line protocol IP 
on the interface GigabitEthernet0/0/2 has entered the UP state. 
[r5-GigabitEthernet0/0/2]int l0
[r5-LoopBack0]ip add    
[r5-LoopBack0]ip address 5.5.5.5 32
[r6]int g 0/0/0
[r6-GigabitEthernet0/0/0]ip add    
[r6-GigabitEthernet0/0/0]ip address 36.1.1.2 24
Jan 27 2024 21:02:00-08:00 r6 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r6-GigabitEthernet0/0/0]int g 0/0/1
[r6-GigabitEthernet0/0/1]ip add    
[r6-GigabitEthernet0/0/1]ip address 46.1.1.2 24
Jan 27 2024 21:02:26-08:00 r6 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol IP 
on the interface GigabitEthernet0/0/1 has entered the UP state. 
[r6-GigabitEthernet0/0/1]int g 0/0/2
[r6-GigabitEthernet0/0/2]ip add    
[r6-GigabitEthernet0/0/2]ip address 68.1.1.1 24
[r6-GigabitEthernet0/0/2]
Jan 27 2024 21:02:43-08:00 r6 %%01IFNET/4/LINK_STATE(l)[2]:The line protocol IP 
on the interface GigabitEthernet0/0/2 has entered the UP state. 
[r6-GigabitEthernet0/0/2]int l0
[r6-LoopBack0]ip add    
[r6-LoopBack0]ip address 6.6.6.6 32
[r7]int g 0/0/0
[r7-GigabitEthernet0/0/0]ip add    
[r7-GigabitEthernet0/0/0]ip address 57.1.1.2 24
[r7-GigabitEthernet0/0/0]
Jan 27 2024 21:03:55-08:00 r7 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r7-GigabitEthernet0/0/0]int l0
[r7-LoopBack0]ip add    
[r7-LoopBack0]ip address 7.7.7.7 32
[r8]int g 0/0/0
[r8-GigabitEthernet0/0/0]ip add    
[r8-GigabitEthernet0/0/0]ip address 68.1.1.2 24
Jan 27 2024 21:04:32-08:00 r8 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP 
on the interface GigabitEthernet0/0/0 has entered the UP state. 
[r8-GigabitEthernet0/0/0]int l0
[r8-LoopBack0]ip add    
[r8-LoopBack0]ip address 8.8.8.8 32

ospf宣告

[r2]os    
[r2]ospf 1 ro    
[r2]ospf 1 router-id 2.2.2.2
[r2-ospf-1]area 0
[r2-ospf-1-area-0.0.0.0]net    
[r2-ospf-1-area-0.0.0.0]network 23.1.1.1 0.0.0.0
[r2-ospf-1-area-0.0.0.0]net    
[r2-ospf-1-area-0.0.0.0]network 24.1.1.1 0.0.0.0
[r2-ospf-1-area-0.0.0.0]net    
[r2-ospf-1-area-0.0.0.0]network 2.2.2.2 0.0.0.0
[r3]ospf 1 ro    
[r3]ospf 1 router-id 3.3.3.3 
[r3-ospf-1]area 0
[r3-ospf-1-area-0.0.0.0]nt    
[r3-ospf-1-area-0.0.0.0]net    
[r3-ospf-1-area-0.0.0.0]network 0.0.0.0 255.255.255.255
[r4]ospf 1 ro    
[r4]ospf 1 router-id 4.4.4.4 
[r4-ospf-1]area 0
[r4-ospf-1-area-0.0.0.0]net    
[r4-ospf-1-area-0.0.0.0]network 0.0.0.0 255.255.255.255
[r5]os    
[r5]ospf 1 ro    
[r5]ospf 1 router-id 5.5.5.5 
[r5-ospf-1]area 0
[r5-ospf-1-area-0.0.0.0]net    
[r5-ospf-1-area-0.0.0.0]network 35.1.1.2 0.0.0.0
[r5-ospf-1-area-0.0.0.0]net    
[r5-ospf-1-area-0.0.0.0]network 45.1.1.2 0.0.0.0
[r5-ospf-1-area-0.0.0.0]net
[r5-ospf-1-area-0.0.0.0]network 5.5.5.5 0.0.0.0
[r6]os    
[r6]ospf 1 ro    
[r6]ospf 1 router-id 6.6.6.6
[r6-ospf-1]area 0
[r6-ospf-1-area-0.0.0.0]net    
[r6-ospf-1-area-0.0.0.0]network 36.1.1.2 0.0.0.0
[r6-ospf-1-area-0.0.0.0]net    
[r6-ospf-1-area-0.0.0.0]network 46.1.1.2 0.0.0.0
[r6-ospf-1-area-0.0.0.0]net    
[r6-ospf-1-area-0.0.0.0]network 6.6.6.6 0.0.0.0

bgp建邻

[r2]bgp 100
[r2-bgp]ro    
[r2-bgp]route-select
[r2-bgp]router-id 2.2.2.2
[r2-bgp]pe    
[r2-bgp]peer 5.5.5.5 as    
[r2-bgp]peer 5.5.5.5 as-number 100
[r2-bgp]pe    
[r2-bgp]peer 5.5.5.5 co    
[r2-bgp]peer 5.5.5.5 connect-interface lo 0 
[r2-bgp]pr    
[r2-bgp]pe    
[r2-bgp]peer 6.6.6.6 as    
[r2-bgp]peer 6.6.6.6 as-number 100
[r2-bgp]pe    
[r2-bgp]peer 6.6.6.6 co    
[r2-bgp]peer 6.6.6.6 connect-interface lo 0

[r5]bgp 100
[r5-bgp]ipv    
[r5-bgp]ipv4-family vp    
[r5-bgp]ipv4-family vpnv4
[r5-bgp-af-vpnv4]pe    
[r5-bgp-af-vpnv4]peer 2.2.2.2 e    
[r5-bgp-af-vpnv4]peer 2.2.2.2 enable 
Jan 27 2024 21:35:03-08:00 r5 %%01BGP/3/STATE_CHG_UPDOWN(l)[2]:The status of the
 peer 2.2.2.2 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=CEASE/Other Configuration Change)  
[r5-bgp-af-vpnv4]
[r5-bgp-af-vpnv4]pe    
[r5-bgp-af-vpnv4]peer 6.6.6.6 e    
[r5-bgp-af-vpnv4]peer 6.6.6.6 enable 
Jan 27 2024 21:35:22-08:00 r5 %%01BGP/3/STATE_CHG_UPDOWN(l)[3]:The status of the
 peer 6.6.6.6 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=CEASE/Other Configuration Change)  
[r5-bgp-af-vpnv4]
[r5-bgp-af-vpnv4]pe    
[r5-bgp-af-vpnv4]peer 2.2.2.2 n    
[r5-bgp-af-vpnv4]peer 2.2.2.2 next-hop-invariable
[r5-bgp-af-vpnv4]pe    
[r5-bgp-af-vpnv4]peer 6.6.6.6 n    
[r5-bgp-af-vpnv4]peer 6.6.6.6 next-hop-invariable
[r6]bgp 100
[r6-bgp]ipv    
[r6-bgp]ipv4-family
Jan 27 2024 21:35:53-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[3]:The status of the
 peer 5.5.5.5 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r6-bgp]ipv4-family vp    
[r6-bgp]ipv4-family vpnv4
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 2.2.2.2 e    
[r6-bgp-af-vpnv4]peer 2.2.2.2 enable 
Jan 27 2024 21:36:12-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[4]:The status of the
 peer 2.2.2.2 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=CEASE/Other Configuration Change)  
[r6-bgp-af-vpnv4]
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 5.5.5.5 e    
[r6-bgp-af-vpnv4]peer 5.5.5.5 enable 
Jan 27 2024 21:36:20-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[5]:The status of the
 peer 5.5.5.5 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=CEASE/Other Configuration Change)  
[r6-bgp-af-vpnv4]
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 2.2.2.2 n    
[r6-bgp-af-vpnv4]peer 2.2.2.2 next-hop-invariable
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 2.2.2.2 n    
[r6-bgp-af-vpnv4]peer 
Jan 27 2024 21:36:43-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[6]:The status of the
 peer 2.2.2.2 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r6-bgp-af-vpnv4]peer  next-hop-invariable next-hop-invari
Jan 27 2024 21:36:52-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[7]:The status of the
 peer 5.5.5.5 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r6-bgp-af-vpnv4]peer 5.5.5.5 n    
[r6-bgp-af-vpnv4]p5.5.5.5 n
                 ^
Error: Unrecognized command found at '^' position.
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 5.5.5.5     
[r6-bgp-af-vpnv4]peer 5.5.5.5 n    
[r6-bgp-af-vpnv4]peer 5.5.5.5 next-hop-invariable

mpls

[r3]mpls ls    
[r3]mpls lsr-id 3.3.3.3
[r3]
[r3]mp    
[r3]mpls ld
Warning: Global MPLS is not enabled.
[r3]mpls ldp
Warning: Global MPLS is not enabled.
[r3]mpls
Info: Mpls starting, please wait... OK!
[r3-mpls]mpls    
[r3-mpls]mpls ld
[r3-mpls-ldp]q
[r3]int g 0/0/0
[r3-GigabitEthernet0/0/0]mp    
[r3-GigabitEthernet0/0/0]mpls 
[r3-GigabitEthernet0/0/0]mp    
[r3-GigabitEthernet0/0/0]mpls ld    
[r3-GigabitEthernet0/0/0]mpls ldp 
[r3-GigabitEthernet0/0/0]q
[r3]int g 0/0/1
[r3-GigabitEthernet0/0/1]mp    
[r3-GigabitEthernet0/0/1]mpls 
[r3-GigabitEthernet0/0/1]mp    
[r3-GigabitEthernet0/0/1]mpls ld    
[r3-GigabitEthernet0/0/1]mpls ldp 
[r3-GigabitEthernet0/0/1]q
[r3]int g 0/0/2
[r3-GigabitEthernet0/0/2]mp    
[r3-GigabitEthernet0/0/2]mpls 
[r3-GigabitEthernet0/0/2]mp    
[r3-GigabitEthernet0/0/2]mpls ld    
[r3-GigabitEthernet0/0/2]mpls ldp 

[r4]mpls ls    
[r4]mpls lsr-id 4.4.4.4 
[r4]mp    
[r4]mpls 
Info: Mpls starting, please wait... OK!
[r4-mpls]mp    
[r4-mpls]mpls ld    
[r4-mpls]mpls ld
[r4-mpls-ldp]q
[r4]int g 0/0/0
[r4-GigabitEthernet0/0/0]mp    
[r4-GigabitEthernet0/0/0]mpls 
[r4-GigabitEthernet0/0/0]mp    
[r4-GigabitEthernet0/0/0]mpls ld    
[r4-GigabitEthernet0/0/0]mpls ldp 
[r4-GigabitEthernet0/0/0]q
[r4]int g 0/0/1
[r4-GigabitEthernet0/0/1]mp    
[r4-GigabitEthernet0/0/1]mpls 
[r4-GigabitEthernet0/0/1]mp    
[r4-GigabitEthernet0/0/1]mpls ld    
[r4-GigabitEthernet0/0/1]mpls ldp 
[r4-GigabitEthernet0/0/1]q
[r4]int g 0/0/2
[r4-GigabitEthernet0/0/2]mp    
[r4-GigabitEthernet0/0/2]mpls 
[r4-GigabitEthernet0/0/2]mp    
[r4-GigabitEthernet0/0/2]mpls ld    
[r4-GigabitEthernet0/0/2]mpls ldp 
[r5]mp    
[r5]mpls ls    
[r5]mpls lsr-id 5.5.5.5 
[r5]mp    
[r5]mpls 
Info: Mpls starting, please wait... OK!
[r5-mpls]mp    
[r5-mpls]mpls ld
[r5-mpls-ldp]q
[r5]int g 0/0/0
[r5-GigabitEthernet0/0/0]mp    
[r5-GigabitEthernet0/0/0]mpls 
[r5-GigabitEthernet0/0/0]mp    
[r5-GigabitEthernet0/0/0]mpls  ld    
[r5-GigabitEthernet0/0/0]mpls  ldp 
[r5-GigabitEthernet0/0/0]    
[r5-GigabitEthernet0/0/0]
[r5-GigabitEthernet0/0/0]q
[r5]int g 0/0/1
[r5-GigabitEthernet0/0/1]mp    
[r5-GigabitEthernet0/0/1]mpls 
[r5-GigabitEthernet0/0/1]mp    
[r5-GigabitEthernet0/0/1]mpls ld    
[r5-GigabitEthernet0/0/1]mpls ldp 
[r5-GigabitEthernet0/0/1]q
[r6]mp    
[r6]mpls ls    
[r6]mpls lsr-id 6.6.6.6 
[r6]mp    
[r6]mpls 
Info: Mpls starting, please wait... OK!
[r6-mpls]mp    
[r6-mpls]mpls ld    
[r6-mpls]mpls ld
[r6-mpls-ldp]q
[r6]int g 0/0/0
[r6-GigabitEthernet0/0/0]mp    
[r6-GigabitEthernet0/0/0]mpls 
[r6-GigabitEthernet0/0/0]mp    
[r6-GigabitEthernet0/0/0]mpls ld    
[r6-GigabitEthernet0/0/0]mpls ldp 
[r6-GigabitEthernet0/0/0]q
[r6]int g 0/0/1
[r6-GigabitEthernet0/0/1]mp    
[r6-GigabitEthernet0/0/1]mpls 
[r6-GigabitEthernet0/0/1]mp    
[r6-GigabitEthernet0/0/1]mpls ld    
[r6-GigabitEthernet0/0/1]mpls ldp

ipv4

[r2]ip vp    
[r2]ip vpn-instance 1
[r2-vpn-instance-1]ro    
[r2-vpn-instance-1]route-distinguisher     
[r2-vpn-instance-1]routing-table
[r2-vpn-instance-1]route-distinguisher 1:1
[r2-vpn-instance-1-af-ipv4]vp    
[r2-vpn-instance-1-af-ipv4]vpn-target 1:1 e    
[r2-vpn-instance-1-af-ipv4]vpn-target 1:1 export-extcommunity 
 EVT Assignment result: 
Info: VPN-Target assignment is successful.
[r2-vpn-instance-1-af-ipv4]vp    
[r2-vpn-instance-1-af-ipv4]vpn-    
[r2-vpn-instance-1-af-ipv4]vpn-target 2:2 3:3 im    
[r2-vpn-instance-1-af-ipv4]vpn-target 2:2 3:3 import-extcommunity 
 IVT Assignment result: 
Info: VPN-Target assignment is successful.
[r5]bgp 100
[r5-bgp]ipv    
[r5-bgp]ipv4-family vp    
[r5-bgp]ipv4-family vpnv4
[r5-bgp-af-vpnv4]pe    
[r5-bgp-af-vpnv4]peer 2.2.2.2 e    
[r5-bgp-af-vpnv4]peer 2.2.2.2 enable 
Jan 27 2024 21:35:03-08:00 r5 %%01BGP/3/STATE_CHG_UPDOWN(l)[2]:The status of the
 peer 2.2.2.2 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=CEASE/Other Configuration Change)  
[r5-bgp-af-vpnv4]
[r5-bgp-af-vpnv4]pe    
[r5-bgp-af-vpnv4]peer 6.6.6.6 e    
[r5-bgp-af-vpnv4]peer 6.6.6.6 enable 
Jan 27 2024 21:35:22-08:00 r5 %%01BGP/3/STATE_CHG_UPDOWN(l)[3]:The status of the
 peer 6.6.6.6 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=CEASE/Other Configuration Change)  
[r5-bgp-af-vpnv4]
[r5-bgp-af-vpnv4]pe    
[r5-bgp-af-vpnv4]peer 2.2.2.2 n    
[r5-bgp-af-vpnv4]peer 2.2.2.2 next-hop-invariable
[r5-bgp-af-vpnv4]pe    
[r5-bgp-af-vpnv4]peer 6.6.6.6 n    
[r5-bgp-af-vpnv4]peer 6.6.6.6 next-hop-invariable
[r5-bgp-af-vpnv4]
Jan 27 2024 21:35:35-08:00 r5 %%01BGP/3/STATE_CHG_UPDOWN(l)[4]:The status of the
 peer 2.2.2.2 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r5-bgp-af-vpnv4]
Jan 27 2024 21:35:54-08:00 r5 %%01BGP/3/STATE_CHG_UPDOWN(l)[5]:The status of the
 peer 6.6.6.6 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r5-bgp-af-vpnv4]
Jan 27 2024 21:36:20-08:00 r5 %%01BGP/3/STATE_CHG_UPDOWN(l)[6]:The status of the
 peer 6.6.6.6 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=Notification Message Received)  
[r5-bgp-af-vpnv4]
Jan 27 2024 21:36:53-08:00 r5 %%01BGP/3/STATE_CHG_UPDOWN(l)[7]:The status of the
 peer 6.6.6.6 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r5-bgp-af-vpnv4]    
[r5-bgp-af-vpnv4]q
[r5-bgp]q
[r5]ip v    
[r5]ip vpn-instance 2
[r5-vpn-instance-2]ro    
[r5-vpn-instance-2]route-distinguisher     
[r5-vpn-instance-2]routing-table
[r5-vpn-instance-2]route-distinguisher 2:2 
[r5-vpn-instance-2-af-ipv4]vp    
[r5-vpn-instance-2-af-ipv4]vpn-target 2:2 e    
[r5-vpn-instance-2-af-ipv4]vpn-target 2:2 export-extcommunity 
 EVT Assignment result: 
Info: VPN-Target assignment is successful.
[r5-vpn-instance-2-af-ipv4]vp    
[r5-vpn-instance-2-af-ipv4]vpn-    
[r5-vpn-instance-2-af-ipv4]vpn-target 1:1 3:3 im    
[r5-vpn-instance-2-af-ipv4]vpn-target 1:1 3:3 import-extcommunity 
 IVT Assignment result: 
Info: VPN-Target assignment is successful.
[r6]bgp 100
[r6-bgp]ipv    
[r6-bgp]ipv4-family
Jan 27 2024 21:35:53-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[3]:The status of the
 peer 5.5.5.5 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r6-bgp]ipv4-family vp    
[r6-bgp]ipv4-family vpnv4
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 2.2.2.2 e    
[r6-bgp-af-vpnv4]peer 2.2.2.2 enable 
Jan 27 2024 21:36:12-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[4]:The status of the
 peer 2.2.2.2 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=CEASE/Other Configuration Change)  
[r6-bgp-af-vpnv4]
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 5.5.5.5 e    
[r6-bgp-af-vpnv4]peer 5.5.5.5 enable 
Jan 27 2024 21:36:20-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[5]:The status of the
 peer 5.5.5.5 changed from ESTABLISHED to IDLE. (InstanceName=Public, StateChang
eReason=CEASE/Other Configuration Change)  
[r6-bgp-af-vpnv4]
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 2.2.2.2 n    
[r6-bgp-af-vpnv4]peer 2.2.2.2 next-hop-invariable
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 2.2.2.2 n    
[r6-bgp-af-vpnv4]peer 
Jan 27 2024 21:36:43-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[6]:The status of the
 peer 2.2.2.2 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r6-bgp-af-vpnv4]peer  next-hop-invariable next-hop-invari
Jan 27 2024 21:36:52-08:00 r6 %%01BGP/3/STATE_CHG_UPDOWN(l)[7]:The status of the
 peer 5.5.5.5 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)  
[r6-bgp-af-vpnv4]peer 5.5.5.5 n    
[r6-bgp-af-vpnv4]p5.5.5.5 n
                 ^
Error: Unrecognized command found at '^' position.
[r6-bgp-af-vpnv4]pe    
[r6-bgp-af-vpnv4]peer 5.5.5.5     
[r6-bgp-af-vpnv4]peer 5.5.5.5 n    
[r6-bgp-af-vpnv4]peer 5.5.5.5 next-hop-invariable
[r6-bgp-af-vpnv4]q
[r6-bgp]q
[r6]ip v    
[r6]ip vpn-instance 3
[r6-vpn-instance-3]ro    
[r6-vpn-instance-3]route-distinguisher 3:3 
[r6-vpn-instance-3-af-ipv4]vp    
[r6-vpn-instance-3-af-ipv4]vpn-target-    
[r6-vpn-instance-3-af-ipv4]vpn-target 3:3 e    
[r6-vpn-instance-3-af-ipv4]vpn-target 3:3 export-extcommunity 
 EVT Assignment result: 
Info: VPN-Target assignment is successful.
[r6-vpn-instance-3-af-ipv4]vp    
[r6-vpn-instance-3-af-ipv4]vpn-    
[r6-vpn-instance-3-af-ipv4]vpn-target  1:1 2:2 im    
[r6-vpn-instance-3-af-ipv4]vpn-target  1:1 2:2 import-extcommunity 
 IVT Assignment result: 
Info: VPN-Target assignment is successful.
 

Michael_LDZ
关注
  • 15
    点赞
  • 踩
  • 19
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
break net
qq_41875506的博客
07-07 508
LLDP switch mac flapping ip flapping 浮动IP（FLOAT IP） MPLSOverlay网络 VXLAN（L2 over UDP） GRE NVGRE（L2 over GRE） STT(L2 over TCP) VLAN和VXLAN LLDP【LLDP，Link Layer Discovery Protocol】：链路层发现协议。 IEEE 802.1AB中定义的第二层发现协议，可以使得不同厂商设备之间的企业或运营商通过该功能可以清楚的了解整个网络的拓扑结构恢复
Linux学习十一
qq_33761739的博客
07-26 1716
Linux学习十一 iptables服务把用于处理或过滤流量的策略条目称之为规则，多条规则可以组成一个规则链，而规则链则依据数据包处理位置的不同进行分类，具体如下： 在进行路由选择前处理数据包（PREROUTING）； 处理流入的数据包（INPUT）； 处理流出的数据包（OUTPUT）； 处理转发的数据包（FORWARD）； 在进行路由选择后处理数据包（POSTROUTING） iptables服务的术语中分别是 ACCEPT（允许流量通过） REJECT（拒绝流量通过） LOG（记录日志信息） DROP（
华为设备配置MPLS TE隧道属性
Tony_long7483的博客
05-18 808
华为设备配置MPLS TE隧道属性
MPLS 初学者的常见问题
　　　　　KISSMonX
06-06 1505
中文:  ================================================================================================================================ 问题 前言  什么是多协议标签交换 (MPLS)？  什么是标签？ 标签的结构是什么？  标签将附加到数据包
拓扑实验记录配置OSPF单域
解启超
03-30 494
1）配置OSPF实现全网互通。 2）使用命令验证配置。 搭建实验环境： 现此案例需要按照如下步骤进行。 //R1的配置 ospf 1 router-id 1.1.1.1 area 0 network 192.168.10.0 0.0.0.255 network 192.168.1.1 0.0.0.0 network 192.168...
H3C MPLS实验学习实验手册.rar
08-16
实验一：基本的L3 MPLS 实验二、MPLS之HubSpoken模式 实验三 IP Public方式访问公网 实验四 CE使用外接NAT设备访问公网 实验五 将上网出口划分到一个VRF上网 实验六 HoVPN的典型配置 实验七 多角色主机的典型配置 ...
mpls 实验拓扑，详细实验步骤
最新发布
07-10
对于mpls的实验操作，若完全理解该实验中对于mpls 的操作，可以熟练的掌握并理解mpls 的工作原理，以及注意事项
南京邮电大学MPLS基本配置实验报告.doc
12-23
MPLS实验的主要目的是让学生理解和掌握MPLS的基本概念，包括标签分配、标签交换路径（LSP）建立、标签分发协议（LDP）的配置，以及MPLS如何提高网络性能。此外，实验还旨在训练学生在实际网络环境中配置和验证MPLS的...
mpls实验的问题.docx
02-24
在给定的文档中，我们关注的是MPLS（多协议标签交换）实验的相关配置，以及涉及的一些网络设备和协议。MPLS是一种用于高效数据传输的网络技术，它通过在IP分组上添加标签来简化和加速路由过程。下面我们将深入探讨这...
HoRity系列MPLS实验手册
06-11
### HoRity系列MPLS实验手册：深化MPLS理解 #### MPLS（多协议标签交换）概览 MPLS是一种数据包转发技术，它在第二层和第三层之间运作，允许网络运营商在单一的网络基础设施上提供多种服务。这种技术通过将固定...
OSPF 笔记 1
weixin_33819479的博客
05-23 234
IGP 协议 内部网关协议 IGP 属于同一个AS 自治系统号，内部路由器使用相同的路由协议或者不同的路由协议，RIP OSPF IS-ISEGP 协议 外部网关协议 属于不同的AS，通过BGP协议进行路由的传递和更新或者进行路径的选择 OSPF Open shortest path First特征：链路状态协议基于IP协议，协议号 89所有的路由器使用组播地址224.0.0.5 还有224.0....
华为OSPF配置小实验演示（1）
weixin_34348805的博客
11-28 481
实验名称：华为OSPF配置演示（1） 实验拓扑： 实验设置：路由器R1 与R2之间配置192.168.12.0/24网段，R2与R3之间配置192.168.23.0/24网段，R3与R4之间配置192.168.34.0/24网段，R4与R5之间配置192.168.45.0/24网段，R1设置loopback10.10.1.1 /24，R2设置loopba...
启动MongoDB提示报警信息：“WARNING: Access control is not enabled for the database.”
风雪独秀
08-30 2万+
启动MongoDB提示报警信息：“WARNING: Access control is not enabled for the database.” 原因分析：新版本的MongDB增加了安全性设计，推荐用户创建使用数据库时进行验证。
使用#pragma阻止一些warnings
小朴朴的博客
12-18 5358
转自：http://www.cnblogs.com/csutanyu/p/4451093.html 使用#pragma阻止一些warnings 这篇博客的内容都是记的网上的。是流水账。只是记录下来以便日后之有，避免每次重新google。 #pragma除了可以用来把不同功能的代码进行分隔组织外还可以用来disable一些warnings。这在引入一些第三方带有warnings的库的时
ISE/Vivado调试过程中经常遇到的几种warning，以及解决办法，一些verilog使用技巧
热门推荐
weiyunguan8611的博客
09-02 8万+
由于最近已经也刚刚接手项目，遇到特别多的问题，所以把遇到的问题记录一下，自己学习的同时，把过程分享出来，希望对大家有一定的帮助，共同进步。下面就是ISE调试过程中经常遇到的几种warning，以及解决办法，自己整理成文档，以供参考： 1、Redeclaration of ansi port XX is not allowed “不允许重新声明ansi端口XX”。 出现的原因是在程序中声明了两......
CCIE学习笔记之MPLS与MPLS ×××
weixin_34319640的博客
08-13 427
CCIE学习笔记之MPLS与MPLS ×××配置：接口下启用：mpls ipmpls label protocol ldp | tdp | both配置LDP RID（全局）:mpls ldp route-id interface [force]如mpls ldp route-idloopback0 force注：force强制命令立即生效，注意对方的...
MPLS（多协议标签交换）实验——华为设备
qq_43754475的博客
11-08 1504
实验要求：中间ISP区域为公网，周围有四个私网，要求A公司可以ping通A公司，B公司可以ping通B公司，但是AB之间不互通，要求要涉及到MPLS技术来完成实验； 思路： 先配置ISP公网区域，要求将公网区域全网可达，这里利用OSPF协议； 然后整个公网的开启MPLS——MPLS LDP，然后在公网的所有接口上调用； 之后就是在与CE直连的PE上创建VR空间，然后将于C...
MPLS Segment Routing实验：BGP-LS配置与实践
本实验手册是针对MPLS Segment Routing (SR) 的第三模块第四实验室，标题为"segement routing-3-module_4_lab_guide_-_bgp-ls_v1.0"，由APNIC SDN Workshop提供，创建日期为2014年6月24日，最近更新也是同一天。...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值