The Forward Explicit Congestion Notification (FECN, pronounced "feckon") bit is set to zero by default, and will be set to 1 if congestion was experienced by the frame in the direction in which the frame was traveling. A DCE (frame relay switch) will set this bit, and a DTE (router) will receive it, and see that congestion was encountered along the frame's path.
If network congestion exists in the opposite direction in which the frame was traveling, the Backward Explicit Congestion Notification (BECN, pronounced "beckon") will be set to 1 by a DCE.
If this is your first time working with BECNs and FECNs, you might wonder why the BECN even exists - after all, why send a "backwards" notification? The BECN is actually the most important part of this entire process, since it's the BECN bit that indicates to the sender that it needs to slow down!
For example, frames sent from Kansas City to Green Bay encounter congestion in the FR cloud. A Frame Switch sets the FECN bit to 1. In order to alert KC that it's sending data too fast, GB will send return frames with the BECN bit set. When KC sees the BECN bit is set to 1, the KC router knows that the congestion occurred when frames were sent from KC to GB.
Frame Relay BECN Adaptive Shaping allows a router to dynamically throttle back on its transmission rate if it receives frames from the remote host with the BECN bit set. In this case, KC sees that the traffic it's sending to GB is encountering congestion, because the traffic coming back from GB has the BECN bit set. If BECN Adaptive Shaping is running on KC, that router will adjust to this congestion by slowing its transmission rate. When the BECNs stop coming in from GB, KC will begin to send at a faster rate.
BECN Adaptive Shaping is configured as follows:
KC(config)#int s0
KC(config-if)#frame-relay adaptive-shaping becn
To see how many frames are coming in and going out with the BECN and FECN bits set, run show frame pvc.
R3#show frame pvc
< some output removed for clarity >
input pkts 306 output pkts 609 in bytes 45566
out bytes 79364 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 568 out bcast bytes 75128
pvc create time 01:26:27, last time pvc status changed 01:26:27
Just watch the "in"s and "out"s of BECN, FECN, and DE in both the exam room and your production networks!
Ccna Practice Certification Exam # 1
To pass your CCNA exam and earn this coveted certification, you've got to master the seven layers of the OSI model and what each layer does. For those of you taking the two-exam path, you can expect quite a few OSI model questions on the Intro exam. In this seven-part series, we'll spend some time taking a look at each of the OSI model layers, starting with the Physical layer.
Often, CCNA candidates ask if the OSI model has any practical uses for network administrators. I used to wonder the same thing, and I can now tell you that the answer is definitely yes!
The OSI model isn't something you want to memorize and then forget about, as using the OSI model gives you a structured approach for troubleshooting. Whenever a network device isn't working properly, I always say to "start at the physical layer". The Physical layer is Layer One of the OSI model, and this is where troubleshooting should always start. Is the device on? Is it properly connected? If everything is fine at Layer One, you just move up to Layer Two, and continue in this structured fashion until the problem is identified.
The Physical layer is the layer at which bits are transmitted over the physical media. There is no routing or switching going on at this layer. The data has been broken down into more manageable pieces until the data takes the form of ones and zeroes at the Physical layer.
Even though there's no routing or switching at the Physical layer, CCNA candidates should be familiar with a couple of network devices that work at Layer One. A repeater is a device that regenerates an electrical signal, allowing the signal to travel longer distances without fading. (The process of an electrical signal gradually fading in strength over distance is "attenuation".) A hub is basically a multiport repeater, and both of these devices are considered Physical layer devices. Ethernet and Token Ring both operate at the Physical layer as well.
Learning the OSI model's Physical layer isn't just important in your CCNA exam studies, it's the first step in any network troubleshooting. After all, your network's end users are going to have a tough time sending print jobs to a printer that's turned off!
Chris Bryant has sinced written about articles on various topics from CISCO CCNA, Personal Desktop and Cisco CCNP. Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage , home of free and CCNP tutorials! Pass the. Chris Bryant's top article generates over 27100 views. to your Favourites.
