Does anyone have any recommendations for a database or IPAM platform that can house IS-IS addressing? Can’t seem to find anything out there. Thanks J~
My recommendation would be not to bother. :) Just encode the router loopback IPv4 address in the system identifier bytes and call it a day. On Mon, Apr 13, 2020 at 9:55 AM JASON BOTHE via NANOG <nanog@nanog.org> wrote:
Does anyone have any recommendations for a database or IPAM platform that can house IS-IS addressing? Can’t seem to find anything out there.
Thanks
J~
+1 On 4/13/20 4:02 PM, Tom Beecher wrote:
My recommendation would be not to bother. :)
Just encode the router loopback IPv4 address in the system identifier bytes and call it a day.
On Mon, Apr 13, 2020 at 9:55 AM JASON BOTHE via NANOG <nanog@nanog.org <mailto:nanog@nanog.org>> wrote:
Does anyone have any recommendations for a database or IPAM platform that can house IS-IS addressing? Can’t seem to find anything out there.
Thanks
J~
+1, No need to worry, just use your loopback address as the SystemID.
On 13 Apr 2020, at 18:02, Tom Beecher <beecher@beecher.cc> wrote:
My recommendation would be not to bother. :)
Just encode the router loopback IPv4 address in the system identifier bytes and call it a day.
On Mon, Apr 13, 2020 at 9:55 AM JASON BOTHE via NANOG <nanog@nanog.org <mailto:nanog@nanog.org>> wrote: Does anyone have any recommendations for a database or IPAM platform that can house IS-IS addressing? Can’t seem to find anything out there.
Thanks
J~
I've always wondered about folks' opinions about one thing, though: In y'all's opinion, do you prefer/recommend using base-10 digits or hex in your NSAP addresses? I like the former for readability, but the latter can (could) be better for automation. Maybe. I got into a heated argument about this once with ATM back in the day, but my brain's to frazzled to remember the takeaways. On 4/13/20 7:37 PM, Randy Bush wrote:
Just encode the router loopback IPv4 address in the system identifier bytes and call it a day.
i think asp wrote this up back in the early '90s. anyone have a cite?
randy
In y'all's opinion, do you prefer/recommend using base-10 digits or hex in your NSAP addresses?
it's the decimal representation of the octets lo0 { description "main loopback"; unit 0 { family inet { address 127.0.0.1/32; address 192.168.254.10/32 { primary; } } family iso { address 47.0001.1921.6825.4010.00; } } } some glorp omitted to protect the innocent randy
Our atm network in san diego was the full base 16 hex for the 13 byte nsap prefix of all the atm switches in our 4-level PNNI cloud This may be slightly off topic of ISIS practices though But, yeah, we didn't encode any switch mgmt. ip into the nsap addressing as I recall... just the pnni peer groups had hex identities -Aaron -----Original Message----- From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Bryan Holloway Sent: Monday, April 13, 2020 12:46 PM To: Randy Bush; Tom Beecher Cc: Nanog Subject: Re: IS-IS IPAM platform I've always wondered about folks' opinions about one thing, though: In y'all's opinion, do you prefer/recommend using base-10 digits or hex in your NSAP addresses? I like the former for readability, but the latter can (could) be better for automation. Maybe. I got into a heated argument about this once with ATM back in the day, but my brain's to frazzled to remember the takeaways. On 4/13/20 7:37 PM, Randy Bush wrote:
Just encode the router loopback IPv4 address in the system identifier bytes and call it a day.
i think asp wrote this up back in the early '90s. anyone have a cite?
randy
participants (6)
-
Aaron Gould -
Bryan Holloway -
JASON BOTHE -
Musa Stephen Honlue -
Randy Bush -
Tom Beecher