<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=2975524&amp;fmt=gif">
BLOG

Network TAPs are Not Toys, No Batteries Included!

January 14, 2016

garland technology network TAPs network monitoring network security

After weeks of shopping and preparation, the holiday season is always upon us. And the big gift of the year? Hoverboards? Drones? These toys bring to life the sort of fun seen in classic Back to the Future films. There’s just one problem—people everywhere are complaining that their hoverboards are catching fire because of malfunctioning lithium-ion batteries (watch the video here).

If you can’t trust the lithium-ion batteries in children’s toys, what makes you think you can trust them in your data center? Some active TAPs on the market rely on battery backups, which is a commonly understood as not a best practice.

Let’s make one thing clear, lithium-ion battery fires are not new news. They don’t often get media attention due to ongoing investigations and settlement agreements, but even major organizations like NASA and AT&T have fallen prey to lithium-ion battery explosions.

Why do companies continue to deploy these batteries? They may seem necessary for backup power, but it’s important to fully understand the dangers of using lithium-ion batteries.

Why Are Lithium-Ion Batteries So Dangerous?

Lithium-ion batteries are so popular because they’re cheap. But aside from being so cheap, they require rigorous quality assurance processes for testing and keeping the cells free from contaminants. Any slight missteps in the production process can lead to future cell failures, fires and the release of dangerous fumes and liquids.

Unfortunately, even a well-produced battery can cause explosions when paired with poor charging circuits. You might think that you can rely on FCC or CE approvals to determine high-quality production, but even that’s a stretch. 

Download Now: Network TAPs 101 - The Networking User Guide [Free eBook]

Lithium-Ion Battery Regulation is a Conflicting Standards

The low-quality batteries that cause fires and explosions are generally associated with low-cost goods. To combat the rampant battery issues that began in 1991 with a cell phone battery explosion causing toxic burns on a man’s face, multiple conflicting lithium-ion battery standards have emerged.

For starters, the Underwriters Laboratories (UL) have instituted both the Standard for Lithium Batteries (UL 1642) and the Standard for Household and Commercial Batteries (UL 2054) to regulate production. In addition, there are standards from IEEE, ANSI, the United Nations, ISO/IEC and even specific countries to add to the confusion.

Lithium-ion batteries are so dangerous that there are additional regulations and restrictions for transportation. The TSA has specific bans for different kinds of lithium-ion batteries and some airlines have gone so far as to make their own statements. See what Southwest Airlines has recently decided:

“Due to concerns regarding the lithium batteries used in hoverboards (balance boards, gravity boards, self-balancing devices, etc.), effective Saturday, December 12, 2015, Southwest Airlines will not transport hoverboards in either checked luggage or as a carryon item.”

With so many potential problems, network professionals simply must say NO to batteries in their networks and data centers.

Why say NO to Batteries in Your Network:

  • Static electrical events can damage safety devices and charging circuits, leading to eventual catastrophic failure
  • External damage causes dangerous leaks no matter how well-made the battery is
  • Operating the battery outside of its specified temperature range can cause dangerous accidents

A Safe and Reliable Power Redundancy Scenario

Network professionals that implement lithium-ion batteries as protection against power-outages on network TAPs need a proven and safer approach to power redundancy. There are more reliable ways to keep monitoring networks in times of power failures. The most reliable solution is dual power planes with separate power sources hooked up to a primary power and a secondary power supply.  The secondary power supply is then connected to the network backup power (a UPS, generator, etc.).

A real network TAP does not provide a possible point of failure. If it’s a passive TAP, power is not required, if it’s an active TAP it should have failsafe technology that keeps your network links up and running even in case of power outages.

Why take a chance with the same batteries that are blowing up toys?

Looking to add active TAPs  to your next deployment, but not sure where to start? Join us for a brief network Design-IT consultation or demo. No obligation - it’s what we love to do!

Network TAPS 101 Basics for IT Security engineers

See Everything. Secure Everything.

Contact us now to secure and optimized your network operations

Heartbeats Packets Inside the Bypass TAP

If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.

If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.

While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.

Some of you may have noticed a flaw in the logic behind this solution!  You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.

Glossary

  1. Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.

  2. Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.

  3. Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.

NETWORK MANAGEMENT | THE 101 SERIES