[193003] in North American Network Operators' Group
Re: SNMP syslocation field for GPS coordinates, and use with
daemon@ATHENA.MIT.EDU (Eric Kuhnke)
Fri Dec 9 17:30:36 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <DB5PR04MB1111F2358DADAA3871CB3A62A7870@DB5PR04MB1111.eurprd04.prod.outlook.com>
From: Eric Kuhnke <eric.kuhnke@gmail.com>
Date: Fri, 9 Dec 2016 14:30:32 -0800
To: Alan Buxey <A.L.M.Buxey@lboro.ac.uk>
Cc: "nanog@nanog.org list" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Yes, that's along the lines of what I was thinking. Pre-define a certain
number of columns of data that will fit in the snmp syslocation field in
most devices (some vendors have surprisingly short string length limits,
grrrrrr). And use something like a pipe delimited CSV format in that field,
so it has the comma separated decimal degrees lat/long in one column, and
human readable street address in another.
Also worth noting that many recent SNMP-enabled, high capacity point to
point microwave radios have built in GPS receivers for timing and location
purposes, which gather elevation data (in meters above MSL usually).
Perhaps a column for elevation in meters MSL. The sort of data that is
useful for a mobile network operator with thousands of point to point RF
links on rooftops and towers, for auditing and compliance purposes.
On Fri, Dec 9, 2016 at 2:09 PM, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
> Yes. But don=E2=80=99t just put in coordinates... Put in other details an=
d use a
> standard separator =F0=9F=98=8A
>
>
>
>
>
> alan
>
