MPLS TE with MPLS VPN
Hi there,
I'm looking for some basic configuration to turn on mpls te over existing mpls vpn. Worried to effect mpls vpn customers.
Perhaps a link would be great!
thanks in advance.
maher
There is many scenarios involving TE and MPLS VPN.
If you have MPLS TE from ingress to egress PE, the lsp used to go from one PE to the other is signalled using RSVP instead of LDP/TDP.
If you configure TE between the core routers then you need to runn LDP/TDP on the tunnel interface for LDP to learn labels via that pseudo interface. This second scenario involves that at some point up to 3 labels (TE lsp label, IGP label, service label) might be applied to the MPLS packets instead of your regular 2 label (IGP label, service label).
Hope this helps,
Similar Messages
-
Full mesh VPN solution for on MPLS network with PE and CPEs
Hi,
We are trying to evaluate some best solution for Hub-Spoke mesh vpn solution in a MPLS network. The VPN hub router will be in PE router and all the VPN spoke will be in CPE.
Can someone please let us know what will be the best vpn solution, we understands that there will be some technical limitations going with GETVPN but still we did counld find any documenation for possiblity of using DMVPN.
How about the recent flexvpn, can fex-vpn work on this requirement, where can i get a design/configuration document.?
thanks in advance.Hello,
GetVPN is intended for (ANY-to-ANY) type of VPN communication, over an MPLS network with Hub and Spoke Topology, your best Option is to look for Cisco (DMVPN) implementation where this type of VPN is primarily designed for Hub & Spoke.
Regards,
Mohamed -
SLB with MPLS VPN, is ti possible ?
Hi to all, is it possible to configure IOS SLB (on 7200 or 6500 platform) to be able to balance server inside a configured vrf ?
anyone already tested it ?
many thanks
maxHi Max,
the IOS SLB code on the C6k platform is not VRF aware at the moment (can only speak of c6k - never tried c7200). It is 'interface-aware' - which means that you can run IOS SLB on a VRF-lite box where the client and real-server facing interfaces are both in the same VRF.
However IOS SLB currently does not support incoming packets with MPLS labels since the corresponding TCAM filter only matches on pure IP packets - so no support on PE boxes :-(
To make it work on a PE we did some nasty workaround:
Loop back a port on the c6k PE and configure the both ends with different VRFs. Route between them and you have a VRF-lite box 'behind' a PE in the same chassis. Not too straight forward though but works as an interim solution ;-)
hth
cheers,
Stefan -
Load Balance with MPLS on a network with several links paralels
I have a question,...
Can you load balance on a network with mpls throght of several links with the same cost/metric?
Thanks!
Saul BarraganO.k.
I dont know very well MPLS, neither VPN, but I know very well other type of protocols of IGP (like RIP,IGRP, EIGRP, OSPF) or EGP (like BGP), and I know how to balance the load by packets or by session, but I have this doubt and I want to know if its dificult or is the same but with something near/close-looks like it.
Can you tell me what does CE/TE Mean please.
Note: I know, I have to read a good book of MPLS.
Thanks a lot by your answer.
Saul Barragan -
IOS with MPLS for 2610XM ?
There is no image with mpls that I can find, the lowest router is the 2651xm.
However for my home lab I have 2610XM maxed out with 256meg mem and 48meg flash.
Is there any IOS I can run that will allow me to configure MPLS VPN ?
ThanksHi, dtushing
Please ignore my first post. There is a typo. The letter "i" and "j" look so simalar that I made a mistake when I used "cut&paste", I cut the wrong one.
c2600-ik9s-mz-123-10b.bin is an IP PLUS feature set. It doesn't support MPLS.
c2600-jk9s-mz-123-10f.bin is an ENTERPRISE PLUS feature set. It does support MPLS. As far as I tested on my router, it can support most of the features on topics like LDP, MPLS VPN, and MPLS TE.
The Feature Navigator is a helpful tool but not for MPLS. It is not that accurate to find MPLS-related features on 2600 platform like it does on other features.
As for the file, go to the Google and type the image name in the serach box and see what you can find there.
HTH
SSLIN -
Cisco 7200 as managed cpe with mpls enabled
Is there any real network that is using managed CPE (CPE router managed by SP) with mpls enabled (MPLS-TE, VPN) etc.
Is anybody using cisco 7200 as a managed cpe router with mpls.
Thanks.
subodhwith PE router, Service provider handles so many CE routers (of customers).
Managed CPE router will be placed at the customer site and will handle only one customer.
Is there any company/customer that have so big network that they need cisco 7200 at there site and this CPE does MPLS-TE,MPLS-VPN.
could u pl. name some companies that are availing this king of services from service provider.
{as cisco 7200 is also capable of providing voip solution to customer}. -
Hi,
I'm trying some configurations MPLS-TE with PBR in 7600 with SRC3 code and has not been able to make it work.
I have tried CBTS and regular autoroute tunnels and they work fine but not a regular mpls-te with PBR.
I've been following sample configurations and still not been able to make it work.
The lab has the following setup:
CE1->PE1->P->PE2->CE2
The configuration at PE1 looks like this:
interface GigaEthernet2/1
description Connection to CE1
ip vrf forwarding test
ip address 10.1.1.1 255.255.255.252
ip policy route-map PBR_in
interface Tunnel105
description MPLS-TE Test
ip unnumbered Loopback0
mpls ip !<-- also have tried without mpls
tunnel destination 172.16.100.22
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 3 3
tunnel mpls traffic-eng bandwidth sub-pool 250
tunnel mpls traffic-eng affinity 0x0 mask 0x0
tunnel mpls traffic-eng path-option 1000 dynamic
no routing dynamic
route-map PBR_in permit 10
match ip address CE_Loops
set mpls-label !<-- also have tried without this
set interface Tunnel105 !<-- also have tried set ip next-hop <remote-loop>
route-map PBR_in permit 100
ip access-list extended CE_Loops
10 permit ip host 1.1.1.1 host 2.2.2.2
20 permit ip host 2.2.2.2 host 1.1.1.1
And I can see the counters of Tunnel 105 going up but no response, nor any debugging related to it.
sh int tun 104
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input never, output 00:00:05, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
2364 packets output, 168564 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
I have done "debug mpls packet" and but I can't see anything related to labels going on.
What am I missing? Is MPLS-TE with PBR really possible? How does it apply labels to the PBR packets?
WilliamHi Shivlu,
To have a dedicated tunnel per VPN:
1- Static routes in the VRF should work by specifying only the tunnel interface as the outgoing interface (no next-hop).
2- Another solution can be to change the BGP NH for each VPN:
- You have two VPNs configured on PE1 and PE2
- You have two TE tunnels T1 and T2 between PE1 and PE2. PE1 is the head-end
- BGP is build over Loopback0 IP addresses as usual
The idea is to create two new loopbacks one PE2 (L1 and L2) and to configure PE2 to use those loopbacks as BGP NH:
ip vrf VPN1
bgp next-hop loopback 1
ip vrf VPN2
bgp next-hop loopback 2
Now PE1 will receive VPNv4 updates from PE2 with BGP NH set to L1 for VPN1 and L2 for VPN2
on PE1 just add two static route so each loopback will be reachable via two different TE tunnels:
ip route L1/32 T1
ip route L2/32 T2
If you have other PEs with sites connected to these VPNS as well and you are not using TE tunnels, you need to redistribute L1 and L2 into the IGP so those other PEs will have a LSP to PE2 as well.
I agree if PBR could be aware of the interface in the GRT, it would be an easier solution.
Thanks
Laurent. -
BGP Next-hop conflict with MPLS Label.
Hi, Experts
Equipment: Cisco ASR9922, IOS-XR 4.3.2
Issue: I have problem that my RR do the next-hop-self by using route-policy for client routers, the next-hop is changed as intended but the MPLS label doesn’t changed to reflect the new next-hop.
What I would like to achieve: I would like RR to set next-hop-self only for selected prefixes(172.168.0.0/24, 0.0.0.0/0) but maintain original next-hop for the rest, I do this by using route-policy.
Detail:
I have routers running MPLS infrastructure with ASR9922 as an RR. RN router is in neighbor-group RN and CPE-xx routers are in neighbor-group AN.
•- Every routers are in same BGP AS64549.
•- RN sends prefixes 0.0.0.0/0 and 172.168.0.0/24 to RR.
•- CPE-25 sends prefix 192.168.25.1/32 to RR.
Neighbor-group AN has the route-policy AN-OUT2 to set next-hop of prefix 172.168.0.0/24 and 0.0.0.0/0 to RR#loopback1 before send out update to CPE routers. Below is BGP and RPL configuration at RR.
router bgp 64549
nsr
bgp graceful-restart
ibgp policy out enforce-modifications
address-family vpnv4 unicast
additional-paths receive
additional-paths send
additional-paths selection route-policy ADD-PATH-iBGP
retain route-target all
neighbor-group AN
remote-as 64549
cluster-id 172.16.1.11
update-source Loopback1
address-family vpnv4 unicast
route-reflector-client
route-policy AN-OUT2 out
soft-reconfiguration inbound
route-policy AN-OUT2
if destination in DEFAULT or destination in RNC then
set next-hop 192.168.10.11
else
pass
endif
end-policy
This is what RR advertises to CPE-24
RP/0/RP0/CPU0:RR#show bgp vpnv4 unicast neighbors 192.168.10.24 advertised-routes
Fri Dec 20 15:23:14.931 BKK
Network Next Hop From AS Path
Route Distinguisher: 64549:3339
0.0.0.0/0 192.168.10.11 172.16.1.1 ?
172.16.1.2 ?
172.168.0.0/24 192.168.10.11 172.16.1.1 ?
172.16.1.2 ?
192.168.0.1/32 192.168.10.11 192.168.10.24 i
192.168.0.26/32 192.168.10.26 192.168.10.26 i
192.168.25.1/32 192.168.10.25 192.168.10.25 i
192.168.211.8/30 192.168.10.22 192.168.10.22 i
The IP part works as intended but MPLS Label doesn’t work as intended. Please take a look at RN who is originates 172.168.0.0/24, label 16025 is locally assigned.
RP/0/RP0/CPU0:RN1#show bgp vpnv4 unicast labels
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale, N Nexthop-discard
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 64549:3339 (default for vrf VLAN3339)
*> 0.0.0.0/0 0.0.0.0 nolabel 16025
* i 172.16.1.11 16068 16025
* i 172.16.1.13 16033 16025
*> 172.168.0.0/24 0.0.0.0 nolabel 16025
* i 172.16.1.11 16059 16025
* i 172.16.1.13 16024 16025
172.168.0.0/24 at RR, label 16059 is locally assigned, label 16025 is receive from RN router. It should send 172.168.0.0/24 with label 16059 to CPE-24 to reflect next-hop changed.
RP/0/RSP0/CPU0:RR#show bgp vpnv4 unicast labels
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale, N Nexthop-discard
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 64549:3339
*>i0.0.0.0/0 172.16.1.1 16025 16068
* i 172.16.1.2 16007 16068
*>i172.168.0.0/24 172.16.1.1 16025 16059
* i 172.16.1.2 16007 16059
*>i192.168.0.1/32 192.168.10.24 131070 16060
*>i192.168.25.1/32 192.168.10.25 131070 16062
*>i192.168.211.8/30 192.168.10.22 131070 16065
What I found at CPE-24 which is Alcatel router is that, RR send prefix 172.168.0.0/24, nh 192.168.10.11 with label 16025 which is incorrect.
A:CPE-24# show router bgp routes vpn-ipv4 172.168.0.0/24
===============================================================================
BGP Router ID:192.168.10.24 AS:64549 Local AS:64549
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best, b - backup
===============================================================================
BGP VPN-IPv4 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop Path-Id VPNLabel
As-Path
u*>? 64549:3339:172.168.0.0/24 100 0
192.168.10.11 None 16025
No As-Path
Routes : 1
===============================================================================
On RR If I just remove the policy and do the next-hop-self under vpv4 address family, CPE-24 will get corrent nh with correct label(16059) but that won’t achieve our requirement to change nh only on selected prefixes. Is this software problem? Or is there any solution to work around?
Regard,
MaritHello Marit,
I am able to recreate this in the lab, and unfortunately this scenario is not supported. BGP does not advertise allocated label if we set nexhop using route policy. The only way is by next-hop-self configured on RR, and yes it eventually will applies to all prefixes advertised to neighbor-group AN. Currently i do not have workaround available.
Below is the capture of what i have tested in the lab:
The topology:
CRS-4-02 ---------- CRS-8-01 ------------ ASR-9006-1
CRS-8-01 is Route-reflector of CRS-4-02 and ASR-9006-1.
CRS-4-02 advertise some prefixes.
This issue occurs when RR have route-policy toward ASR-9006-1, where it assign incorrect label. But it assign correct label if CRS-8-01 use next-hop-self.
Below is the test done in the lab if RR use next-hop-self:
RP/0/RP0/CPU0:CRS-4-02#show run router bgp
Tue Jan 7 08:16:18.945 UTC
router bgp 1
bgp router-id 172.16.4.1
ibgp policy out enforce-modifications
address-family ipv4 unicast
address-family vpnv4 unicast
neighbor 172.16.8.3
remote-as 1
update-source Loopback0
address-family ipv4 unicast
address-family vpnv4 unicast
route-policy PASS in
route-policy PASS out
vrf RTAMAELA
rd 100:1
address-family ipv4 unicast
redistribute connected
RP/0/RP0/CPU0:CRS-4-02#show bgp vpnv4 unicast advertised summary
Tue Jan 7 08:16:29.001 UTC
Network Next Hop From Advertised to
Route Distinguisher: 100:1
78.22.11.2/32 172.16.4.1 Local 172.16.8.3
78.22.11.3/32 172.16.4.1 Local 172.16.8.3
93.22.15.61/32 172.16.4.1 Local 172.16.8.3
RP/0/RP0/CPU0:CRS-4-02#
RP/0/RP0/CPU0:CRS-4-02#show bgp vpnv4 unicast labels
Tue Jan 7 08:16:53.655 UTC
BGP router identifier 172.16.4.1, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0
BGP main routing table version 57
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 100:1 (default for vrf RTAMAELA)
*>i22.51.32.77/32 172.16.8.3 16056 nolabel
*> 78.22.11.2/32 0.0.0.0 nolabel 16003
*> 78.22.11.3/32 0.0.0.0 nolabel 16003
*> 93.22.15.61/32 0.0.0.0 nolabel 16003
Processed 4 prefixes, 4 paths
RP/0/RP0/CPU0:CRS-4-02#
RP/0/RP1/CPU0:CRS-8-01#show run router bgp
Wed Jan 8 11:07:05.436 UTC
router bgp 1
bgp graceful-restart
ibgp policy out enforce-modifications
address-family ipv4 unicast
allocate-label all
address-family vpnv4 unicast
retain route-target all
neighbor-group AN
remote-as 1
update-source Loopback0
address-family vpnv4 unicast
route-reflector-client
next-hop-self <-- use next-hop-self toward ASR-9006-1
soft-reconfiguration inbound
neighbor-group RN
remote-as 1
update-source Loopback0
graceful-restart
address-family vpnv4 unicast
route-reflector-client
next-hop-self
soft-reconfiguration inbound
neighbor 10.10.10.10
remote-as 1
address-family ipv4 unicast
neighbor 72.15.48.5
use neighbor-group AN
neighbor 172.16.4.1
use neighbor-group RN
RP/0/RP1/CPU0:CRS-8-01#show bgp vpnv4 unicast labels
Wed Jan 8 11:07:09.091 UTC
BGP router identifier 172.16.8.3, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0 RD version: 344169
BGP main routing table version 92
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 100:1
*>i22.51.32.77/32 72.15.48.5 16000 16056
*>i78.22.11.2/32 172.16.4.1 16003 16053
*>i78.22.11.3/32 172.16.4.1 16003 16054
*>i93.22.15.61/32 172.16.4.1 16003 16055
Processed 4 prefixes, 4 paths
RP/0/RP1/CPU0:CRS-8-01#
RP/0/RSP1/CPU0:ASR-9006-01#show run router bgp
Wed Jan 8 17:02:02.796 UTC
router bgp 1
bgp router-id 72.15.48.5
bgp graceful-restart
ibgp policy out enforce-modifications
address-family ipv4 unicast
address-family vpnv4 unicast
retain route-target all
neighbor-group RR
remote-as 1
update-source Loopback0
graceful-restart
address-family vpnv4 unicast
route-reflector-client
soft-reconfiguration inbound
neighbor 172.16.8.3
use neighbor-group RR
neighbor 192.169.1.2
remote-as 1
update-source Loopback0
address-family vpnv4 unicast
route-policy PASS in
route-policy PASS out
vrf RTAMAELA
rd 100:1
address-family ipv4 unicast
redistribute connected
RP/0/RSP1/CPU0:ASR-9006-01#show bgp vpnv4 unicast labels
Wed Jan 8 17:02:04.381 UTC
BGP router identifier 72.15.48.5, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0 RD version: 253825
BGP main routing table version 126
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 100:1 (default for vrf RTAMAELA)
*> 22.51.32.77/32 0.0.0.0 nolabel 16000
*>i78.22.11.2/32 172.16.8.3 16053 nolabel <== 172.16.8.3 is the loopback address of CRS-8-01
*>i78.22.11.3/32 172.16.8.3 16054 nolabel
*>i93.22.15.61/32 172.16.8.3 16055 nolabel
Processed 4 prefixes, 4 paths
RP/0/RSP1/CPU0:ASR-9006-01#
From output above we can see that ASR-9006-01 received correct label for each prefix.
Below is the output with route-policy configured and ASR-9006-01 receive incorrect label:
RP/0/RP1/CPU0:CRS-8-01#show run router bgp
Wed Jan 8 11:04:46.310 UTC
router bgp 1
bgp graceful-restart
ibgp policy out enforce-modifications
address-family ipv4 unicast
allocate-label all
address-family vpnv4 unicast
retain route-target all
neighbor-group AN
remote-as 1
update-source Loopback0
address-family vpnv4 unicast
route-reflector-client
route-policy RTAMAELA out
soft-reconfiguration inbound
neighbor-group RN
remote-as 1
update-source Loopback0
graceful-restart
address-family vpnv4 unicast
route-reflector-client
next-hop-self
soft-reconfiguration inbound
neighbor 72.15.48.5
use neighbor-group AN
neighbor 172.16.4.1
use neighbor-group RN
RP/0/RP1/CPU0:CRS-8-01#show run route-policy RTAMAELA
Wed Jan 8 11:16:06.847 UTC
route-policy RTAMAELA
if destination in RNC then
set next-hop 172.16.8.3
else
pass
endif
end-policy
RP/0/RP1/CPU0:CRS-8-01#show run prefix-set RNC
Wed Jan 8 11:16:12.099 UTC
prefix-set RNC
78.22.11.3/32
end-set
RP/0/RP1/CPU0:CRS-8-01#show bgp vpnv4 unicast labels
Wed Jan 8 11:04:33.512 UTC
BGP router identifier 172.16.8.3, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0 RD version: 344013
BGP main routing table version 92
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 100:1
*>i22.51.32.77/32 72.15.48.5 16000 16056
*>i78.22.11.2/32 172.16.4.1 16003 16053
*>i78.22.11.3/32 172.16.4.1 16003 16054
*>i93.22.15.61/32 172.16.4.1 16003 16055
Processed 4 prefixes, 4 paths
RP/0/RP1/CPU0:CRS-8-01#
RP/0/RSP1/CPU0:ASR-9006-01#show run router bgp
Wed Jan 8 16:59:41.601 UTC
router bgp 1
bgp router-id 72.15.48.5
bgp graceful-restart
ibgp policy out enforce-modifications
address-family ipv4 unicast
address-family vpnv4 unicast
retain route-target all
neighbor-group RR
remote-as 1
update-source Loopback0
graceful-restart
address-family vpnv4 unicast
route-reflector-client
soft-reconfiguration inbound
neighbor 172.16.8.3
use neighbor-group RR
neighbor 192.169.1.2
remote-as 1
update-source Loopback0
address-family vpnv4 unicast
route-policy PASS in
route-policy PASS out
vrf RTAMAELA
rd 100:1
address-family ipv4 unicast
redistribute connected
RP/0/RSP1/CPU0:ASR-9006-01#show bgp ipv4 unicast labels
Wed Jan 8 16:59:52.173 UTC
RP/0/RSP1/CPU0:ASR-9006-01#show bgp vpnv4 unicast labels
Wed Jan 8 17:00:00.457 UTC
BGP router identifier 72.15.48.5, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0 RD version: 253701
BGP main routing table version 123
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 100:1 (default for vrf RTAMAELA)
*> 22.51.32.77/32 0.0.0.0 nolabel 16000
*>i78.22.11.2/32 172.16.4.1 16003 nolabel
*>i78.22.11.3/32 172.16.8.3 16003 nolabel <-- It receive label 16003, which is wrong. it should receive label 16054.
*>i93.22.15.61/32 172.16.4.1 16003 nolabel
Processed 4 prefixes, 4 paths
RP/0/RSP1/CPU0:ASR-9006-01#
Rivalino -
Troubleshooting MPLS L2 and L3 VPNs
Would really appriciate if someone could suggest a link with details on troubleshooting MPLS L2 and L3 VPNs.
Buy 'Troubleshooting Virtual Private Networks'
(ISBN 1587051044):
www.ciscopress.com/1587051044
It includes:
About 150+ pages on MPLS layer 3 VPNs (in-depth troubleshooting/troubleshooting case studies/etc).
About 80+ pages on AToM (Martini draft) - technology/config/in-depth troubleshooting.
Then there's (off the top of my head) about 70+ pages
on L2TPv3 pseudowire (technology/config/in-depth
troubleshooting) just in case you want to compare
pseudowire technologies :)
And also about 100 pages of in-depth IPsec
troubleshooting, etc, etc.
You can download a 40 page
excerpt of the MPLS layer 3 VPN troubleshooting
chapter from the Cisco Press website. -
Hi
We have just bought an Apple Time Capsule with 3TB of storage, to make backups of our users macbooks. It works fine at the office1 where it is located, but from our other office, time machine backup doesn't work. The offices are connected through a 100Mbit MPLS connection with no firewall - everybody in office1 can see everything at office2, and vice versa. The users at office2 can ping the time capsule, and they can also browse network shares on it.
The only thing that doesn't work, are time machine backups.
The only difrence I can imagine is, that the the machines at office2 are on a different IP subnet, that is being routed through the MPLS connection.
Is there a problem with the AFP perhaps? SMB and ping works fine, my guess is, that AFP doesn't like the fact that the clients are on a different subnet than the time capsule. But what can be done about this?
Best regards
Peter BakThanks Linc ......you were right on the money. Your help has been awsome. I spent 3 hours last night doing stuff with out any solutions. May I ask you another question if you have the time and patience please. My orriginal setup was 2 windows laptops with XP on them connected with a timecapsule attached to a router. Hence the time capsule made a wireless signal aswell as being an external hard drive. On one of the laptops i have a printer attached to it which was shared so that the other computer could print documents through the network however the computer attached to the printer has to be on. Do you know what i have to do so these new 2 mac book pros can print to that printer? Thanks again for all your previous help. Nick
-
6500 sup 720 with MPLS, GRE and FWSM problem
We have 6500 sup 720 with MPLS configured and FWSM in transparent mode. We also terminate GRE tunnels on the same 6500.
After implementing the command “mls mpls tunnel-recir” GRE tunnels are hardware switched (which we want them to be), but we don’t have any more connection from locations thru GRE tunnels to servers behind FWSM.
Does anybody have idea how to solve this problem?Hi,
not sure what you mean exactly.
the command “mls mpls tunnel-recir” is needed to avoid packets corruption in cases where the Supervisor engine is handling both the GRE header encapsulation and the MPLS label stack imposition. Since it cannot do it in one single shot (without causing random corruption) recirculation is needed. Nevertheless its presence does not influence whether the GRE traffic is handled in hardware or in software. Even without it, IF THE GRE TUNNELS ARE CORRECTLY CONFIGURED (meaning that each GRE tunnels has its unique source address etc.), the traffic is handled in hardware.
However since you say that after you enabled it you don't have connectivty anymore I suppose that some issue related to recirculation is happening (i.e. traffic ends up in the wrong internal vlan after recirculation).
Unfortunately the support forum is not meant to help in this case as in-depth troubleshooting is required. For that you need a TAC case.
regards,
Riccardo -
im an Cisco certified engineer, i just want to have some inputs on mpls. that is our team got a plan to merg voip with MPLS. PLz give me any inputs on VOMPLS .. so that we can proceed with our project.
regards,
srini.
[email protected]hi ;
Actualy this is the Future .
In SP world we call it the NGN network starting step
NGN ( Next Generation Networks ) instead of having sepearte cloud for every thing you will Consoloidate every thing on one network. I would like to say that now there is lot of service providers world wide working on that and Actualy it is not a PLUG and PLAY process ,you need to read in MPLS TE MPLE QOS and lot of Voice over IP after that you need to understand Delay senstive applications and Voice requirment then you need to start testing and make sure that this network will move your Provider to the new Era -
Tracking ATM PVC enabled with MPLS
We are trying to identify a method where the ATM sub-interface enabled with Mpls shows line protocol UP but the ip reachability to the other side of the PVC is not there due to some issues in the ATM backbone.
Can we would be able to use the track 1 interface ip routing would help us . If so ,when it identifies the ip reachability on the PVC is done,will it log into the router or can it send to the management station. We are trying to deploy the same in 7600 switches running 12.2(18)SXF4.
Thanks
Regards
Anantha Subramanian NatarajanYou may want to think of using OAM for PVC management. As it sends Loopback cell echoes between the end points and upon failure to receive the configured Echo Cell replies it brings the corresponding PVC down.
This may as well prevent blackholing of the traffic till the OSPF adjacency is bought down due to the failure.
Here is a link on this feature:
http://www.cisco.com/warp/public/121/oam.html
HTH-Cheers,
Swaroop -
Hello. I am not to well versed in MPLS but would like to know if there is something that provides the PRO's and CON's to MPLS plus learning a little something to be able to help. I have a client that just moved into a ATM cloud with an ISP and they have some 75xx, 73xx, and 38xx routers and wants some documentation on cost, feasability, and if it's worth the effort. Anything would be helpful.
ThanksI think the best thing to do at this point is to familiarize yourself with MPLS. A good starting point would be www.cisco.com/go/mpls, which contains a wealth of information pertaining to MPLS.
Hope this helps, -
MIB walk for a router with MPLS enabled interfaces
To perform some testing in an agent I am building, I need a MIB walk for a router with MPLS enabled interfaces. I would greatly appreciate help with this MIB walk
You can do a walk-through of the MIB by running a command such as getmany -v2c public mplsLsrMIB . For detailed instructions refer http://cisco.com/en/US/docs/ios/12_2t/12_2t2/feature/guide/lsrmibt.html.
Maybe you are looking for
-
How do I access my iCloud email on my Windows Phone 7
I have an iCloud account but I can not access my email on my Windows Phone 7 Device that i have. it will not conect to the servers, I even manual put in the correct settings on the phone via Apples Support iCloud Mail Server Settings. Any help would
-
Service tax value required updating while posting GR in MIGO transaction
Dear Friends, We have a following scenario where service tax value required updating while posting Goods Receipt MIGO transaction. 1. Purchase Order created for first line item where Qty. 1 and Net Rate Rs.1000/- so total Gross value will be Rs.1000/
-
In Adobe Send, I have sent files several times now and when the recipient clicks the link to open, it says page cannot be found. This just started happening. What needs to be corrected?
-
Configuration of BW 7.0 in coordination with ECC 6.0
The SAP version is "4.6c", and BW is 7.0 (BI). Now , user wanna upgrade SAP version to ECC 6.0 What should to be configured within BW ? Just migration DataSource from 3.x to 7.0 ? Tks !
-
Since Windows 2003 Services ending we moving Sharepoint Services 3.0 to Windows 2008R2, Any help how can this be done ? We have 1 Server and single Farm. I have build New 2008 R2 Server and planning to restore Backup taken from Old server to this new