[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
OOB
- Subject: OOB
- From: morrowc.lists at gmail.com (Christopher Morrow)
- Date: Tue, 26 Jul 2011 10:14:21 -0400
- In-reply-to: <018501cc4b9c$bdb1f6c0$3915e440$@org>
- References: <CAB_zYd+Dswo=+YXSDz9qW4EKXX0LZE8i66rYDjFH+hXmhDpH5g@mail.gmail.com> <018501cc4b9c$bdb1f6c0$3915e440$@org>
On Tue, Jul 26, 2011 at 10:03 AM, Paul Stewart <paul at paulstewart.org> wrote:
> We do everything in-band with strict monitoring/policies in place.
what do you do if your in-band fails? if a router/switch/ROADM is
isolated from the rest of your network?
(isn't that the core point of the OP?)
> -----Original Message-----
> From: harbor235 [mailto:harbor235 at gmail.com]
> Sent: Tuesday, July 26, 2011 9:57 AM
> To: NANOG list
> Subject: OOB
>
> I am curious what is the best practice for OOB for a core
> infrastructure environment. Obviously, there is
> an OOB kit for customer managed devices via POTS, Ethernet, etc ... And
> there is OOB for core infrastructure
> typically a separate basic network that utilizes diverse carrier and diverse
> path when available.
>
> My question is, is it best practice to extend an inband VPN throughout for
> device management functions as well?
> And are all management services performed OOB, e.g network management, some
> monitoring, logging,
> authentication, flowdata, etc ..... If a management VPN is used is it also
> extended to managed customer devices?
>
> What else is can be done for remote management and troubleshooting
> capabilities?
>
> Mike
>
>
>
- Follow-Ups:
- OOB
- From: JTyler at fiberutilities.com (Jensen Tyler)
- OOB
- From: paul at paulstewart.org (Paul Stewart)
- OOB
- From: mansaxel at besserwisser.org (Måns Nilsson)
- References:
- OOB
- From: harbor235 at gmail.com (harbor235)
- OOB
- From: paul at paulstewart.org (Paul Stewart)