[143001] in North American Network Operators' Group
Re: OOB
daemon@ATHENA.MIT.EDU (Arnold Nipper)
Tue Jul 26 10:41:35 2011
Date: Tue, 26 Jul 2011 16:40:23 +0200
From: Arnold Nipper <arnold@nipper.de>
To: Cameron Byrne <cb.list6@gmail.com>
In-Reply-To: <CAD6AjGTcxzh42bM=hk80CPo5yU5eB55_aY5iK0bKe27oRP03hQ@mail.gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7AFEF9E14E88830ABFAFE4A7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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 ... An=
d
>> 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?
>>
>=20
> IMHO, it is always a good idea to have completely different infrastruct=
ure
> 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
--=20
Arnold Nipper / nIPper consulting, Sandhausen, Germany
email: arnold@nipper.de phone: +49 6224 9259 299
mobile: +49 152 53717690 fax: +49 6224 9259 333
--------------enig7AFEF9E14E88830ABFAFE4A7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4u0dcACgkQrz6CwpRB/ExMnACgrs0+oJgfALYxSv+Lk3gKYhjX
+5gAnirOfoB8h8Bj+XitYyl16U4ovWy4
=xYKz
-----END PGP SIGNATURE-----
--------------enig7AFEF9E14E88830ABFAFE4A7--
