Adding subnets to sites and services

Sponsored Links

I have a question that is specific to adding a new subnet. In this scenario
we are adding a 10.54.3.0 /25. What I would like clarified is should the
subnet be set with 10.54.3.128 because of the /25 bit SM or can I define it
as 10.54.3.0 /25? Reason for the question is it was brought up today as we
are re-iping some of our sites. I was under the impression that you could use
10.54.3.0 /25 and the .0 would cover everything that is in the .3 net? So
another scenario would be 10.54.3.0 /26, is this correct or does it need to
be 10.54.3.64 because of the /26? I found a little information on the web but
nothing that came out and said this is the way it should or should not be.
Any help is appreciated and hopefully someone can give a good explanation,
thanks!

Mike
as per the CIDR notation, which is used in this case, 10.54.3.0/25 and
10.54.3.128/25 designate two separate IP address ranges. If each of them is
supposed to be allocated to a distinct site, then you should be specific and
assign them accordingly - otherwise (if both of them are part of the same
site), you can simply use 10.54.3.0/24...

hth
Marcin

"Mike L" <MikeL@discussions.microsoft.com> wrote in message
news:1238DDB7-C4A7-402D-B495-725D86B7B6C0@microsoft.com...
>I have a question that is specific to adding a new subnet. In this scenario
> we are adding a 10.54.3.0 /25. What I would like clarified is should the
> subnet be set with 10.54.3.128 because of the /25 bit SM or can I define
> it
> as 10.54.3.0 /25? Reason for the question is it was brought up today as we
> are re-iping some of our sites. I was under the impression that you could
> use
> 10.54.3.0 /25 and the .0 would cover everything that is in the .3 net? So
> another scenario would be 10.54.3.0 /26, is this correct or does it need
> to
> be 10.54.3.64 because of the /26? I found a little information on the web
> but
> nothing that came out and said this is the way it should or should not be.
> Any help is appreciated and hopefully someone can give a good explanation,
> thanks!

Hey Marcin thanks for the reply! Just want to clarify a couple of things. The
servers at this site will have a 10.54.3.x address with a 255.255.255.128
SM. So if a node has this setup doesn't sites and services need the subnet
entry 10.54.3.0 /25 in order to route their DC requests to the correct site?
Below you state that you can use a 3.0 /24 instead, will this cover all
setups (/26 /27 /28 etc.) if its the same site? I have always entered in
subnets with an IP address that ends in .0 with whatever the SM of the site
is. Thanks and have a good one!


"Marcin" wrote:

> Mike
> as per the CIDR notation, which is used in this case, 10.54.3.0/25 and
> 10.54.3.128/25 designate two separate IP address ranges. If each of them is
> supposed to be allocated to a distinct site, then you should be specific and
> assign them accordingly - otherwise (if both of them are part of the same
> site), you can simply use 10.54.3.0/24...
>
> hth
> Marcin
>
> "Mike L" <MikeL@discussions.microsoft.com> wrote in message
> news:1238DDB7-C4A7-402D-B495-725D86B7B6C0@microsoft.com...
> >I have a question that is specific to adding a new subnet. In this scenario
> > we are adding a 10.54.3.0 /25. What I would like clarified is should the
> > subnet be set with 10.54.3.128 because of the /25 bit SM or can I define
> > it
> > as 10.54.3.0 /25? Reason for the question is it was brought up today as we
> > are re-iping some of our sites. I was under the impression that you could
> > use
> > 10.54.3.0 /25 and the .0 would cover everything that is in the .3 net? So
> > another scenario would be 10.54.3.0 /26, is this correct or does it need
> > to
> > be 10.54.3.64 because of the /26? I found a little information on the web
> > but
> > nothing that came out and said this is the way it should or should not be.
> > Any help is appreciated and hopefully someone can give a good explanation,
> > thanks!
>
>
>

Hello Mike,

You have to add the subnets to ADSS if the new subnet is behind a router
to router(WAN) connection. Otherwise they belong to the same site.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I have a question that is specific to adding a new subnet. In this
> scenario we are adding a 10.54.3.0 /25. What I would like clarified is
> should the subnet be set with 10.54.3.128 because of the /25 bit SM or
> can I define it as 10.54.3.0 /25? Reason for the question is it was
> brought up today as we are re-iping some of our sites. I was under the
> impression that you could use 10.54.3.0 /25 and the .0 would cover
> everything that is in the .3 net? So another scenario would be
> 10.54.3.0 /26, is this correct or does it need to be 10.54.3.64
> because of the /26? I found a little information on the web but
> nothing that came out and said this is the way it should or should not
> be. Any help is appreciated and hopefully someone can give a good
> explanation, thanks!
>

Mike,
you should be able to combine multiple "classless" subnets when defining AD
site coverage (i.e. use 10.54.3.0/24 instead of having two entries that
cover the same IP address range - 10.54.3.0/25 and 10.54.3.128/25)...

hth
Marcin

"Mike L" <MikeL@discussions.microsoft.com> wrote in message
news:707AB197-78AB-42AF-A950-1F8F89DF9470@microsoft.com...
> Hey Marcin thanks for the reply! Just want to clarify a couple of things.
> The
> servers at this site will have a 10.54.3.x address with a 255.255.255.128
> SM. So if a node has this setup doesn't sites and services need the subnet
> entry 10.54.3.0 /25 in order to route their DC requests to the correct
> site?
> Below you state that you can use a 3.0 /24 instead, will this cover all
> setups (/26 /27 /28 etc.) if its the same site? I have always entered in
> subnets with an IP address that ends in .0 with whatever the SM of the
> site
> is. Thanks and have a good one!
>
>
> "Marcin" wrote:
>
>> Mike
>> as per the CIDR notation, which is used in this case, 10.54.3.0/25 and
>> 10.54.3.128/25 designate two separate IP address ranges. If each of them
>> is
>> supposed to be allocated to a distinct site, then you should be specific
>> and
>> assign them accordingly - otherwise (if both of them are part of the same
>> site), you can simply use 10.54.3.0/24...
>>
>> hth
>> Marcin
>>
>> "Mike L" <MikeL@discussions.microsoft.com> wrote in message
>> news:1238DDB7-C4A7-402D-B495-725D86B7B6C0@microsoft.com...
>> >I have a question that is specific to adding a new subnet. In this
>> >scenario
>> > we are adding a 10.54.3.0 /25. What I would like clarified is should
>> > the
>> > subnet be set with 10.54.3.128 because of the /25 bit SM or can I
>> > define
>> > it
>> > as 10.54.3.0 /25? Reason for the question is it was brought up today as
>> > we
>> > are re-iping some of our sites. I was under the impression that you
>> > could
>> > use
>> > 10.54.3.0 /25 and the .0 would cover everything that is in the .3 net?
>> > So
>> > another scenario would be 10.54.3.0 /26, is this correct or does it
>> > need
>> > to
>> > be 10.54.3.64 because of the /26? I found a little information on the
>> > web
>> > but
>> > nothing that came out and said this is the way it should or should not
>> > be.
>> > Any help is appreciated and hopefully someone can give a good
>> > explanation,
>> > thanks!
>>
>>
>>