Re: Temperature monitoring

2017-07-13 Thread Eric Kuhnke
If all that you require is temperature monitoring, I recommend going
through the SNMP MIBs and doing an snmpwalk of your devices to identify the
sensors at the air intake...  Unfortunately there are some devices which do
not have air intake sensors, but only a sensor somewhere generally in the
center of the motherboard. But other devices have temperature diodes nearly
everywhere. This chart example from an Arista 1U switch is a device which
is really good about identifying the location of the individual sensors in
the MIB.

http://imgur.com/a/4CfpK

When purchasing a temperature monitoring standalone device, I highly
recommend something that is capable of not only temperature sensors but
also highly useful things like relay controls, wire contacts for other
equipment alarms, contacts for things like door/cabinet opening sensors,
etc. With the right high-frequency snmp polling and trap setup you can use
such a thing for a great deal more than just temperature. I have seen
examples of the Tinycontrol v3 used by NOCs to grant third parties access
to POPs via remotely triggered relays and magnetic strike door locks.

Here's a couple of good examples:

http://tinycontrol.pl/en/lan-controller/

http://tinycontrol.pl/en/accessories-lk-3-sensor/

http://www.controlbyweb.com/x332/

On Thu, Jul 13, 2017 at 10:45 PM, Richard Holbo  wrote:

> http://tyconsystems.com/index.php/products/tycon-power/
> tpdin-monitor-web/751-tpdin-monitor-web2
>
> Is what I use in my cabinets. Has two temp sensors, one internal and one
> external.  I put the external near the AC cold air output so I can get a
> diff and know if the AC is on.  SNMP cacti graphs them nicely.  I use one
> of the voltage sensors to monitor the cabinet doors via reed switches. In
> remote mountain sites also use for battery/solar voltages and to monitor
> wall warts for Utility power loss.
>
> /rh
>
> On Thu, Jul 13, 2017 at 7:33 PM, Dovid Bender  wrote:
>
> > All,
> >
> > We had an issue with a DC where temps were elevated. The one bit of
> > hardware that wasn't watched much was the one that sent out the initial
> > alert. Looking for recommendations on hardware that I can mount/hang in
> > each cabinet that is easy to set up and will alert us if temps go beyond
> a
> > certain point.
> >
> > TIA.
> >
> > Dovid
> >
>


Re: Temperature monitoring

2017-07-13 Thread Richard Holbo
http://tyconsystems.com/index.php/products/tycon-power/tpdin-monitor-web/751-tpdin-monitor-web2

Is what I use in my cabinets. Has two temp sensors, one internal and one
external.  I put the external near the AC cold air output so I can get a
diff and know if the AC is on.  SNMP cacti graphs them nicely.  I use one
of the voltage sensors to monitor the cabinet doors via reed switches. In
remote mountain sites also use for battery/solar voltages and to monitor
wall warts for Utility power loss.

/rh

On Thu, Jul 13, 2017 at 7:33 PM, Dovid Bender  wrote:

> All,
>
> We had an issue with a DC where temps were elevated. The one bit of
> hardware that wasn't watched much was the one that sent out the initial
> alert. Looking for recommendations on hardware that I can mount/hang in
> each cabinet that is easy to set up and will alert us if temps go beyond a
> certain point.
>
> TIA.
>
> Dovid
>


Re: Temperature monitoring

2017-07-13 Thread Mel Beckman
Weathergoose by IT watchdogs. 1U rackmount devices with very shallow depth of 
about an inch or two. Sensors are cheap, varied, and you can daisychain dozens 
of them together. So one server box can monitor entire row of racks. Loads of 
other features too for notification, escalation, and SNMP manageable.

-mel via cell

> On Jul 13, 2017, at 9:27 PM, Pete Baldwin  wrote:
> 
> We have Sensaphones (sensaphone.com) in remote offices.  We use IMS-4000s.  
> They are a 1RU box with RJ45 jacks on the front.  You can run CAT-5 to where 
> you want to monitor something, and stick a module on the end of the cable.   
> They have temp, humidity, generic NO/NC sensors, power sensors to graph 
> voltage and alert on voltage swings etc.   They can send emails, SNMP traps, 
> or dial out with a modem.  They also have a built in mic that can alert 
> on noise increases. Some models allow you to dial in and listen to the 
> room. 
> 
> 
> 
>> On July 13, 2017 10:33:22 PM EDT, Dovid Bender  wrote:
>> All,
>> 
>> We had an issue with a DC where temps were elevated. The one bit of
>> hardware that wasn't watched much was the one that sent out the initial
>> alert. Looking for recommendations on hardware that I can mount/hang in
>> each cabinet that is easy to set up and will alert us if temps go
>> beyond a
>> certain point.
>> 
>> TIA.
>> 
>> Dovid


Re: Temperature monitoring

2017-07-13 Thread Pete Baldwin
We have Sensaphones (sensaphone.com) in remote offices.  We use IMS-4000s.  
They are a 1RU box with RJ45 jacks on the front.  You can run CAT-5 to where 
you want to monitor something, and stick a module on the end of the cable.   
They have temp, humidity, generic NO/NC sensors, power sensors to graph voltage 
and alert on voltage swings etc.   They can send emails, SNMP traps, or dial 
out with a modem.  They also have a built in mic that can alert on noise 
increases. Some models allow you to dial in and listen to the room. 

 

On July 13, 2017 10:33:22 PM EDT, Dovid Bender  wrote:
>All,
>
>We had an issue with a DC where temps were elevated. The one bit of
>hardware that wasn't watched much was the one that sent out the initial
>alert. Looking for recommendations on hardware that I can mount/hang in
>each cabinet that is easy to set up and will alert us if temps go
>beyond a
>certain point.
>
>TIA.
>
>Dovid


Re: Temperature monitoring

2017-07-13 Thread Harlan Stenn

On 7/13/17 7:33 PM, Dovid Bender wrote:
> All,
> 
> We had an issue with a DC where temps were elevated. The one bit of
> hardware that wasn't watched much was the one that sent out the initial
> alert. Looking for recommendations on hardware that I can mount/hang in
> each cabinet that is easy to set up and will alert us if temps go beyond a
> certain point.
> 
> TIA.
> 
> Dovid

Are you running ntpd on your boxes?  See what happens when you plot its
drift against other temperature sensors, the closer to the clock chip
the better.

If you do this on enough boxes, you should have an easy time seeing what
happens on boxes where you have an easier time watching ntpd's drift
value than you have watching a nearby dedicated temperature sensor.

-- 
Harlan Stenn 
http://networktimefoundation.org - be a member!


Re: Temperature monitoring

2017-07-13 Thread Andrew Latham
On Thu, Jul 13, 2017 at 9:33 PM, Dovid Bender  wrote:

> All,
>
> We had an issue with a DC where temps were elevated. The one bit of
> hardware that wasn't watched much was the one that sent out the initial
> alert. Looking for recommendations on hardware that I can mount/hang in
> each cabinet that is easy to set up and will alert us if temps go beyond a
> certain point.
>
> TIA.
>
> Dovid
>

Most everything has temperature sensors from switches, servers and most
modern PDUs. A dedicated solution is just creating the problem again in the
future. Monitor the temps on everything and gain knowledge related to
failure rates. Most companies with physical infrastructure could pay for
another engineer to discover these unexpected expenses. Also note that
modern air conditioning and refrigeration have SNMP or BACNET protocol
support, just download the manual.

-- 
- Andrew "lathama" Latham -


Re: Temperature monitoring

2017-07-13 Thread Gary E. Miller
Yo Dovid!

On Thu, 13 Jul 2017 22:33:22 -0400
Dovid Bender  wrote:

> Looking for recommendations on hardware that I can
> mount/hang in each cabinet that is easy to set up and will alert us
> if temps go beyond a certain point.

I use a lot of TEMPer USB Thermometers.  Cheap, small, easy to poll.

It is easy to use from many programing languages and lots of open source
software supports it dierctly or indirectly.

RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com  Tel:+1 541 382 8588

Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin


pgpO4M2bC1kLy.pgp
Description: OpenPGP digital signature


Temperature monitoring

2017-07-13 Thread Dovid Bender
All,

We had an issue with a DC where temps were elevated. The one bit of
hardware that wasn't watched much was the one that sent out the initial
alert. Looking for recommendations on hardware that I can mount/hang in
each cabinet that is easy to set up and will alert us if temps go beyond a
certain point.

TIA.

Dovid


Re: Testing methodology for the Chinese quantum satellite link?

2017-07-13 Thread Marshall Eubanks
On Thu, Jul 13, 2017 at 12:57 PM, Bill Woodcock  wrote:

> Does anyone who understands quantum networking better than I do have an
> opinion on the testing methodology that the Chinese team used to confirm
> entanglement?


Their paper

https://arxiv.org/abs/1707.01339

This is somewhat higher level

http://vcq.quantum.at/fileadmin/Publications/Entanglement-based%20quantum%20communication%20over%20144km.pdf

More math

https://arxiv.org/pdf/1410.1319.pdf



> I guess, more specifically, my question is: when they say that they got
> 911 positive results out of “millions” of attempts, does this significantly
> exceed any expected false-positive rate for the confirmation methodology?
> If so, by what margin?  Obviously, if you were just flipping coins, and
> measured the results once, you’d get 50% positive correlation, twice and
> you’d get 25% correlation, ten times and you’d get 0.1% correlation, and
> you’d be at 911 out of a million.  So, how much better than that are we
> talking about?
>

Look at Figure 2b in the Ursin paper. You are always doing this against
some background, looking for a statistically significant peak.

Regards
Marshall


>
> -Bill
>
>
>
>
>
>


Re: BGP peering question

2017-07-13 Thread Owen DeLong
If you develop a well tuned process for creating BGP sessions and even a 
moderate
system for monitoring not the individual sessions, but meaningful traffic 
events on
your network, then, maintaining a large number of peers and a promiscuous 
peering
policy is not such a daunting process.

As a general rule, promiscuous peering improves efficiency and keeps your 
options for
traffic delivery open. Restrictive peering generally has the opposite effect.

Route servers are a lazy form of promiscuous peering, with an attendant fate 
sharing
which can produce suboptimal results. YMMV.

I’ve worked for several networks of various sizes and observed the industry in 
general
for many years. As a general rule, a restrictive peering policy is a great way 
to lose
momentum in the market and convert a major ISP into a bit-player (e.g. SPRINT), 
whereas
promiscuous peering can be a key component in moving a trivial ISP into a major 
player
in the industry (e.g. HE).

Again, YMMV.

Owen

> On Jul 13, 2017, at 11:04 , Baldur Norddahl  wrote:
> 
> Speaking as a small ISP with 10 to 20 Gbps peak traffic. We are heavy
> inbound as a pure eyeball network.
> 
> We use the route servers. We only maintain direct BGP sessions with a few
> large peers. Think Google, Netflix, Akamai etc.
> 
> The reason for this is simply administrative overhead. Every BGP session
> has to be configured and monitored. We know that it will not move a large
> percentage of our traffic. We simply do not have the ressources currently
> when the gain is so little.
> 
> Anyone who wants to pass traffic efficiently to us can either use the route
> server or they can peer with Hurricane Electric. The later option will get
> the traffic to us almost as efficiently as peering directly with us. In
> this sense we outsourced the peering to them.
> 
> Regards
> 
> Baldur
> 
> Den 11. jul. 2017 18.42 skrev "craig washington" <
> craigwashingto...@hotmail.com>:
> 
>> Hello,
>> 
>> 
>> Newbie question, what criteria do you look for when you decide that you
>> want to peer with someone or if you will accept peering with someone from
>> an ISP point of view.
>> 
>> 
>> Thanks.
>> 
>> 
>> 
>> 



Re: BGP peering question

2017-07-13 Thread Baldur Norddahl
Speaking as a small ISP with 10 to 20 Gbps peak traffic. We are heavy
inbound as a pure eyeball network.

We use the route servers. We only maintain direct BGP sessions with a few
large peers. Think Google, Netflix, Akamai etc.

The reason for this is simply administrative overhead. Every BGP session
has to be configured and monitored. We know that it will not move a large
percentage of our traffic. We simply do not have the ressources currently
when the gain is so little.

Anyone who wants to pass traffic efficiently to us can either use the route
server or they can peer with Hurricane Electric. The later option will get
the traffic to us almost as efficiently as peering directly with us. In
this sense we outsourced the peering to them.

Regards

Baldur

Den 11. jul. 2017 18.42 skrev "craig washington" <
craigwashingto...@hotmail.com>:

> Hello,
>
>
> Newbie question, what criteria do you look for when you decide that you
> want to peer with someone or if you will accept peering with someone from
> an ISP point of view.
>
>
> Thanks.
>
>
>
>


RE: noction vs border6 vs kentik vs fcp vs ?

2017-07-13 Thread Aaron Gould
I have 3 different well-known caches local to my network...

45% of my subscriber traffic hits the caches
55% of my subscriber traffic hits the internet uplinks

I love my caches, but I REALLY love the Netflix cache.  It's a huge savings on 
my internet uplinks.

-Aaron




RE: 10G MetroE 1-2U Switch

2017-07-13 Thread Aaron Gould
Hi Erik, as a follow-up to this email from back in April...previously I
hadn't yet tested any qos things on the ACX5048.  Now I have tested some
policing and seems to be working thus far in the lab.  I am policing at the
unit (subinterface) level to I can accomplish per-vlan/per-unit policers.

I have 5 policers like this 

{master:0}
agould@eng-lab-5048-2> show configuration firewall | display set | grep
policer

set firewall policer test-policer-1000 if-exceeding bandwidth-limit 100k
set firewall policer test-policer-1000 if-exceeding burst-size-limit 3125
set firewall policer test-policer-1000 then discard

set firewall policer test-policer-1001 if-exceeding bandwidth-limit 100k
set firewall policer test-policer-1001 if-exceeding burst-size-limit 3125
set firewall policer test-policer-1001 then discard

set firewall policer test-policer-1002 if-exceeding bandwidth-limit 100k
set firewall policer test-policer-1002 if-exceeding burst-size-limit 3125
set firewall policer test-policer-1002 then discard

set firewall policer test-policer-1003 if-exceeding bandwidth-limit 100k
set firewall policer test-policer-1003 if-exceeding burst-size-limit 3125
set firewall policer test-policer-1003 then discard

set firewall policer test-policer-1004 if-exceeding bandwidth-limit 100k
set firewall policer test-policer-1004 if-exceeding burst-size-limit 3125
set firewall policer test-policer-1004 then discard

{master:0}
agould@eng-lab-5048-2> show configuration interfaces ge-0/0/19 | display set
set interfaces ge-0/0/19 flexible-vlan-tagging
set interfaces ge-0/0/19 mtu 9216
set interfaces ge-0/0/19 encapsulation flexible-ethernet-services

set interfaces ge-0/0/19 unit 1000 description "TEST att mtso - tower 98
Drain 1 - vlan 1000"
set interfaces ge-0/0/19 unit 1000 encapsulation vlan-vpls
set interfaces ge-0/0/19 unit 1000 vlan-id 1000
set interfaces ge-0/0/19 unit 1000 input-vlan-map pop
set interfaces ge-0/0/19 unit 1000 output-vlan-map push
set interfaces ge-0/0/19 unit 1000 statistics
set interfaces ge-0/0/19 unit 1000 family vpls policer input
test-policer-1000

set interfaces ge-0/0/19 unit 1001 description "TEST att mtso - tower 99
Drain 1 - vlan 1001"
set interfaces ge-0/0/19 unit 1001 encapsulation vlan-vpls
set interfaces ge-0/0/19 unit 1001 vlan-id 1001
set interfaces ge-0/0/19 unit 1001 input-vlan-map pop
set interfaces ge-0/0/19 unit 1001 output-vlan-map push
set interfaces ge-0/0/19 unit 1001 statistics
set interfaces ge-0/0/19 unit 1001 family vpls policer input
test-policer-1001

set interfaces ge-0/0/19 unit 1002 description "TEST att mtso - tower 100
Drain 1 - vlan 1002"
set interfaces ge-0/0/19 unit 1002 encapsulation vlan-vpls
set interfaces ge-0/0/19 unit 1002 vlan-id 1002
set interfaces ge-0/0/19 unit 1002 input-vlan-map pop
set interfaces ge-0/0/19 unit 1002 output-vlan-map push
set interfaces ge-0/0/19 unit 1002 statistics
set interfaces ge-0/0/19 unit 1002 family vpls policer input
test-policer-1002

set interfaces ge-0/0/19 unit 1003 description "TEST att mtso - tower 101
Drain 1 - vlan 1003"
set interfaces ge-0/0/19 unit 1003 encapsulation vlan-vpls
set interfaces ge-0/0/19 unit 1003 vlan-id 1003
set interfaces ge-0/0/19 unit 1003 input-vlan-map pop
set interfaces ge-0/0/19 unit 1003 output-vlan-map push
set interfaces ge-0/0/19 unit 1003 statistics
set interfaces ge-0/0/19 unit 1003 family vpls policer input
test-policer-1003

set interfaces ge-0/0/19 unit 1004 description "TEST att mtso - tower 102
Drain 1 - vlan 1004"
set interfaces ge-0/0/19 unit 1004 encapsulation vlan-vpls
set interfaces ge-0/0/19 unit 1004 vlan-id 1004
set interfaces ge-0/0/19 unit 1004 input-vlan-map pop
set interfaces ge-0/0/19 unit 1004 output-vlan-map push
set interfaces ge-0/0/19 unit 1004 statistics
set interfaces ge-0/0/19 unit 1004 family vpls policer input
test-policer-1004



-Original Message-
From: Erik Sundberg [mailto:esundb...@nitelusa.com] 
Sent: Friday, April 14, 2017 10:30 AM
To: Aaron Gould ; nanog@nanog.org
Subject: RE: 10G MetroE 1-2U Switch 

Aaron,

Do you know if the ACS5048 has any QOS limitations on this platform?

Is each EVC on a ENNI able to have a separate QOS policy or is it port
based? Just wondering how it would compare to the Cisco NCS5001\NCS5501

Thanks

Erik

Erik Sundberg
Sr. Network Engineering
Network Engineering Department
p: 773.661.5532
c: 708.710.7419
e: esundb...@nitelusa.com
Main: 888.450.2100
NOC 24/7: 866.892.0915
350 North Orleans Street, Suite 1300N Chicago, IL 60654 www.nitelusa.com

Managed Telecom Services
MPLS | Ethernet | Private Line | Internet | Voice | Security




Re: BGP peering question

2017-07-13 Thread Martin Hannigan
On Mon, Jul 10, 2017 at 4:12 PM, craig washington <
craigwashingto...@hotmail.com> wrote:

> Hello,
>
>
> Newbie question, what criteria do you look for when you decide that you
> want to peer with someone or if you will accept peering with someone from
> an ISP point of view.
>


You didn't say what kind of 'peering'. That could mean over an IXP or to be
directly connected. You do not need to be a member of an IX to peer.

There are at least three types of criteria to evaluate. Technical, business
and legal.  Take a look here for a few ideas on technical and business
criteria:

http://bit.ly/2ue2t0P

"Me too" with the rest of the thread. If peering serves your mutual
interests (or just yours even), its an easy decision.

The Dr Peering http://drpeering.net/ website is also a resource for folks
new to peering.

http://drpeering.net/


Best Regards,

-M<


Testing methodology for the Chinese quantum satellite link?

2017-07-13 Thread Bill Woodcock
Does anyone who understands quantum networking better than I do have an opinion 
on the testing methodology that the Chinese team used to confirm entanglement?  
I guess, more specifically, my question is: when they say that they got 911 
positive results out of “millions” of attempts, does this significantly exceed 
any expected false-positive rate for the confirmation methodology?  If so, by 
what margin?  Obviously, if you were just flipping coins, and measured the 
results once, you’d get 50% positive correlation, twice and you’d get 25% 
correlation, ten times and you’d get 0.1% correlation, and you’d be at 911 out 
of a million.  So, how much better than that are we talking about?

-Bill






signature.asc
Description: Message signed with OpenPGP


Re: noction vs border6 vs kentik vs fcp vs ?

2017-07-13 Thread ShaColby Jackson
If my servers are watching Netflix all day I’ve got another problem way
beyond traffic visibility.


On July 12, 2017 at 12:37:48 PM, valdis.kletni...@vt.edu (
valdis.kletni...@vt.edu) wrote:

On Wed, 12 Jul 2017 11:03:50 -0700, ShaColby Jackson said:

> I know solutions like Kentik do a lot more but I’m focusing on just the
> above use case. Also ignoring the cloud vs. on-prem difference, assume
that
> doesn’t matter.

Might want to re-think that. In a world where some eyeball networks are
reporting that 60%+ of the traffic is Netflix, there's a big difference
between the Netflix CDN cloud and having a local Netflix cache box on
the local net. Akamai is another company making coin assuming it does
matter.

(I'm assuming you don't actually know what percent of your traffic is
Netflix/Akamai - if you already had that breakout, you'd not be asking
for suggestions as you have already have an in-house solution...)