多角色主机VRP 3.4实现.doc

各个设备的配置如下：PEA 的配置： CEA 的配置: PEB 的配置： CE2的配置： CE3 的配置：概念：一个CE设备可能需要通过一个物理接口访问多个VPN，这种需求可以通过设置多个逻辑接口来满足，但会增加额外的配置，使用起来有一定的局限性。多角色主机特性可用于解决上述问题：通过配置针对IP地址的策略路由，区分访问不同VPN的报文，再配置静态路由控制从PE到CE的下行数据流。多角色主机应用中的静态路由不同于普通意义上的静态路由，一个VPN的静态路由的出接口可以被指定为其他VPN或公网的接口，从而达到使用一个接口访问多个VPN的目的个人总结点：多角色主机实现中，个人观点手册有些写的不是很通顺，需要注意地方：1）PE1-route-policy apply access-vpn vpn-instance vpn1 vpn2 配置策略路由，对于PC1发出的报文，如果在本接口所属的VPN-instance中没有找到路由，就在名为vpn2的VPN-instance中查找私网路由并转发。（依次查找vpn路由）2）PE1 ip route-static vpn-instance vpn2 100.1.0.0 16 vpn-instance vpn1 1.1.1.2配置静态路由，使PC1访问VPN2的返回报文能够在PE1的VPN-instance vpn1中找到正确的路由，回到PC1。（应这样理解比较通吧：来自Vpn 2中的报文访问目的网段 是vpn 1中的100.1.0.0 /16，那么就到vpn1里面去查找路由，下一跳为1.1.1.2需求一的实现的测试结果成功：CE3ping -a 11.11.11.11 50.50.50.2 PING 50.50.50.2: 56 data bytes, press CTRL_C to break Reply from 50.50.50.2: bytes=56 Sequence=1 ttl=253 time=1 ms Reply from 50.50.50.2: bytes=56 Sequence=5 ttl=253 time=10 ms - 50.50.50.2 ping statistics - 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/6/10 ms CE3ping -a 11.11.11.11 50.50.50.1 PING 50.50.50.1: 56 data bytes, press CTRL_C to break Reply from 50.50.50.1: bytes=56 Sequence=1 ttl=254 time=10 ms Reply from 50.50.50.1: bytes=56 Sequence=5 ttl=254 time=10 ms - 50.50.50.1 ping statistics - 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/6/10 ms CE3ping -a 11.11.11.11 12.12.12.12 PING 12.12.12.12: 56 data bytes, press CTRL_C to break Reply from 12.12.12.12: bytes=56 Sequence=1 ttl=254 time=1 ms Reply from 12.12.12.12: bytes=56 Sequence=5 ttl=254 time=1 ms - 12.12.12.12 ping statistics - 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/1 msPE-BDIS BGP V ALL routing-table Flags: # - valid - active I - internal D - damped H - history S - aggregate suppressed B - balance Dest/Mask Next-Hop Med Local-pref Origin Path - Route Distinguisher:200:1 (VPN instance:ok2) # 11.11.11.11/32 0.0.0.0 0 INC # 12.12.12.12/32 0.0.0.0 0 INC # 40.40.40.0/24 0.0.0.0 0 INC Route Distinguisher:300:1 (VPN instance:ok3) # 60.60.60.0/24 0.0.0.0 0 INC Route Distinguisher:100:1 #I 50.50.50.0/24 2.2.2.2 0 100 INC Route Distinguisher:1000:1 (VPN instance:ok1) # 11.11.11.11/32 0.0.0.0 0 INC # 70.70.70.70/32 0.0.0.0 0 INC Routes total: 7 PE-B *0.42124831 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, IP forward: output slot=0, next hop address=40.40.40.2 *0.42125000 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, IP forward: output slot=0, next hop address=40.40.40.2 *0.42125170 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, IP forward: output slot=0, next hop address=40.40.40.2 *0.42125340 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, IP forward: output slot=0, next hop address=40.40.40.2 *0.42125510 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, IP forward: output slot=0, next hop address=40.40.40.2 PE-B *0.42135832 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42137833 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42140008 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42140150 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42140300 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42140450 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42140600 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42142352 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42142500 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42142650 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index=3, MPLS forward: output slot=0, LspToken=0 *0.42142800 PE-B POLICY-R/8/POLICY-ROUTING:IP Policy routing success : VPN index 需求二测试结果成功：PE-A配置： PEB router id 为3.3.3.3ntp-servic