Saturday, 2 June 2018

Cisco ASA and PoE Access Point -Quick Note



Lot of People are searching over internet for LLDP or CDP support for Cisco ASA. Well Cisco Adoptive Security Appliance does not support this feature. If somebody ask WHY? the simple answer is.
IT IS SECURITY APPLIANCE AND IT DOES NOT SUPPORT CDP OR LLDP.

Reference:
https://supportforums.cisco.com/t5/lan-switching-and-routing/lldp-on-asa-5505/td-p/2308326

If you are still willing to discover neighbor devices  you can run this command

#show arp

or
check out this guy what he is saying.

Reference:
http://www.packetsar.com/cdp-on-an-asa-to-some-extent/

Topic of Today. 

Today we were working with PoE access Points. We configured all nodes and they started working as expected except one. Yes that one the TP-LINK TL-WA5210G. This device was nearly having CISCO ASA to provide PoE. Yes now problem begins. We were not having nearest PoE switch to make it work so we decided to power it up with Cisco ASA because it has some PoE ports.

Problem with Cisco ASA 

We connected AP with PoE on ASA after configuring Vlan and other stuff on the port but it did not power up the AP. Surprised!!! When we connected Cisco AP it started working automatically without making any changes in negotiation setting of port.
We dig into more details. Issued following commands on ASA

#show power inline
shows output with ports power statistics
<config-if>#power inline auto
Error!

Surprised again.
We did not mess with PoE thing on ASA before. Causally trying to configure as usual we do on Cisco PoE switches.

In short After digging into hardware compatibility sheet. We found Cisco ASA only support IEEE 802.3af  standard devices. Yes TP-LINK TL-WA5210g is not supported for that.

ASA chapter closed here. We did not get in luck from this device.


Problem with TP-Link  Passive PoE Injector Module

Well now we started looking at another solution when we came in mind about TP-Link PoE injector came with TL-WA5210g Box.
We took the Ethernet Link from ASA because this is only nearest LAN source and we connected injector LAN port to it and connected PoE AP cable on PoE port of injector.

This time injector seems very handy to quickly power up AP.

This Injector module runs over 12V 1 Amp adapter that also came in the box with device. But this time we did follow exactly instructions in the manuals where it was clearly written this device could support upto 60M of PoE length with Cat 6 or Cat5e cables. We might be wrong about it may be they considered PSU except injector with 12V DC power.

Our distance was exactly 130Ft and we had the same length cable to make this AP work. 130 Feets exactly becomes 39.624 Meters. Yes the cable connected to injector PoE port was about 130 feets long. Simply it did not work even the device never powered up properly. Worried again. We thought it might be a Voltage problem so we checked the following

Connected 24V adapter- No Luck TL-WA5210g supports upto 22v.
Conneted 12v 3 Amp adapter- same behavior as 12v 1amp
Connected 12v 2 Amp adapter - same behavior as 12v 1amp.

Damn still no luck.

If you are still reading you will definitely LAUGH at what we did next to test this device at over own.
We were more curios to check how much distance this device supports with PoE injector. We had 130ft Cat 5e cable so we decided to make it shorter as 100ft it might work on that because TP-LINK wrote in documentation it supports upto 60M. It was just 100Ft so we expected it would work. No Luck again.  So we  cut the cable 5 times as mentioned below

100ft long. No luck
80 ft long. No luck
60 ft long . No lcuk
50 ft. long. No luck - Same behavior as 130ft
40ft long..............................YES it started working. Wasted the whole cable at that point by cutting into many pieces....

Although we already replaced AP that works fine with Cisco ASA runs on Cat6, Just did testing because we did not find correct information on device manuals. To be continued....  

No comments:

Post a Comment