[j-nsp] OSPF Area Problem with Directly Connected Vlan not being Advertised

Jose Madrid jmadrid2 at gmail.com
Sat May 22 14:09:47 EDT 2010


Hello everyone,

I am setting up some new devices at a physically separate data center
and am seeing some weird OSPF behavior.  In order to get the default
route injected, I setup this new DC as a stub area (area 0.0.0.1) and
that worked well enough.  In this stub area, I have 3 devices, 2
Brocade and 1 Juniper J2320.  I have a policy on the Juniper that
exports direct and static routes.  I added a new vlan on the Juniper
which works fine and from a host on the Vlan, I can reach the Juniper.
 For some reason, although this vlan is turned on and configured, the
/29 in use wont be advertised into OSPF.  In order to make it work, I
was forced to add the specific sub-interface for vlan 50 into my OSPF
config and was wondering if you guys could tell me how/why I can
overcome this behavior.  The reason this is a problem is that now
whenever we add a new customer vlan, I have to remind the tech to add
that specific vlan to OSPF and its just adding overhead to what is an
automatic process when using area 0.  Below is my config and comments
are welcome.  I would like to also add that I am rather new to OSPF
and to be honest havent gotten too down and dirty as it has always
"just worked" :)

term connected {
    from {
        protocol direct;
        family inet;
    }
    then accept;
}
term connected6 {
    from {
        protocol direct;
        family inet6;
    }
    then accept;
}

    ospf {
export [ static connected ];
area 0.0.0.1 {
    stub default-metric 40 summaries;
    interface ge-0/0/0.13 {
        metric 10;
    }
    interface ge-0/0/1.14 {
        metric 10;
    }
    interface lo0.0 {
        passive;
    }
    interface ge-0/0/0.50 {    <-----THIS HAD TO BE ADDED FOR THIS TO
BE ADVERTISED
        metric 10;
    }
}

P.S. I turned on OSPF debugging and found the following error
May 22 13:32:29.532875 OSPF:  Route x.x.x.x/29 with no TSI, route ignored
May 22 13:34:17.314319 OSPF:  Route x.x.x.x/29 with no TSI, route ignored


-- 
It has to start somewhere, it has to start sometime.  What better
place than here? What better time than now?


More information about the juniper-nsp mailing list