Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • NOTE: It is not my choice to have VLAN 48 as the trunk native VLAN - I'd like to correct that, but I have to schedule a service outage to do so... so not today. :( Commented Oct 9, 2014 at 23:33
  • To add: I am beginning to suspect a frame tagging issue, but am not wholly certain either way. Commented Oct 9, 2014 at 23:34
  • A colleague pointed out the following command: "vlan associate subnet" under the VLAN configurations - this appears to be a Layer 3 inspection way to assign VLAN tags to frames by looking at source-IP in the encapsulated packets. Commented Oct 10, 2014 at 0:05
  • 1
    I am beginning to suspect that the edge switches are re-writing VLAN tags on return traffic from the core. Commented Oct 10, 2014 at 0:05