Routing descriptor block how to code#

We are flowing from Area 0 (R2 is an ABR now) to Area 123 to Area 234. We have basically made area 123 a transit area that can carry traffic to destinations not in it’s own area.

Routing descriptor block how to code#

So in this case, we have allowed R2 to use it direct path to R3 instead of it’s own path through the backbone area. If you wish to block the number at certain times of day, you can use Time Profiles to accomplish this by routing to the Barred Short Code at specific times and to the desired User/Hunt Group at other times. “The OSPF Area Transit Capability feature provides an OSPF Area Border Router (ABR) with the ability to discover shorter paths through the transit area for forwarding traffic that would normally need to travel through the virtual-link path.” Routing entry for 192.168.1.0/24 Known via 'connected', distance 0, metric 0 (connected, via interface) Routing Descriptor Blocks: directly connected, via Ethernet0/0 Route metric is 0, traffic share count is 1 The solution to this problem is to configure a static route to Null0 for 192.168.0.0/16 on cust-R2. ok no problem, we will fix it on R2: R2(config)#router ospf 1 lets check by trace command: R2#trace 4.4.4.4 Route metric is 194, traffic share count is 1ĭefinitely, a loop has been occurred. Known via 'ospf 1', distance 110, metric 194, type inter area Lets take a look at that route towards R4 again: R2#sh ip route 4.4.4.4 OSPF_V元 from LOADING to FULL, Loading Done So we can build a virtual-link to R1: R2(config)#router ospf 1 Since, R2 does not have an interface in area 0.

Only the messages that go to the operator console have a destination section. When there is no destination indicated, the message is returned to the user. The routing and descriptor codes for these messages are shown with the message explanations. Now let’s say R2 needs to add a network to area 2 as follows R2(config)#int lo 0 z/OS Security Server RACF Messages and Codes. Route metric is 66, traffic share count is 1 Known via 'ospf 1', distance 110, metric 66, type inter area R3 has become an ABR and R2 will use R3 to get R4’s loopback: R2#sho ip route 4.4.4.4 R1 has a virtual link to R3 in order to connect area 234 to area 0. Now, I have disabled capability transit on all routers using below command, but I found that in this lab R2 is where the action is, so that might be only place we need to do it: router ospf 1 So we can understand easily where traffic is flowing. Each router’s interface IP address ends with the router number. I will focus on R2’s path to R4’s loopback of 4.4.4.4. So we can understand the issues which can create due to it as well understand more how OSPF works. We will understand the use of capability transit command.