Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."
Today's Topics:
1. Re: Using API to search for IPBlock custom attributes
(Matej Vadnjal)
----------------------------------------------------------------------
Message: 1
Date: Mon, 7 Aug 2017 08:10:47 +0200
From: Matej Vadnjal <[email protected]>
Subject: Re: [Netdot-users] Using API to search for IPBlock custom
attributes
To: [email protected], "Sparks, Alan (GSTS-SDO)"
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Hi Alan
I haven't tested this, but I think you could filter for the wanted
IpblockAttr and then get all subnets that have that attribute from that.
Kind regards
Matej
On 07/14/2017 10:14 PM, Sparks, Alan (GSTS-SDO) wrote:
>
> I?m researching how I could implement something like the following in
> Netdot using pynetdot. Can?t find any hints Googling, so?
>
> I?m considering ?tagging? IP blocks using the custom attributes
> functionality. For instance, to tag which region the block is
> assigned to, production or nonproduction, etc. Was looking for some
> way to search IP blocks then for those attributes, to find the
> specific container I need to allocate from.
>
> I haven?t been able to find anything on how (or if I could) search
> with pynetdot (or the API) for an ipblock with a given custom
> attribute name and value. Has anyone done that? Otherwise, it would
> appear I?d have to enumerate all the containers and their attributes
> and filter by hand. Was hoping there?s a better way.
>
> Any suggestions on what I might look at appreciated.
>
> -Alan
>
>
>
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20170807/554c32b4/attachment-0001.html
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 100, Issue 4
********************************************
