Tag Archive for Access Point

PoE Overworked

PoE OverworkedGary Audin at No Jitter warns that Power over Ethernet (PoE) is not always a plug-and-play environment and PoE should be monitored, managed, and efficient. In this article, Mr. Audin observes that PoE has evolved into an electrical power device utility platform. POE started out as a centralized power source for IP phones, backed up with an Uninterruptible Power Supply (UPS). (rb- Click here and here for my overview of PoE) Since those early Cisco dominated days. The article says PoE now is called upon to support wireless access points; environmental controls; point, tilt, and zoom cameras; lighting control; clocks; door controls; Bluetooth devices; RFID; now laptops, and still more to come.

The LAN switch is the PoE source, but the article warns it can be overwhelmed with the power drain, which produces headaches for IT. Unless properly managed, the PoE function can experience:

  • power drainA blown-out power supply. Smoke is an indicator of this condition.
  • Reduced power to all devices with degraded service from all the attached devices.
  • An added PoE device does not work.
  • The more power is drawn by PoE, the shorter the UPS battery life. The original UPS design could last 20 minutes. Added PoE devices could shorten this to 3 minutes.

PoE IP phones and other devices can signal to the PoE network what class of device it belongs to and how much power it may need. Class 0 devices, usually older devices, do not indicate their PoE power requirements. These devices may draw any power level from none to maximum. The other standard classes, 1-3, range from very low power to mid-level power consumption.

Class 4 is a newer class of device requiring PoE+ (802.1at) and needs to draw more than the 12.95 Watt maximum provided by the original standard PoE. Class 4 devices must be powered by PoE+ ports and may not function correctly on an 802.3af PoE port. Most IP phones are in class 2. IP phones with color screens and other advanced features may be categorized as class 3 devices.

PoE classes

PoE Access Points Wireless LAN access points are also common PoE devices, many of which started out as class 2 and 3 devices. As the wireless speeds increased, so did the power requirements. The 802.11ac standard means that the access points (AP) will have a 1 Gbps connection back to the switches and routers.

site-surveyAt issue is the PoE required. It is likely that each AP could need 20 to 30 watts, the limit that the 802.1at PoE+ standard delivers. Many installed switches cannot support PoE+. So the enterprise has to buy new switches or power supplies or power injectors. (rb- add this to your site-survey when you plan to implement 802.11ac)

Mr. Audin spoke to Tim Titus, CTO, and founder of PathSolutions, (they happen to sell a network management tool) about what he considers a good approach to monitoring and managing POE. He told No Jitter,

“Regardless of whether there are any PoE or PoE+ devices on a network, it can be very helpful to monitor the health of our network equipment’s power supplies. The best monitoring system watches the status and power consumption of each power supply, what percentage of utilization it is running, and which interfaces are drawing power, so power policing can be achieved.”

He provided this example of missing power management.

“Keeping an eye on power supplies avoids unpleasant discoveries. One unlucky network administrator had two power supplies installed in a network chassis (one primary and one backup). Unfortunately, when the primary power supply stopped working, nobody knew, since the backup power supply was doing its job of keeping everything running. The problem wasn’t noticed for over six months. Nobody was in the empty remote wiring closet to notice the lack of lights on the power supply. The users remained blissfully unaware of impending doom until the wee hours of a weekend when the second power supply was shut off by a circuit-breaker trip!” 

Mr. Titus pointed out to Mr. Audin, that monitoring should happen at the port level,

“Not only will a monitoring system show you what mode a PoE port is operating in, but it should also provide a view of relevant error counters.

  • MPS Absent and Invalid Signature errors frequently point to broken or defective powered devices.
  • Overload conditions and short-circuits typically point to wiring problems (or somebody re-wiring devices in use).
  • Denied errors can point to devices asking for more power than the switch has available, and may indicate that it is time to consider adding another power supply to a large Ethernet chassis.”

How did that happen?

Finally, many network engineers try to buy limited PoE due to the cost premium of POE ports, only to find that half of their PoE ports are used by non-PoE devices such as PCs. With a monitoring tool, the engineers could have avoided buying expensive PoE ports or purchased less expensive “ordinary” Ethernet ports.  The engineers should have an up-to-date PoE port inventory and use it to avoid over-buying the PoE by playing safe in their design. (rb- Been there done that, I’ve been in many customer’s closets and found POE switches full of PC and printer access ports.)

rb-

The author warns not to assume that PoE is always a plug-and-play environment. PoE should be handled like a utility–monitored, managed, and efficient.

I have tried to build custom fields by working with reports in SolarWind’s Orion by working with MIBs, it’s not the funnest thing in the world. I wonder if this product does a better job.

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Power over Ethernet 802.3af

Power over Ethernet 802.3afA client recently asked what happened to the network design rule of thumb which said do not install data cables anywhere near electrical cables? The fear of cross-talk, interference, and corruption of the data traffic seems to have disappeared with Power over Ethernet (PoE). He rightly pointed out that now it seems OK to mix data and power in the same cable going to a networked device. 

Read part 2 here.

Plain Old Telephone SystemPoE is similar in principle to the way that the copper wire pair that carries your POTS (Plain Old Telephone System) telephone signals into your house also carries enough electricity (48v DC) from the telco Central Office to power the phone’s core elements of the headset, dial, and ringer. Power over Ethernet’s development started with early implementations of Voice over Internet Protocol VoIP)phone systems. VoIP pioneers did not have a telco CO to power the phones and powering the VoIP phones with wall warts proved unreliable. The phones stopped working when unplugged from the wall or if the building lost power.

In 2000 Cisco (CSCO) developed the first successful technique of putting 48v DC on the LAN data cable along with the data traffic. This proprietary system allowed Cisco to overcome customer objections to wall warts and sell a lot of VoIP systems.

Cisco logoCisco’s original PoE equipment was capable of delivering up to 10W per port. The endpoint and the Cisco switch negotiated the amount of power to be delivered based on a power value in the proprietary Cisco Discovery Protocol (CDP). The Power Sourcing Equipment (PSE) will send a Fast Link Pulse (FLP) on the transmit pair. The Powered Device (PD) connects the transmit line to the receiving line via a low pass filter. And thus the PSE gets the FLP in return. Cisco’s original PoE implementation is not software upgradeable to the IEEE 802.3af standard. Cisco manufactured many IP phones and WLAN access points devices that were not compliant with the IEEE 802.3-2005 Clause 33 including:

Cisco pre-standard IP phones
7985G7960G7940G7910G7910G + SW
7912G7905G7902G7970G
Cisco IEEE 802.3af and pre-standard IP phones
7970G7961G7906G7941G
7911G7962G
The Cisco 7936 Conference Phone does not support any LAN based power and requires a Cisco power injection adapter
Source

Throughout 2001 and 2002, other VoIP and Wireless Access Point (WAP) vendors saw Cisco’s success and developed their own proprietary (and often non-interoperable) powering systems. As more proprietary systems were developed the Institute of Electrical and Electronics Engineers (IEEE) recognized the need to standardize PoE. The IEEE 802.3 Ethernet Committee assigned PoE technology to a new working subcommittee called 802.3af. The IEEE working group’s charge was to create a standardized version of the Power Over Ethernet so that any manufacturer who wanted to could make their products PoE ready. The IEEE working group took commentary from 2001 to 2003 and released the ratified IEEE 802.3af-2003 Power over Ethernet standard in June 2003 which added clause 33 to the IEEE 802.3 standard

Institute of Electrical and Electronics Engineers (IEEE) 802.3 Ethernet CommitteeThe 802.3af document describes how PoE systems should work.  The standard defines two types of PoE equipment, Power Sourcing Equipment (PSE) and the Powered Device (PD). Power Sourcing Equipment sends the power out over the LAN cabling system to the Powered Device. The PSE would send out a maximum of 15.4 watts DC per link to each device, (limited to standard Ethernet distances). 12.95 watts are assumed to be available at the PD because some power is lost in the cable.

The nominal voltage is 48 V, over two of the four available pairs on a Cat. 3/Cat. 5e cable. “Phantom power” is used to allow the powered pairs to also carry data. This permits PoE to be used with 10BASE-T and 100BASE-TX, which use only two of the four pairs in the cable, but also with 1000BASE-T (gigabit Ethernet), which uses all four pairs for data transmission. This is possible because all versions of Ethernet over twisted pair cable specify differential data transmission over each pair with transformer coupling; the DC supply and load connections can be made to the transformer center-taps at each end. Each pair thus operates in “common mode” as one side of the DC supply, so two pairs are required to complete the circuit. The polarity of the DC supply may be inverted by cross cables; the powered device must work with either pair: spare pairs 4-5 and 7-8 or data pairs 1-2 and 3-6. Polarity is required on data pairs and ambiguously implemented for spare pairs, with the use of a bridge rectifier. (Source)

VOIP devicesPower Sourcing Equipment can be in two form factors. A PSE can be implemented as an endspan which is an Ethernet switch with powered ports (a PoE enabled switch) or midspan which is a power hub that is used along with a non-powered switch the end-user already has in place. PD’s can receive PoE equally well from either type of PSE per the standard. The decision to use an endspan or a midspan is left up to the end-user.  The end device can use either powering technique.

The Powered Device (PD) is a network device like VoIP phones, Wireless Access Points, and IP cameras. which are capable of taking the power off the LAN cable, through the RJ-45 (8P8C) connector and using it to power itself. Some pre-standard PoE devices are incompatible with 802.3af equipment. More PoE ready PD’s are available every year  PoE ready end devices can reduce installation costs by as much as 90% over traditional powering techniques.  Among the newer PoE PD’s devices on the market or coming soon are IP Paging, Speaker Systems, POS Terminals, Door and Gate Security hardware, Public Information signs, Building Access, Temperature Control Systems, Stage Lighting, and Computers. These newer PD’s were pushing 802.3af to its limits and the IEEE began work to evolve the standard. This power limitation prevented “high power” devices that required up to 30W to be supported via the industry-standard PoE solution.

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Wi-Fi Mesh Standards Coming Soon

Wi-Fi Mesh Standards Coming SoonIt was noted in the July 2006 IEEE Spectrum, that soon (sometime in late 2008) Wi-Fi Access Points (AP’s) will be able to form mesh networks. Mesh Wi-Fi networks can help make wireless networks cheaper to build and operate by allowing a group of AP’s to communicate with each other and share only one high-speed connection to the Internet. This functionality was provisionally formalized in March 2006 by IEEE in the 802.11s standard. The standard still needs to go through several more IEEE approvals before it is “official.”

IEEE logoThe article pointed out that several manufacturers already have mesh technologies in their AP’s, including Motorola, Nortel, and Tropos. In our opinion, it is reasonable to expect some vendors to push pre-standard products to market prior to official IEEE approval. It is unclear how these pre-standard products will be tested for compatibility and interoperability with other vendor’s products. Vendors may take a “best shot” at their interpretation of the standard and then make their products “standard” after the fact via patches or upgrades. Of course, this patching would be done by the owners and at the owner’s expense, driving up the total cost of ownership.

Cherry, Steven. “Wi-Fi Nodes to Talk Amongst Themselves.” IEEE Spectrum. July 2006. 55-56.

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.