The DLCI doesn't have anything to do the forwarding or routing mechanism of Frame Relay, other than to specify the L2 destination address. The actual forwarding path is unseen by the end devices, and can often change without notice. You throw data into the Frame Relay network, and it finds its way to the other side. Like magic.
Thanks! Therefore, like routing table in router, or forwarding mechanism in layer2 which can be configured, users of frame relay can't configure any routing or forwarding mechanism?
Thanks. useful for my exam. from India
Thanks for the Information, however as far as I know we don't use the OSI Model, we use the TCP/IP
The OSI model is the industry standard. You generally won't see any references to the TCP/IP model outside of a classroom.
@@professormesser He obviously doesn't listen to your study group, think I've heard you preach about the OSI model vs TCP/IP model about 30 times now.
Thank you
The Frame Relay use the "DLCI" to provide reference of routing, not "magically" go to anther side as you said in this video.
The DLCI doesn't have anything to do the forwarding or routing mechanism of Frame Relay, other than to specify the L2 destination address. The actual forwarding path is unseen by the end devices, and can often change without notice. You throw data into the Frame Relay network, and it finds its way to the other side. Like magic.
Thanks! Therefore, like routing table in router, or forwarding mechanism in layer2 which can be configured, users of frame relay can't configure any routing or forwarding mechanism?