All,
Juniper does allow you to use a specific route table for management, it's
inet.0. You then create a VR, and place all your transit ports in the VR.
Ideal would be to do the reverse of that, create a VR and put the mgmt
ports in the VR, but it is not supported today. Still it is doable
Sorry, this is late, as far as this thread goes but I think I'd add one
more thing since I've got oob networks big enough to have to add l3
boundries in them...
juniper's not the only vendor with this issue by far...
On 9/19/11 13:59 , Jonathan Lassoff wrote:
On Mon, Sep 19, 2011 at 1:42 PM,
From a data center perspective we use it for building more than anything.
We're using Nexus kit in our DC's mostly and they have full OOB support. Its
nice to be able to load code, configure, burn-in, etc.. before you bring the
container onto the core. All of the benefits after the fact are just
On Sat, Sep 17, 2011 at 8:14 AM, Chris Evans chrisccnpsp...@gmail.com wrote:
One main downfall I'm running into is that I cannot copy or install software
using the FXP port as my source for traffic. Does anyone know of a command
that will allow me to select the logical system? The current
2011/9/17 Chris Evans chrisccnpsp...@gmail.com
Juniper devices have out of band ethernet ports, but have the HUGE HUGE
downfall of being in the main routing table conflicting with every other
route.
BTW, can anyone give a good real-world example of a _routed_ OOB management
network usage?
As far as I understand the whole concept of OOB MGT IP interface
Sorry, really meant dedicated physical interfaces, of course.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
On Mon, Sep 19, 2011 at 1:42 PM, Pavel Lunin plu...@senetsy.ru wrote:
2011/9/17 Chris Evans chrisccnpsp...@gmail.com
Juniper devices have out of band ethernet ports, but have the HUGE HUGE
downfall of being in the main routing table conflicting with every other
route.
BTW, can anyone
I see two ways one can go about this. Either programmatically tunnel into
an OOB L2 segment via a bastion host in an on-demand fashion, or point
some routes (dynamically, or otherwise) into your internal network for
management use.
The risk of pointing routes into your internal network, IMO,
On 09/19/11 16:59, Jonathan Lassoff wrote:
BTW, can anyone give a good real-world example of a_routed_ OOB management
network usage?
As far as I understand the whole concept of OOB MGT IP interface was
invented to make the management network totally isolated from any transit
traffic.
On Mon, Sep 19, 2011 at 2:16 PM, Pavel Lunin plu...@senetsy.ru wrote:
I see two ways one can go about this. Either programmatically tunnel into
an OOB L2 segment via a bastion host in an on-demand fashion, or point
some routes (dynamically, or otherwise) into your internal network for
On Mon, Sep 19, 2011 at 2:04 PM, Chris Morrow morr...@ops-netman.netwrote:
On 09/19/11 16:59, Jonathan Lassoff wrote:
BTW, can anyone give a good real-world example of a_routed_ OOB
management
network usage?
As far as I understand the whole concept of OOB MGT IP interface was
how about like management networks on ss7 deployments?
Not sure I correctly understand how the analogy from IP world should look
like. I can imagine a network of, say, access devices whether L2 or L3, for
which OOB mgt is really needed. But I don't know much people who use
dedicated mgt ports
On 9/19/11 14:04 , Chris Morrow wrote:
On 09/19/11 16:59, Jonathan Lassoff wrote:
BTW, can anyone give a good real-world example of a_routed_ OOB
management
network usage?
yeah, I I find that oob networks larger than a /21 are sort of hard to
manage therefore we split them up into l3
Juniper devices have out of band ethernet ports, but have the HUGE HUGE
downfall of being in the main routing table conflicting with every other
route. This limits it usage, however a work around is to put the FXP
interface into a logical system (on support devices). This has downfalls
too, but
Hi,
Don't know if this will work, but have you tried executing the file copy
command from within the logical system by set cli logical-system blah ?
if this works, i don't know if you can install software from that location
or not unfortunately.
On Sat, Sep 17, 2011 at 8:14 AM, Chris Evans
Not an answer, but a related work-around I have used is to put everything
_else_ in a virtual router instance.
This, however, has other major limitations, such as network/tunnel VPN's
terminate in, and other features depend on inet0.
The management interface not having a separate routing
I agree with all of these points, and it's a pretty classic problem with
managing devices that route.
The path I've gone down in most setups I've done is to simplify.
I place all devices within a site within an out of band LAN/broadcast
domain, and setup one (or two, depending on HA
17 matches
Mail list logo
