[racktables-users] Re: Available IPv4 blocks to allocate
- From: Chris James <chris@xxxxxxxxxxxx>
- To: racktables-users@xxxxxxxxxxxxx
- Date: Thu, 10 Apr 2014 07:30:28 -0700
Yes - that would work perfect. But how....
[image: Datacate, Inc] <http://www.datacate.com>
Chris James / CTO
916-668-5851/ chris@xxxxxxxxxxxx
Datacate, Inc Office: 916-526-0737
2999 Gold Canal Dr. Rancho Cordova, CA 95670
http://www.datacate.com
On Thu, Apr 10, 2014 at 7:27 AM, Simon Green <simon@xxxxxxxxxxxx> wrote:
> I was thinking similar. Perhaps we could “tag” the networks in some way
> to differentiate between an allocation to us vs. an assignment to an end
> user?
>
>
>
> Simon
>
>
>
> *From:* racktables-users-bounce@xxxxxxxxxxxxx [mailto:
> racktables-users-bounce@xxxxxxxxxxxxx] *On Behalf Of *Chris James
> *Sent:* 10 April 2014 15:23
> *To:* racktables-users@xxxxxxxxxxxxx
> *Subject:* [racktables-users] Re: Available IPv4 blocks to allocate
>
>
>
> This does work now and has major potential. The only problem I see is that
> I still see all the allocated blocks - i.e. we allocate a /27 to an
> end-user and it shows in this report as having 2x /26 available.
>
> Any thoughts on when creating a smaller network within a larger one - how
> to mark it as 100% used (meaning not available to us for further
> allocation?)
>
>
>
> I guess another way to look at this report is instead of asking what
> smaller blocks can we created within a larger block.
>
> Instead ask - "What smaller blocks within this block has NOT been created?
>
>
>
> Alexey - do you accept side work?
>
>
> [image: Datacate, Inc] <http://www.datacate.com>
>
> *Chris James* / CTO
> 916-668-5851/ chris@xxxxxxxxxxxx
>
> *Datacate, Inc* Office: 916-526-0737
> 2999 Gold Canal Dr. Rancho Cordova, CA 95670
> http://www.datacate.com
>
>
>
> On Thu, Apr 10, 2014 at 1:48 AM, Alexey Andrianov <alan@xxxxxxxxxx> wrote:
>
> I've found and fixed this bug. The exception appeared when there is a
> /32 network in database.
>
> 09.04.2014 21:21, Chris James пишет:
>
> Possibly - I do think I tried this before but always receive "Argument
> 'prefix_len' of value 33 is invalid."
>
> Thoughts?
>
>
> [image: Datacate, Inc] <http://www.datacate.com>
>
> *Chris James* / CTO
> 916-668-5851/ chris@xxxxxxxxxxxx
>
> *Datacate, Inc* Office: 916-526-0737
> 2999 Gold Canal Dr. Rancho Cordova, CA 95670
> http://www.datacate.com
>
>
>
> On Wed, Apr 9, 2014 at 10:11 AM, Alexey Andrianov <alan@xxxxxxxxxx> wrote:
>
> Hi.
>
> I have a plug-in for that:
>
> https://github.com/RackTables/racktables-contribs/blob/master/new-ip-range.php
>
> Hope this would help.
>
> 09.04.2014 20:36, Chris James wrote:
>
> I wonder if someone has already or could assist me with creating a
> report to outline available blocks at their largest size and total. We have
> taken to racktables as a primary DCIM. This product is amazing, just need
> to get to that next step.
>
>
>
> The problem:
>
> We are using Racktables to manage 6 locations currently adding a 7th in
> the next few months.
>
> We have 20+ allocations from ARIN as well as carrier allocations. We are
> currently tracing where each block is broadcast via tags.
>
> IPv4 Blocks are up to a /19 in size.
>
> We broadcast as small as a /24
>
> So you end up with a /19 for example with pieces broadcast from all
> locations. Therefore the graphic and availability reported on the main page
> does not actually apply.
>
> The graphic is not necessarily correct to begin with because if the block
> is allocated - it is not available - however unless you assign each IP then
> it shows available.
>
> Additionally drilling though a /16 of space is a real pain.
>
>
>
> The solution:
>
> A report or tab that shows only available blocks with tagging.
>
> When you create a network you are currently able to click the box to
> automatically allocate the network and broadcast - how about a tick-box to
> allocate the entire network.
>
>
>
> I would greatly appreciate any assistance and would be glad to donate for
> this functionality.
>
>
>
> Best,
>
> Chris.
>
> [image: Datacate, Inc] <http://www.datacate.com>
>
> *Chris James* / CTO
> 916-668-5851/ chris@xxxxxxxxxxxx
>
> *Datacate, Inc* Office: 916-526-0737
> 2999 Gold Canal Dr. Rancho Cordova, CA 95670
> http://www.datacate.com
>
>
> This e-mail message may contain confidential or legally privileged
> information and is intended only for the use of the intended recipient(s).
> Any unauthorized disclosure, dissemination, distribution, copying or the
> taking of any action in reliance on the information herein is prohibited.
> E-mails are not secure and cannot be guaranteed to be error free as they
> can be intercepted, amended, or contain viruses. Anyone who communicates
> with us by e-mail is deemed to have accepted these risks. This company is
> not responsible for errors or omissions in this message and denies any
> responsibility for any damage arising from the use of e-mail. Any opinion
> and other statement contained in this message and any attachment are solely
> those of the author and do not necessarily represent those of the company.
>
>
>
> --
>
> Best regards,
>
> Alexey
>
>
>
>
> This e-mail message may contain confidential or legally privileged
> information and is intended only for the use of the intended recipient(s).
> Any unauthorized disclosure, dissemination, distribution, copying or the
> taking of any action in reliance on the information herein is prohibited.
> E-mails are not secure and cannot be guaranteed to be error free as they
> can be intercepted, amended, or contain viruses. Anyone who communicates
> with us by e-mail is deemed to have accepted these risks. This company is
> not responsible for errors or omissions in this message and denies any
> responsibility for any damage arising from the use of e-mail. Any opinion
> and other statement contained in this message and any attachment are solely
> those of the author and do not necessarily represent those of the company.
>
>
>
> --
>
> Best regards,
>
> Alexey
>
>
>
>
> This e-mail message may contain confidential or legally privileged
> information and is intended only for the use of the intended recipient(s).
> Any unauthorized disclosure, dissemination, distribution, copying or the
> taking of any action in reliance on the information herein is prohibited.
> E-mails are not secure and cannot be guaranteed to be error free as they
> can be intercepted, amended, or contain viruses. Anyone who communicates
> with us by e-mail is deemed to have accepted these risks. This company is
> not responsible for errors or omissions in this message and denies any
> responsibility for any damage arising from the use of e-mail. Any opinion
> and other statement contained in this message and any attachment are solely
> those of the author and do not necessarily represent those of the company.
>
--
This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended recipient(s).
Any unauthorized disclosure, dissemination, distribution, copying or the
taking of any action in reliance on the information herein is prohibited.
E-mails are not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, or contain viruses. Anyone who communicates
with us by e-mail is deemed to have accepted these risks. This company is
not responsible for errors or omissions in this message and denies any
responsibility for any damage arising from the use of e-mail. Any opinion
and other statement contained in this message and any attachment are solely
those of the author and do not necessarily represent those of the company.
Other related posts:
