Trunking: Aironet 1200 - Cat2950

I have been having issues configuring trunking between my 1200AP and

2950 switch. After modifying the AP config with subif/dot1q/vlans i am able to maintain access to it (native vlan1 operational, Vlan3,4 are not). But as soon as I put the switchport in trunking mode (dot1q only on 2950) i lose all connectivity to the AP.

SSID AP mapped to VLAN 3 SSID PDA mapped to VLAN 4 native vlan 1

AP CONFIG:

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

VC2FL_AP1>en Password: VC2FL_AP1#show run Building configuration...

Current configuration : 2563 bytes ! version 12.2 no service pad service timestamps debug datetime msec service timestamps log datetime msec service password-encryption ! hostname VC2FL_AP1 ! enable secret 5 ! username Cisco password ip subnet-zero ! ! bridge irb ! ! interface Dot11Radio0 no ip address no ip route-cache ! ssid ap vlan 3 authentication open guest-mode ! ssid pda vlan 4 authentication open ! speed 1.0 basic-2.0 5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0

54.0 rts threshold 2312 power local cck 30 channel 2462 station-role root ! interface Dot11Radio0.1 encapsulation dot1Q 1 native no ip route-cache bridge-group 1 bridge-group 1 subscriber-loop-control bridge-group 1 block-unknown-source no bridge-group 1 source-learning no bridge-group 1 unicast-flooding bridge-group 1 spanning-disabled ! interface Dot11Radio0.3 encapsulation dot1Q 3 no ip route-cache bridge-group 3 bridge-group 3 subscriber-loop-control bridge-group 3 block-unknown-source no bridge-group 3 source-learning no bridge-group 3 unicast-flooding bridge-group 3 spanning-disabled ! interface Dot11Radio0.4 encapsulation dot1Q 4 no ip route-cache bridge-group 4 bridge-group 4 subscriber-loop-control bridge-group 4 block-unknown-source no bridge-group 4 source-learning no bridge-group 4 unicast-flooding bridge-group 4 spanning-disabled ! interface FastEthernet0 no ip address no ip route-cache duplex auto speed auto ! interface FastEthernet0.1 encapsulation dot1Q 1 native no ip route-cache bridge-group 1 no bridge-group 1 source-learning bridge-group 1 spanning-disabled ! interface FastEthernet0.3 encapsulation dot1Q 3 no ip route-cache bridge-group 3 no bridge-group 3 source-learning bridge-group 3 spanning-disabled ! interface FastEthernet0.4 encapsulation dot1Q 4 no ip route-cache bridge-group 4 no bridge-group 4 source-learning bridge-group 4 spanning-disabled ! interface BVI1 ip address 128.3.75.4 255.255.255.0 no ip route-cache ! ip default-gateway 128.3.75.1 ip http server ip http help-path
formatting link
http access-class 10 ip radius source-interface BVI1 access-list 10 permit 128.1.2.180 access-list 10 permit 128.1.1.221 access-list 10 permit 128.1.2.22 access-list 10 permit 128.1.1.53 access-list 10 permit 128.1.1.90 access-list 10 permit 128.1.1.99 bridge 1 route ip ! ! line con 0 line vty 0 4 access-class 10 in password login line vty 5 15 login ! end

--------------------------------------------------------------------------------------------------------------------------- Switch CONFIG:

------------------------ ! interface FastEthernet0/24 description VC2FL_AP1 switchport trunk allowed vlan 1,3,4 switchport mode trunk switchport nonegotiate !

Fa0/24 VC2FL_AP1 connected trunk a-full a-100

10/100BaseTX

ClosetF#show vtp status VTP Version : 2 Configuration Revision : 0 Maximum VLANs supported locally : 250 Number of existing VLANs : 8 VTP Operating Mode : Transparent VTP Domain Name : MedicalPark VTP Pruning Mode : Disabled VTP V2 Mode : Enabled VTP Traps Generation : Disabled MD5 digest : 0x62 0x2B 0xE8 0xD6 0x06 0xE1 0x58

0x44 Configuration last modified by 0.0.0.0 at 0-0-00 00:00:00 ClosetF#

---------------------------------------------------------------------------------------------------------- I would appreciate any suggestions or comments you may have about my problem!

Thanks, Todd

Reply to
toddedu
Loading thread data ...

What is the encapsulation used on the CAT 2950 ? try "switchport trunk encapsulation dot1q"

Reply to
Merv

The "encapsulation dot1q" part of the "switchport trunk" command is not supported on the 2950 platform, since dot1q is the only encapsulation supported.

Reply to
toddedu

snipped-for-privacy@yahoo.com schrieb:

The only thing I noticed that is different from our configuration is that your bridge-group 1 consists of interface Dot11Radio0.1 and FastEthernet0.1, whereas in our configuration, Dot11Radio0 is member of bridge-group 1, but I'm not quite sure if that could be related to your problem.

Martin

Reply to
Martin Turba

AP config looks fine. this is my switch config on a 3560

interface FastEthernet0/21 switchport trunk encapsulation dot1q switchport trunk native vlan 200 switchport trunk allowed vlan 200,341-346 switchport mode trunk

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

Reply to
BG

Martin I tried changing bridge-group 1 to the Dot11Radio0 and completely removing Dot11Radio0.1, there was no change in the AP responces. It may have something to do with Virtual-Dot11Radio interfaces. Looking at the output of "show vlan" on my AP and one i found online i can see a difference, but i can find no info on how to set up those virtual interfaces: show vlan from my AP:

-------------------------------------------------------------------------------------------------------- Virtual LAN ID: 1 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interfaces: Dot11Radio0.1 FastEthernet0.1

This is configured as native Vlan for the following interface(s) : Dot11Radio0 FastEthernet0

Protocols Configured: Address: Received: Transmitted: Bridging Bridge Group 1 7260 3409 Other 0 150

0 packets, 0 bytes input 1744 packets, 117461 bytes output Bridging Bridge Group 1 7260 3409 Other 0 150 3401 packets, 283323 bytes input 23 packets, 8280 bytes output

Virtual LAN ID: 3 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interfaces: Dot11Radio0.3 FastEthernet0.3

Protocols Configured: Address: Received: Transmitted: Bridging Bridge Group 3 783 869 Other 0 9

225 packets, 34462 bytes input 677 packets, 72060 bytes output Bridging Bridge Group 3 783 869 Other 0 9 558 packets, 45870 bytes input 205 packets, 33352 bytes output

Virtual LAN ID: 4 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interfaces: Dot11Radio0.4 FastEthernet0.4

Protocols Configured: Address: Received: Transmitted: Bridging Bridge Group 4 378 378 Other 0 7

0 packets, 0 bytes input 385 packets, 27237 bytes output Bridging Bridge Group 4 378 378 Other 0 7 378 packets, 25704 bytes input 0 packets, 0 bytes output

----------------------------------------------------------------------------------------------------------------------------- show vlan on cisco's web site:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Virtual LAN ID: 1 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interfaces: FastEthernet0.1 Dot11Radio0.1 Virtual-Dot11Radio0.1

This is configured as native Vlan for the following interface(s) : FastEthernet0 Dot11Radio0 Virtual-Dot11Radio0

Protocols Configured: Address: Received: Transmitted: Bridging Bridge Group 1 36954 0 Bridging Bridge Group 1 36954 0

Virtual LAN ID: 10 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interfaces: FastEthernet0.10 Dot11Radio0.10 Virtual-Dot11Radio0.10

Protocols Configured: Address: Received: Transmitted: Bridging Bridge Group 10 5297 0 Bridging Bridge Group 10 5297 0 Bridging Bridge Group 10 5297 0

Virtual LAN ID: 30 (IEEE 802.1Q Encapsulation)

vLAN Trunk Interfaces: FastEthernet0.30 Dot11Radio0.30 Virtual-Dot11Radio0.30

Protocols Configured: Address: Received: Transmitted: Bridging Bridge Group 30 5290 0 Bridging Bridge Group 30 5290 0 Bridging Bridge Group 30 5290 0

Reply to
toddedu

What version of IOS are you running on the AP? I heard that this was a problem with the bleeding edge version of IOS.

-E

Reply to
E Recio

The AP is running 12.3(7)JA2

Reply to
toddedu

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.