[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
OOB
- Subject: OOB
- From: paul at paulstewart.org (Paul Stewart)
- Date: Tue, 26 Jul 2011 10:03:05 -0400
- In-reply-to: <CAB_zYd+Dswo=+YXSDz9qW4EKXX0LZE8i66rYDjFH+hXmhDpH5g@mail.gmail.com>
- References: <CAB_zYd+Dswo=+YXSDz9qW4EKXX0LZE8i66rYDjFH+hXmhDpH5g@mail.gmail.com>
We do everything in-band with strict monitoring/policies in place.
Paul
-----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: cabenth at gmail.com (Eric Clark)
- OOB
- From: morrowc.lists at gmail.com (Christopher Morrow)
- References:
- OOB
- From: harbor235 at gmail.com (harbor235)