Re: 2nd DHCP Scope?
- From: "Oliver O'Boyle" <ooboyle@xxxxxxxxxxxxx>
- Date: Wed, 21 Dec 2005 17:46:10 -0500
> According to DELL they are layer 3 switches. Power connect 5324.
Ah. well. Layer 3 switches work differently. They switch by IP, not by mac
(for the most part). So you also have that to deal with.
>
> on the switch that will have both ip ranges, I added a VLAN called 2.
> maybe I should do the vlan trunks. What would suggest?
>
if you want to keep them chained, and you want them in separate VLANs, then
create 2 VLANs; one on each switch. Configure the uplink ports as trunks,
and make sure they have both VLANs in the trunk. Make sure the router
interface has 2 VLANs configured with the same numbers as your switch VLANs
(you'll need to use subinterfaces; one for each vlan) and give each VLAN an
IP address for the appropriate subnet.
This will effectively allow the switches to see the router, but keep the
segments separate. Once the router can be pinged by the switches, it should
be able to route automatically, because it will show the VLANs as connected
interfaces. This means the routing table will automatically be populated
according to your needs.
You might, however, want to consider putting your server (with 2 NICs) on
both switches (VLANs). If you don't do this, you will need to configure the
router to act as a DHCP relay agent, otherwise your second VLAN won't get
their IP addresses. It works, but it's probably better for you to add 2 NICs
in this case. Doing so will have the added benefit of taking some strain off
your router and server's first NIC.
Oliver
> "Oliver O'Boyle" <ooboyle@xxxxxxxxxxxxx> wrote in message
> news:OiPyRtnBGHA.3156@xxxxxxxxxxxxxxxxxxxxxxx
>>> Switches are chained (switch 2 plugs into switch 1, which plugs into the
>>> router.
>>
>> I'm assuming these are layer 2 switches. please tell me if I'm wrong.
>>
>>>
>>> What I find now is when I try to ping an IP on the new range, I get a
>>> reply from the firewall but TTL is expired in transit. I beleive I need
>>> to add an entry to the firewall but not sure what to put in it.
>>>
>>
>> what vlan nunber are you using, and on which switch? if you want both
>> subnets to go through both switches, each switch need to be on the same
>> vlan, or you need to configure the uplink ports as vlan trunks (they will
>> pass traffic on both vlans).
>>
>> Oliver
>>
>>>
>>> "Oliver O'Boyle" <ooboyle@xxxxxxxxxxxxx> wrote in message
>>> news:ejQVMdmBGHA.3064@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> The router is the current gateway. It also connects the 3rd location
>>>>> with a T1.
>>>>
>>>> ok. So yes, you will a static route pointing to the third location, as
>>>> you have done.
>>>>
>>>>> Added the static route in the router/gateway.
>>>>
>>>>> Added VLAN to the switch and assigned it an IP from the new range.
>>>>> Created the second scope on the windows 2000 server and activated it.
>>>>
>>>> are your switches chained (switch 2 plugs into switch 1, which plugs
>>>> into the router)? Or are they each directly connected into the router?
>>>>
>>>> Oliver
>>>>
>>>>
>>>>>
>>>>> I can't reach the switch that is plugged into the one above that I
>>>>> added the VLAN to.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> "Oliver O'Boyle" <ooboyle@xxxxxxxxxxxxx> wrote in message
>>>>> news:OZY9bskBGHA.4076@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>
>>>>>>
>>>>>>> I added an IP of the new range to the server and if I connect from
>>>>>>> the switch at the end with the new IP and perform a ipconfig renew,
>>>>>>> I receive an IP from the original IP range. If I assign an IP from
>>>>>>> the new range, I can reach the server and ping the switch, however I
>>>>>>> can not get to anything on the .4.x network.
>>>>>>>
>>>>>>> Does this make since?
>>>>>>
>>>>>> sort of... it's a bit confusing. However, if your 2811 is multihomed
>>>>>> (or has two interfaces, each connected to a separate switch), then it
>>>>>> needs to do the routing for you, unless you also put the server on
>>>>>> the second range (might be easier, depending on your particular
>>>>>> needs).
>>>>>>
>>>>>> If you don't put the server on the second range, then each subnet
>>>>>> needs to point to the router as the default gw. The router will have
>>>>>> a route to each range by default, because they are both connected to
>>>>>> it.
>>>>>>
>>>>>> I'm not sure what else you are using the router for, but it might
>>>>>> just be simpler to multihome your server. You could put two NICs in
>>>>>> it, and have it communicate directly on each subnet.
>>>>>>
>>>>>> Oliver
>>>>>>
>>>>>>>
>>>>>>> Thanks!!!
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
.
- Follow-Ups:
- Re: 2nd DHCP Scope?
- From: Stranger
- Re: 2nd DHCP Scope?
- From: Stranger
- Re: 2nd DHCP Scope?
- From: Stranger
- Re: 2nd DHCP Scope?
- From: Stranger
- Re: 2nd DHCP Scope?
- References:
- 2nd DHCP Scope?
- From: Stranger
- Re: 2nd DHCP Scope?
- From: Oliver O'Boyle
- Re: 2nd DHCP Scope?
- From: Jack H
- Re: 2nd DHCP Scope?
- From: Oliver O'Boyle
- Re: 2nd DHCP Scope?
- From: Jack H
- Re: 2nd DHCP Scope?
- From: Oliver O'Boyle
- Re: 2nd DHCP Scope?
- From: Jack H
- 2nd DHCP Scope?
- Prev by Date: Re: 2nd DHCP Scope?
- Next by Date: Re: 2nd DHCP Scope?
- Previous by thread: Re: 2nd DHCP Scope?
- Next by thread: Re: 2nd DHCP Scope?
- Index(es):
Relevant Pages
|
Loading