Then, does it mean the source router does not need to know the DLCI on the other end? And the frame-relay switch use the source DLCI to route the frames? Is it the truth that before exit the final switch, the q.922 address in the frame header is the source DLCI, after exit the final switch, the q.922 address will be changed to destination DLCI by the final switch, to indicate to the end router of which pvc the frame comes from?
Yeah, the source router does not need to know the DLCI at the destination side. It only cares about the DLCI at its end (hence, local significance).
An example follows:
16 39 63 48
RtrA ---- SwA ----- SwB ----- SwC ---- RtrB
In the above figure, RtrA, RtrB are routers, SwA, SwB, SwC are frame-relay switches and the number on top of the dotted lines is the DLCI. RtrA sends out q922 frames with DLCI = 16. SwA gets the frame and sends it out to SwB with a new DLCI of 39. SwB gets the frame and sends it out to SwB with a new DLCI of 63. Finally, SwC gets the frame and sends it out to the destination, RtrB with a final DLCI of 48.
Only the frame-relay switches need to know about the intervening DLCIs as the frame goes from RtrA to RtrB. The routers only need to know the DLCI that they see.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...