[j-nsp] Addressing fxp0

Manu Chao linux.yahoo at gmail.com
Mon Apr 24 02:59:52 EDT 2006


just put your fxp0 in a specific VRF (L3VPN).

routing-instance {
  OOB {
interface-type l3vpn
   interface fxp0.0
      routing-options {
         static {
            route 0/0 next-hop <OOB-IP-GW>

It should work


R/
Manu

On 4/23/06, Jee Kay <jeekay at gmail.com> wrote:
>
> I'm wondering how everyone else uses fxp0 for their OOB management...
>
> Basically, what I am doing at the moment is that I have a 'network
> management' VLAN. Into this VLAN does the Junipers' fxp0 interface, as
> well as management interfaces for the various L2 switches in a given
> environment.
>
> The 'correct' route for data to flow to this VLAN/subnet should be as
> follows:
>
> Client -> Router (Juniper..) -> Firewall -> Device being managed
>
> Now the problem is that the Router has an interface in the management
> subnet. As a result, when the packet hits the Juniper it says firstly
> 'oh look I have a directly connected interface to there', shortly
> followed by 'oh its fxp0; ICMP Destination Unreachable'.
>
> Is there any way to tell the Juniper to not attempt to use fxp0 for
> routing _at all_? Since it actually won't route to there anyway I
> don't really see why it's even considering this interface when making
> lookup decisions.
>
> Failing that, how does everyone else get around this problem?
>
>
> Thanks,
> Ras
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list