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. Merging Subnets in Netdot v1.0.6 (Boyer, Eric)
2. Re: Merging Subnets in Netdot v1.0.6 (Matt Zagrabelny)
3. Re: Merging Subnets in Netdot v1.0.6 (Boyer, Eric)
----------------------------------------------------------------------
Message: 1
Date: Mon, 13 Feb 2017 22:50:20 +0000
From: "Boyer, Eric" <[email protected]>
Subject: [Netdot-users] Merging Subnets in Netdot v1.0.6
To: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hey everyone,
Does anyone know if there is a way within Netdot to merge multiple subnets
together into a larger subnet? For example, I have 2 /26 networks and 1 /25
network that are all contiguous. The desire is to merge these three networks
into 1 /24 without losing any data. I don?t want to create a container of these
subnets, but rather merge the current subnets into the larger /24 subnet. A
container could work but it?s not the organizational structure I?d like to use.
Does Netdot support this? If not, any recommendations on accomplishing this
somewhat easily?
Thanks,
----------------
Eric Boyer
Senior Network Engineer
National Center for Supercomputing Applications
[email protected]<mailto:[email protected]>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20170213/6f349cf4/attachment-0001.html
------------------------------
Message: 2
Date: Mon, 13 Feb 2017 17:02:10 -0600
From: Matt Zagrabelny <[email protected]>
Subject: Re: [Netdot-users] Merging Subnets in Netdot v1.0.6
To: "Boyer, Eric" <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID:
<CAOLfK3XQ19KhfiqgQkrO3N=am-5n-+ysop3sri1puacauyd...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hey Eric,
On Mon, Feb 13, 2017 at 4:50 PM, Boyer, Eric <[email protected]> wrote:
> Hey everyone,
>
> Does anyone know if there is a way within Netdot to merge multiple subnets
> together into a larger subnet?
Yep. I just ran through your example as a test. Pretty easy:
A => 1.5.0.0/26
B => 1.5.0.64/26
C => 1.5.0.128/25
Delete B and C (do not delete children blocks!)
Then edit A to be a /24.
-m
------------------------------
Message: 3
Date: Mon, 13 Feb 2017 23:34:59 +0000
From: "Boyer, Eric" <[email protected]>
Subject: Re: [Netdot-users] Merging Subnets in Netdot v1.0.6
To: Matt Zagrabelny <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Matt,
That worked great, thanks for the help!
----------------
Eric Boyer
Senior Network Engineer
National Center for Supercomputing Applications
217-244-6608
[email protected]<mailto:[email protected]>
On Feb 13, 2017, at 5:02 PM, Matt Zagrabelny
<[email protected]<mailto:[email protected]>> wrote:
Hey Eric,
On Mon, Feb 13, 2017 at 4:50 PM, Boyer, Eric
<[email protected]<mailto:[email protected]>> wrote:
Hey everyone,
Does anyone know if there is a way within Netdot to merge multiple subnets
together into a larger subnet?
Yep. I just ran through your example as a test. Pretty easy:
A => 1.5.0.0/26
B => 1.5.0.64/26
C => 1.5.0.128/25
Delete B and C (do not delete children blocks!)
Then edit A to be a /24.
-m
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20170213/8c5381fb/attachment-0001.html
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 94, Issue 5
*******************************************
