Re: DWDM on 250 Km dark fiber without re-amplification

[Josh Galvez]

Jeremy,

SmartOptics is one such vendor that I've used in the past that may be able
to do this.

http://www.smartoptics.com/

-Josh

On Tue, Dec 27, 2016 at 10:41 AM, Brian R  wrote:

> I have to agree with Brandon.  I have not worked with Ciena equipment
> directly but have work with carriers that use it.  I worked with Adtran on
> this kind of setup and like Brandon said they require a lot of information
> to build what is needed for each specific run (fiber type, quality, wave
> length optimization, number of splices, etc).  I've seen the tools Adtran
> uses to calculate exactly what equipment is required and it is pretty
> complex for distances even close to what you are talking about.
>
> Definitely check for a re-gen site(s), most likely the carrier has to
> re-gen their own runs down this fiber path (another thing to consider in
> the calculation matrix especially if you are not trying to re-gen your run).
>
>
> I have to give Baldur kudos for finding that I'm still amazed that
> Fiberstore is claiming that's possible without a lot of information.  I
> have worked with Fiberstore and they are a cooperative vendor and their
> products work for what we have used them for.
>
>
> My suggestion is to reach out to Fiberstore, Ciena, Adtran, and other
> vendors that people recommend with a detailed email of what you would like
> to accomplish and the information you can get.  Ask for a design engineer
> (I know Adtran has them and assume others do) to get the info you need and
> see what they can mock up for you.
>
>
> Brian
>
>
> 
> From: NANOG  on behalf of Brandon Martin <
> lists.na...@monmotha.net>
> Sent: Sunday, December 25, 2016 12:41 AM
> To: nanog@nanog.org
> Subject: Re: DWDM on 250 Km dark fiber without re-amplification
>
> On 12/23/2016 07:14 PM, Jeremy wrote:
> > Hi all,
> >
> > First, i'm sorry for my english, i'm french and i don't have a good
> > level in this language. But i want some informations and i'm sure,
> > someone will be give the good anwser about my question.
> >
> > So, i'm regarding to rent a dual dark fiber in France, the estimated
> > distance is 225 Km, but i know there are a lot of optical switching on
> > the highway where it's fiber is installed (in theory, all 80 Km). So, i
> > used the bad scenario, in adding 25 Km on my need.
> >
> > I would like to buy a amplificator and multiplexer DWDM to add some
> > 10Gb/s waves on this dark fiber. I've see that the amplification is
> > better on 100 Gb/s synchronised ports, but we don't have enoug capacity
> > on our router to add 100 Gb/s interfaces.
> >
> > So, someone has installed this type of hardware on a dark fiber without
> > regeneration  on 250 Km of distance ?
> > If yes, with what kind of hardware ? If you are commercial for this
> > hardware, please contact me in private message.
>
>
> Look up Raman amplification.  The short of what this does is it pumps a
> ton of power into the near end of the fiber span and creates what looks
> somewhat like a typical color-blind amplifier somewhere several dozen km
> out on the span.  You'll also need to dump a ton of power into the span
> at the far end using an EDFA or similar.  Even with both of those, that
> distance is still going to push the raw optical power budget of even
> most state-of-the-art transceivers especially if the fiber is old or of
> low quality (high loss, high dispersion, etc.).
>
> The longest span I've ever gotten a vendor to commit to an engineered
> design for was about 140km, and of course they needed full
> characterization of the span before they'd do it.  At those distances,
> distance alone is no longer sufficient to throw together a design.
>
> It seems highly likely that there's at least one re-gen facility along
> that span.  I'd definitely see if there is one and if you can get some
> space in it.  That will knock you down into the 100-130km range on both
> sides of the re-gen, hopefully, which is perfectly doable.
>
> You are somewhat correct that 100Gb interfaces often handle longer
> distances better, but it's because they are often using coherent
> receivers and carrier-synchronous transmitters rather than raw power
> receivers and ASK pulsed transmitters.  There are vendors that sell
> coherent 10Gb transceivers, too, and they'll be cheaper than 100Gb
> solutions especially if you don't need the extra capacity anyway.  I'd
> definitely check them out for this type of application especially if you
> can't get any dispersion compensation in the middle since coherent
> optics are usually much more tolerant of chromatic dispersion.
>
> The big vendor I've worked with in the past on this sort of stuff is
> Ciena (and they're certainly a juggernaut in the industry) though I have
> no connection to them other than as a satisfied (if occasionally broke
> after a PO or out of breath after seeing a quotation) customer/integrator.
>
> --
> Brandon Martin
>

Re: Automated alarm notification

[Josh Galvez]

I've used Zabbix, Nagios, etc to handle receiving and parsing traps,
set/clear etc.  Then have them send a trap (or via email to script that
sends a trap) to SIPShout to actually generate the callout.  It's worked
well.

-Josh

On Thu, Feb 11, 2016 at 2:51 PM, Frank Bulk  wrote:

> Is anyone aware of software, or perhaps a service, that will take SNMP
> traps, properly parse them, and perform the appropriate call outs based on
> certain content, after waiting 5 or 10 minutes for any alarms that don't
> clear?
>
> I looked at PagerDuty, but they don't do any SNMP trap parsing, and nothing
> with set/clear.
>
> Frank
>
>

ipp.gov and Google DNS (8.8.8.8)

[Josh Galvez]

Google Public DNS (8.8.8.8, 8.8.4.4) is failing to resolve ipp.gov,
returning a SERVFAIL.  Other DNS servers seem to resolve this just fine
(ie. OpenDNS)

If I use dig +trace, I get appropriate results all the way down.

DNSSEC seems to be validating properly.
http://dnssec-debugger.verisignlabs.com/ipp.gov
http://dnsviz.net/d/ipp.gov/dnssec/

Is there any one here from Google that can help with this?

See dig results and traceroutes below.

-Josh

$ dig @8.8.8.8 ipp.gov soa +trace

;  DiG 9.8.3-P4  @8.8.8.8 ipp.gov soa +trace
; (1 server found)
;; global options: +cmd
.   2209IN  NS  e.root-servers.net.
.   2209IN  NS  h.root-servers.net.
.   2209IN  NS  d.root-servers.net.
.   2209IN  NS  i.root-servers.net.
.   2209IN  NS  k.root-servers.net.
.   2209IN  NS  j.root-servers.net.
.   2209IN  NS  l.root-servers.net.
.   2209IN  NS  a.root-servers.net.
.   2209IN  NS  b.root-servers.net.
.   2209IN  NS  c.root-servers.net.
.   2209IN  NS  f.root-servers.net.
.   2209IN  NS  g.root-servers.net.
.   2209IN  NS  m.root-servers.net.
;; Received 228 bytes from 8.8.8.8#53(8.8.8.8) in 1218 ms

gov.172800  IN  NS  a.gov-servers.net.
gov.172800  IN  NS  b.gov-servers.net.
;; Received 132 bytes from 128.63.2.53#53(128.63.2.53) in 113 ms

ipp.gov.86400   IN  NS  ns1.federalreserve.org.
ipp.gov.86400   IN  NS  ns2.federalreserve.org.
ipp.gov.86400   IN  NS  ns3.federalreserve.org.
;; Received 97 bytes from 69.36.157.30#53(69.36.157.30) in 375 ms

ipp.gov.30  IN  SOA ns1.federalreserve.org.
dns.ids.frb.org. 5 1200 1800 1209600 21600
ipp.gov.30  IN  NS  ns1.federalreserve.org.
ipp.gov.30  IN  NS  ns3.federalreserve.org.
ipp.gov.30  IN  NS  ns2.federalreserve.org.
;; Received 193 bytes from 199.169.208.138#53(199.169.208.138) in 40 ms




$ dig @8.8.8.8 ipp.gov soa

;  DiG 9.8.3-P4  @8.8.8.8 ipp.gov soa
; (1 server found)
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: SERVFAIL, id: 17671
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ipp.gov.   IN  SOA

;; Query time: 3353 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu May 30 14:55:08 2013
;; MSG SIZE  rcvd: 25



$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 40 byte packets
 1  ve1003.mpls1.core.prco.etv.net (66.111.113.1)  5.989 ms  0.534 ms
 0.222 ms
 2  interface-74-214-233-10 (74.214.233.10)  5.205 ms  2.618 ms  2.615 ms
 3  te-8-3.car2.SaltLakeCity1.Level3.net (4.53.42.153)  146.414 ms  178.280
ms  3.753 ms
 4  ae-11-11.car1.SaltLakeCity1.Level3.net (4.69.133.121)  30.170 ms
 33.988 ms  40.203 ms
 5  * * *
 6  ae-91-91.csw4.LosAngeles1.Level3.net (4.69.137.14)  30.178 ms  30.058 ms
ae-81-81.csw3.LosAngeles1.Level3.net (4.69.137.10)  30.047 ms
 7  * * *
 8  GOOGLE-INC.edge1.LosAngeles9.Level3.net (4.53.228.6)  30.293 ms  29.913
ms  29.950 ms
 9  216.239.46.40 (216.239.46.40)  30.129 ms
64.233.174.238 (64.233.174.238)  86.755 ms
216.239.46.40 (216.239.46.40)  30.164 ms
10  64.233.174.192 (64.233.174.192)  67.074 ms
64.233.174.188 (64.233.174.188)  30.725 ms
64.233.174.186 (64.233.174.186)  46.088 ms
11  72.14.239.153 (72.14.239.153)  42.234 ms
72.14.239.159 (72.14.239.159)  42.772 ms
72.14.239.160 (72.14.239.160)  43.318 ms
12  64.233.174.129 (64.233.174.129)  41.513 ms  41.510 ms
64.233.174.131 (64.233.174.131)  42.157 ms
13  * * *
14  google-public-dns-a.google.com (8.8.8.8)  42.258 ms  42.423 ms  42.408
ms




$ traceroute 8.8.4.4
traceroute to 8.8.4.4 (8.8.4.4), 64 hops max, 40 byte packets
 1  ve1003.mpls1.core.prco.etv.net (66.111.113.1)  0.287 ms  0.290 ms
 0.175 ms
 2  interface-74-214-233-10 (74.214.233.10)  7.919 ms  2.576 ms  2.687 ms
 3  te-8-3.car2.SaltLakeCity1.Level3.net (4.53.42.153)  2.848 ms  2.767 ms
 2.758 ms
 4  ae-11-11.car1.SaltLakeCity1.Level3.net (4.69.133.121)  30.160 ms
 30.289 ms  30.147 ms
 5  * * *
 6  ae-81-81.csw3.LosAngeles1.Level3.net (4.69.137.10)  30.222 ms
ae-61-61.csw1.LosAngeles1.Level3.net (4.69.137.2)  30.070 ms  30.220 ms
 7  * * *
 8  GOOGLE-INC.edge1.LosAngeles9.Level3.net (4.53.228.6)  30.086 ms  30.301
ms  30.325 ms
 9  64.233.174.238 (64.233.174.238)  30.178 ms  30.228 ms
216.239.46.40 (216.239.46.40)  30.440 ms
10  64.233.174.192 (64.233.174.192)  30.392 ms
64.233.174.190 (64.233.174.190)  30.564 ms
72.14.238.0 

frontiernet.net Email Server Admin

[Josh Galvez]

Can someone who administers frontiernet.net email servers please contact me
off list?

Your bounce message does not indicate why our access to submit messages to
this e-mail system has been rejected

Thanks.

Re: IP Address Management IPAM software for small ISP

[Josh Galvez]

This tool handle most of what you are asking for:

http://www.nocproject.org/

-Josh

On Thu, Dec 20, 2012 at 2:30 AM, Thilo Bangert thilo.bang...@gmail.comwrote:

 On Thursday 20 December 2012 09:11:43 Saku Ytti wrote:
  On (2012-12-20 03:24 +), Blake Pfankuch wrote:
   I actually was doing research on this today as well.  Anyone have any
   experience with the solutions that implement VLAN management as well
 like
   Gestioip?
  I'm not remotely interested in externally developed software for this
  problem.

 what do you mean. i'd be fine with an opensource project providing this.

  But it's fair question. Generally this tool should not be IP or
  VLAN based but generic resource reservation tool, IP, VLAN, RD, RT,
  VPLS-ID, site-id, pseudowireID what have you.
 
  For me, humans would not do much directly with the tool. They'd give it
  large chunk of resource. Then maybe mine it to pools like 'coreLink',
  'coreLoop', 'custLink', 'custLAN' etc.
  Then in your provisioning tools, you'd request resource from specific
 pool
  via restful API. Humand would never manually write RD/RT/IP/VLAN in the
  tool or in the configs. And this type of system is vastly simpler than
 the
  IPAMs I see listed, once you get rid of all the UI candy, it gets rather
  easy problem to solve.

 this is a pretty accurate description of our requirements, as well. off the
 top of my head we'd also manage phone numbers, key ids, and key box ids,
 with
 it, but that would almost be a minor detail. ;-)