26 Feb
2020
26 Feb
'20
5:30 a.m.
I just updated the current nodenames on a CISCO router after quite a
while using this. Posting this here in case this is useful for others
with CISCOs, possibly saving some awking and sedding.
This includes today's addition of A2RTR.
Best,
Supratim
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
26 Feb
26 Feb
8:57 a.m.
On 2020-02-26 05:30, Supratim Sanyal wrote:
I just updated the current nodenames on a CISCO router
after quite a
while using this. Posting this here in case this is useful for others
with CISCOs, possibly saving some awking and sedding.
This includes today's addition of A2RTR.
I can generate such a file automatically on any change to the nodename
database, if people would find it useful.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
11:35 a.m.
I don't have a Cisco router anymore, but I find the automatic generation
of the nodename database in Tops-20 SETNOD format to be /very/// useful.
I have a weekly recurring batch job which checks connectivity to MIM::
and if it is up, it grabs a copy of the file.? This is pushed through
SETNOD to update the monitor's data base.? Back in the day, it would
have been called trivial in that there is no editing: no TECO and
certainly no awk or sed.? I suspect it would largely be useful on
Tops-10 if you have any familiarity with Galaxy batch.
It has a limitation in that it while it will report removed nodes, it
does not remove them from the monitor's data base. This requires an
undocumented feature in NODE% and some in SETNOD enhancements to compute
set differences.? As I've said in the past, SETNOD could benefit from a
buff and polish or perhaps a complete rewrite.
Drop me a note if you'd like a copy.
------------------------------------------------------------------------
On 2/26/20 2:57 AM, Johnny Billquist wrote:
I can generate such a file automatically on any change to the nodename
database, if people would find it useful.
? Johnny
> ------------------------------------------------------------------------
> On 2020-02-26 05:30, Supratim Sanyal wrote:
>
> I just updated the current nodenames on a CISCO router after quite a
> while using this. Posting this here in case this is useful for others
> with CISCOs, possibly saving some awking and sedding.
>
> This includes today's addition of A2RTR.
1733
days inactive
1733
days old
2 comments
3 participants
participants (3)
-
bqt＠softjar.se -
supratim＠riseup.net -
tommytimesharing＠gmail.com