I started this lab by connecting a pc and a switch together via console cable. Using putty I used the serial connection type to get into the switch and configure. I started by using the console connection and then configured a password for privileged executive mode using the enable secret command. I then set a hostname using the hostname {name-here} command. Before doing both of these commands I used EN to go up to privileged exec mode as well as configure terminal (conf t) which enables global configuration mode. When in global configuration mode I used the (line con 0 command to enable logging synchronous. I then exited back to global configuration mode to set the ip using these commands: (int vlan 1, (ip add {ip here, subnet here}), and (no shut). From global configuration mode I also enable ssh using the following commands. (username {} password {}), (ip domain-name Greene.com), (crypto key generate rsa.) (enter 2048 for key), (line vty 0 15, (transport input ssh), (login local). I then used putty to ssh to the switch as well as connected two switches to ping in between PCs.
Eric and I began by gathering the necessary equipment for the lab setup. We used two routers to simulate a Wide Area Network WAN and one switch with an end device per network, creating two small Local Area Netorks LAN connected to form a WAN, as shown in the network topology below. To maintain organization during the setup, we first reviewed our notes and topology. I configured Router 2 (R2, while Eric configured Router 1 R1. During the router configuration, we accessed the correct interface and assigned the appropriate IP addresses, including the gateway and WAN IP. We then established static routes to each others networks to ensure proper WAN functionality. Following the router configuration, we set IP addresses on both end devices (PCs), aligning them with their respective LANs and including the correct gateway settings. After configuring the routers and end devices, we verified all cable connections and performed pings to confirm connectivity between the routers. The final step involved pinging each other's PCs across the different networks to validate successful communication.
At the beginning of this lab, I set up the subnets and IP addresses based on the number of users involved. I then organized and visualized the network topology using Packet Tracer to ensure alignment with the project plan. Our team proceeded to set up the physical equipment, using PuTTY to connect to the routers for proper configuration. We configured the IP addresses and subnets for the routers, as well as the appropriate IP and subnet settings for the WAN. The next step involved setting the IP addresses and subnets for the PCs, followed by pinging our default gateways (router IPs) to verify connectivity. We concluded the lab by successfully pinging across the WAN to the other network, confirming proper functionality.
I began by configuring the physical equipment, which involved setting up two switches and two PCs connected to the same VLA N across different switches. After properly organizing and co nnecting the Ethernet and console cables, I proceeded to conf igure the network devices. I created the same four VLANs (VLAN 10, 20, 30, and 40) on bo th switches to ensure consistency. Next, I configured the tru nk link between the switches to enable inter-switch communica tion and implemented switchport security to shut down a port if an unauthorized MAC address was detected. After assigning IP addresses to the PCs, I conducted ping tes ts between devices on the same VLAN across different switches to confirm the trunk link was functioning correctly. Finally, I tested the switchport security by connecting an unauthorize VLANs and Switchport Security Lab 2 d PC, which successfully triggered the port to shut down upon detecting an incorrect MAC address.
I began by creating the VLANs and assigning the appropriate ports to each VLAN. Next, I accessed the Layer 3 switch (multi layer switch) and configured the VLAN interfaces to enable proper inter-VLAN routing. After completing both the hardware a nd software configurations, I conducted ping tests between VL ANs to verify that the routing was functioning correctly.
I began by creating a physical topology in Packet Tracer to p rovide a clear visualization of the intended network setup. O nce completed, I connected the topology and used PuTTY to con sole into devices, configuring the necessary networks and WAN connections for both EIGRP and OSPF protocols. After establis hing successful communication between two networks using EIGR P, verified through ping tests, I connected the EIGRP network to an OSPF-configured network via a switch. I proceeded to co nfigure both sides for OSPF. Finally, I verified functionalit y through successful ping tests across both networks and conf irmed OSPF adjacency establishment, ensuring proper network integration and communication.
A switch interconnects devices on a LAN. Co axel Cables and Fiber optics. Electro magnetic spectrum sending data over waves. Data going through ethernet is going through copper (Electricity) where fiber is glass (Traveling through light). Starlink, Data through satellites. Internet cables running through the cables under the ocean. Shark biting cable XD. Octets and ip address. Common CMD commands (Ipconfig, ping) Power is needed especially for IT class. Computers being up and operational. Seeing grades and assignments (Moodle has to be up). LMS needs to be up. Student data where is it at and how is it (Being kept up). Network documentation is very important. Manual on the network map of the environment. For example if there's a AD server, you need to know physically where its at as well as what switch it connects to what vlan etc etc. If no one knows where database is or something on the network that goes down it needs to be labeled somewhere so that its accessible. In a technical environment there are typically end devices, network device, servers. End device, is a computer or phone a “End user” that's working.