[ietf83-tech] Why do trunk ports have 'swport access vlan NN' left?
Chris Elliott
chelliot at pobox.com
Sat Mar 24 11:12:54 PDT 2012
On Sat, Mar 24, 2012 at 6:07 PM, Bjoern A. Zeeb <
bzeeb-lists at lists.zabbadoz.net> wrote:
> Hey,
>
> why configuring a monitor port again to debug that RA problem I seem
> to be seeing here still I notcied that there's a swport access vlan 48
> on the port to the AP? Why is that? It looks wrong.
Cruft. But not harmful. Does nothing unless port is in access mode.
sw-noc#sh run int gigabitEthernet 0/12
Building configuration...
>
> Current configuration : 384 bytes
> !
> interface GigabitEthernet0/12
> description ap131
> switchport access vlan 48
> switchport trunk encapsulation dot1q
> switchport trunk allowed vlan 1,7,8,16,32,80,96,112
> switchport mode trunk
> ip access-group killDHCPservers in
> ipv6 traffic-filter v6_Access_IN in
> snmp trap mac-notification change added
> snmp trap mac-notification change removed
> spanning-tree portfast trunk
> end
>
>
> wej is checking for other exmaples, I'll make him follow-up in case
> there are more.
>
>
> --
> Bjoern A. Zeeb You have to have visions!
> Stop bit received. Insert coin for new address family.
> _______________________________________________
> ietf83-tech mailing list
> ietf83-tech at daedelus.com
> http://www.daedelus.com/mailman/listinfo/ietf83-tech
>
--
Chris Elliott
chelliot at pobox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.daedelus.com/pipermail/ietf83-tech/attachments/20120324/3b29df6f/attachment.html
More information about the ietf83-tech
mailing list