Frame Processing
137
Frame Processing
All frames that are received on a physical interface and not explicitly
directed to the system or discarded are delivered to the corresponding
bridge port. The bridge port either forwards each frame to another
bridge port or discards it.
The system can discard an incoming frame for the following reasons:
■
The destination station is on the same segment as the source station.
■
The receive bridge port is blocked.
■
There is a problem with the frame.
The physical interface does not deliver frames with errors to the bridge
port. Thus, the
rxFrames
fields in the Ethernet statistics display and
bridge statistics display often report different values — that is, the
latter value is lower because it does not count frames in error.
■
A user-defined packet filter indicated not to receive the frame.
A frame that is forwarded from a physical interface to a bridge port is
then transmitted to a physical interface unless it is discarded. The system
can discard a frame at this point for the following reasons:
■
The transmit bridge port is blocked.
■
The frame is too large for the corresponding physical interface.
■
A user-defined packet filter indicated not to forward the frame.
Summary of Contents for CoreBuilder 3500
Page 44: ...44 CHAPTER 2 MANAGEMENT ACCESS ...
Page 58: ...58 CHAPTER 3 SYSTEM PARAMETERS ...
Page 86: ...86 CHAPTER 5 ETHERNET ...
Page 112: ...112 CHAPTER 6 FIBER DISTRIBUTED DATA INTERFACE FDDI ...
Page 208: ...208 CHAPTER 9 VIRTUAL LANS ...
Page 256: ...256 CHAPTER 10 PACKET FILTERING ...
Page 330: ...330 CHAPTER 12 VIRTUAL ROUTER REDUNDANCY PROTOCOL VRRP ...
Page 356: ...356 CHAPTER 13 IP MULTICAST ROUTING ...
Page 418: ...418 CHAPTER 14 OPEN SHORTEST PATH FIRST OSPF ...
Page 519: ...RSVP 519 Figure 94 Sample RSVP Configuration Source station End stations Routers ...
Page 566: ...566 CHAPTER 18 DEVICE MONITORING ...
Page 572: ...572 APPENDIX A TECHNICAL SUPPORT ...
Page 592: ...592 INDEX ...