[143028] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: OOB

daemon@ATHENA.MIT.EDU (Leigh Porter)
Tue Jul 26 14:49:08 2011

From: Leigh Porter <leigh.porter@ukbroadband.com>
To: Jeff Kell <jeff-kell@utc.edu>, nanog <nanog@nanog.org>
Date: Tue, 26 Jul 2011 18:49:04 +0000
In-Reply-To: <4E2ED5FC.5020700@utc.edu>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


We have a management VRF/L3VPN across the network but we also have automat=
ic backup via a OOB network. The OOB network is cheap, based on 3rd party =
ADSL connectivity that does not touch our network or rely on IXs etc.

We then run IPSec over the ADSL network.

The probability of both our node AND the DSL going down at the same time i=
s minimal, especially as the DSL is copper to a local exchange.

--
Leigh Porter


________________________________________
From: Jeff Kell [jeff-kell@utc.edu]
Sent: 26 July 2011 16:00
To: nanog
Subject: Re: OOB

On 7/26/2011 10:19 AM, Jensen Tyler wrote:
> We use a console server like 'opengear' with either a POTS or wireless b=
roadband to provide access to stranded network.
>

We use a management VRF (which is still technically in-band, but otherwise=
 quite
isolated), plus a few terminal servers for out-of-band console access to t=
he critical
devices.

Jeff


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email=20
______________________________________________________________________


home help back first fref pref prev next nref lref last post