IP-Fast Reroute with MPLS remote LFA tunnels

I have a simple ring network with 4 3600Xs with IP/MPLS 10 gig backbone between all units (with OSPF running in the core).  Per the 3600 design guide I turned on IPFRR under OSPF for fast reroute of traffic around faults.  I have a l3vpn on the 3600s that I'm using to test.  The FRR works quite well when the repair route is a ECMP (equal cost multipath) route, I don't even notice an interruption in ping between l3vpn sites when an 'active' link goes down.
The issue arises when the repair route is a remote-LFA (loop free alternative) MPLS tunnel.  I've done a few tests, and the failover time when the repair route is a remote LFA tunnel is the same as when FRR isn't turned on at all, it's just the normal route convergence time and there is a significant traffic interruption (as compared to FRR when an ECMP route is the repair route).
The thing is I'm not quite sure how even to diagnose this.  I was thinking that maybe the remote FLA tunnel was using the link that failed, so it in essence was 'down' as well, hence the traffic interruption as routing fully converged.  But I looked at the remote-LFA interfaces, and as much as I understand them they are taking the right path out of the router anyway (that is, away from the link that would fail in order to activate the remote-LFA route).
Are there any resources or tips to help troubleshoot why these remote-LFA tunnel repair routes don't seem to be working well?

Thanks for the reply Nagendra.  When you ask if I've seen the back path installed in RIB/FIB, I'm not exactly sure what you mean.  I do see repair paths referncing remote LFAs on both the 3600 that would be the source and the destination of the test traffic.  Like this:
  * 172.16.0.3, from 10.10.10.3, 01:55:50 ago, via TenGigabitEthernet0/2
      Route metric is 2, traffic share count is 1
      Repair Path: 10.10.10.4, via MPLS-Remote-Lfa40
and on the other router:
  * 172.16.0.2, from 10.10.10.1, 01:56:34 ago, via TenGigabitEthernet0/1
      Route metric is 2, traffic share count is 1
      Repair Path: 10.10.10.2, via MPLS-Remote-Lfa32
If you're looking for some specific command output, let me know.

Similar Messages

  • MPLS: changing mtu-size on a fast reroute tunnel

    Hi,
    please can someone tell me how to change the MTU of a fast reroute tunnel interface ?
    Best regards

    You should be able to change the MTU on the interface tunnel itself. Using the "ip MTU xxx" command.
    Regards,
    Niranjan

  • Fast-Reroute on a ring with Gig Interface

    Hi,
    I'm trying to setup a fast-reroute option on a 4 routers ring connected through gige with OSPF.
    The main idea is to be able to use xconnect between A & B for normal route with a backup through C & D in case of Gig failure AB.
    I created two tunnel as follow on A
    interface Tunnel50
    ip unnumbered Loopback0
    tunnel mode mpls traffic-eng
    tunnel destination b.b.b.b
    tunnel mpls traffic-eng autoroute announce
    tunnel mpls traffic-eng priority 2 2
    tunnel mpls traffic-eng path-option 1 explicit name b-fast
    tunnel mpls traffic-eng fast-reroute node-protect
    interface Tunnel51
    ip unnumbered Loopback0
    tunnel mode mpls traffic-eng
    tunnel destination b.b.b.
    tunnel mpls traffic-eng autoroute announce
    tunnel mpls traffic-eng priority 5 5
    tunnel mpls traffic-eng path-option 10 explicit name b-low
    and configure A to B interfaces with
    mpls traffic-eng backup-path Tunnel51
    ip rsvp bandwidth
    router ospf
    mpls traffic-eng router-id Loopback0
    mpls traffic-eng area 0
    Same kind of conf on B side...
    Well, if I shutdown A to B interface, the fast-reroute doesn't seems to operate and the xconnect resume on a ospf convergence base latency.
    Should I also create tunnel A-C, A-D, B-C, B-D, ... like a full mesh ? or point to point on a ring AB, BC, CD, DA ?
    Thanks for your help.
    Laurent

    I tried a xconnect between br01 and br04.
    Routers are on a ring : br01(ge3/2)--(ge3/1)br03--br02--br04(ge3/2)--(ge3/1)br01
    tunnel50 is the straight route and tunnel 51 is the low route
    *Here the output from br04
    br04-7600-mtp02#show mpls traffic-eng tunnels brief
    Signalling Summary:
        LSP Tunnels Process:            running
        Passive LSP Listener:           running
        RSVP Process:                   running
        Forwarding:                     enabled
        Periodic reoptimization:        every 3600 seconds, next in 2803 seconds
        Periodic FRR Promotion:         Not Running
        Periodic auto-bw collection:    every 300 seconds, next in 103 seconds
    P2P TUNNELS/LSPs:
    TUNNEL NAME                      DESTINATION      UP IF      DOWN IF    STATE/PROT
    br04-7600-mtp02_t50              94.103.128.56    -         Gi3/2     up/up
    br04-7600-mtp02_t51              94.103.128.56    -         Gi3/1     up/up
    br01-7600-par01_t50              94.103.128.59    Gi3/2      -          up/up
    br01-7600-par01_t51              94.103.128.59    Gi3/1      -          up/up
    Displayed 2 (of 2) heads, 0 (of 0) midpoints, 2 (of 2) tails
    P2MP TUNNELS:
    Displayed 0 (of 0) P2MP heads
    P2MP SUB-LSPS:
    Displayed 0 P2MP sub-LSPs:
              0 (of 0) heads, 0 (of 0) midpoints, 0 (of 0) tails
    br04-7600-mtp02#show mpls traffic-eng fast-reroute database
    P2P Headend FRR information:
    Protected tunnel               In-label Out intf/label   FRR intf/label   Status
    Tunnel50                       Tun hd   Gi3/2:implicit-n Tu51:implicit-nu Ready
    P2P LSP midpoint frr information:
    LSP identifier                 In-label Out intf/label   FRR intf/label   Status
    P2MP Sub-LSP FRR information:
    *Sub-LSP identifier
    src_lspid[subid]->dst_tunid    In-label Out intf/label   FRR intf/label   Status
    * Sub-LSP identifier format: _[SubgroupID]->_
      Note: Sub-LSP identifier may be truncated.
      Use 'detail' display for the complete key.
    br04-7600-mtp02#show mpls traffic-eng tunnels backup
    br04-7600-mtp02_t51
      LSP Head, Admin: up, Oper: up
      Tun ID: 51, LSP ID: 35, Source: 94.103.128.59
      Destination: 94.103.128.56
      Fast Reroute Backup Provided:
        Protected i/fs: Gi3/2
        Protected LSPs/Sub-LSPs: 1, Active: 0
        Backup BW: any pool unlimited; inuse: 0 kbps
        Backup flags: 0x0
    *Here the output from br01
    br01-7600-par01#show mpls traffic-eng tunnels brief
    Signalling Summary:
        LSP Tunnels Process:            running
        Passive LSP Listener:           running
        RSVP Process:                   running
        Forwarding:                     enabled
        Periodic reoptimization:        every 3600 seconds, next in 2489 seconds
        Periodic FRR Promotion:         Not Running
        Periodic auto-bw collection:    every 300 seconds, next in 89 seconds
    P2P TUNNELS/LSPs:
    TUNNEL NAME                      DESTINATION      UP IF      DOWN IF    STATE/PROT
    br01-7600-par01_t50              94.103.128.59    -         Gi3/1     up/up
    br01-7600-par01_t51              94.103.128.59    -         Gi3/2     up/up
    br04-7600-mtp02_t50              94.103.128.56    Gi3/1      -          up/up
    br04-7600-mtp02_t51              94.103.128.56    Gi3/2      -          up/up
    Displayed 2 (of 2) heads, 0 (of 0) midpoints, 2 (of 2) tails
    P2MP TUNNELS:
    Displayed 0 (of 0) P2MP heads
    P2MP SUB-LSPS:
    Displayed 0 P2MP sub-LSPs:
              0 (of 0) heads, 0 (of 0) midpoints, 0 (of 0) tails
    br01-7600-par01#show mpls traffic-eng fast-reroute database
    P2P Headend FRR information:
    Protected tunnel               In-label Out intf/label   FRR intf/label   Status
    Tunnel50                       Tun hd   Gi3/1:implicit-n Tu51:implicit-nu Ready
    P2P LSP midpoint frr information:
    LSP identifier                 In-label Out intf/label   FRR intf/label   Status
    P2MP Sub-LSP FRR information:
    *Sub-LSP identifier
    src_lspid[subid]->dst_tunid    In-label Out intf/label   FRR intf/label   Status
    * Sub-LSP identifier format: _[SubgroupID]->_
      Note: Sub-LSP identifier may be truncated.
      Use 'detail' display for the complete key.
    br01-7600-par01#show mpls traffic-eng tunnels backup
    br01-7600-par01_t51
      LSP Head, Admin: up, Oper: up
      Tun ID: 51, LSP ID: 30, Source: 94.103.128.56
      Destination: 94.103.128.59
      Fast Reroute Backup Provided:
        Protected i/fs: Gi3/1
        Protected LSPs/Sub-LSPs: 1, Active: 0
        Backup BW: any pool unlimited; inuse: 0 kbps
        Backup flags: 0x0
    Thx,
    Laurent

  • MPLS TE Fast ReRoute

    Hi Experts,
    I'm just getting started with MPLS TE and wondering on how fast the "fast reroute" feature can be.
    I'm planning to create two tunnels for a specific traffic of my network, and looks like MPLS TE with FRR is the most reliable option if we are talking about a really 0% packet loss network.
    I saw on some documentations that with MPLS TE is possible to reroute the traffic with 50 ms of RTT  and no packet loss at all, considering that the backup tunnel is so reliable as the primary is.
    Is this true? I'm new on this subject so I would like to know more about what I could achieve in terms of high availability.
    Regards
    Paulo Varanda

    Hi,
    Yes MPLS-TE with FRR gives faster convergence in range of 50ms (usually 50ms is standard convergence time for SDH/Sonet network). But there are some pre-requisities for MPLS-TE FRR to provide that faster convergence.
    Tunnel Headend -- Router 1 --- Router 2 ---- Router 3--- Tunnel Tailend
                            -- Router 4 ---- Router 5----
    MPLS-TE FRR protects a particular link or a particular node.
    For link protection, the concept is to have a primary tunnel protected by a backup tunnel. The backup tunnel path should be on completely different and fault tolerant physical path when the primary tunnel path fails i.e. both the tunnels should not be in same SRLG links. In the above case if link between Router1-Router2-Router3 fails the tunnel should fallback over Router 4 and Router 5.
    Detecting the link or node goes down should require a keepalive mechanism, usually RSVP hellos are used to detect the failure.
    Node protection by default provides link protection. So when Router 2 goes down the traffic falls back over backup path.
    MPLS-TE FRR wokrs by pre-signalling LSP over both primary and secondary paths even before the failure occurs. In normal conditions (with multiple path-option), only when primary LSP on primary path goes down, LSP gets signalled over secondary path option.
    HTH
    Arun

  • MPLS TE Fast-Reroute question?

    Hi:
    I am trying to configure the mpls te fast-reroute command but the router complains!!
    I am running 12.4 Enterprise on a 3640.
    Does this only work on a 7200 and up?
    Thanks.

    Niraj,
    The 3640 doesn't support FRR. It does support traffic engineering but can not be used as the Point of Local Repair (PLR) router, which is the router where the backup tunnel is configured.
    Hope this helps,

  • RSVP Hello for Fast Reroute

    Hi,
    i am trying to set up TE tunnels with Fast Reroute protection. As i am using FastEthernet and GigabitEthernet links i need to use RSVP Hello for link or node failure detection.
    I have a little problem understanding and properly configuring the rsvp hello feature. The topology looks as follows:
    PE1 - P1 - PE2
      |                |
    P3 ----------- P4
    I am trying to set up fast reroute to  protect the connection PE1-P1-PE2 with backup path PE1-P3-P4-PE2. Both primary and backup tunnels are set up and working. I configure RSVP Hello on the link between PE1 and P1 with following commands on  PE1 and P1:
    PE1#configure terminal
    PE1(config)#interface Fastethernet 0/0
    PE1(config-if)ip rsvp signalling hello
    PE1(config-if)ip rsvp signalling hello refresh interval 50
    P1#configure terminal
    P1(config)#interface Fastethernet 0/0
    P1(config-if)ip rsvp signalling hello
    P1(config-if)ip rsvp signalling hello refresh interval 50
    After issuing the sh ip rsvp hello instance detail command on PE1 i can see that the RSVP hello session is active:
    Neighbor 195.10.3.1 (router ID: 3.3.3.3)  Source  195.10.3.254
        Type: Active    (sending requests)
        I/F:  FastEthernet0/0
        State:   Up        (Since: 2012 January Thursday 12 00:14:22 )
        Clients: Fast Reroute
        LSPs protecting: 1
        Missed acks: 4, IP DSCP: 0x30
        Refresh Interval (msec)
          Configured: 50
    However on the P1 router the output shows different values:
    Neighbor 195.10.3.254 (router ID: 33.33.33.33)  Source  195.10.3.1
        Type: Active    (sending requests)
        I/F:  FastEthernet0/0
        State:   Up        (Since: 2012 January Wednesday 11 23:43:18 )
        Clients: ReRoute
        LSPs protecting: 3
        Missed acks: 4, IP DSCP: 0x30
        Refresh Interval (msec)
          Configured: 2000
    The configuration guide for IOS 12.2SR refers to active instances:
    If a neighbor is unreachable when an LSP is ready  to be fast  rerouted, an active Hello instance is needed. Create an  active Hello  instance for each neighbor with at least one LSP in this  state.
    and to passive instances:
    Passive  Hello instances respond to Hello Request  messages (sending Ack  messages), but do not initiate Hello Request  messages and do not cause  LSPs to be fast rerouted.
    At this point i am not sure if i configured the RSVP Hello properly. After shuting the interface FastEthernet 0/0 on P1 down i do get the backup tunnel active and rerouted, but the convergence time is too slow. I would expect the convergence time to be 4xRSVP Hello interval which is 4x50=200ms. However, the testing revealed the convergence time to be round 2,5 seconds. My goal is to get the convergence time under 300ms.
    The question is, what is the actual difference between active and passive rsvp hello session? What does the Clients statement in the sh ip rsvp hello instance detail command mean and shoud i see the same interval on both ends of the link?
    If you need any other specification, i will provide any other show command outputs necessary.
    Thank you for any help or clarifiation.
    Adrian

    Adrian,
    Would it be possible to post the relevant tunnel configurations from your PE routers? From what you described, I am not sure if you want to achieve an MPLS path protection, MPLS link protection (NHOP) or MPLS node protection (NNHOP) here.
    Best regards,
    Peter

  • Fast-reroute: failure detection on ATM

    Hi,
    I have read in Designing MPLS TE Networks book that in essence fast-reroute feature failure detection of under 50ms is possible on pure POS interfaces and not possible on ATM interfaces which might also be runnig over POS.
    I have noticed a command that had been available since 12.1T - "oam ais-rdi". According to this command description, it is possible to bring down ATM PVC after receiving one AIS indicating cell.
    Isn't that exactly how it works on POS?
    Was this Ciscopress book so much outdated or am I missing something?
    Thanks,
    David

    Hello,
    there is a major difference (on a ms time scale) in POS and in ATM AIS. With POS interfaces one utilizes the error indication in the SONET/SDH frame. This means the first frame after failure detection of end OR intermediate systems (muxer) will contain the error bits needed to bring down the interface and trigger fast reroute.
    If you look into an ATM solution, then only ATM equipment will be able to insert ATM cells for failure indication. This means a mux will not be able to indicate anything. Only ATM switches or end devices might "help" out, but for them failure detection is maybe bound to keepalives as well.
    So you MIGHT get very low recovery times, but you could also have failure conditions only detectable by keepalive mechanisms. The latter are slower than in POS.
    Once you are relying on keepalives you could also use subsecond keepalives with OSPF or ISIS to achieve pretty fast recovery times.
    Hope this helps! Please rate all posts.
    Regards, Martin

  • HT200154 My apple tv is frozen sits on main page light blinks twice fast trying to use remote but will not change just goes to sleep or picture mode untill i unplg it then the same all over

    My apple tv just froze or hung , it was working then nothing, only way to power it up is to unplug then plug it in , but staays on the main screen frozen, if i try to use the remote it just flashes 2 x fast and does nothing, i assume its connected or i would not see my itunes etc

    Your Apple TV may have become paired with another remote. Hold the remote close to and pointed at the Apple TV, hold down the menu and Rewind buttons together for 6 seconds or until you see a broken chain icon on screen.

  • Problem with a simple GRE tunnel

    Hello everyone:
    I have a problem with a simple GRE tunnel, and can not make it work, the problem lies in the instruction "tunnel source loopback-0" if I use this command does not work, now if I use "tunnel source <ip wan >" if it works, someone can tell me why?
    Thanks for your help
    Router 1: 2811
    version 12.4
    no service password-encryption
    hostname cisco2811
    no aaa new-model
    ip cef
    interface Loopback0
    ip address 2.2.2.2 255.255.255.255
    interface Tunnel0
    ip address 10.10.1.1 255.255.255.0
    tunnel source Loopback0
    tunnel destination 217.127.XXX.188
    interface Tunnel1
    ip address 10.10.2.1 255.255.255.0
    tunnel source Loopback0
    tunnel destination 80.32.XXX.125
    interface FastEthernet0/0
    description LOCAL LAN Interface
    ip address 192.168.1.254 255.255.255.0
    ip nat inside
    ip virtual-reassembly
    duplex auto
    speed auto
    interface FastEthernet0/1
    description WAN Interface
    ip address 195.77.XXX.70 255.255.255.248
    ip nat outside
    ip virtual-reassembly
    duplex auto
    speed auto
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 195.77.XXX.65
    ip route 192.168.3.0 255.255.255.0 Tunnel0
    ip route 192.168.4.0 255.255.255.0 Tunnel1
    ip nat inside source route-map salida-fibra interface FastEthernet0/1 overload
    access-list 120 deny ip 192.168.1.0 0.0.0.255 192.168.3.0 0.0.0.255
    access-list 120 deny ip 192.168.1.0 0.0.0.255 192.168.4.0 0.0.0.255
    access-list 120 permit ip 192.168.1.0 0.0.0.255 any
    route-map salida-fibra permit 10
    match ip address 120
    Router 2: 2811
    version 12.4
    service password-encryption
    ip cef
    no ip domain lookup
    multilink bundle-name authenticated
    username admin privilege 15 password 7 104CXXXXx13
    interface Loopback0
    ip address 4.4.4.4 255.255.255.255
    interface Tunnel0
    ip address 10.10.1.2 255.255.255.0
    tunnel source Loopback0
    tunnel destination 195.77.XXX.70
    interface Ethernet0
    ip address 192.168.3.251 255.255.255.0
    ip nat inside
    ip virtual-reassembly
    hold-queue 100 out
    interface ATM0
    no ip address
    no ip route-cache cef
    no ip route-cache
    no atm ilmi-keepalive
    dsl operating-mode auto
    interface ATM0.1 point-to-point
    ip address 217.127.XXX.188 255.255.255.192
    ip nat outside
    ip virtual-reassembly
    no ip route-cache
    no snmp trap link-status
    pvc 8/32
    encapsulation aal5snap
    ip route 0.0.0.0 0.0.0.0 ATM0.1
    ip route 192.168.1.0 255.255.255.0 Tunnel0
    ip nat inside source route-map nonat interface ATM0.1 overload
    access-list 100 permit ip 192.168.3.0 0.0.0.255 192.168.1.0 0.0.0.255
    access-list 120 deny ip 192.168.3.0 0.0.0.255 192.168.1.0 0.0.0.255
    access-list 120 permit ip 192.168.3.0 0.0.0.255 any
    route-map nonat permit 10
    match ip address 120

    Hello, thank you for the answer, as to your question, I have no connectivity within the tunnel, whether from Router 1, I ping 10.10.1.2 not get response ...
    Now both routers remove the loopback, and the interface tunnel 0 change the tunnel source to "tunnel source " tunnel works perfectly, the problem is when I have to use the loopback. Unfortunately achieved when the tunnel work, this will have to endure multicast, and all the examples found carrying a loopback as' source '... but this is a step back ..
    Tunnel0 is up, line protocol is up
    Hardware is Tunnel
    Internet address is 10.10.1.1/24
    MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation TUNNEL, loopback not set
    Keepalive not set
    Tunnel source 2.2.2.2 (Loopback0), destination 217.127.XXX.188
    Tunnel protocol/transport GRE/IP
    Key disabled, sequencing disabled
    Checksumming of packets disabled
    Tunnel TTL 255
    Fast tunneling enabled
    Tunnel transmit bandwidth 8000 (kbps)
    Tunnel receive bandwidth 8000 (kbps)
    Last input 09:04:38, output 00:00:19, 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
    11101 packets output, 773420 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 unknown protocol drops
    0 output buffer failures, 0 output buffers swapped out

  • 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

  • MPLS over GRE Tunnel

    Hi,
    Can any one guide me about the benefits of MPLS over GRE Tunnels. Do this serve the purpose of MPLS (except TE, which is suppose is not possible on GRE Tunnels) as Layer-3 is already involved before Label Switching even starts.
    thanx and regards,
    Shakeel Ahmad

    I have a problem with MPLS over GRE. When i try to apply a policy to shape the traffic it seems that the default-class dosent see the mpls packets.
    Im trying to shape the traffic to 256k but it seems that the shaping never are activated.
    Anyone have any idea how to solve this?
    Example:
    class-map match-all PING
    match access-group 171
    policy-map class-default
    class PING
    bandwidth percent 15
    policy-map PING
    class class-default
    shape average 256000
    service-policy class-default
    INterfacexx
    service-policy output PING
    access-list 171 permit icmp any any

  • Fast Reroute on 7600 platform

    Hi,
    One quick enquiry, does 7600 platform support MPLS Fast Reroute.
    Practical inputs would be of immense help.
    Thanks
    Cheers
    ~sultan

    The MPLS Traffic EngineeringFast Reroute MIB provides Simple Network Management Protocol (SNMP)-based network management of the Multiprotocol Label Switching (MPLS) Fast Reroute (FRR) feature in Cisco IOS software.
    The Fast Reroute MIB has the following features:
    "Notifications can be created and queued.
    "Command-line interface (CLI) commands enable notifications, and specify the IP address to where the notifications will be sent.
    "The configuration of the notifications can be written into nonvolatile memory.
    Refer to MPLS Traffic EngineeringFast Reroute MIB section for more information
    http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_fast_rr_mib_ps6922_TSD_Products_Configuration_Guide_Chapter.html#wp1101191

  • Vrf-Lite with MPLS requires a PE at the customer side?

    Folks,
    Looking at a cisco doc, which gives a sample configuration of VRF lite with MPLS (multiple customers in the same building using same MPLS cloud). My question is that how is it done in the real world. Does the provider place a PE at the customer site? cause the connection between the CE and PE has to be a link that can carry dot1Q (ethernet or fast etheret) atleast the example shows that.
    Any real world experience would be highly appreciated.
    Thanks,

    Hi,
    the customer needs no PE router installed at his site.
    You can use vrf-lite (aka multi-vrf) even on a Cisco router, which does not support MPLS at all. On the CE each dot1Q subinterface can be placed in a vrf. All you need is a routing process started within the vrf being adjacent to the PE.
    Example CE:
    ip vrf CE-VRF1
    rd 65000:1
    interface FastEthernet0.100
    encapsualtion dot1Q 100
    ip vrf forwarding CE-VRF1
    ip address 10.1.1.1 255.255.255.0
    router ospf 100 vrf CE-VRF1
    network 10.1.1.1 0.0.0.0 area 1
    The PE would have MBGP and different RD and RTs defined, whatever is needed to setup VRFs in the provider network. Infact PE and CE each do not know about each others VRF configs at all.
    VRFs on the CE define a separate IP routing context (control plane). The separation on the data plane is done via dot1Q headers (frame-relay, ATM PVC etc. would do as well) on the link between CE and PE. In an MPLS network data plane separation is done via labels.
    Hope this helps
    Martin

  • How do I use iCloud to collaborate on a GarageBand project with a remotely located musician?

    How do I use iCloud to collaborate on a GarageBand project with a remotely located musician?  He is in Valencia, Spain, I am in Green Bay, Wisconsin.  We'd like to be able to work on the same GarageBand document together, laying down tracks, etc.
    Is there a tutorial I should look at?

    Are you using GarageBand on a Mac or on an iPad?
    With iCloud you can store your GarageBand projects in iCloud, so you can work on the same project on all your iPads, iPods, iPhones, and transfer it from your iDevices to your Mac.  But you cannot use iCloud to share a project between people with different AppleIDs.  
    To send GarageBand projects back and forth, compress the the ":band" files and mail them, if they are small enough or put them in a Dropbox or other cloud storage and mail the link.

  • IMac (Mountain Lion) does not pair with Apple Remote

    Hi,
    my iMac (2009, Mountain Lion) does pair with my remote. Otherwise the remote (or remotes, I tried two) are working fine with the iMac, it just wont pair.
    I need it to pair as I have an iMac and MPB and each having its own remote (each computer should react only to its remote, not the other computer remote)
    I googled this extensively, here is what I did so far:
    - obviously, trying the normail "pair remote" procedure as the support page says
    - checking that infrared remote pairing is enabled and no other remote is currenly paired
    - restarting Mac OS
    - removing and reinsterting battery in remote
    - making sure I am an Admin
    - disabling the remote function in Plex and killing all Plex (and EyeTV and similar) processes via Activity Monitor (thought they might somehow limite the OS control over the remote)
    - tried the same with another remote (does not pair as well)
    This is very annoying.
    Can anyone help out?
    Much appreciated

    Hi den,
    Does the remote remember which computer it is paired to? I though only the computer remebers that.
    In any case, currently there is not remote paired to any computer (both computers have clean new Mountain Lion installations). And I cannot pair any remote to any of my machines. In between, I tried with the laptop as well, and it is not pairing as well. I also tried an (old, still working) third remote... nothing is happening.
    Some apps seem to take control of the remote (e.g. pressing menu start Plex on my systems). Could that be the issue? Is there a Terminal command to give Mac OS back full control over the remote?
    Or could it be something else? 'Is there an app for that' a la ForcePair.app?
    Thank you
    p.s. this is the page that I was refering to ealier, not working for me

Maybe you are looking for