[188850] in North American Network Operators' Group
Re: Software for circuit documentation
daemon@ATHENA.MIT.EDU (Faisal Imtiaz)
Mon Apr 18 14:36:38 2016
X-Original-To: nanog@nanog.org
Date: Mon, 18 Apr 2016 18:36:31 +0000 (GMT)
From: Faisal Imtiaz <faisal@snappytelecom.net>
Cc: nanog list <nanog@nanog.org>
In-Reply-To: <61C208E8-7775-4F32-8372-A1BA613E59AB@beckman.org>
Errors-To: nanog-bounces@nanog.org
Anyone used these folks ? Any feedback ?
http://www.i-doit.com/
Regards
Faisal Imtiaz
Snappy Internet & Telecom
7266 SW 48 Street
Miami, FL 33155
Tel: 305 663 5518 x 232
Help-desk: (305)663-5518 Option 2 or Email: Support@Snappytelecom.net
----- Original Message -----
> From: "Mel Beckman" <mel@beckman.org>
> To: "Eric Kuhnke" <eric.kuhnke@gmail.com>
> Cc: "nanog list" <nanog@nanog.org>
> Sent: Monday, April 18, 2016 1:41:00 PM
> Subject: Re: Software for circuit documentation
> I=E2=80=99ve been meaning to get pricing for Ericsson=E2=80=99s Adaptive =
Inventory (formerly
> Granite) for a mid-sized ISP client. It=E2=80=99s world-class, but it may=
turn out to
> be insanely expensive. I=E2=80=99m also investigating cloud solutions. Mo=
st of the
> legacy commercial products are stuck in the LEC/CLEC inventory regime of =
T1s,
> T3s, and circuit grooming, with little support for MPLS, IPv6, or SLA
> management. Those are the big pain points today for most ISPs grappling w=
ith
> provisioning complexity.
>=20
> -mel
>=20
>=20
>> On Apr 18, 2016, at 10:09 AM, Eric Kuhnke <eric.kuhnke@gmail.com> wrote:
>>=20
>> mediawiki set up for individual user accounts, https only access, in
>> internal tool IP space/ACL/firewalled.
>>=20
>> First develop a hierarcically organized 'blank' template you can copy an=
d
>> paste for each POP, and then fill it out. Works great for large scale fi=
ber
>> patch panel assignments/crossconnect tracking, listings of equipment in =
a
>> POP, MPLS XCs, etc. It only works properly if the persons making each OS=
I
>> layer 1 change edit the wiki after each change (or the NOC/neteng staff
>> directing the field technicians edit it at the same time as updating a w=
ork
>> ticket).
>>=20
>> One of the great advantages is that it's near infinitely flexible in how
>> you can lay out and arrange the page, and tracks each and every change m=
ade
>> by ever user. In case of a mistake it's easy to revert to an earlier
>> version.
>>=20
>> I am not so sure about its use for OSP fiber tracking which gets into th=
e
>> territory of GIS software and customized vector based diagramming softwa=
re.
>>=20
>> On Mon, Apr 18, 2016 at 8:33 AM, Manuel Mar=C3=ADn <mmg@transtelco.net> =
wrote:
>>=20
>>> Dear Nanog community
>>>=20
>>> We are looking for a network inventory software to document logical
>>> circuits and fibers. We have been using Racktables for cross connects a=
nd
>>> racks documentation and works great, but we did find a way to document
>>> MPLS, Eline/ELAN, OTN, SONET, IP circuits, external plant (fibers), etc=
.
>>>=20
>>> I would appreciate if you can share what you use for documentation.
>>>=20
>>> Thank you and have a great day
>>>=20
>>> Regards
