Vlsm and Vlan Configuration

Based on last week’s instructions to utilize VLSM (variable length subnet mask) and CIDR (classless interdomain routing) notation to take a class C IP address of 192.168.1.0 and subnet it into multiple segmented individual networks. I utilized a /25, /26, /27 and a /30 CIDR notation in order to accurately create the networks and allocate the correct number of host IP addresses to each network. I also created a network diagram to reflect the network topology and IP addressing scheme as well as my configuration file of the commands I used. I also submitted my show ip interface brief output I created in the Toolwire simulator to reflect the accuracy and validity of my configuration commands.

This week’s instructions for the learning team collaboration are as follows, we were to apply basic device configuration on Switch 1, Router 1, Router 4, Core router and the PC workstation devices as well as configure and enable the appropriate interfaces for each device and assign the IP addressing scheme to individual interfaces that was created in week one.

As far as the learning team collaboration the only student to make any contact so far is Rolando and no one has made any configuration contributions to our network design and implementation. So it appears that I will have to do the majority of the work of the outlined assignment. I have looked ahead in the weeks to come and I can see this being fairly difficult to accomplish by myself.

I started with the Core router configuration and with all of the devices I began the configurations with some level of password protection from the enable secret protection to service password-encryption. I understand this security is weak at best and I have only so much time in the simulator. I then began to configure the Core routers interfaces by enabling them to the up / up states as well as assigning IP addresses to the appropriate interfaces. I also need to note that after I assigned the 192.168.1.126 255.255.255.128 address on the Core router fa0/0. I then tried to assign the 192.168.1.62 255.255.255.192 address on the Core router fa0/1 interface and received an overlapping IP address error I tried to assign it a couple of different ways to no avail so I went ahead and assigned it an address of 192.168.2.62 255.255.255.192 to accommodate the network functionality. It does not make any sense because they are on two different networks unless it is the simulator. Please note that my IP addressing scheme will be reflected in my show ip interface brief output as well as my subnet table.

Pinged OK from R1 to Sw1 Mgmt. Interface 192.168.1.1 /27

Pinged OK from Sw1 to R1 s0/0/0 192.168.1.241 /30

Ping not successful Sw1 to Core s0/0/1 192.168.1.242 /30

Pinged OK from Sw1 to R1 fa0/0.2 192.168.1.62 /27

Pinged OK from R1 to Core s0/0/1 192.168.1.242 /30

Ping not successful from R1 to Core s0/1/0 172.16.0.1 /16

Ping not successful from R1 to R4 s0/0 172.16.255.254 /16

Ping not successful from R1 to PC 192.168.1.33 /27

Pinged OK from Sw1 to R1 fa0/0.3 192.168.1.94 /27

Extended ping OK from Sw1 Mgmt. interface 192.168.1.1 /27 to R1 fa0/0.3 192.168.94 /27

I then went on to configure and enable router R4’s interfaces and assigned the appropriate host IP addresses. One additional entry was the inclusion of the loopback 0 interface. Now it is time to configure the switch and with that I first configured the management interface on VLAN 1 IP address 192.168.1.1 255.255.255.224. I then created VLAN 10 and VLAN 20 since VLAN 1 is already configured by default. And the last two devices to configure is the PC workstation and the router R1, with the PC it will be assigned an IP address of 192.168.1.33 255.255.255.224 there was no default gateway ever specified so I went ahead and used the next hop router which is R1’s s0/0/0 interface IP address of 192.168.1.241. And finally R1’s configuration which is setting up and enabling the s0/0/0 interface and the fa0/0 fast ethernet interface no IP address is needed on that interface because we will be configuring three sub interfaces for the three VLANs to enable inter VLAN routing, one of the sub interfaces is fa0/0.1 for VLAN 1 then we have to encapsulate the interfaces with the dot1q encapsulation protocol. I am including a table to reflect the results of the ping command I executed to check for connectivity within the network. I was able to ping successfully on about half of the addresses, like I did an extended ping successfully from Sw1 VLAN 1 Mgmt. interface 192.169.1.1 /27 to R1’s fa0/0.3 sub interface IP address of 192.168.1.94 /27 which it should because they are on the same network or subnet. I was not able to ping successfully from R1 to R4 s0/0 172.16.255.254 /16 which tells me they are not on the same network. Now once we get a dynamic routing protocol implemented into the network we should have connectivity to the different networks.

Configure Core router interfaces and assign IP addresses

Router>enable

Router#config t

Router(config)#hostname Core

Core(config)#enable secret cyberus

Core(config)#username admin password cyberus

Core(config)#service password-encryption

Core(config)#int s0/0/1

Core(config-if)#ip address 192.168.1.242 255.255.255.252

Core(config-if)#no shutdown

Core(config-if)#int s0/1/0

Core(config-if)#ip address 172.16.0.1 255.255.0.0

Core(config-if)#no shutdown

Core(config-if)#int fa0/0

Core(config-if)#ip address 192.168.1.126 255.255.255.128

Core(config-if)#no shutdown

Core(config-if)#int fa0/1

Core(config-if)#ip address 192.168.2.62 255.255.255.192

Core(config-if)#no shutdown

Core(config-if)#exit

Configure R4 router interfaces and assign IP addresses

Router>enable

Router#config