date:20200904

Re: Centurylink having a bad morning?

2020-09-04 Thread Tomas Lynch via NANOG

On Thu, Sep 3, 2020 at 2:37 PM Mark Tinka  wrote:

>
>
> On 31/Aug/20 17:57, Bryan Holloway wrote:
>
> > Not everyone will peer with you, notably, AS3356 (unless you're big
> > enough, which few can say.)
>
> I think Tomas meant more diverse peering, not peering with CL.
>

Oh, yes! Let's not start another "what's a tier one" war!

>
> Mark.
>
>

RE: rsvp-te admission control - i don't see it

2020-09-04 Thread Aaron Gould via NANOG

That’s it!  Thanks dip

 

Using “signalled-bandwidth 5000”  on headend te-tunnel int

 

 

RP/0/0/CPU0:r20#sh run int tt1

Fri Sep  4 13:27:14.833 CST

interface tunnel-te1

bandwidth 20

ipv4 unnumbered Loopback0

signalled-name r20--->r22

signalled-bandwidth 5000

autoroute announce

!

destination 10.20.0.22

path-option 10 dynamic

!

 

On HE…

 

RP/0/0/CPU0:r20#sh mpls traffic-eng tunnels name r20--->r22 | in and

Fri Sep  4 13:28:28.918 CST

Name: tunnel-te1  Destination: 10.20.0.22  Ifhandle:0x1d0 

Bandwidth Requested: 5000 kbps  CT0

Bandwidth: 5000 kbps (CT0) Priority:  7  7 Affinity: 0x0/0x

 

RP/0/0/CPU0:r20#sh rsvp reservation detail | in ate

Fri Sep  4 13:25:51.509 CST

Rate: 0 bits/sec. Burst: 1K bytes. Peak: 0 bits/sec.

State expires in 0.000 sec.

Rate: 500 bits/sec. Burst: 1K bytes. Peak: 5M bits/sec.

State expires in 358.630 sec.

 

RP/0/0/CPU0:r20#sh rsvp int   

Fri Sep  4 13:26:03.738 CST

 

*: RDM: Default I/F B/W % : 75% [default] (max resv/bc0), 0% [default] (bc1)

 

Interface MaxBW (bps)  MaxFlow (bps) Allocated (bps)  
MaxSub (bps) 

-  -  
-

GigabitEthernet0/0/0/0   750M*  750M 0 (  0%)   
 0*

GigabitEthernet0/0/0/1   750M*  750M5M (  0%)   
 0*

 

 

On transit lsr in core…

 

RP/0/0/CPU0:r24#sh rsvp session detail | in ate

Fri Sep  4 13:18:25.258 CST

   Tspec: avg rate=0, burst=1K, peak rate=0

   Fspec: avg rate=0, burst=1K, peak rate=0

   Tspec: avg rate=5M, burst=1K, peak rate=5M

   Fspec: avg rate=5M, burst=1K, peak rate=5M

 

RP/0/0/CPU0:r24#sh rsvp int

Fri Sep  4 13:18:33.508 CST

 

*: RDM: Default I/F B/W % : 75% [default] (max resv/bc0), 0% [default] (bc1)

 

Interface MaxBW (bps)  MaxFlow (bps) Allocated (bps)  
MaxSub (bps) 

-  -  
-

GigabitEthernet0/0/0/0   750M*  750M 0 (  0%)   
 0*

GigabitEthernet0/0/0/1   750M*  750M5M (  0%)   
 0*

Re: Project/Tool to deploy and maintain Edge Servers (VMs) remotely

2020-09-04 Thread JP

On Fri, Sep 04, 2020 at 07:52:07AM -0300, Douglas Fischer wrote:
> I'm looking for some tool to work as a Comand and Control of several remote
> nodes.
> 
> The idea is to have many-many nodes of Virtual Machines running on every
> ASN voluntarily to deploy some services spread everywhere we can.
> 
> 
> Something like a Call-Home, that allows the headquarter to track operation,
> health state, deploy commands.
> (Re-reading this phrase, it could sound like a newbie
>  hacker trying to create his own Mirai. haha...
>  It's not the case... I'm not on the dark side of the force.)
> 
> 
> I was thinking in use something like reverse ssh and ansible.
> But I thought that I'm probably reinventing part of the wheel.
> 
> I want to believe that there already some projects that would put-me some
> steps further on this project.
> 
> 
> Could anyone give-me some-tip?

Saltstack and Puppet typically fill this niche, although some folks have
used Chef in a similar fashion.

I usually advocate Saltstack for this. Broad offering with CM,
orchestration, C control bus, and more available. Ansible scales (in
fleet management as well as codebase complexity) quite poorly, so don't
waste time on that.

Contact me off-list if you want to chat more about this.

-J

Weekly Routing Table Report

2020-09-04 Thread Routing Analysis Role Account

This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.

The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.

Daily listings are sent to bgp-st...@lists.apnic.net

For historical data, please see http://thyme.rand.apnic.net.

If you have any comments please contact Philip Smith .

Routing Table Report   04:00 +10GMT Sat 05 Sep, 2020

Report Website: http://thyme.rand.apnic.net
Detailed Analysis:  http://thyme.rand.apnic.net/current/

Analysis Summary


BGP routing table entries examined:  821017
Prefixes after maximum aggregation (per Origin AS):  312846
Deaggregation factor:  2.62
Unique aggregates announced (without unneeded subnets):  395670
Total ASes present in the Internet Routing Table: 69243
Prefixes per ASN: 11.86
Origin-only ASes present in the Internet Routing Table:   59481
Origin ASes announcing only one prefix:   24693
Transit ASes present in the Internet Routing Table:9762
Transit-only ASes present in the Internet Routing Table:303
Average AS path length visible in the Internet Routing Table:   4.3
Max AS path length visible:  45
Max AS path prepend of ASN ( 37385)  42
Prefixes from unregistered ASNs in the Routing Table:   812
Number of instances of unregistered ASNs:   828
Number of 32-bit ASNs allocated by the RIRs:  9
Number of 32-bit ASNs visible in the Routing Table:   27491
Prefixes from 32-bit ASNs in the Routing Table:  127658
Number of bogon 32-bit ASNs visible in the Routing Table:30
Special use prefixes present in the Routing Table:1
Prefixes being announced from unallocated address space:427
Number of addresses announced to Internet:   2851819264
Equivalent to 169 /8s, 251 /16s and 79 /24s
Percentage of available address space announced:   77.0
Percentage of allocated address space announced:   77.0
Percentage of available address space allocated:  100.0
Percentage of address space in use by end-sites:   99.5
Total number of prefixes smaller than registry allocations:  274951

APNIC Region Analysis Summary
-

Prefixes being announced by APNIC Region ASes:   216770
Total APNIC prefixes after maximum aggregation:   63346
APNIC Deaggregation factor:3.42
Prefixes being announced from the APNIC address blocks:  210584
Unique aggregates announced from the APNIC address blocks:86530
APNIC Region origin ASes present in the Internet Routing Table:   10836
APNIC Prefixes per ASN:   19.43
APNIC Region origin ASes announcing only one prefix:   3038
APNIC Region transit ASes present in the Internet Routing Table:   1596
Average APNIC Region AS path length visible:4.5
Max APNIC Region AS path length visible: 28
Number of APNIC region 32-bit ASNs visible in the Routing Table:   5932
Number of APNIC addresses announced to Internet:  770417536
Equivalent to 45 /8s, 235 /16s and 163 /24s
APNIC AS Blocks4608-4864, 7467-7722, 9216-10239, 17408-18431
(pre-ERX allocations)  23552-24575, 37888-38911, 45056-46079, 55296-56319,
   58368-59391, 63488-64098, 64297-64395, 131072-141625
APNIC Address Blocks 1/8,  14/8,  27/8,  36/8,  39/8,  42/8,  43/8,
49/8,  58/8,  59/8,  60/8,  61/8, 101/8, 103/8,
   106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8,
   116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8,
   123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8,
   163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8,
   203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8,
   222/8, 223/8,

ARIN Region Analysis Summary


Prefixes being announced by ARIN Region ASes:240383
Total ARIN prefixes after maximum aggregation:   110652
ARIN Deaggregation factor: 2.17
Prefixes being announced from the ARIN address blocks:   237989
Unique aggregates announced from the ARIN address blocks:116491
ARIN Region origin ASes present in the Internet Routing Table:18558
ARIN Prefixes per ASN:12.82
ARIN

Re: rsvp-te admission control - i don't see it

2020-09-04 Thread dip

can you try this
https://www.cisco.com/c/en/us/td/docs/ios_xr_sw/iosxr_r3-7/mpls/command/reference/gr37mpte.html#wp2134470


On Fri, Sep 4, 2020 at 10:26 AM  wrote:

> Thanks dip, let me know what you think.
>
> r20 is headend and r22 is tailend   r20>r22
>
> r22 is headed and r20 is tailend  r22>r20
>
> RP/0/0/CPU0:r20#sh run int tt1
>
> Fri Sep  4 12:25:09.198 CST
>
> interface tunnel-te1
>
> bandwidth 20
>
> ipv4 unnumbered Loopback0
>
> signalled-name r20--->r22
>
> autoroute announce
>
> !
>
> destination 10.20.0.22
>
> path-option 10 dynamic
>
>
>
>
>
> RP/0/0/CPU0:r22#sh run int tt1
>
> Fri Sep  4 11:50:01.581 CST
>
> interface tunnel-te1
>
> bandwidth 20
>
> ipv4 unnumbered Loopback0
>
> signalled-name r22--->r20
>
> autoroute announce
>
> !
>
> destination 10.20.0.20
>
> path-option 10 dynamic
>
>
>
>
>
>
>
>
>
> *From:* dip 
> *Sent:* Friday, September 4, 2020 11:15 AM
> *To:* Aaron 
> *Cc:* Mark Tinka ; NANOG 
> *Subject:* Re: rsvp-te admission control - i don't see it
>
>
>
> What's the signalled bandwidth being reserved by the headend "R20" in your
> example? it's a hunch that you may not have that defined and it becomes
> Zero bandwidth LSPs.
>
>
>
> On Fri, Sep 4, 2020 at 9:09 AM  wrote:
>
> Thanks Mark, I have a tunnel traversing those interfaces.  Customer
> routers (r10, r30) can ping end to end via tunnel.
>
>
>
> Not sure if I’m missing something here.  I wonder if I’m not signaling for
> the rsvp bandwidth correctly.  I just don’t see any allocated bandwidth in
> the rsvp interfaces anywhere.
>
>
>
> Here’s one of the transit routers… r24…. Should I see “allocated (bps)”
> here ?
>
>
>
> RP/0/0/CPU0:r24#sh rsvp int
>
> Fri Sep  4 10:54:16.451 CST
>
>
>
> *: RDM: Default I/F B/W % : 75% [default] (max resv/bc0), 0% [default]
> (bc1)
>
>
>
> Interface MaxBW (bps)  MaxFlow (bps) Allocated (bps)
> MaxSub (bps)
>
> -  - 
> -
>
> GigabitEthernet0/0/0/0   750M*  750M 0 (
> 0%)0*
>
> GigabitEthernet0/0/0/1   750M*  750M 0 (
> 0%)0*
>
>
>
>
>
> Details….
>
>
>
> LSP/TE-tunnel has dynamic path option, but I disallow it to flow via r21…
> so tunnel takes the southbound path via r20-24-r25-r23-r22
>
>
>
> (2) unidirectional te-tunnels
>
>
>
> r20 is headend and r22 is tailend   r20>r22
>
> r22 is headed and r20 is tailend  r22>r20
>
>
>
>
>
> R10  R30
>
> |   |
>
> |   |
>
> r20-r21-r22
>
> |   |
>
> |   |
>
> |   |
>
> r24-r25-r23
>
>
>
> r20’s tunnel…
>
>
>
> RP/0/0/CPU0:r20#sh mpls traffic-eng tun br
>
> Fri Sep  4 10:59:51.509 CST
>
>
>
>  TUNNEL NAME DESTINATION  STATUS  STATE
>
>   tunnel-te1  10.20.0.22  up  up
>
>   r22--->r20  10.20.0.20  up  up
>
> Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails
>
> Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
>
>
>
> RP/0/0/CPU0:r20#sh mpls traffic-eng tun name tunnel-te1 | be count
>
> Fri Sep  4 10:59:54.309 CST
>
>   Node hop count: 4
>
>   Hop0: 10.20.1.21
>
>   Hop1: 10.20.1.18
>
>   Hop2: 10.20.1.17
>
>   Hop3: 10.20.1.14
>
>   Hop4: 10.20.1.13
>
>   Hop5: 10.20.1.10
>
>   Hop6: 10.20.1.9
>
>   Hop7: 10.20.0.22
>
> Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails
>
> Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
>
>
>
> r22’s tunnel….
>
>
>
> RP/0/0/CPU0:r22#sh mpl tr tun br
>
> Fri Sep  4 10:25:32.668 CST
>
>
>
>  TUNNEL NAME DESTINATION  STATUS  STATE
>
>   tunnel-te1  10.20.0.20  up  up
>
>   r20--->r22  10.20.0.22  up  up
>
> Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails
>
> Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
>
>
> RP/0/0/CPU0:r22#sh mpl tr tun name tunnel-te1 | be count
>
> Fri Sep  4 10:25:35.858 CST
>
>   Node hop count: 4
>
>   Hop0: 10.20.1.10
>
>   Hop1: 10.20.1.13
>
>   Hop2: 10.20.1.14
>
>   Hop3: 10.20.1.17
>
>   Hop4: 10.20.1.18
>
>   Hop5: 10.20.1.21
>
>   Hop6: 10.20.1.22
>
>   Hop7: 10.20.0.20
>
> Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails
>
> Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
>
>
>
> X = router number
>
> 10.20.0.0/16
>
> 10.20.0.X/24  - loopbacks
>
> 10.20.1.0/24  – /30’s between routers
>
> (numbered clockwise, lowest to highest, start at r20)
>
> (r20 is .1 , r21 is .2 , r21 is .5 , etc)
>
> 10.20.1.0/30  – r20---r21
>
> 10.20.1.4/30  – r21---r22
>
> 10.20.1.8/30  – r22---r23
>
> 10.20.1.12/30 – r23---r25
>
> 10.20.1.16/30 – r25---r24
>
> 10.20.1.20/30 – r24---r20
>
>
>
> r10#sh ip int br | in up
>
> GigabitEthernet3   1.0.0.2 YES

RE: rsvp-te admission control - i don't see it

2020-09-04 Thread aaron1

Thanks dip, let me know what you think.

r20 is headend and r22 is tailend   r20>r22

r22 is headed and r20 is tailend  r22>r20

RP/0/0/CPU0:r20#sh run int tt1

Fri Sep  4 12:25:09.198 CST

interface tunnel-te1

bandwidth 20

ipv4 unnumbered Loopback0

signalled-name r20--->r22

autoroute announce

!

destination 10.20.0.22

path-option 10 dynamic

 

 

RP/0/0/CPU0:r22#sh run int tt1

Fri Sep  4 11:50:01.581 CST

interface tunnel-te1

bandwidth 20

ipv4 unnumbered Loopback0

signalled-name r22--->r20

autoroute announce

!

destination 10.20.0.20

path-option 10 dynamic

 

 

 

 

From: dip  
Sent: Friday, September 4, 2020 11:15 AM
To: Aaron 
Cc: Mark Tinka ; NANOG 
Subject: Re: rsvp-te admission control - i don't see it

 

What's the signalled bandwidth being reserved by the headend "R20" in your 
example? it's a hunch that you may not have that defined and it becomes Zero 
bandwidth LSPs.

 

On Fri, Sep 4, 2020 at 9:09 AM mailto:aar...@gvtc.com> > 
wrote:

Thanks Mark, I have a tunnel traversing those interfaces.  Customer routers 
(r10, r30) can ping end to end via tunnel.

 

Not sure if I’m missing something here.  I wonder if I’m not signaling for the 
rsvp bandwidth correctly.  I just don’t see any allocated bandwidth in the rsvp 
interfaces anywhere.

 

Here’s one of the transit routers… r24…. Should I see “allocated (bps)” here ?

 

RP/0/0/CPU0:r24#sh rsvp int  

Fri Sep  4 10:54:16.451 CST

 

*: RDM: Default I/F B/W % : 75% [default] (max resv/bc0), 0% [default] (bc1)

 

Interface MaxBW (bps)  MaxFlow (bps) Allocated (bps)  
MaxSub (bps) 

-  -  
-

GigabitEthernet0/0/0/0   750M*  750M 0 (  0%)   
 0*

GigabitEthernet0/0/0/1   750M*  750M 0 (  0%)   
 0*

 

 

Details….

 

LSP/TE-tunnel has dynamic path option, but I disallow it to flow via r21… so 
tunnel takes the southbound path via r20-24-r25-r23-r22

 

(2) unidirectional te-tunnels

 

r20 is headend and r22 is tailend   r20>r22

r22 is headed and r20 is tailend  r22>r20

 

 

R10  R30

|   |

|   |

r20-r21-r22

|   |

|   |

|   |

r24-r25-r23

 

r20’s tunnel…

 

RP/0/0/CPU0:r20#sh mpls traffic-eng tun br

Fri Sep  4 10:59:51.509 CST

 

 TUNNEL NAME DESTINATION  STATUS  STATE

  tunnel-te1  10.20.0.22  up  up

  r22--->r20  10.20.0.20  up  up

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

 

RP/0/0/CPU0:r20#sh mpls traffic-eng tun name tunnel-te1 | be count

Fri Sep  4 10:59:54.309 CST

  Node hop count: 4

  Hop0: 10.20.1.21

  Hop1: 10.20.1.18

  Hop2: 10.20.1.17

  Hop3: 10.20.1.14

  Hop4: 10.20.1.13

  Hop5: 10.20.1.10

  Hop6: 10.20.1.9

  Hop7: 10.20.0.22

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

 

r22’s tunnel….

 

RP/0/0/CPU0:r22#sh mpl tr tun br

Fri Sep  4 10:25:32.668 CST

 

 TUNNEL NAME DESTINATION  STATUS  STATE

  tunnel-te1  10.20.0.20  up  up

  r20--->r22  10.20.0.22  up  up

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads


RP/0/0/CPU0:r22#sh mpl tr tun name tunnel-te1 | be count

Fri Sep  4 10:25:35.858 CST

  Node hop count: 4

  Hop0: 10.20.1.10

  Hop1: 10.20.1.13

  Hop2: 10.20.1.14

  Hop3: 10.20.1.17

  Hop4: 10.20.1.18

  Hop5: 10.20.1.21

  Hop6: 10.20.1.22

  Hop7: 10.20.0.20

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

 

X = router number

10.20.0.0/16  

10.20.0.X/24  - loopbacks

10.20.1.0/24    – /30’s between routers

(numbered clockwise, lowest to highest, start at r20)

(r20 is .1 , r21 is .2 , r21 is .5 , etc)

10.20.1.0/30    – r20---r21

10.20.1.4/30    – r21---r22

10.20.1.8/30    – r22---r23

10.20.1.12/30   – r23---r25

10.20.1.16/30   – r25---r24

10.20.1.20/30   – r24---r20

 

r10#sh ip int br | in up

GigabitEthernet3   1.0.0.2 YES manual upup

 

RP/0/0/CPU0:r30#sh ip int br | in Up

GigabitEthernet0/0/0/2 1.1.1.2 Up  Up   default

 

r10#trace 1.1.1.2   

Type escape sequence to abort.

Tracing the route to 1.1.1.2

VRF info: (vrf in

Re: rsvp-te admission control - i don't see it

2020-09-04 Thread dip

What's the signalled bandwidth being reserved by the headend "R20" in your
example? it's a hunch that you may not have that defined and it becomes
Zero bandwidth LSPs.

On Fri, Sep 4, 2020 at 9:09 AM  wrote:

> Thanks Mark, I have a tunnel traversing those interfaces.  Customer
> routers (r10, r30) can ping end to end via tunnel.
>
>
>
> Not sure if I’m missing something here.  I wonder if I’m not signaling for
> the rsvp bandwidth correctly.  I just don’t see any allocated bandwidth in
> the rsvp interfaces anywhere.
>
>
>
> Here’s one of the transit routers… r24…. Should I see “allocated (bps)”
> here ?
>
>
>
> RP/0/0/CPU0:r24#sh rsvp int
>
> Fri Sep  4 10:54:16.451 CST
>
>
>
> *: RDM: Default I/F B/W % : 75% [default] (max resv/bc0), 0% [default]
> (bc1)
>
>
>
> Interface MaxBW (bps)  MaxFlow (bps) Allocated (bps)
> MaxSub (bps)
>
> -  - 
> -
>
> GigabitEthernet0/0/0/0   750M*  750M 0 (
> 0%)0*
>
> GigabitEthernet0/0/0/1   750M*  750M 0 (
> 0%)0*
>
>
>
>
>
> Details….
>
>
>
> LSP/TE-tunnel has dynamic path option, but I disallow it to flow via r21…
> so tunnel takes the southbound path via r20-24-r25-r23-r22
>
>
>
> (2) unidirectional te-tunnels
>
>
>
> r20 is headend and r22 is tailend   r20>r22
>
> r22 is headed and r20 is tailend  r22>r20
>
>
>
>
>
> R10  R30
>
> |   |
>
> |   |
>
> r20-r21-r22
>
> |   |
>
> |   |
>
> |   |
>
> r24-r25-r23
>
>
>
> r20’s tunnel…
>
>
>
> RP/0/0/CPU0:r20#sh mpls traffic-eng tun br
>
> Fri Sep  4 10:59:51.509 CST
>
>
>
>  TUNNEL NAME DESTINATION  STATUS  STATE
>
>   tunnel-te1  10.20.0.22  up  up
>
>   r22--->r20  10.20.0.20  up  up
>
> Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails
>
> Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
>
>
>
> RP/0/0/CPU0:r20#sh mpls traffic-eng tun name tunnel-te1 | be count
>
> Fri Sep  4 10:59:54.309 CST
>
>   Node hop count: 4
>
>   Hop0: 10.20.1.21
>
>   Hop1: 10.20.1.18
>
>   Hop2: 10.20.1.17
>
>   Hop3: 10.20.1.14
>
>   Hop4: 10.20.1.13
>
>   Hop5: 10.20.1.10
>
>   Hop6: 10.20.1.9
>
>   Hop7: 10.20.0.22
>
> Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails
>
> Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
>
>
>
> r22’s tunnel….
>
>
>
> RP/0/0/CPU0:r22#sh mpl tr tun br
>
> Fri Sep  4 10:25:32.668 CST
>
>
>
>  TUNNEL NAME DESTINATION  STATUS  STATE
>
>   tunnel-te1  10.20.0.20  up  up
>
>   r20--->r22  10.20.0.22  up  up
>
> Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails
>
> Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
>
>
> RP/0/0/CPU0:r22#sh mpl tr tun name tunnel-te1 | be count
>
> Fri Sep  4 10:25:35.858 CST
>
>   Node hop count: 4
>
>   Hop0: 10.20.1.10
>
>   Hop1: 10.20.1.13
>
>   Hop2: 10.20.1.14
>
>   Hop3: 10.20.1.17
>
>   Hop4: 10.20.1.18
>
>   Hop5: 10.20.1.21
>
>   Hop6: 10.20.1.22
>
>   Hop7: 10.20.0.20
>
> Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails
>
> Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
>
>
>
> X = router number
>
> 10.20.0.0/16
>
> 10.20.0.X/24  - loopbacks
>
> 10.20.1.0/24  – /30’s between routers
>
> (numbered clockwise, lowest to highest, start at r20)
>
> (r20 is .1 , r21 is .2 , r21 is .5 , etc)
>
> 10.20.1.0/30  – r20---r21
>
> 10.20.1.4/30  – r21---r22
>
> 10.20.1.8/30  – r22---r23
>
> 10.20.1.12/30 – r23---r25
>
> 10.20.1.16/30 – r25---r24
>
> 10.20.1.20/30 – r24---r20
>
>
>
> r10#sh ip int br | in up
>
> GigabitEthernet3   1.0.0.2 YES manual up
> up
>
>
>
> RP/0/0/CPU0:r30#sh ip int br | in Up
>
> GigabitEthernet0/0/0/2 1.1.1.2 Up  Up
> default
>
>
>
> r10#trace 1.1.1.2
>
> Type escape sequence to abort.
>
> Tracing the route to 1.1.1.2
>
> VRF info: (vrf in name/id, vrf out name/id)
>
>   1 1.0.0.1 23 msec 5 msec 7 msec
>
>   2 10.20.1.21 [MPLS: Labels 24000/24010 Exp 0] 43 msec 50 msec 40 msec
>
>   3 10.20.1.17 [MPLS: Labels 19/24010 Exp 0] 49 msec 42 msec 41 msec
>
>   4 10.20.1.13 [MPLS: Labels 24001/24010 Exp 0] 42 msec 46 msec 46 msec
>
>   5 10.20.1.9 42 msec 38 msec 34 msec
>
>   6 1.1.1.2 55 msec *  44 msec
>
>
>
> RP/0/0/CPU0:r30#traceroute 1.0.0.2
>
> Fri Sep  4 15:25:10.129 UTC
>
>
>
> Type escape sequence to abort.
>
> Tracing the route to 1.0.0.2
>
>
>
> 1  1.1.1.1 29 msec  0 msec  0 msec
>
>  2  10.20.1.10 [MPLS: Labels 24000/24009 Exp 0] 49 msec  49 msec  49 msec
>
>  3  10.20.1.14 [MPLS: Labels 20/24009 Exp 0] 39 msec  49 msec  39 msec
>
>  4  10.20.1.18 [MPLS: Labels 24001/24009 Exp 0] 49 msec  39 msec  49

RE: rsvp-te admission control - i don't see it

2020-09-04 Thread aaron1

Thanks Mark, I have a tunnel traversing those interfaces.  Customer routers 
(r10, r30) can ping end to end via tunnel.

 

Not sure if I’m missing something here.  I wonder if I’m not signaling for the 
rsvp bandwidth correctly.  I just don’t see any allocated bandwidth in the rsvp 
interfaces anywhere.

 

Here’s one of the transit routers… r24…. Should I see “allocated (bps)” here ?

 

RP/0/0/CPU0:r24#sh rsvp int  

Fri Sep  4 10:54:16.451 CST

 

*: RDM: Default I/F B/W % : 75% [default] (max resv/bc0), 0% [default] (bc1)

 

Interface MaxBW (bps)  MaxFlow (bps) Allocated (bps)  
MaxSub (bps) 

-  -  
-

GigabitEthernet0/0/0/0   750M*  750M 0 (  0%)   
 0*

GigabitEthernet0/0/0/1   750M*  750M 0 (  0%)   
 0*

 

 

Details….

 

LSP/TE-tunnel has dynamic path option, but I disallow it to flow via r21… so 
tunnel takes the southbound path via r20-24-r25-r23-r22

 

(2) unidirectional te-tunnels

 

r20 is headend and r22 is tailend   r20>r22

r22 is headed and r20 is tailend  r22>r20

 

 

R10  R30

|   |

|   |

r20-r21-r22

|   |

|   |

|   |

r24-r25-r23

 

r20’s tunnel…

 

RP/0/0/CPU0:r20#sh mpls traffic-eng tun br

Fri Sep  4 10:59:51.509 CST

 

 TUNNEL NAME DESTINATION  STATUS  STATE

  tunnel-te1  10.20.0.22  up  up

  r22--->r20  10.20.0.20  up  up

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

 

RP/0/0/CPU0:r20#sh mpls traffic-eng tun name tunnel-te1 | be count

Fri Sep  4 10:59:54.309 CST

  Node hop count: 4

  Hop0: 10.20.1.21

  Hop1: 10.20.1.18

  Hop2: 10.20.1.17

  Hop3: 10.20.1.14

  Hop4: 10.20.1.13

  Hop5: 10.20.1.10

  Hop6: 10.20.1.9

  Hop7: 10.20.0.22

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

 

r22’s tunnel….

 

RP/0/0/CPU0:r22#sh mpl tr tun br

Fri Sep  4 10:25:32.668 CST

 

 TUNNEL NAME DESTINATION  STATUS  STATE

  tunnel-te1  10.20.0.20  up  up

  r20--->r22  10.20.0.22  up  up

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 1 (of 1) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads


RP/0/0/CPU0:r22#sh mpl tr tun name tunnel-te1 | be count

Fri Sep  4 10:25:35.858 CST

  Node hop count: 4

  Hop0: 10.20.1.10

  Hop1: 10.20.1.13

  Hop2: 10.20.1.14

  Hop3: 10.20.1.17

  Hop4: 10.20.1.18

  Hop5: 10.20.1.21

  Hop6: 10.20.1.22

  Hop7: 10.20.0.20

Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails

Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

 

X = router number

10.20.0.0/16

10.20.0.X/24  - loopbacks

10.20.1.0/24  – /30’s between routers

(numbered clockwise, lowest to highest, start at r20)

(r20 is .1 , r21 is .2 , r21 is .5 , etc)

10.20.1.0/30  – r20---r21

10.20.1.4/30  – r21---r22

10.20.1.8/30  – r22---r23

10.20.1.12/30 – r23---r25

10.20.1.16/30 – r25---r24

10.20.1.20/30 – r24---r20

 

r10#sh ip int br | in up

GigabitEthernet3   1.0.0.2 YES manual upup

 

RP/0/0/CPU0:r30#sh ip int br | in Up

GigabitEthernet0/0/0/2 1.1.1.2 Up  Up   default

 

r10#trace 1.1.1.2   

Type escape sequence to abort.

Tracing the route to 1.1.1.2

VRF info: (vrf in name/id, vrf out name/id)

  1 1.0.0.1 23 msec 5 msec 7 msec

  2 10.20.1.21 [MPLS: Labels 24000/24010 Exp 0] 43 msec 50 msec 40 msec

  3 10.20.1.17 [MPLS: Labels 19/24010 Exp 0] 49 msec 42 msec 41 msec

  4 10.20.1.13 [MPLS: Labels 24001/24010 Exp 0] 42 msec 46 msec 46 msec

  5 10.20.1.9 42 msec 38 msec 34 msec

  6 1.1.1.2 55 msec *  44 msec

 

RP/0/0/CPU0:r30#traceroute 1.0.0.2

Fri Sep  4 15:25:10.129 UTC

 

Type escape sequence to abort.

Tracing the route to 1.0.0.2

 

1  1.1.1.1 29 msec  0 msec  0 msec 

 2  10.20.1.10 [MPLS: Labels 24000/24009 Exp 0] 49 msec  49 msec  49 msec 

 3  10.20.1.14 [MPLS: Labels 20/24009 Exp 0] 39 msec  49 msec  39 msec 

 4  10.20.1.18 [MPLS: Labels 24001/24009 Exp 0] 49 msec  39 msec  49 msec 

 5  10.20.1.22 49 msec  49 msec  39 msec 

 6  1.0.0.2 69 msec  *  49 msec 

RP/0/0/CPU0:r30#

 

 

 

 

 

From: NANOG  On Behalf Of Mark Tinka
Sent: Thursday, September 3, 2020 10:58 PM
To: nanog@nanog.org
Subject: Re: rsvp-te admission control - i don't see it

 

 

On 3/Sep/20 22:20, aar...@gvtc.com   wrote:

Thanks, how do I see the control plane reservation?  I don’t seem to be seeing 
anything getting

Re: Project/Tool to deploy and maintain Edge Servers (VMs) remotely

2020-09-04 Thread Siyuan Miao

Saltstack / Chef may be the solution you need.

If you're already using ansible, how about ansible-pull?

On Fri, Sep 4, 2020 at 7:03 PM Jared Mauch  wrote:

>
>
> > On Sep 4, 2020, at 6:52 AM, Douglas Fischer 
> wrote:
> >
> > I'm looking for some tool to work as a Comand and Control of several
> remote nodes.
> >
> > The idea is to have many-many nodes of Virtual Machines running on every
> ASN voluntarily to deploy some services spread everywhere we can.
> >
> >
> > Something like a Call-Home, that allows the headquarter to track
> operation, health state, deploy commands.
> > (Re-reading this phrase, it could sound like a newbie
> >  hacker trying to create his own Mirai. haha...
> >  It's not the case... I'm not on the dark side of the force.)
> >
> >
> > I was thinking in use something like reverse ssh and ansible.
> > But I thought that I'm probably reinventing part of the wheel.
> >
> > I want to believe that there already some projects that would put-me
> some steps further on this project.
> >
> >
> > Could anyone give-me some-tip?
> >
>
> You may want to look at the NLNOG Ring both for examples, but also for how
> to have interesting views from around the world, similar to RIPE Atlas.
>
> - Jared
>
>

Re: Project/Tool to deploy and maintain Edge Servers (VMs) remotely

2020-09-04 Thread Jens Link

Douglas Fischer  writes:

> I was thinking in use something like reverse ssh and ansible.  But I
> thought that I'm probably reinventing part of the wheel.

If your familiar with ansible:  ansible-pull? 

"pulls playbooks from a VCS repo and executes them for the local host"

https://docs.ansible.com/ansible/2.5/cli/ansible-pull.html

Other tools like e.g. puppet use an agent that querys a central server
on a regluar basis.

Jens
-- 

| Delbrueckstr. 41| 12051 Berlin, Germany   | +49-151-18721264 |
| http://blog.quux.de | jabber: jensl...@quux.de| ---  |

Re: Project/Tool to deploy and maintain Edge Servers (VMs) remotely

2020-09-04 Thread Jared Mauch




> On Sep 4, 2020, at 6:52 AM, Douglas Fischer  wrote:
> 
> I'm looking for some tool to work as a Comand and Control of several remote 
> nodes.
> 
> The idea is to have many-many nodes of Virtual Machines running on every ASN 
> voluntarily to deploy some services spread everywhere we can.
> 
> 
> Something like a Call-Home, that allows the headquarter to track operation, 
> health state, deploy commands.
> (Re-reading this phrase, it could sound like a newbie
>  hacker trying to create his own Mirai. haha...
>  It's not the case... I'm not on the dark side of the force.)
> 
> 
> I was thinking in use something like reverse ssh and ansible.
> But I thought that I'm probably reinventing part of the wheel.
> 
> I want to believe that there already some projects that would put-me some 
> steps further on this project.
> 
> 
> Could anyone give-me some-tip?
> 

You may want to look at the NLNOG Ring both for examples, but also for how to 
have interesting views from around the world, similar to RIPE Atlas.

- Jared

Project/Tool to deploy and maintain Edge Servers (VMs) remotely

2020-09-04 Thread Douglas Fischer

I'm looking for some tool to work as a Comand and Control of several remote
nodes.

The idea is to have many-many nodes of Virtual Machines running on every
ASN voluntarily to deploy some services spread everywhere we can.


Something like a Call-Home, that allows the headquarter to track operation,
health state, deploy commands.
(Re-reading this phrase, it could sound like a newbie
 hacker trying to create his own Mirai. haha...
 It's not the case... I'm not on the dark side of the force.)


I was thinking in use something like reverse ssh and ansible.
But I thought that I'm probably reinventing part of the wheel.

I want to believe that there already some projects that would put-me some
steps further on this project.


Could anyone give-me some-tip?

Thanks in advance.


-- 
Douglas Fernando Fischer
Engº de Controle e Automação

Re: Centurylink having a bad morning?

RE: rsvp-te admission control - i don't see it

Re: Project/Tool to deploy and maintain Edge Servers (VMs) remotely

Weekly Routing Table Report

Re: rsvp-te admission control - i don't see it

RE: rsvp-te admission control - i don't see it

Re: rsvp-te admission control - i don't see it

RE: rsvp-te admission control - i don't see it

Re: Project/Tool to deploy and maintain Edge Servers (VMs) remotely

Re: Project/Tool to deploy and maintain Edge Servers (VMs) remotely

Re: Project/Tool to deploy and maintain Edge Servers (VMs) remotely

Project/Tool to deploy and maintain Edge Servers (VMs) remotely

12 matches

Site Navigation

Mail list logo

Footer information