The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: vpn question
Kevin,
Under normal configuration r1 can not ping to r4 also r2 can not ping to r3. Your backbone doesn't know customer (edge) info.
You should ping from r3 to r4. Double check your r1 and r2 configurations.
>>> "kevin Young" <kvyoung@21cn.com> 11/21/00 05:46AM >>>
hi, group
when i config mpls vpn, r1 and r2 are 3640, as PE; r3 and r4 are 2610, as CE. IOS are 12.1.3T
r3-------------r1--------------r2---------------r4
ether atm ether
r1 could ping r3, and r2 could ping r4, r3 and r4 could see each other routes, but r3 couldn't ping r4
and r1 couldn't ping r4, r2 could not ping r3.
i fould r1 and r2 didn't tag the vpn, this is the show on r1:
r1#sh tag-switching for vrf vpn-lab detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
16 Untagged 136.5.1.0/24[V] 0 Fa0/1 10.1.1.1
MAC/Encaps=0/0, MTU=1500, Tag Stack{}
VPN route: vpn-lab
Per-packet load-sharing
17 Aggregate 10.1.1.0/24[V] 0
MAC/Encaps=0/0, MTU=0, Tag Stack{}
VPN route: vpn-lab
Per-packet load-sharing
any advice are appreciated.
one another question: one PE in a AS through static route connects to another PE in another AS,
could it can solve the mpls vpn could not span AS problem ? thanks.
This is same as mpls vpn over multiple AS.
Regards.
Ibrahim Bac
-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
|
|