[55962] in North American Network Operators' Group
Re: mfnx
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Wed Feb 19 21:09:27 2003
Date: Wed, 19 Feb 2003 21:08:51 -0500
From: Leo Bicknell <bicknell@ufp.org>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <Pine.GSO.4.44.0302191001530.12853-100000@mailpod.wworks.net>
Errors-To: owner-nanog-outgoing@merit.edu
--VS++wcV0S1rZb1Fb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In a message written on Wed, Feb 19, 2003 at 10:02:24AM -0800, Scott Granad=
os wrote:
> Nope, nobody responded from noc@above.net so I tried here, got a response
> and was all set. Helpful once you get around the noc where we had no
> response.
This is not in response to Scott's specific problem, but since MFN
was brought up I will inform a bit about how we work.
noc@ opens a ticket. You should get an auto reply within a couple
of minutes. No auto-reply probably means things are broken enough
that the phone is necessary. The phone number in the above.net,
mfnx.net, and AS 6461 records will (after a bit of IVR) get you to
someone who can help.
peering@ also opens a ticket. The same applies.
Note, for us noc@ and peering@ go two different places. noc@ is
realtime issues, peering@ is policy/requests and other non-realtime
issues.
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
--VS++wcV0S1rZb1Fb
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE+VDizNh6mMG5yMTYRAjG8AJ46ZriEjGFvEkcTrg/kVMuzSodk1ACePO5Y
67SByLbr8fHSF4IYT9XEKpo=
=+e2O
-----END PGP SIGNATURE-----
--VS++wcV0S1rZb1Fb--
