Re: Hurricane Maria: Summary of communication status - and lack of

[Wayne Bouchard]

On Tue, Sep 26, 2017 at 12:52:29AM -0400, Sean Donelan wrote:
> T-Mobile also mentions while T-Mobile's field engineering crew was at the 
> Luis Mu??oz Mar??n Airport, they were drafted to help install a generator 
> for the FAA Control Tower. That's one way to help get your supplies on the 
> island.

You know, that's a really good point. In such situations, the sooner
you can get the basic infrastructure operational again and
transportation, electrical systems, and fuel distribution (generators
have to run on something...) in particular, the faster everything can
start coming back together. First and foremost, this means making the
place habitable again so you actually have customers to serve. So any
time spent doing something like what is related above is extremely
worth while and can only serve to facilitate future work for everyone
on the island.


---
Wayne Bouchard
w...@typo.org
Network Dude
http://www.typo.org/~web/

Re: Hurricane Maria: Summary of communication status - and lack of

[Sean Donelan]

It looks like someone kicked the cellular carriers public relations people 
into gear. Today, instead of the normal "we care" messages; they released 
statements providing more concrete details about their restoration 
activity in PR and USVI.


Overall, 91.2% cell sites out of service in Puerto Rico. 34 of 78 counties 
have 100% cell sites out of service.  This will continue to change up and 
down, as sites are restored and circuits are damaged by cleanup activity.


There are over 2,671 cell sites on Puerto Rico and 106 cell sites in U.S. 
Virgin Islands.  As carriers bring in tens of generators and repair 
equipment at a time, gives you some idea how long restoration will take.



In alphabetical order...

ATT:
"We continue to send aircraft with essential supplies and network 
resources as we help the people of Puerto Rico. These flights include 
portable temporary cell sites, high capacity generators to provide 
temporary power, and other larger network equipment on cargo planes and 
barges to help restore services on the island. We planning to set up a 
number of portable cell sites in the San Juan area as soon as possible.


So far, we’ve sent multiple flights carrying the following supplies:
More than 30 generators
5,000+ gallons of water
We are also focused on network restoration in the U.S. Virgin Islands are 
bringing additional resources there."



Claro (google translate from Spanish):
They reported that in the metropolitan area specifically, Claro's signal 
was already reaching 31 percent of customers in San Juan, 22 percent in 
Guaynabo and 18 percent in Carolina and Bayamón.


At the island level, the Claro signal is up in 14 municipalities today, 
covering an average of 20 percent of the clients in Aguada, Manatí, 
Mayaguez, San Germán, Cabo Rojo, Trujillo Alto, Dorado, Camuy, 
Quebradillas, Humacao, Juncos , Caguas, Aguadilla and Toa Baja.


That number will increase in the coming days.


Sprint:
"A vessel has already arrived in Puerto Rico with the generators and parts 
required to begin the work. In turn, a body of over 40 Sprint engineers 
and technicians in the United States were sent to the Island to join the 
local technical staff, coordinate the delivery of the equipment received 
and continue work to speed up the communication.
A second shipment will arrive on the island this Wednesday, September 27 
with additional spare parts and materials."



T-Mobile:
"The damage to the infrastructure is unprecedented, but equally it is the 
support we are receiving from T-Mobile US. Between Saturday and Sunday, 
six MD11 cargo planes and one AM124 (second largest cargo plane in the 
world) arrived with 80 generators, 16 trucks, equipment to build 100 
communication facilities. More cargo planes will arrive today with more 
equipment and personnel."


T-Mobile also mentions while T-Mobile's field engineering crew was at the 
Luis Muñoz Marín Airport, they were drafted to help install a generator 
for the FAA Control Tower. That's one way to help get your supplies on the 
island.



If you have information about other telecommunication providers in Puerto 
Rico or U.S. Virgin Islands, let me know.




Due to damage to the FAA communications and guidance systems, only a 
dozen or so commercial flights can land during daylight hours each day. 
Airlines report over 20,000 people on standby lists, and nearly 1,000 
people waiting at the airport for any flight.


The Port of San Juan is open, daylight hours only, and receiving freight 
barges. While there is a plenty of fuel, food and supplies at the port; 
getting truck drivers to the port and damage/blocked roads is slowing 
distribution of supplies to the rest of the island. U.S. Mail and other 
express delivery companies still do not have service in Puerto Rico. 
Limited U.S. Mail hand-out service is available at a few post offices in 
U.S. Virgin Islands.

Re: Hurricane Maria: Summary of communication status - and lack of

[Mike Hammett]

You're assuming the WISP isn't providing infrastructure to critical facilities. 




- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

- Original Message -

From: "Jean-Francois Mezei"  
To: nanog@nanog.org 
Sent: Monday, September 25, 2017 6:55:41 PM 
Subject: Re: Hurricane Maria: Summary of communication status - and lack of 

On 2017-09-24 17:13, Sean Donelan wrote: 

> I'm not sure what clearances they are waiting for. If they are already in 
> Puerto Rico, self-sufficient, and respect curfews and other emergency 
> responders, they should be able to start local restoration and recovery 
> activities. 

Priority is to restore communications to emergency responders, restore 
power to hospitals and other critical infrastructure). So workers that 
clear roads, remove dangling electrical wires would prioritize fixing of 
that critical infrastructure. That road you need cleared to get to your 
fixed wireless antenna will wait. 

Similarly, I get the impression that all cargo capacity into the island 
is still controlled to prioritize essentials. So those spare circuit 
board you need to fix a router have to wait. 

Also, with residences overwhelmingly without power, fixing the "normal" 
ISP business won't do much when nobody can use it. It is best to focus 
on wi-fi in central locations such as shelters, and cellular for first 
responders and others. 

There are good reasons local governments work out disaster plans because 
they need to identify in advance what gets priority after a disaster. 

Re: Hurricane Maria: Summary of communication status - and lack of

[Jean-Francois Mezei]

On 2017-09-24 17:13, Sean Donelan wrote:

> I'm not sure what clearances they are waiting for.  If they are already in 
> Puerto Rico, self-sufficient, and respect curfews and other emergency 
> responders, they should be able to start local restoration and recovery 
> activities.

Priority is to restore communications to emergency responders, restore
power to hospitals and other critical infrastructure). So workers that
clear roads, remove dangling electrical wires would prioritize fixing of
that critical infrastructure.  That road you need cleared to get to your
fixed wireless antenna will wait.

Similarly, I get the impression that all cargo capacity into the island
is still controlled to prioritize essentials. So those spare circuit
board you need to fix a router have to wait.

Also, with residences overwhelmingly without power, fixing the "normal"
ISP business won't do much when nobody can use it. It is best to focus
on wi-fi in central locations such as shelters, and cellular for first
responders and others.

There are good reasons local governments work out disaster plans because
they need to identify in advance what gets priority after a disaster.

Re: Hurricane Maria: Summary of communication status - and lack of

[Sean Donelan]

As of this morning, the ILEC Claro is reporting

8 central offices have voice, data and long distance service operating, 
mostly in metro areas.  This does not include outside plant or local loops 
serving customers.


Central offices serving 55 of 78 municipalities have local voice service, 
no inter-office or long-distance service.  Again, not including the local 
loop to a customer.


27% of cell sites in service, mostly in the north and east parts of the 
island, operating.  I'm not sure if this is 27% of all cell sites on the 
island, or 27% of cell sites only in the north and east.


Other providers say they are working to restore service, but are not 
releasing specific data about their network status (AT&T, Open Mobile, 
Sprint, T-Mobile). Cable provider, LibertyPR, hasn't said anything to local 
reporters that I could find in any of the PR newspaper websites; and 
appears to be completely out of service.


There are several competitive providers and small providers I don't have 
information about in PR.  I just don't know the market.  If anyone has 
status about any small providers operating, let me know their status.

Open-IX BCOP Committee Call for Volunteers

[Chris Grundemann]

Pardon the interruption.

There is a new effort underway to ensure that BCOP has a home in North
America and your help is needed.

Following the publication of the Open-IX Document Development Policy (OIX
DDP) and the formation of the Best Current Operational Practices committee
(BCOP) , the Open-IX Board of
Directors is now seeking volunteers to take on this valuable work.

Open-IX Best Current Operational Practices (BCOP) Committee members are
expected to seek out subject matter experts and encourage the documentation
of BCOPs from the global network engineering community. This is typically
done through activity on mailing lists, conversations at industry events,
and leveraging personal relationships. Committee members are further
expected to shepherd appropriate documents through the process from Appeal
to published BCOP, including updates to existing documents as needed.

If you share a passion for sharing knowledge, increasing the resiliency and
efficiency of the global internet infrastructure, and have a few hours a
month to dedicate to this effort, we encourage you to volunteer! Please
send your name, email address, and a brief statement of interest to
cgrundemann  open-ix.org.

While we continuously seek new voices for all committees, this call is
expected to close on 31 October, 2017. Please submit before that time to be
considered for an immediate opening on the BCOP committee.

Thank you,
~Chris

RE: DHCPv6-PD -> Lack of route injection in RFC

[mohamed.boucadair]

Dear Steve, 

We used to have this in the IETF: 
https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-03 and 
https://tools.ietf.org/html/draft-petrescu-relay-route-pd-problem-00. 

We abandoned that effort because there wasn't sufficient support for it at that 
time. 

Cheers,
Med

> -Message d'origine-
> De : NANOG [mailto:nanog-bounces+mohamed.boucadair=orange@nanog.org]
> De la part de Steve Teusch
> Envoyé : vendredi 22 septembre 2017 09:12
> Cc : nanog@nanog.org
> Objet : DHCPv6-PD -> Lack of route injection in RFC
> 
> I am running into venders that do not support injection of a delegated
> route when operating as a DHCPv6 relay (or server for that matter).
> Brocade supports this, but I am not finding this as part of any of the
> RFC's.  This is to deliver home ISP service, so it is very important or
> return packets won't go to the client unless the route is manually added
> as a routing protocol is not an option.  There should be a MUST activity
> for this somewhere.
> 
> Anyone know what gives?

Re: Regex expression

[TR Shaw]

\d{12,}

> On Sep 25, 2017, at 9:31 AM, craig washington  
> wrote:
> 
> Hello all, not sure if this is the right place for this.
> 
> I am not the best with Regex and was looking for an expression in a Juniper 
> that will match on only so many numbers.
> 
> Meaning, I am looking at the mpls lsp statistics "show mpls lsp transit 
> statistics" and I only want to see the LSP's that have larger Bytes, for 
> instance I only want to see stuff that has at least 12 digits or longer.
> 
> 
> 
> Any help would be greatly appreciated, and if this is the wrong thing to ask 
> here, I have no qualms with that either 😊
> 
> 
> Thanks again.
> 



signature.asc
Description: Message signed with OpenPGP

Re: Regex expression

[Job Snijders]

Hi Craig,

You are probably best off by reaching out to the Juniper NSP mailing list
at https://puck.nether.net/mailman/listinfo/juniper-nsp

Kind regards,

Job

On Mon, Sep 25, 2017 at 3:31 PM, craig washington <
craigwashingto...@hotmail.com> wrote:

> Hello all, not sure if this is the right place for this.
>
> I am not the best with Regex and was looking for an expression in a
> Juniper that will match on only so many numbers.
>
> Meaning, I am looking at the mpls lsp statistics "show mpls lsp transit
> statistics" and I only want to see the LSP's that have larger Bytes, for
> instance I only want to see stuff that has at least 12 digits or longer.
>
>
>
> Any help would be greatly appreciated, and if this is the wrong thing to
> ask here, I have no qualms with that either 😊
>
>
> Thanks again.
>
>

Regex expression

[craig washington]

Hello all, not sure if this is the right place for this.

I am not the best with Regex and was looking for an expression in a Juniper 
that will match on only so many numbers.

Meaning, I am looking at the mpls lsp statistics "show mpls lsp transit 
statistics" and I only want to see the LSP's that have larger Bytes, for 
instance I only want to see stuff that has at least 12 digits or longer.



Any help would be greatly appreciated, and if this is the wrong thing to ask 
here, I have no qualms with that either 😊


Thanks again.

RE: DHCPv6-PD -> Lack of route injection in RFC

[Aaron Gould]

I don't know about brocade, but here's what I see in Junos and IOS...


dhcpv6 relay binding seen...

{master:0}
agould@eng-lab-5048-2> show dhcpv6 relay binding routing-instance three
Prefix  Session Id  Expires  StateInterfaceClient
DUID
2699:2699:0:7::100/128  199 2591002  BOUNDirb.26
LL_TIME0x1-0x1861ed8c-e8:03:9a:eb:0d:21

that same binding above is seen as a /128 route of type
access-internal...

{master:0}
agould@eng-lab-5048-2> show route table three.inet6.0 2699:2699:0:7::100/128

three.inet6.0: 16 destinations, 38 routes (16 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2699:2699:0:7::100/128
   *[Access-internal/12] 1w5d 03:19:06
> to fe80::fd61:6bfe:da75:4801 via irb.26

---

dhcpv6 relay binding seen...

eng-lab-3600-1#sh ipv6 dhcp relay binding vrf three

Prefix: 2699:2699:FE00:30::/64 (Vlan26)
  DUID: 00030001B0B2DCCB1D1E
  IAID: Unknown
  lifetime: 2592000
  expiration: 06:21:48 CDT Oct 25 2017

that same binding above is seen as a /64 route of type static...

eng-lab-3600-1#sh ipv6 route vrf three 2699:2699:FE00:30::/64
Routing entry for 2699:2699:FE00:30::/64
  Known via "static", distance 1, metric 0
  Route count is 1/1, share count 0
  Routing paths:
FE80::B2B2:DCFF:FECB:1D1E, Vlan26
  Last updated 3w4d ago

eng-lab-3600-1#sh ipv6 route vrf three static
IPv6 Routing Table - three - 18 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
   B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
   IA - ISIS interarea, IS - ISIS summary, ND - ND Default, NDp - ND
Prefix
   DCE - Destination, NDr - Redirect, O - OSPF Intra, OI - OSPF Inter
   OE1 - OSPF ext 1, OE2 - OSPF ext 2, ON1 - OSPF NSSA ext 1
   ON2 - OSPF NSSA ext 2

S   2699:2699:FE00:30::/64 [1/0]
 via FE80::B2B2:DCFF:FECB:1D1E, Vlan26

...and as you can see, I have no static routes configured ... so it's
interesting that these routes are seen as static

eng-lab-3600-1#sh run | in ip route
eng-lab-3600-1#



-Aaron Gould

Re: IPv6 migration steps for mid-scale isp

[JORDI PALET MARTINEZ]

There are several ISPs doing trials (thousands of users).

RFC6877 (464XLAT), section 4. Network Architecture, indicates clearly “Wireline 
Network Architecture can be used in situations where there
   are clients behind the CLAT, regardless of the type of access service
   -- for example, fiber to the home (FTTH), Data Over Cable Service
   Interface Specification (DOCSIS), or WiFi.”

Vendors confirmed two weeks ago they have implementations in CEs.

RFC7084 was created before all the new transition technologies (including 
464XLAT and MAP, for example, or even lw4o6 that has many advantages compared 
to DS-LITE, being the same but requiring a much simpler CGN), so that’s why I’m 
working to update it (most probably as an “accompanying document” only for the 
transition part:

https://datatracker.ietf.org/doc/draft-ietf-v6ops-rfc7084-bis
https://datatracker.ietf.org/doc/draft-palet-v6ops-rfc7084-bis-transition

New versions to be publish this week hopefully …

Regards,
Jordi
 

-Mensaje original-
De: NANOG  en nombre de Mikael Abrahamsson 

Organización: People's Front Against WWW
Responder a: 
Fecha: sábado, 23 de septiembre de 2017, 13:22
Para: Fredrik Sallinen 
CC: 
Asunto: Re: IPv6 migration steps for mid-scale isp

On Sat, 23 Sep 2017, Fredrik Sallinen wrote:

> Please correct me If I'm wrong, AFAIK 464XLAT works best with mobile
> networks and its not suitable for fixed broadband. right?

It's most widely deployed in mobile networks, yes. There is nothing that 
says it couldn't work anywhere else.

However, in fixed networks with PPPoE the most commonly used model is dual 
stack with RFC7084 style routers.

-- 
Mikael Abrahamssonemail: swm...@swm.pp.se




**
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the exclusive use of the 
individual(s) named above and further non-explicilty authorized disclosure, 
copying, distribution or use of the contents of this information, even if 
partially, including attached files, is strictly prohibited and will be 
considered a criminal offense. If you are not the intended recipient be aware 
that any disclosure, copying, distribution or use of the contents of this 
information, even if partially, including attached files, is strictly 
prohibited, will be considered a criminal offense, so you must reply to the 
original sender to inform about this communication and delete it.