Ingress And Egress Rules - Siemens RUGGEDCOM ROX II User Manual

RUGGEDCOM ROX II
CLI User Guide
An edge port attaches to a single end device, such as a PC or Intelligent Electronic Device (IED). An edge port
carries traffic on the native VLAN.
Trunk ports are part of the network and carry traffic for all VLANs between switches. Trunk ports are automatically
members of all VLANs configured in the switch.
The switch can 'pass through' traffic, forwarding frames received on one trunk port out of another trunk port. The
trunk ports must be members of all VLANs that the 'pass through' traffic is part of, even if none of those VLANs
are used on edge ports.
Frames transmitted out of the port on all VLANs other than the port's native VLAN are always sent tagged.
NOTE
It may be desirable to manually restrict the traffic on the trunk to a specific group of VLANs. For
example, when the trunk connects to a device, such as a Layer 3 router, that supports a subset of the
available LANs. To prevent the trunk port from being a member of the VLAN, include it in the VLAN's
Forbidden Ports list.
For more information about the Forbidden Ports list, refer to
Port Type
Edge
Trunk
Section 5.37.1.4

Ingress and Egress Rules

Ingress and egress rules determine how traffic is received and transmitted by the switch.
Ingress rules are applied as follows to all frame when they are received by the switch:
a
Frame Received
VLAN ID associated with the frame
Frame dropped due to its tagged/untagged format
Frame dropped if the frame associated with the VLAN is not
configured (or learned) in the switch
Frame dropped if the ingress port is not a member of the VLAN the
frame is associated with
a
Does not depend on the ingress port's VLAN configuration parameters.
Egress rules are applied as follows to all frames when they are transmitted by the switch.
Ingress and Egress Rules
VLANs Supported PVID Format
1 (Native) Untagged
Configured
All Configured Tagged or Untagged
Usage
VLAN Unaware Networks: All frames are sent and received without
the need for VLAN tags.
Tagged VLAN Aware Networks: VLAN traffic domains are enforced on a
single VLAN.
switch-to-Switch Connections: VLANs must be manually created
and administered, or can be dynamically learned through GVRP.
Multiple-VLAN End Devices: Implement connections to end devices
that support multiple VLANs at the same time.
Untagged
PVID
No
Setup and Configuration
Section 5.37.1.5, "Forbidden Ports
Priority Tagged
(VID = 0)
PVID
No
Chapter 5
List".
Tagged (Valid VID)
VID in the Tag
No
Yes
No
543