[j-nsp] SNMP on logical-system fxp0

[Brandon Ross]

On Thu, 25 Apr 2013, Saku Ytti wrote:

> On (2013-04-24 20:54 -0400), Jeff Wheeler wrote:
>
>> My view is that fxp0 is an out-of-band interface for manual
>> intervention; not one that I ever use for SNMP.
>
> My view is that fxp0 is completely useless interface.
>
> It's not OOB, it's completely fate-sharing the freebsd/junos.

OOB in this context refers to having a different path through the network 
than the path used for production IP traffic.  I see the value in having 
an Ethernet/IP interface that is not fate-sharing with the core OS as 
well, but that doesn't make fxp0 completely useless as previously stated.

> In RS232 you can at least do 'panic-on-break', not having to rely
> freebsd/junos to work to kick the box.
> But RS232 sucks otherwise:

I'm not sure why we are suddenly debating the benefits and drawbacks of 
RS232.  The two interface types are there for very different reasons.

> Of course correct solution would be, to connect fxp0 to separate HW,
> running its own miniOS, from which you could copy imagees, reload RE etc.

That essentially what we are talking about.  Connect fxp0 to a SEPARATE 
switch that is used for only out of band traffic.  You then use this 
network to copy images, etc.  What am I missing here?

> And no, you would not use this FXP0 for SNMP or Netflow or whatnot.

Sure you can, I've done it, others here have said they've done it. 
Assuming the OOB network is well protected from outside traffic to avoid 
attacks and the like, why not?

-- 
Brandon Ross                                      Yahoo & AIM:  BrandonNRoss
+1-404-635-6667                                                ICQ:  2269442
Schedule a meeting:  https://doodle.com/bross            Skype:  brandonross