Re: [j-nsp] IPAM like tool/DB for managing communities

Hello there, Same issue with PHPIPAM. RDs are the unique identifier and always mapping towards the VRF name. You can add custom fields to VRFs where you can place your RTs. If you are running a unique RD per PE the VRF is configured in then the RD is not that important anyway it’s the RTs

Re: [j-nsp] IPAM like tool/DB for managing communities

Yes I tried NINAP, but as others IPAM tools out there it has this 1:1 relationship between VRF and RT I could hack around this and use the main RT thing as sort of an arbitrary ID (or main VRF RT) and add the actual/additional RTs as TAGs. Tried the same thing in netbox. But these are hacks

Re: [j-nsp] MPC7 / QSFP28 I2C issue

Ha, well done! Thank you for sharing Theo. :-) -Original Message- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Theo Voss Sent: 15 December 2018 12:08 To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] MPC7 / QSFP28 I2C issue Hi all, we’ve found the root