Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Beware AIR-PWRINJ6= does NOT work as published with B-domain APs - DOCs are defective

Beware AIR-PWRINJ6= does NOT work as published with B-domain APs - DOCs are defective.

TAC is stumped; the specific testing where this defect was revealed was using AIR-AP2802I-B-K9; however the bigger APs are even more hungry so good luck following the spec there too :)

How does this manifest itself on the APs? Both radios are DOWN and console log (serial console that is) clearly shows:

Nov 15 20:27:50 brain: boot time: 51.140 seconds, 7684 processes spawned
Nov 15 20:27:50 kernel: [*11/15/2016 20:27:50.7476] Radio1 not started, not enough POE power
Nov 15 20:27:50 kernel: [*11/15/2016 20:27:50.7605] DOT11_DRV[1]: set_channel Channel set to 36
Nov 15 20:27:54 kernel: [*11/15/2016 20:27:54.9204] waiting for POE negotiation to complete
Nov 15 20:27:54 kernel: [*11/15/2016 20:27:54.9204]
Nov 15 20:27:59 kernel: [*11/15/2016 20:27:59.9209] waiting for POE negotiation to complete
Nov 15 20:27:59 kernel: [*11/15/2016 20:27:59.9209]
Nov 15 20:28:04 kernel: [*11/15/2016 20:28:04.9214] waiting for POE negotiation to complete
Nov 15 20:28:04 kernel: [*11/15/2016 20:28:04.9214]
Nov 15 20:28:09 kernel: [*11/15/2016 20:28:09.9219] waiting for POE negotiation to complete
Nov 15 20:28:09 kernel: [*11/15/2016 20:28:09.9219]
Nov 15 20:28:14 kernel: [*11/15/2016 20:28:14.9224] waiting for POE negotiation to complete
Nov 15 20:28:14 kernel: [*11/15/2016 20:28:14.9224]
Nov 15 20:28:19 kernel: [*11/15/2016 20:28:19.9228] waiting for POE negotiation to complete
Nov 15 20:28:19 kernel: [*11/15/2016 20:28:19.9228]
Nov 15 20:28:24 kernel: [*11/15/2016 20:28:24.9233] waiting for POE negotiation to complete
Nov 15 20:28:24 kernel: [*11/15/2016 20:28:24.9233]
Nov 15 20:28:29 kernel: [*11/15/2016 20:28:29.9238] waiting for POE negotiation to complete

Nov 15 20:30:38 kernel: [*11/15/2016 20:30:38.0000] CAPWAP State: DTLS Setup
Nov 15 20:30:41 kernel: [*11/15/2016 20:30:41.0897] CAPWAP State: Join
Nov 15 20:30:45 kernel: [*11/15/2016 20:30:45.7953] CAPWAP State: Image Data
Nov 15 20:30:45 kernel: [*11/15/2016 20:30:45.7954] CAPWAP State: Configure
Nov 15 20:30:45 kernel: [*11/15/2016 20:30:45.8897] Radio0 not started, not enough POE power
Nov 15 20:30:45 kernel: [*11/15/2016 20:30:45.8900] Radio1 not started, not enough POE power
Nov 15 20:30:45 kernel: [*11/15/2016 20:30:45.8905] Radio0 not started, not enough POE power
Nov 15 20:30:45 kernel: [*11/15/2016 20:30:45.8909] Radio1 not started, not enough POE power
Nov 15 20:30:46 kernel: [*11/15/2016 20:30:46.4610] Radio0 not started, not enough POE power
Nov 15 20:30:46 kernel: [*11/15/2016 20:30:46.5234] Radio1 not started, not enough POE power
Nov 15 20:30:46 syslog: +ifconfig wired0 promisc
Nov 15 20:30:46 kernel: [*11/15/2016 20:30:46.8110] Radio0 not started, not enough POE power
Nov 15 20:30:46 kernel: [*11/15/2016 20:30:46.8115] Radio1 not started, not enough POE power
Nov 15 20:30:46 kernel: [*11/15/2016 20:30:46.8122] Radio0 not started, not enough POE power
Nov 15 20:30:46 kernel: [*11/15/2016 20:30:46.8130] Radio1 not started, not enough POE power
Nov 15 20:30:46 kernel: [*11/15/2016 20:30:46.8254] Radio0 not started, not enough POE power
Nov 15 20:30:47 kernel: [*11/15/2016 20:30:47.0067] Radio1 not started, not enough POE power
Nov 15 20:30:47 kernel: [*11/15/2016 20:30:47.1612] CAPWAP State: Run

7 REPLIES
Hall of Fame Super Gold

This looks like a firmware

This looks like a firmware issue.  

Ask TAC if they can publish an engineering fix for you.

New Member

Hi bbiandov,

Hi 

Did you get this issue resolved?

New Member

@cheng.cathy  I was wrong -

[@cheng.cathy]  I was wrong - it wasn't an injector issue; it was a crappy batch of AIR-AP2802I-B-K9 and all brand new. We got them from a class A distributor not some shady shop but Ciscio's bare metal box quality has gone where TAC has been for years...

Bottom line -- I got one big RMA crated and returned all AIR-AP2802I-B-K9 then re-ordered them in smaller batches and the new ones work. 

It seems there are batches of defective AIR-AP2802I-B-K9 in the manufacturing time period from week 40 of 2016 on until the beginning of 2017

New Member

Hello bbiandov,

Hello bbiandov,

I hope you are doing well, my name is Jonathan and I am one of the Engineers here at Cisco's Small Business.


I am sorry to hear that the unit is not what you expected, also i am afraid this is not the correct department as we are the Small Business tech support line, we don't handle this specific units AIR-AP2802I-B-K9, if you need further assistance with this units, please feel free to contact us at the following number. 1-800-553-2447.

thanks.

Hall of Fame Super Gold

It seems there are batches of

It seems there are batches of defective AIR-AP2802I-B-K9 in the manufacturing time period from week 40 of 2016 on until the beginning of 2017

Can you post the Cisco Bug ID for this or part of the TAC communication about this subject matter? 

I believe other people can benefit from this information.  

NOTE:  This thread has been moved from Small Business to the Wireless group.

New Member

@Leo Laohoo  Bug ID? Leo just

leolaohoo  Bug ID? No I don't have one because creating one would require coherent communication with a customer in trouble by competently staffed TAC, research and causality process in order to arrive at a root cause, no? 

Pardon the bit of sarcasm, the conclusion was based on cat-and-mouse chase between purchasing different batches and a steady stream of RMA boxes back to distribution. At the end a stable fleet of working AIR-AP2802I-B-K9 was achieved and all I can share postmortem are observations taken for each physical unit as it arrived or it was sent back.

The "seems" piece in my opinion was meant to clarify that this isn't an "official" determination.

Hall of Fame Super Gold

Ok, thanks for the

Ok, thanks for the information.

540
Views
0
Helpful
7
Replies
CreatePlease to create content