nanog mailing list archives
Re: OOB
From: Cameron Byrne <cb.list6 () gmail com>
Date: Tue, 26 Jul 2011 07:25:14 -0700
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 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?
IMHO, it is always a good idea to have completely different infrastructure supporting Oob. It is the only way you can recover remotely from many types of network errors. If the router is hung at rommon, somebody has to get on console .... or accidentally removes your igp instanance ... But, the business criticality of the network needs to justify the cost (dial, DSL, 3rd party L3 vpn ....) Cb
Mike
Current thread:
- Re: OOB, (continued)
- Re: OOB Måns Nilsson (Jul 26)
- Re: OOB Christopher Morrow (Jul 26)
- Re: OOB Joel Jaeggli (Jul 26)
- Re: OOB Måns Nilsson (Jul 26)
- Re: OOB PC (Jul 27)
- Re: OOB Arnold Nipper (Jul 26)
- Re: OOB harbor235 (Jul 26)