[c-nsp] stange vlan 1 output
Pete Templin
petelists at templin.org
Fri Oct 7 13:40:58 EDT 2016
DTP faulted on the port in question, causing it to not trunk even though
the mode is trunk.
Any chance the adjacent device is a 4948? I've seen that platform do
this a lot where the 4948 participates in DTP enough for the other side
to drop to access but the 4948 forgets to match it.
On 10/7/2016 9:17 AM, james list wrote:
> Hi experts,
>
> an issue on my c6500 sup720 12.2(33)SXI5.
>
>
>
> I have two equal trunk configuration ports:
>
>
>
> xxx#sh run int g8/45
>
> interface GigabitEthernet8/45
>
> switchport
>
> switchport trunk encapsulation dot1q
>
> switchport trunk allowed vlan 269
>
> switchport mode trunk
>
> logging event link-status
>
> logging event trunk-status
>
> load-interval 30
>
> spanning-tree portfast edge trunk
>
>
>
> xxx#sh run int g9/27
>
> interface GigabitEthernet9/27
>
> switchport
>
> switchport trunk encapsulation dot1q
>
> switchport trunk allowed vlan 48
>
> switchport mode trunk
>
> logging event link-status
>
> logging event trunk-status
>
> load-interval 30
>
> udld port
>
> spanning-tree portfast edge trunk
>
>
>
> Do you see any reason why using "show interface status" I see vlan 1
> associated to g9/27 instead of trunk as for example of interface g8/45 ?
>
>
>
> xxx#sh interface status
>
> Port Name Status Vlan
> Duplex Speed Type
>
> Gi8/45 xxxx connected trunk
> full 1000 1000BaseT
>
> Gi9/27 xxxx connected 1
> full 1000 1000BaseT
>
>
>
> I see as well native vlan is not associated to gi9/27
>
>
>
> xxx#sh interfaces trunk
>
>
>
> Port Mode Encapsulation Status Native vlan
>
> Te1/1 on 802.1q trunking 1
>
> Te1/2 on 802.1q trunking 1
>
> Te1/3 on 802.1q trunking 1
>
> Te1/4 on 802.1q trunking 1
>
> Te2/1 on 802.1q trunking 1
>
> Te2/2 on 802.1q trunking 1
>
> Te2/3 on 802.1q trunking 1
>
> Te3/4 on 802.1q trunking 1
>
> Te3/6 on 802.1q trunking 1
>
> Te3/7 on 802.1q trunking 1
>
> Te3/8 on 802.1q trunking 1
>
> Te7/1 on 802.1q trunking 1
>
> Te7/3 on 802.1q trunking 1
>
> Te7/9 on 802.1q trunking 1
>
> Te7/13 on 802.1q trunking 1
>
> Te7/14 on 802.1q trunking 1
>
> Gi8/3 on 802.1q trunking 1
>
> Gi8/9 on 802.1q trunking 1
>
> Gi8/13 on 802.1q trunking 1
>
> Gi8/29 on 802.1q trunking 1
>
> Gi8/30 on 802.1q trunking 1
>
> Gi8/43 on 802.1q trunking 1
>
> Gi8/44 on 802.1q trunking 1
>
> Gi8/45 on 802.1q trunking 1
>
> Gi9/8 on 802.1q trunking 1
>
> Gi9/9 on 802.1q trunking 1
>
> Gi9/17 on 802.1q trunking 1
>
> Gi9/18 on 802.1q trunking 1
>
> Gi9/20 on 802.1q trunking 1
>
> Gi9/21 on 802.1q trunking 1
>
> Gi9/29 on 802.1q trunking 1
>
> Gi9/30 on 802.1q trunking 1
>
> Gi9/33 on 802.1q trunking 1
>
> Gi9/35 on 802.1q trunking 1
>
> Gi9/40 on 802.1q trunking 1
>
> Gi9/43 on 802.1q trunking 1
>
> Gi9/45 on 802.1q trunking 1
>
> Gi9/46 on 802.1q trunking 1
>
>
>
> Thanks in advance for any feedback.
>
>
> Cheers
>
> James
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list