cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
881
Views
5
Helpful
1
Replies

[n00b] L3 Switch Setup

Hey guys, complete noob here, I apologize if I have posted in the wrong place & I'll move it if I have.

I'm setting up a layer 3 Catalyst 3650 switch. I want the network to be just the L3 switch with hosts attached.

I'm trying to set it up as follows:

vlan 2 has fa0/2-24

fa0/1 is a trunk running 802.1q

dhcp pool 10.1.1.0 255.255.255.0

 

My running config is:

-------------------------------------------------------------
!
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Switch
!
boot-start-marker
boot-end-marker
!
no logging console
!
no aaa new-model
system mtu routing 1500
ip dhcp excluded-address 10.1.1.1
ip dhcp excluded-address 10.1.1.240 10.1.1.254
!
ip dhcp pool POOL1
   network 10.1.1.0 255.255.255.0
   dns-server 10.1.1.1
!
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
interface FastEthernet0/1
 switchport trunk encapsulation dot1q
 switchport mode trunk
!
interface FastEthernet0/2
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/3
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/4
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/5
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/6
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/7
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/8
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/9
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/10
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/11
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/12
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/13
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/14
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/15
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/16
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/17
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/18
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/19
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/20
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/21
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/22
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/23
 switchport access vlan 2
 switchport mode access
!
interface FastEthernet0/24
 switchport access vlan 2
 switchport mode access
!
interface GigabitEthernet0/1
!
interface GigabitEthernet0/2
!
interface Vlan1
 no ip address
 shutdown
!
interface Vlan2
 no ip address
!
ip classless
ip http server
ip http secure-server
!
line con 0
line vty 5 15
!
end

-------------------------------------------------------------

In the future I want to set this up so that I have communication between the VLANs and 3rd router (I'm setting up 2 switches like this, both with identical configs except for their subnet). But I cant get a DHCP lease whenever I plug a device into one of the ports. I'm sure I've missed a step or I'm doing something wrong, but I'm not sure what it is! I've google'd a lot, referred to my ICND1 & 2 books, and troubleshot this for the last 2 days. Additionally, once I can get a DHCP lease whenever I have a device plugged into VLAN2 do I need to specify a routing protocol (like RIPv2, its going to be a small network) in order to route between the hosts that have IP leases?

1 Reply 1

Seb Rupik
VIP Alumni
VIP Alumni

Hi there,
Try adding:

!
vlan 2
  ip address 10.1.1.1 255.255.255.0
!
int range fa0/2-24
spanning-tree portfast
!


With regard to running a routing protocol, you only need that to share routing table information between switches/ routers. If you are routing between devices in different VLANs, providing that they can reach their default gateway and the default gateways (SVIs) are on the same switch/ router then a routing protocol is not required.
If you had the routing for different VLANs spread across more than one switch/ router then you would need to run a routing protocol between them (or configure static routes).

cheers,
Seb.