cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1077
Views
0
Helpful
6
Replies

Not getting MAC on port - Cisco WS-C3850-48P

Hello guys,

I have a WAP AIR-CAP702-W-B-K9 connected to a Cisco 3850 port and for some reason the port does not see its mac address.

I have tried.

1.Shut and no shut

2. power inline never and back to power inline auto (to reboot AP)

3. TDR cable test went fine.

4. used a different port on the switch with the same result

5. Rebooted switch

The switch has many other APs on it and they all fine (3600's model). There was a 702w AP on the port in question and I replaced the AP due to faulty radio but now the new AP straight from Cisco wont work due to the MAC address issue.

Some configuration:

current interface configuration:

interface GigabitEthernet1/0/27
 switchport trunk allowed vlan 8,139
 switchport mode trunk
 switchport nonegotiate
 ip device tracking maximum 20
 no vtp
 spanning-tree portfast
 spanning-tree guard root
end

previous interface configuration before starting troubleshoot

interface GigabitEthernet1/0/25
 switchport trunk allowed vlan 8,139
 switchport mode trunk
 switchport nonegotiate
 ip device tracking maximum 20
 power inline never
 power inline police
 power efficient-ethernet auto
 no vtp
 spanning-tree portfast
 spanning-tree guard root
 service-policy input qos-ingress-marking
 service-policy output qos-egress-user
 ip dhcp snooping limit rate 15
end

a port that has an AP and its working:

interface GigabitEthernet1/0/26
 switchport trunk allowed vlan 8,139
 switchport mode trunk
 switchport nonegotiate
 switchport voice vlan 1
 ip device tracking maximum 20
 power inline police
 power efficient-ethernet auto
 no vtp
 spanning-tree portfast
 spanning-tree guard root
 service-policy input qos-ingress-marking
 service-policy output qos-egress-user
 ip dhcp snooping limit rate 15
end

Interface status:

GigabitEthernet1/0/27 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 008e.735c.111b (bia 008e.735c.111b)
  Description: beac858-apt103ap01 (10.125.37.91)
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:39, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 17000 bits/sec, 22 packets/sec
     320 packets input, 92498 bytes, 0 no buffer
     Received 320 broadcasts (38 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 38 multicast, 0 pause input
     0 input packets with dribble condition detected
     83047 packets output, 17443371 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

Please help!

Thank you!

6 Replies 6

lpassmore
Level 1
Level 1

Look to the device and find out why it is not generating any packets in

  5 minute input rate 0 bits/sec, 0 packets/sec

Is it broken?

Do you have another access point (preferably same model) to test on the same switch port?

I did. I tested a working AP in the same port and it ended up working. That is why I did what I said on my previous reply and it is now working but I don't understand why I had to do that in order to work

It sounds like that specific AP has a different configuration on it from your standard which is why it works when you configure the switchport as an Access port. Have you tried factory resetting the AP?

No its not broken. I received it from Cisco recently and it worked when I plugged in the office.

I got it to work now doing some logically "weird" configuration.

I made the port to be access port with the Wireless Vlan

The controller noticed the AP

Configured the AP in controller, under Vlan tagging, to enable and Trunk Vlan ID to be the wireless vlan and the ports to be data Vlan ID.

Reconfigured the switch port just like what I posted and I was able to get everything to work fine.

Does it make sense ? I dont see this being logical within my knowledge.

Thanks

Normally you would set the management IP of the AP on VLAN 0 and set the native VLAN on the trunk to the appropriate value.  Always tag the Wireless Data VLAN.

I suspect 8 is your management VLAN.  If you want to run the AP as untagged, you need to set switchport trunk native vlan 8 on the interface.

I suspect the AP was trying to send data untagged to join the controller and that was ending up in VLAN 1 on your switch

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: