rcamara
asked on
Cisco Catalyst 3512 and 3524: What's the best move for this kind of setup
Hi everyone,
Here is the setup.
+--+ +--+ +--+
| | 3512 | | | |
/--\------- +------+ /--\ /--\
/----\ +-----\+ /-|--\ /-|--\
| | |
+--+ | | |
| | 3512| | |
/---------- +-----|+ | |
/----\ +-----\+ | |
| | |
+--+ | 3524 |
| | 3512| +--------+ 3512
/--\------- +-----|+ | | +-------+
/----\ +----\-+ +--/---\-+ +-/-----+
\---------/ \-------/
All the switches are sitting at 196.x.x.x/24. It's our customer's internal LAN. I know, this IP shouldn't be used internally coz it violates RFC 1918. So, I'm moving them to 192.168.x.x/24 network. This is about 230 workstations that I need to move.
All the switches are connected via fiber, Gigabit ethernet. They have an Internet access via Watchguard firewall. The watchguard is connected on the 3512, far right.
What would you suggest me so that there it's going to be a smooth transitioning to 192.168.x.x/24 network? I've also suggested our customer to setup a DHCP server. My concern is that, I'm not yet familiar with this Catalyst switches. I've also found out that the default VLAN of these switches is only use for management purposes. So, that means, I can just put the DHCP server on any port and configure the Win95/98/NT workstation as "Obtain IP address automatically". I don't need to create VLAN2. Is this true?
I would also be very happy to see an attachment on the reply of a configuration of a Cisco catalyst 3512 and another 3524 with VLAN trunking connected via gigabit, with at least 3 VLAN with 3 different subnets. With this, I will be able to easily apply VLAN if in cases needed sometime down the road. Btw, if this is the configuration, are you going to make use of the gigabit for the VLAN trunking? Is that what you call the ISL stuff also or 802.11q?
Thank you very much and have a great day. :p
Neil
Here is the setup.
+--+ +--+ +--+
| | 3512 | | | |
/--\------- +------+ /--\ /--\
/----\ +-----\+ /-|--\ /-|--\
| | |
+--+ | | |
| | 3512| | |
/---------- +-----|+ | |
/----\ +-----\+ | |
| | |
+--+ | 3524 |
| | 3512| +--------+ 3512
/--\------- +-----|+ | | +-------+
/----\ +----\-+ +--/---\-+ +-/-----+
\---------/ \-------/
All the switches are sitting at 196.x.x.x/24. It's our customer's internal LAN. I know, this IP shouldn't be used internally coz it violates RFC 1918. So, I'm moving them to 192.168.x.x/24 network. This is about 230 workstations that I need to move.
All the switches are connected via fiber, Gigabit ethernet. They have an Internet access via Watchguard firewall. The watchguard is connected on the 3512, far right.
What would you suggest me so that there it's going to be a smooth transitioning to 192.168.x.x/24 network? I've also suggested our customer to setup a DHCP server. My concern is that, I'm not yet familiar with this Catalyst switches. I've also found out that the default VLAN of these switches is only use for management purposes. So, that means, I can just put the DHCP server on any port and configure the Win95/98/NT workstation as "Obtain IP address automatically". I don't need to create VLAN2. Is this true?
I would also be very happy to see an attachment on the reply of a configuration of a Cisco catalyst 3512 and another 3524 with VLAN trunking connected via gigabit, with at least 3 VLAN with 3 different subnets. With this, I will be able to easily apply VLAN if in cases needed sometime down the road. Btw, if this is the configuration, are you going to make use of the gigabit for the VLAN trunking? Is that what you call the ISL stuff also or 802.11q?
Thank you very much and have a great day. :p
Neil
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Layer 2.
The 3512 and 3524 put all traffic on VLAN1 by default, and use VLAN1 for management, too. If you want to use a 2nd VLAN, you will need a router or a Layer 3 switch.
ASKER