nanog mailing list archives

RE: OOB


From: Jensen Tyler <JTyler () fiberutilities com>
Date: Tue, 26 Jul 2011 09:19:02 -0500

We use a console server like 'opengear' with either a POTS or wireless broadband to provide access to stranded network.

Also monitors things like door alarm , temp, humidity and etc.

Jensen Tyler
Sr Engineering Manager
Fiberutilities Group, LLC


-----Original Message-----
From: Christopher Morrow [mailto:morrowc.lists () gmail com] 
Sent: Tuesday, July 26, 2011 9:14 AM
To: Paul Stewart
Cc: NANOG list
Subject: Re: OOB

On Tue, Jul 26, 2011 at 10:03 AM, Paul Stewart <paul () 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 () 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






Current thread: