[j-nsp] SNMP on logical-system fxp0
Saku Ytti
saku at ytti.fi
Thu Apr 25 02:19:35 EDT 2013
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.
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:
* you can't send images over it (not supported in
any modern device, and even when supported, it's faster to fly to router
than upload hundreds of megs of data).
* you can't multiplex over it (oh RS232 is taken by some level2 tech who
has gone to lunch)
* rs232 console servers cost more than switches
* still fate-sharing CPU, memory etc, even with HW interrupted via break
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.
And it dos not really affect BOM at all, I can't imagine why we still have
ridiculously bad OOB capabilities.
And no, you would not use this FXP0 for SNMP or Netflow or whatnot.
--
++ytti
More information about the juniper-nsp
mailing list