nanog mailing list archives
Re: OOB
From: Arnold Nipper <arnold () nipper de>
Date: Tue, 26 Jul 2011 16:40:23 +0200
on 26.07.2011 16:25 Cameron Byrne wrote:
On Jul 26, 2011 6:57 AM, "harbor235" <harbor235 () gmail com> wrote: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 anddiversepath 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,somemonitoring, 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?IMHO, it is always a good idea to have completely different infrastructure supporting Oob.
Fully acked, but with every service migrating to IP how do you make sure that the oob infrastructure is completely different from your production network? Best regards, Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold () nipper de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333
Attachment:
signature.asc
Description: OpenPGP digital signature
Current thread:
- RE: OOB, (continued)
- Re: OOB Arnold Nipper (Jul 26)
- Re: OOB harbor235 (Jul 26)