Re: [c-nsp] config example xconnent between ASR9K and 6500

2017-09-15 Thread Curtis Piehler 
It is a matter of managing labels on the devices that terminate the
attachment circuits.  You don't need to manage the P routers in between.
Coming from a Smart Edge world years ago we did static PWs.  When we
migrated to ASR9Ks static labeling was the only way I could interopt with
the Smart Edges until years later I figured out how to do dynamic PWs.

On Sep 15, 2017 10:37 PM, "Aaron Gould"  wrote:

> Oh ok I think I see what you mean.  So if you configure a PW with a static
> label, then does that mean you have to handle the pw on the next hop device
> or otherwise statically map the lsp at every hop along the way ?
>
>
>
> I’ve always done end to end dynamic pw’s… so I’m very familiar with mtu
> drama, soft (control plane) and hard (fwd’ing plane).
>
>
>
> -Aaron
>
>
>
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] config example xconnent between ASR9K and 6500

2017-09-15 Thread Aaron Gould 
Oh ok I think I see what you mean.  So if you configure a PW with a static 
label, then does that mean you have to handle the pw on the next hop device or 
otherwise statically map the lsp at every hop along the way ?

 

I’ve always done end to end dynamic pw’s… so I’m very familiar with mtu drama, 
soft (control plane) and hard (fwd’ing plane).

 

-Aaron

 

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] config example xconnent between ASR9K and 6500

2017-09-15 Thread Curtis Piehler 
If you use a static label MTUs should not matter.  If you do not use a
static label aka Dynamic PW then both segments will not come up unless MTUs
match.

On Sep 15, 2017 10:31 PM, "Aaron Gould"  wrote:

> Thanks Curtis, Are you saying that mtu’s only matter if you force a static
> mpls label ?
>
>
>
> -Aaron
>
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] config example xconnent between ASR9K and 6500

2017-09-15 Thread Aaron Gould 
Thanks Curtis, Are you saying that mtu’s only matter if you force a static mpls 
label ?

 

-Aaron

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] config example xconnent between ASR9K and 6500

2017-09-15 Thread Curtis Piehler 
Unless you force a static label, then MTUs don't matter :)

On Sep 15, 2017 10:11 PM, "Aaron Gould"  wrote:

>
> I put the MTU show command below, because we all know how much MTU is a
> gotcha in MPLS L2VPN's...
>
> **
>
> 9k...
>
> interface Loopback0
>  ipv4 address 10.101.0.15 255.255.255.255
>
> interface TenGigE0/0/0/1.103 l2transport
>  description eline - company-a
>  encapsulation dot1q 2995
>  rewrite ingress tag pop 1 symmetric
>  mtu 1518
>  l2protocol cpsv tunnel
>
> l2vpn
>  xconnect group eline
>   p2p company-a
>interface TenGigE0/0/0/1.103
>neighbor ipv4 10.101.44.2 pw-id 2995
>
> verify
>
> sh l2v xcon group eline xc-name company-a
> sh l2v xcon group eline xc-name company-a detail
> sh l2v xcon group eline xc-name company-a detail | in MTU
>
> **
>
> Sorry I don't have a 6500, but if 6500 is like a IOS-based ME3600
> then
>
> interface Loopback0
>  ip address 10.101.44.2 255.255.255.255
>
> interface GigabitEthernet0/5
>  description eline - company-a
>  switchport trunk allowed vlan none
>  switchport mode trunk
>  load-interval 30
>  service instance 1 ethernet
>   encapsulation default
>   l2protocol tunnel
>   xconnect 10.101.0.15 2995 encapsulation mpls
>mtu 1500
>
> verify...
>
> sh xcon int g0/5
> sh mpls l2 vc interface g0/5
> sh mpls l2 vc interface g0/5 detail
> sh mpls l2 vc interface g0/5 detail | in MTU
>
>
> - Aaron Gould
>
> ___
> cisco-nsp mailing list  cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] config example xconnent between ASR9K and 6500

2017-09-15 Thread Aaron Gould 

I put the MTU show command below, because we all know how much MTU is a
gotcha in MPLS L2VPN's...

**

9k...

interface Loopback0
 ipv4 address 10.101.0.15 255.255.255.255

interface TenGigE0/0/0/1.103 l2transport
 description eline - company-a
 encapsulation dot1q 2995
 rewrite ingress tag pop 1 symmetric
 mtu 1518
 l2protocol cpsv tunnel

l2vpn
 xconnect group eline
  p2p company-a
   interface TenGigE0/0/0/1.103
   neighbor ipv4 10.101.44.2 pw-id 2995

verify

sh l2v xcon group eline xc-name company-a
sh l2v xcon group eline xc-name company-a detail
sh l2v xcon group eline xc-name company-a detail | in MTU

**

Sorry I don't have a 6500, but if 6500 is like a IOS-based ME3600
then

interface Loopback0
 ip address 10.101.44.2 255.255.255.255

interface GigabitEthernet0/5
 description eline - company-a
 switchport trunk allowed vlan none
 switchport mode trunk
 load-interval 30
 service instance 1 ethernet
  encapsulation default
  l2protocol tunnel
  xconnect 10.101.0.15 2995 encapsulation mpls
   mtu 1500

verify...

sh xcon int g0/5
sh mpls l2 vc interface g0/5
sh mpls l2 vc interface g0/5 detail
sh mpls l2 vc interface g0/5 detail | in MTU


- Aaron Gould

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] ISIS/BFD Monitoring

2017-09-15 Thread Aaron Gould 
Kiwi syslogd or maybe splunk

-Aaron

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[c-nsp] config example xconnent between ASR9K and 6500

2017-09-15 Thread Alejandro Aristizabal 


Hi,

any body has a configuration of a xconnect between two cisco devices 
ASR9K and 6500 with  WS-SUP720-3B.


thnks to every one that can help me !!!
--

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] ASR 9k Multicast commands

2017-09-15 Thread Bryan Holloway 

On 9/15/17 12:33 AM, Mikael Abrahamsson wrote:

On Thu, 14 Sep 2017, Harry Hambi - Atos wrote:


HI All,
Logged onto a ASR9k and trying to find commands to show me the 
following :

BSR router


"show pim bsr", there are multiple commands under that.


Where pim is enabled.


"show pim interface"



... assuming you have the mcast PIE installed, of course.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] ISIS/BFD Monitoring

2017-09-15 Thread Alan Buxey 
RouteExplorer is a nice tool

(Commercial, from Packet Design)



On 15 Sep 2017 10:50 am, "Alex K."  wrote:

> Hello everyone,
>
> A customer of mine, ran into interesting problem - his monitoring software
> unable to provide him with a meaningful alert, in case a link goes down.
>
> As an ISP, they have lots of links, they run ISIS/BFD on all of them but,
> as it regularly happens with carriers, layer 2 never actually goes down
> (apart from SDH and dark fiber links, but those are few).
>
> I tested their equipment (mainly Cisco gear) and all it generates, is a
> trap wich basically say - "ISIS sission 657843347853325524854 went down".
>
> What they looking for, is a monitoring system, which on the scenario above,
> is able to provide the NOC team with a meaningful alert, such as: "ISIS
> status on interface  changed to down. Please notify
> the network team".
>
> Any suggestions and sharing of personal experience will be appreciated.
>
> Thank you.
> ___
> cisco-nsp mailing list  cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[c-nsp] ISIS/BFD Monitoring

2017-09-15 Thread Alex K. 
Hello everyone,

A customer of mine, ran into interesting problem - his monitoring software
unable to provide him with a meaningful alert, in case a link goes down.

As an ISP, they have lots of links, they run ISIS/BFD on all of them but,
as it regularly happens with carriers, layer 2 never actually goes down
(apart from SDH and dark fiber links, but those are few).

I tested their equipment (mainly Cisco gear) and all it generates, is a
trap wich basically say - "ISIS sission 657843347853325524854 went down".

What they looking for, is a monitoring system, which on the scenario above,
is able to provide the NOC team with a meaningful alert, such as: "ISIS
status on interface  changed to down. Please notify
the network team".

Any suggestions and sharing of personal experience will be appreciated.

Thank you.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/