入过滤(Ingress Filtering)

部署运行你感兴趣的模型镜像

入端口(ingress port)是交换机上的这样一个端口——数据包从该端口流入交换机,并且必须在该端口确定其vlan 属性。如果端口的入站过滤(ingress filtering)被设置为生效(enabled),那么,交换机将检查数据包包头中的vlan 信息(如果存在的话),并决定是否转发该数据包。
如果数据包中包含vlan 信息(即被加过标记),那么,入端口首先判定入端口本身是否是标记vlan 的成员端口。如果不是,那么,该数据包将被丢弃,不进行传送。如果是成员端口,那么,交换机将进一步判定目的端口是否是标记vlan 的成员端口。如果不是,那么,该数据包也将被丢弃;反之,该数据包将被转发到目的端口。
如果数据包中不包含vlan 信息(即未被加过标记),那么,入端口将用其pvid 作为数据包的vid 为数据包加上标记(如果该端口是tagging port)。交换机随后判断目的端口是否与入端口属于同一个vlan(即具有相同的vid),如果不是,那么,该数据包将被丢弃,不进行传送。反之,该数据包将被转发到目的端口。
这就是入站过滤(ingress filtering)。在入端口处就丢弃掉那些不在同一个vlan 中的数据包,可以尽可能地保存带宽, 减少后续的目的端口处理数据包的工作量。

您可能感兴趣的与本文相关的镜像

Stable-Diffusion-3.5

Stable-Diffusion-3.5

图片生成
Stable-Diffusion

Stable Diffusion 3.5 (SD 3.5) 是由 Stability AI 推出的新一代文本到图像生成模型,相比 3.0 版本,它提升了图像质量、运行速度和硬件效率

Per-Ingress ePort Unknown/Unregistered/Broadcast Filtering Commands This section defines:  Unknown unicast filtering command – Section 10.11.2.1, Per-Ingress ePort Unknown Unicast Filtering  Unregistered multicast filtering command – Section 10.11.2.2, Per-Ingress ePort Unregistered Multicast Filtering  Unregistered broadcast filtering command – Section 10.11.2.3, Per-Ingress ePort Unregistered Broadcast Filtering The following command types are supported:  FORWARD  MIRROR  TRAP  SOFT DROP  HARD DROP If a HARD DROP or SOFT DROP command is assigned to the packet, it is counted by the Bridge Drop Counter (Section 10.15.1.1, Bridge Drop Counter). The resolution between per-Ingress ePort unknown/unregistered filtering command and per-eVLAN unknown/unregistered filtering command is done as any other packet command resolution (Section 10.14.1, Bridge Phase 1 Packet Command Resolution). 10.11.2.1 Per-Ingress ePort Unknown Unicast Filtering An Unknown Unicast packet is defined as a packet whose MAC DA is Unicast and whose FDB destination lookup does not find a matching entry. A filtering command for Unknown unicast traffic is configured per ingress ePort. If the packet command for this filter is MIRROR or TRAP to the CPU, the packet is assigned a CPU code of BRIDGED_UNKN_UC_TRAP/MIRROR. Configuration To configure the Unknown Unicast Filtering command for an ePort, use the <Ingress Port Unknown UC filter Command> field in the Ingress Bridge ePort Table (Table 392 p. 2333). 10.11.2.2 Per-Ingress ePort Unregistered Multicast Filtering An Unregistered Multicast is defined as a packet with a Multicast MAC DA, whose FDB lookup did not result in a match. The FDB lookup can be IP-Multicast-based as well (Section 10.7, IPv4/6 Multicast (S, G, V) Bridging). A filtering command for unregistered multicast traffic is configured per ingress ePort. If the packet command for this filter is MIRROR or TRAP to CPU, the packet is assigned a CPU code of BRIDGED_NON_IPv4/6_UNREG_MC_TRAP/MIRROR. Configuration To configure the Unregistered Multicast Filtering command for an ePort, use the <Ingress port unregistered MC filter command> field in the Ingress Bridge ePort Table (Table 392 p. 2333). 10.11.2.3 Per-Ingress ePort Unregistered Broadcast Filtering An unregistered Broadcast packet is defined as a packet with a Broadcast MAC DA, whose FDB lookup did not result in a match. A filtering command for unregistered broadcast traffic is configured per ingress ePort. If the packet command for this filter is MIRROR or TRAP to the CPU, the packet is assigned a CPU code of IPv4_BC_TRAP/MIRROR. Configuration To configure the Unregistered Broadcast Filtering command for an ePort, use the <Ingress port BC filter command> field in the Ingress Bridge ePort Table (Table 392 p. 2332). Per-Egress Physical Port Unknown/Unregistered/Broadcast Filtering Commands This section defines:  Unknown unicast filtering command – Section 10.11.3.1, Per-Egress Physical Port Unknown Unicast Filter  Unregistered multicast filtering command – Section 10.11.3.2, Per-Egress Physical Port Unregistered Multicast Filter  Unregistered broadcast filtering command – Section 10.11.3.3, Per-Egress physical Port Unregistered Broadcast Filter 10.11.3.1 Per-Egress Physical Port Unknown Unicast Filter An Unknown Unicast packet is defined as a packet whose MAC DA is Unicast and whose FDB destination lookup does not find a matching entry. Unknown Unicast packets can be filtered based on the packet Egress physical port configuration. Configuration To enable/disable Unknown Unicast packet filtering on a given Egress physical port, use the <Port<32*n+31>> Unknown Unicast Filter Enable>–<Port<32*n+0>> Unknown Unicast Filter Enable> field in the Unknown UC Filter En <n> Register (n=0–3) (Table 860 p. 2795). 10.11.3.2 Per-Egress Physical Port Unregistered Multicast Filter An Unregistered Multicast packet is defined by the following conditions:  MAC DA is Multicast (but not Broadcast)  FDB destination lookup does not find a matching entry  The packet was not routed Unregistered Multicast packets can be filtered based on the packet Egress physical Port configuration. Configuration To enable/disable Unregistered Multicast packet filtering on a given Egress physical Port, use the <Port<32*n+31>> Unregistered Multicast Filtering Enable>–<Port<32*n+0>> Unregistered Multicast Filtering Enable> field in the Unregistered MC Filter En <n> Register (n=0–3) (Table 861 p. 2798). 10.11.3.3 Per-Egress physical Port Unregistered Broadcast Filter An Unregistered Multicast packet is defined by the following conditions:  MAC DA is the Broadcast address  FDB destination lookup does not find a matching entry  The packet was not routed Unregistered Broadcast packets can be filtered based on the packet Egress physical port configuration. Configuration To enable/disable unregistered Broadcast packet filtering on a given Egress physical Port, use the <Port<32*n+31>> Unregistered Broadcast Filtering Enable>–<Port<32*n+0>> Unregistered Broadcast Filtering Enable> field in the Unregistered BC Filter En <n> Register (n=0–3) (Table 862 p. 2802)翻译并解释
11-18
Bridge Counters 10.15.1 Bridge Ingress Counters 10.15.1.1 Bridge Drop Counter The Bridge engine can assign a HARD or SOFT DROP command to packets for many reasons. The Bridge engine maintains a 32-bit counter that can be configured to count all bridge packet drop events, or only count packet drop events due to a specifically configured reason. The specific reasons for a Bridge drop are:  Spanning Tree port state drop (Spanning Tree Filtering)  FDB entry command drop (FDB Entry Command)  MAC SA Moved Event (Moved MAC Command)  ARP CPU code (Router Security Checks for Bridged IPv4/6 and ARP Traffic)  MAC SA is DA (Source Address is destination address)  Source IP Equals Destination IP Event (Source IP (SIP) is Destination IP (DIP))  TCP/UDP Source Port Equals Destination Port (TCP/UDP Source Port is Destination Port)  Invalid SA drop (FDB Source MAC Learning) (FDB Source MAC Learning)  TCP Packet With Fin Flag And Without Ack (TCP Flags with FIN without ACK)  IEEE Reserved Drop (IEEE Reserved Multicast)  ICMP (MLD and Other IPv6 ICMP)  TCP Packet Without Full Header (TCP Without Full Header)  IPv4 RIPv1 (Routing Information Protocol (RIPv1))  IPv6 Neighbor Solicitation (IPv6 Neighbor Solicitation)  Unregistered IPv4 Broadcast drop (Per-eVLAN Unregistered IPv4 Broadcast Filtering)  Unregistered non-IPv4 Broadcast drop (Per-eVLAN Unregistered Non-IPv4 Broadcast Filtering)  Cisco command (Proprietary Layer 2 Control Multicast)  Unregistered Non-IP Multicast drop (Per-eVLAN Unregistered Non-IPv4/6 Multicast Filtering)  Unregistered IPv4 Multicast drop (Per-eVLAN Unregistered IPv4 Multicast Filtering) Unregistered IPv6 Multicast drop (Per-eVLAN Unregistered IPv6 Multicast Filtering)  Unknown Unicast drop (Per-eVLAN Unknown Unicast Filtering)  Secure Automatic Learning Unknown SA drop (Secure Automatic Learning)  eVLAN not valid drop (Invalid eVLAN Filtering)  Physical Port not member in VLAN drop (eVLAN Ingress Filtering)  eVLAN range drop (eVLAN Range Filtering)  Moved static address drop (FDB Static Entries)  MAC Spoof Protection Event (MAC Spoof Protection)  ARP MAC SA Mismatch (ARP MAC SA Mismatch)  Controlled Learning Unknown MAC SA drop (Source MAC Address CPU Controlled Learning)  SYN with data (TCP SYN Packet with Data)  TCP over Multicast (TCP over MAC Multicast/Broadcast)  Bridge Access Matrix (Bridge Access Matrix)  Fragmented ICMPv4 (Fragmented ICMPv4)  TCP Flags Zero (Zero TCP Flags)  TCP Flags FIN, URG and PSH (TCP Flags with FIN-URG-PSH)  TCP Flag SYN and FIN (TCP Flags with SYN-FIN)  TCP Flags SYN and RST (TCP Flags with SYN-RST)  TCP/UDP Port is Zero (Zero TCP/UDP Port)  Bridge Access Matrix Drop (Bridge Access Matrix)  Acceptable Frame Type (Acceptable Frame Type Filtering)  eVLAN MRU (eVLAN Maximum Receive Unit (MRU))  Rate Limiting drop (Ingress Port Storm Rate Limit Enforcement)  Local ePort drop (Bridge Local Switching)  IP Multicast In Iana Range Drop (IP and Non-IP Multicast Filtering)  IP Multicast Not In Iana Range Drop (IP and Non-IP Multicast Filtering)  DSA Tag Source Device is Local Device Drop (Loop Detection) Configuration  To configure the Bridge Drop Counter reason, use the <Bridge Drop Counter Mode> field in the Bridge Global Configuration1 Register (Table 320 p. 2219).  To read/write to the Bridge Drop Counter, read/write to the <BridgeDropCnt> field in the Bridge Filter Counter Register (Table 368 p. 2309) according 10.15.1.2 Bridge Host Counters A set of Host Group counters is maintained for a configured MAC Source Address and MAC Destination Address. These counters correspond to RMON-1 MIB (RFC 2819) Host counters. Configuration  To configure the MAC DA to be used by the host counters, use the MAC Address Count0 Register (Table 373 p. 2311) and the MAC Address Count1 Register (Table 374 p. 2311).  To configure the MAC SA to be used by the host counters, use the MAC Address Count1 Register (Table 374 p. 2311) and the MAC Address Count2 Register (Table 375 p. 2311).  The hostInPkts counter can be read from the Host Incoming Packets Count Register (Table 376 p. 2311). This counter is clear-on-read.  The hostOutPkts counter can be read from Host Outgoing Packets Count Register (Table 377 p. 2311). This counter is clear-on-read.  The hostOutBroadcastPkts counter can be read from Host Outgoing Packets Count Register (Table 377 p. 2311) This counter is clear-on-read.  The hostOutMulticastPkts counter can be read from Host Outgoing Packets Count Register (Table 377 p. 2311). This counter is clear-on-read. 10.15.1.3 Bridge Matrix Group A packet counter is maintained for a single, CPU-configured MAC source/Destination Address pair. These counters correspond to RMON-1 MIB (RFC 2819) Matrix counters. Configuration Read the matrixSDPkts counter from the <MatrixSDPkts> field in the Matrix Source/Destination Packet Count Register (Table 380 p. 2312) accordingly. This counter is clear-on-read. Table 34: Host Counters Counter Name Counter Description hostInPkts The number of good packets1 with a MAC DA matching the CPU-configured MAC DA. hostOutPkts The number of good packets with a MAC SA matching the CPU-configured MAC SA. hostOutBroadcast Pkts The number of good Broadcast packets with a MAC SA matching the configured MAC SA. hostOutMulticastPkts The number of good Multicast Packets with a MAC SA matching the configured MAC SA. 1. Good packets are error-free Ethernet packets that have a valid frame length, per RFC 2819. Table 35: Matrix Source Destination Counters Counter Name Counter Description matrixSDPkts The number of good packets with a MAC SA/DA matching the CPU￾configured MAC SA/DA 10.15.1.4 Bridge ePort/eVLAN/Device Counters There are two sets of Ingress ePort/eVLAN/device bridge counters—Set-0 and Set-1. Each counter-set is applied to a configured packet Ingress stream based on eVLAN and ePort. eVLAN and ePort can be set as a wildcard (traffic from all ePorts for the eVLAN), all traffic for the ePort, and all traffic in the switch. Each counter-set can be configured independently. Each counter-set maintains four counters as described in Table 36. Table 36: Ingress Port/VLAN/Device Counters per Counter-Set Counter Name Counter Description Bridge In Frames Counter Number of packets received by the bridge according to the specified mode criteria. Depending on the mode selected, this counter can be used to satisfy Bridge and SMON MIB objects (RFC 2674 and RFC 2613) such as: • dot1dTpPortInFrames (mode 1). • smonVlanIdStatsTotalPkts (mode 2). • dot1qTpVlanPortInFrames (mode 3). eVLAN Ingress Filtered Packet Counter Number of packets discarded due to invalid eVLAN, eVLAN not in Range, or Ingress physical port not eVLAN member. This counter can be used to satisfy Bridge MIB objectdot1qTpVlanPortInDiscard (mode 3) Security Filtered Packet Counter Number of packets discarded due to Security Filtering measures: • FDB command drop (Section 10.4.4). • Invalid SA drop (Section 10.4.8). • Moved Static address is a Security Breach drop (Section 10.4.9). • Unknown source MAC command drop, and unknown source MAC is Security breach (Section 10.4.8.4). Bridge Filtered Packet Counter Number of packets dropped by the Bridge for reasons other than eVLAN Ingress filtering and Security breach events. This counter counts packets dropped due any of the following reasons: • Rate Limiting drop (Section 10.10, Ingress Port Storm Rate Limit Enforcement) • Local port drop (Section 10.13, Bridge Local Switching) • Spanning Tree state drop (Section 10.3, Spanning Tree Filtering) • IP Multicast drop (Section 10.12, IP and Non-IP Multicast Filtering) • Non-IP Multicast drop (Section 10.12) • Unregistered Non-IPM Multicast drop (Section 10.11.1.2, Per-eVLAN Unregistered Non-IPv4/6 Multicast Filtering) • Unregistered IPv6 Multicast drop (Section 10.11.1.4, Per-eVLAN Unregistered IPv6 Multicast Filtering) • Unregistered IPv4 Multicast drop (Section 10.11.1.3, Per-eVLAN Unregistered IPv4 Multicast Filtering) • Unknown Unicast drop (Section 10.11.1.1, Per-eVLAN Unknown Unicast Filtering) • Unregistered IPv4 Broadcast drop (Section 10.11.1.5, Per-eVLAN Unregistered IPv4 Broadcast Filtering) • Unregistered non-IPv4 Broadcast drop (Section 10.11.1.6, Per-eVLAN Unregistered Non-IPv4 Broadcast Filtering) This counter can be used to satisfy Bridge MIB objects: • dot1dTpPortInDiscards • dot1qTpVlanPortInDiscards Configuration  To configure counter set 0/1 criteria, use the <Set<n>ePort>, and <Set<n>CntMode> fields in the Counters Set<n> Configuration 0 Register (n=0–1) (Table 381 p. 2312) and the <Set<n>eVLAN> field in the Counters Set<n> Configuration 1 Register (n=0–1) (Table 382 p. 2312).  The following counters can be read from their respective registers. These counters are clear on read: • Set<n> VLAN Ingress Filtered Packet Count Register (n=0–1) (Table 384 p. 2313) • Set<n> Security Filtered Packet Count Register (n=0–1) (Table 385 p. 2313) • Set<n> Bridge Filtered Packet Count Register (n=0–1) (Table 386 p. 2313) • Set<n> Incoming Packet Count Register (n=0–1) (Table 383 p. 2313)翻译一下
最新发布
11-18
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值