This is correct fxp0 behaviour.
Just pick any other PFE interface for outband access and put it into
routing-instance.
In this fashion, with dedicated OOB PFE interface, if your M7i RE fails, you
still have OOB access to the node.
HTH
Alex
----- Original Message -----
From: "Alfred Schweder" <[email protected]>
To: <[email protected]>
Cc: "Alfred Schweder" <[email protected]>
Sent: Saturday, November 28, 2009 11:09 AM
Subject: [j-nsp] Routing Instance for fxp0
Hello
I'd like to seperate the routing instance of fxp0 for a real outband Mgmt
Access.
At our ciscos we configure:
ip vrf InternalMgmt
rd 42:42
int eth0
ip vrf forwarding InternalMgmt
ip address 192.168.1.123 255.255.255.0
ip route vrf InternalMgmt 0.0.0.0 0.0.0.0 192.168.1.1
So we can make an outband mgmt acces, but the mgmt interface is seperated
from
the global routing, and the network can used for other purpose.
At junos I cant configure it the same way:
a...@m7i# set routing-instances mgmt instance-type no-forwarding interface
fxp0.0
a...@m7i# commit confirmed
[edit routing-instances mgmt]
'interface fxp0.0'
RT Instance: Interface fxp0.0 not supported under routing-instances.
error: configuration check-out failed
Is there an other way to do this seperation ?
Thanks and regards,
--
Alf
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
