BR-VDX6740 - vlan: traffic between access and trunk ports.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-07-2018 03:13 PM
hi guys,
with a client vlan "unaware" and port channel as this one:
Interface name : Port-channel 25
Switchport mode : trunk
Fcoeport enabled : no
Ingress filter : enable
Acceptable frame types : vlan-tagged only
Native Vlan : 4
Active Vlans : 2,4,1310
Inactive Vlans : -
MAC learn disable Vlans : -
and another port channel like:
Interface name : Port-channel 29
Switchport mode : access
Fcoeport enabled : no
Ingress filter : enable
Acceptable frame types : vlan-untagged only
Default Vlan : 4
Active Vlans : 4
Inactive Vlans : -
MAC learn disable Vlans : -
Is "Acceptable frame types" the reason why nodes cannot talk to each other?
How to rectify this problem?
many thanks, L.
with a client vlan "unaware" and port channel as this one:
Interface name : Port-channel 25
Switchport mode : trunk
Fcoeport enabled : no
Ingress filter : enable
Acceptable frame types : vlan-tagged only
Native Vlan : 4
Active Vlans : 2,4,1310
Inactive Vlans : -
MAC learn disable Vlans : -
and another port channel like:
Interface name : Port-channel 29
Switchport mode : access
Fcoeport enabled : no
Ingress filter : enable
Acceptable frame types : vlan-untagged only
Default Vlan : 4
Active Vlans : 4
Inactive Vlans : -
MAC learn disable Vlans : -
Is "Acceptable frame types" the reason why nodes cannot talk to each other?
How to rectify this problem?
many thanks, L.
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-08-2018 05:32 PM
Where do I find that system / how to open a TAC case?
There should be a simple bugzilla.
All I could find were support contract stuff and I do not think I have such thing.
There should be a simple bugzilla.
All I could find were support contract stuff and I do not think I have such thing.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-08-2018 02:31 PM
Hi Pawel,
Yes, there is a similar system. The issue seems cosmetic, but still a bug. Could you open a TAC case regarding that output?
Yes, there is a similar system. The issue seems cosmetic, but still a bug. Could you open a TAC case regarding that output?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-08-2018 12:00 PM
I'm still new - don't know if ExtremeNetworks runs something like bugzilla but this qualifies as a bug in my mind - "Acceptable frame types : vlan-tagged only"
I get something very wrong or am missing something here. Otherwise it's misleading big time - I would have not made this post if it had not been for that output info.
I get something very wrong or am missing something here. Otherwise it's misleading big time - I would have not made this post if it had not been for that output info.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-07-2018 04:18 PM
Yes, that's the correct command. It maybe just show output issue, since the packets pass correctly
