This series of tutorials will be similar to my posts on a wireless setup, where I take a real world requirement of mine and fit it to a tutorial about NINet.org.
This series will take an existing flat topology with mixed switches running in L2 and convert it to a Cisco Switch Topology mixing L3 and L2. Then we’ll take a bit of step into the sysadmin side of things where we setup infrastructure servers to support the end users. At the time of this writing, in the real world, this network is up and running however the supporting infrastructure is a lower priority than other work items so it may take a while to filter through to here.
All commands should be entered in lowercase, User-defined parts excepted.
All code expects you to be in “configure terminal” mode
en – enters enable mode
conf t – enters configure mode
A good indicator of each mode is:
Hostname>en Hostname#conf t Hostname(config)#
One space in indicates that the commands are within the preceding command:
interface fast 0 shutdown
Appears in the terminal as
Hostname(config)#interface fast 0 Hostname(config-if)#shutdown
On the same column
no username Cisco no secret
Hostname(config)#no username Cisco Hostname(config)#no secret
- (existing) openLDAP Server for user authentication (on different network needs a 2nd NIC to connect to new Dev network)
- (new) freeRadius server to provide authentication for switch admins, should use LDAP for authentication of users
- (new) DHCP Server, currently users use static IPs and note the ones in use in a spreadsheet
- (new) DNS Server, would be nice for users to be able to assign names and not have to remember IP Addresses
- (new) 2x 3750x 48 port with 10Gbic Modules & IPServices
- (new) 2x 3750G 48 port with IPBase
- (new) 1x 2750G 24 port PoE with IPBase
- Part 1
- Part 2