[c-nsp] MPLS TE conver from IOS to IOS-XR

[Vitkovsky, Adam]

Well for auto-tunnel it's dynamic by definition right?
I'm not sure whether you might somehow specify NHs that auto-tunnels should use -doesn't make sense
Though you could use affinities in order to exclude some of the links used by auto-tunnels


adam

-----Original Message-----
From: Gmail [mailto:jstuxuhu0816 at gmail.com] 
Sent: Thursday, February 23, 2012 1:00 PM
To: Vitkovsky, Adam
Cc: Oliver Boehmer (oboehmer); cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] MPLS TE conver from IOS to IOS-XR

I know, but my situation is auto-tunnel mesh.

Thanks and regards,
Xu Hu

On 23 Feb, 2012, at 19:35, "Vitkovsky, Adam" <avitkovsky at emea.att.com> wrote:

> In XR you’ll configure it the same - “path-option 1 dynamic” or “path-option 1 explicit name” under the tunnel-te interface
> 
> adam
> ________________________________
> From: 许虎 [mailto:jstuxuhu0816 at gmail.com]
> Sent: Thursday, February 23, 2012 11:58 AM
> To: Vitkovsky, Adam
> Cc: Oliver Boehmer (oboehmer); cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] MPLS TE conver from IOS to IOS-XR
> 
> Yes, correct. One more thing, in the IOS we configure the " tunnel mpls traffic-eng path-option 1 dynamic"  to automatic calculate the path, now in the IOS-XR, no more?
> 
> Thanks/Xu Hu
> 在 2012年2月23日 下午6:15，Vitkovsky, Adam <avitkovsky at emea.att.com<mailto:avitkovsky at emea.att.com>>写道：
> I'm sorry the auto template is only used in ios
> In XR you can specify the autoroute announce under attribute set
> And than use that with the group
> 
> 
> adam
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net<mailto:cisco-nsp-bounces at puck.nether.net> [mailto:cisco-nsp-bounces at puck.nether.net<mailto:cisco-nsp-bounces at puck.nether.net>] On Behalf Of ??
> Sent: Thursday, February 23, 2012 10:48 AM
> To: Oliver Boehmer (oboehmer)
> Cc: cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] MPLS TE conver from IOS to IOS-XR
> Hi Oil,
> Below is my whole config of the ASR9K,  now the tunnel can up.
> 
> mpls traffic-eng
> interface TenGigE0/0/0/0
> !
> interface TenGigE0/1/0/0.1700
> !
> auto-tunnel mesh
> group 1
>  destination-list 1
> !
> group 2
>  destination-list 2
> !
> tunnel-id min 1001 max 2000
> !
> auto-tunnel backup
> tunnel-id min 2001 max 3000
> !
> reoptimize 25
> !
> mpls ldp
> graceful-restart
> traffic-eng auto-tunnel mesh
> group 1
> group 2
> !
> interface TenGigE0/0/0/0
> !
> interface TenGigE0/1/0/0.1700
> !
> router ospf 100
> area 0.0.0.0
> mpls traffic-eng
> mpls traffic-eng router-id Loopback0
> But i don't find the autoroute-announce under traffic-engineering submode
> or under the group 1& 2.
> 
> Many thanks.
> Hu Xu
> 
> 在 2012年2月21日 下午7:38，Oliver Boehmer (oboehmer) <oboehmer at cisco.com<mailto:oboehmer at cisco.com>>写道：
>> Hu,****
>> 
>> ** **
>> 
>> you indeed want to configure ****
>> 
>> ** **
>> 
>> rsvp****
>> 
>> interface ..****
>> 
>>   bandwidth …****
>> 
>> ** **
>> 
>> in order to be able to use non-zero banwdith reservations. That’s part of
>> your basic MPLS-TE config, which I didn’t include in my config example.. *
>> ***
>> 
>> By default, the bandwidth is zero on interfaces enabled for MPLS-TE (i.e.
>> the ones enabled under “mpls traffic-eng”).. ****
>> 
>> ** **
>> 
>>            oli****
>> 
>> ** **
>> 
>> *From:* 许虎 [mailto:jstuxuhu0816 at gmail.com<mailto:jstuxuhu0816 at gmail.com>]
>> *Sent:* 21 February 2012 10:03
>> *To:* Oliver Boehmer (oboehmer)
>> *Cc:* cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
>> 
>> *Subject:* Re: [c-nsp] MPLS TE conver from IOS to IOS-XR****
>> 
>>  ** **
>> 
>> The MPLS TE signaling usually uses the RSVP, but in the global
>> configuration i didn't see any RSVP configuration, why? Is the the default
>> configuraion? ****
>> 
>> ****
>> 
>> Many thanks.****
>> 
>> Hu Xu****
>> 
>> 在 2012年2月20日 下午9:03，Oliver Boehmer (oboehmer) <oboehmer at cisco.com<mailto:oboehmer at cisco.com>>写道：****
>> 
>> ok.. you can also leave out the “autoroute-announce” for the beginning,
>> then the tunnel won’t take any traffic and you will be able to check if
>> everything is set up correctly (i.e. the primary/mesh tunnels are being
>> built and the backups are being installed), without any impact to the live
>> traffic..****
>> 
>> ****
>> 
>>            oli****
>> 
>> ****
>> 
>> *From:* 许虎 [mailto:jstuxuhu0816 at gmail.com<mailto:jstuxuhu0816 at gmail.com>]
>> *Sent:* 20 February 2012 14:00
>> *To:* Oliver Boehmer (oboehmer)
>> *Subject:* Re: [c-nsp] MPLS TE conver from IOS to IOS-XR****
>> 
>> ****
>> 
>> Thanks, oil, i will try in the live network tomorrow.****
>> 
>> 在 2012年2月20日 下午6:16，Oliver Boehmer (oboehmer) <oboehmer at cisco.com<mailto:oboehmer at cisco.com>>写道：****
>> 
>> Hi,****
>> 
>> 
>> 
>>> Since now I can make sure the "Group" command in IOS-XR is the same to
>> the
>>> "Auto-Template" in IOS,  but my problem is that in the IOS
>> "Auto-Template" I
>>> can use the below command :
>>> 
>>> interface Auto-Template1
>>> mpls mtu 17916
>>> tunnel mpls traffic-eng autoroute announce
>>> tunnel mpls traffic-eng path-option 1 dynamic
>>> 
>>> but in the Group, we just have the below command:
>>> 
>>> XXXX(config-mpls-te)#auto-tunnel mesh
>>> XXXX(config-te-auto-mesh)#group 1 ?
>>>  attribute-set     Attribute-set name of type auto-mesh
>>>  destination-list  Destination-list (prefix-list) name
>>>  disable           Disable the mesh group
>>>  <cr>
>>> 
>>> So I am again wondering the group is not the same compared to the Auto-
>>> Template.****
>> 
>> you need to configure autoroute-announce and attribute-set, which you in
>> turn reference in the group..  look at the "autoroute announce" in the
>> config I sent.
>> As far as I know, path-option is always dynamic for auto-tunnel mesh in
>> XR, so no need to configure this.
>> 
>>       oli****
>> 
>> ****
>> 
>> ** **
>> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> <winmail.dat>