On 04.12.2002 at 03:50:04, Greg Smith <[EMAIL PROTECTED]> wrote: > OSPF_Interface > IP_address=134.67.180.130 > Hello_Interval=10 > Dead_Router_Interval=40 > Router_priority=0 > Name=OSA1 > Cost0=2 > Subnet_mask=255.255.255.252 > Destination_Addr=134.67.180.129 > Attaches_To_Area=0.0.1.144 > MTU=1460 <snip> > when we display the > interface OSA1 from mproute the `designated router\' shows > up as 0.0.0.0. On z/OS the designated router matches the > destination address. Are we doing something wrong here ?
I don\'t think so. Designated Router is a specific term that identifies a core router that knows about all routes in the network. Kind of a \'router of last resort\'. Do your z/OS and z/VM systems connect directly to the same network (LAN)? If not (and I\'m guessing from your subnet mask that they can\'t be), it might be that the DR for the network (the entire network, that is) is not directly accessible from z/VM TCPIP, so is not added to the OSPF domain in your z/VM MPROUTE. A couple of hints (if you weren\'t aware already): all of the interfaces attached to the networks for which you want to propagate routes must be defined to MPROUTE with OSPF_Interface statements too, otherwise they will not be added to your OSPF domain and not re-advertised to your LAN. Also, resist ALL temptation to make your z/VM MPROUTE \"Designated Router Eligible\" -- it might be what you think you want for the Penguin Colony, but it is extremely likely to have catastrophic effects on routing in the rest of the network. HTH! Cheers, Vic
