Government and Military

Reply
This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.
New Contributor

Possible Juniper LLDP issue

Hello all,

I am having issues with powering 270 series APs via Juniper SRX220H-POE (SRX220) device(s). I am working with a particular gov't unit as an integrator, so I do not have direct access to the Juniper device(s). There are currently two 7010 controllers running VRRP for redundancy, two AP-274-F1s, and two AP-277-F1s plugged into one SRX220H-POE.The four APs acting as Mesh Portals can be seen by the controller, but no Mesh Points can be seen. In working with the gov't POC, LLDP has been enabled on the SRX and Class 4/max power has been set on the four ports that have APs connected to them. Below is the output I get from the master controller while troubleshooting the issue.

(***** Master) #show ap debug system-status ap-name B********_Mesh_Portal | begin Power

Power Status

------------

Operational State          POE-AF: Ethernet port 1 disabled; All radios disabled;

-----------------          ------------------------------------------------------

Current HW State           POE-AF: Ethernet port 1 disabled; All radios disabled;

LLDP Negotiated POE Power  0.0W

 

Bandwidth Contracts Information

Received BWM Config:

        ACL                                                            DIR  Contract-ID PerUser UseCount Rate

 

Allocated Contracts:

Contract-ID Rate       UseCount Available-Bytes Max-Bytes Policed-Bytes

System Status Script

---------------------

aruba_dbg_system_status Start time: Thu Feb 16 15:48:59 PST 2017

====== netstat -nla ======

Active Internet connections (servers and established)

Proto Recv-Q Send-Q Local Address           Foreign Address         State

udp        0      0 127.0.0.1:19999         0.0.0.0:*

udp        0      0 0.0.0.0:54838           0.0.0.0:*

udp        0      0 0.0.0.0:1144            0.0.0.0:*

udp        0      0 :::8209                 :::*

udp        0      0 :::8211                 :::*

udp        0      0 :::546                  :::*

raw        0      0 :::58                   :::*                    0

Active UNIX domain sockets (servers and established)

Proto RefCnt Flags       Type       State         I-Node Path

unix  2      [ ]         DGRAM                    1299   /tmp/.sock/8223.sock

unix  2      [ ]         DGRAM                    1301   /tmp/.sock/9223.sock

unix  2      [ ]         DGRAM                    1318   /tmp/.sock/8451.sock

unix  2      [ ]         DGRAM                    1320   /tmp/.sock/9451.sock

unix  2      [ ]         DGRAM                    1322   /tmp/.sock/8452.sock

unix  2      [ ]         DGRAM                    1324   /tmp/.sock/9452.sock

unix  2      [ ]         DGRAM                    1457   /tmp/.sock/8225.sock

unix  2      [ ]         DGRAM                    1459   /tmp/.sock/9225.sock

unix  2      [ ]         DGRAM                    1480   /tmp/.sock/8433.sock

unix  2      [ ]         DGRAM                    1482   /tmp/.sock/9433.sock

unix  2      [ ]         DGRAM                    1229   /tmp/.sock/8370.sock

unix  2      [ ]         DGRAM                    1487   /tmp/.sock/15208.sock

unix  2      [ ]         DGRAM                    1231   /tmp/.sock/9370.sock

unix  2      [ ]         DGRAM                    1489   /tmp/.sock/16208.sock

unix  2      [ ]         DGRAM                    1234   /tmp/msghdlr_comm

unix  2      [ ]         DGRAM                    1493   /tmp/meshd_hostapd_sync

unix  2      [ ]         DGRAM                    1238   /tmp/.sock/8210.sock

unix  4      [ ]         DGRAM                    1241   /dev/log

unix  2      [ ]         DGRAM                    1513   /tmp/.sock/8410.sock

unix  2      [ ]         DGRAM                    1515   /tmp/.sock/9410.sock

unix  2      [ ]         DGRAM                    1611

unix  2      [ ]         DGRAM                    1509

unix  2      [ ]         STREAM                   1002

unix  3      [ ]         STREAM     CONNECTED     996

unix  3      [ ]         STREAM     CONNECTED     995

 

/proc/net/softnet_stat:

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00001f2d 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

 

cat  /proc/net/anul_ap_stats

 

ANUL AP stats

TX-txnid:0

RX-txnid:0

TX-Tot:0

RX-Tot:0

RX-Err:0

RX-Throttle:0

Non-80211:0

Mgmt-tot:0

CTL:0

Data:0

Other:0

Mgmt-err:0

Mgmt-subtypes:

aruba_dbg_system_status Finished time: Thu Feb 16 15:48:59 PST 2017

aruba_dbg_system_status: Read 3201 bytes in 61 lines. Truncated:FALSE

 

As a possible fix, I enabled LLDP on the controller uplink port as well, but the SRX is inline between the controller and APs.

 

(***** Master) # show lldp interface gigabitethernet 0/0/0

 

Interface: GE0/0/0

LLDP Tx: Enabled, LLDP Rx: Enabled

Proprietary Neighbor Discovery: Disabled

LLDP-MED: Disabled

Fast Transmit interval: 1, Fast Transmit message counter: 4

Transmit interval: 30, Transmit hold 4, Hold timer: 120

 

(***** Master) # show lldp statistics ?

interface               Interface

|                       Output Modifiers

 

(***** Master) # show lldp statistics interface gigabitethernet 0/0/0

 

LLDP Statistics

---------------

Interface  Received  Unknown TLVs  Malformed  Transmitted

---------  --------  ------------  ---------  -----------

GE0/0/0    0         0             0          79

 (***** Master) # show lldp neighbor interface gigabitethernet 0/0/0

 

Capability codes: (R)Router, (B)Bridge, (A)Access Point, (P)Phone, (S)Station

                  (r)Repeater, (O)Other

LLDP Neighbor Information

-------------------------

Local Intf  Chassis ID  Capability  Remote Intf  Expiry (Secs)  System Name

----------  ----------  ----------  -----------  -------------  -----------

 

Number of neighbors: 0

 

 

3 REPLIES
Guru Elite

Re: Possible Juniper LLDP issue

What version of ArubaOS is this?


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

New Contributor

Re: Possible Juniper LLDP issue

6.4.4.10

Highlighted
New Contributor

Re: Possible Juniper LLDP issue

By adding an inline PoE+ power injector between the SRX and AP, the AP comes up with the following:

 

(***** Master) #show ap debug system-status ap-name B385-TS3A_Mesh_Portal | begin Power

Power Status

------------

Operational State          POE-AT: No restrictions

-----------------          -----------------------

Current HW State           POE-AT: No restrictions

LLDP Negotiated POE Power  0.0W

 

Bandwidth Contracts Information

-------------------------------

Received BWM Config:

--------------------

--------------------

        ACL                                                            DIR  Contract-ID PerUser UseCount Rate

 

Allocated Contracts:

--------------------

Contract-ID Rate       UseCount Available-Bytes Max-Bytes Policed-Bytes

 

Unfortunately, using inine power injectors throughout this solution is not feasible. I've simply done so for testing.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: