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. Juniper Logical System Discovery (Michael H Lambert)
2. RESTful interface questions (Patrick Landry)
----------------------------------------------------------------------
Message: 1
Date: Fri, 8 Feb 2013 16:04:30 -0500
From: Michael H Lambert <[email protected]>
Subject: [Netdot-users] Juniper Logical System Discovery
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
It doesn't appear that logical systems on Junipers are automatically discovered
(or if they are, I have something misconfigured).
Querying <community> at foo.net returns tables for the base physical router.
Querying <logical-system>/default@<community> at foo.net should return tables
for the logical system named <logical-system> (note that the address being
queried must be on the physical router).
It looks like the table containing the names of the logical systems can be
returned by querying vacmContextTable (1.3.6.1.6.3.16.1.1). Logical systems
will be returned as matching vacmContextName."<logical-system>/default".
I sense that this is not completely unrelated to the question about Nexus VRFs
I saw from July.
How difficult would this be to implement? Easy? Hard? Go away?
Thanks,
Michael
-----
Michael H Lambert, GigaPoP Coordinator Phone: +1 412 268-4960
Pittsburgh Supercomputing Center/3ROX FAX: +1 412 268-5832
300 S Craig St, Pittsburgh, PA 15213 USA [email protected]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
Url :
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20130208/79151fff/attachment-0001.bin
------------------------------
Message: 2
Date: Fri, 8 Feb 2013 16:09:02 -0600 (CST)
From: Patrick Landry <[email protected]>
Subject: [Netdot-users] RESTful interface questions
To: [email protected]
Message-ID:
<14032184.3844.1360361340508.JavaMail.javamailuser@localhost>
Content-Type: text/plain; charset="utf-8"
I am working on integrating Netdot into my provisioning system. When a machine
is provisioned each network interface is assigned to a VLAN. I would then like
to use the RESTful interface to obtain an IP address for each interface.
Unfortunately getting a list of VLANs via the RESTful interface does not
provide information about which subnets are associated with the VLANs.
(/rest/vlan)
So I can go the ipblock route (/rest/ipblock). Unfortunately when I try to
select only ipblocks associated with a certain vlan (/rest/ipblock?vlan=123) I
get "Not Found" and I know VLAN 123 is associated with a subnet. Should this
work?
So far now I am getting all subnet Ipblocks (/rest/ipblock?status=subnet) and
searching through those for those associated with vlan 123.
--
patrick
Patrick Landry
University of Louisiana at Lafayette
Director, University Computer Support Services
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20130208/c42dfb5e/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Landry, Patrick.vcf
Type: text/directory
Size: 11870 bytes
Desc: not available
Url :
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20130208/c42dfb5e/attachment-0001.bin
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 51, Issue 1
*******************************************
