Scenario - The user Faced Internet access is slow intermittently throughout the day.

 ipconfig /all on PC2: Verified valid IP configuration (IPv4 address, subnet mask, default
gateway, DHCP server, DNS server) and DHCP functionality (no APIPA address).
 ping 192.168.1.1 from PC2: Confirmed reachability to the local default gateway (R1's
LAN interface) and proper VLAN assignment for PC2's switch port (SW1 port 2).
 Ping to Internet and R2 Loopback: Validated end-to-end routing between Site 1, the
Internet, and Site 2.
 show interface FastEthernet0/2 on SW1: Identified half-duplex configuration on PC2's
connected port (SW1 port 2).
 Resolution:

 Recognized half-duplex mismatch as a potential cause of intermittent slowness and

voice quality issues due to collisions and retransmissions during high network utilization.
 Proposed changing SW1 port 2 to full-duplex.
 Recommended ensuring PC2's NIC is configured for auto-negotiation or full-duplex to
match the switch port.
 Emphasized following change control procedures: documentation, backup, rollback
plan.
 Suggested post-change testing and comparison against a performance baseline.
 Mentioned the likelihood of Layer 2 QoS (CoS) implementation for prioritizing voice
traffic.

Sceniro :- User in PC6 at site 3 is accessing a SQL Server application and database that is running in site
1. But unable to reach but on site 1 user able to connect the server

1. Virtualized SQL Server and NAS: Identified the SQL Server application running on a
virtualized machine utilizing iSCSI and Fibre Channel NAS.
2. Jumbo Frame Verification: Confirmed switches supporting NAS communication were
configured for jumbo frames.
3. WAN Link Suspected: Hypothesized the WAN connection as the bottleneck due to
successful local report generation at Site 1.
4. NetFlow Implementation: Deployed Cisco NetFlow on routers and switches to collect
traffic statistics (utilization, traffic types, top talkers, protocols, bandwidth usage).
5. NetFlow Analysis: Used a NetFlow collector to aggregate and analyze data over a
month, establishing a baseline.
6. Bottleneck Identification: Discovered full image backups over the WAN near the
month's end causing significant congestion.
7. Resolution:
o Backup Rescheduling: Implemented a procedure to schedule backups during off-
peak hours.
o Traffic Shaping: Applied traffic shaping on WAN router interfaces to manage
bandwidth usage.
 o QoS Implementation: Configured Quality of Service (QoS) on WAN routers to
prioritize critical applications (SQL Server) and real-time traffic during
congestion.

Sceniro New site are bulid but facing multiple issue how to rectify all

Untested and/or improper updates to servers, routers, switches and other network devices.  Personally
owned user devices interrupting the network services.

 Inventory and System Assessment: Conduct a thorough inventory of all devices and
systems at Site 3.
 SCADA System Isolation:

 Implement separate VLANs for the SCADA network.

 Implement separate wireless networks for SCADA.
 Enforce no routing or limited access via ACLs between user and SCADA networks.
 Disable/remove insecure protocols (Telnet, FTP) on legacy SCADA systems (system
hardening).

 Guest Wireless Network: Create a separate network for guest access using VLANs and
ACLs for isolation.
 Testing Lab Implementation:

 Establish a dedicated test network.

 Mandate testing of all updates (firmware, drivers) before production deployment.
 Define and test rollback procedures for updates.
 Define and test downgrading procedures for software/systems.
 Implement regular configuration backups for network devices.

 BYOD Policy Enforcement:

 Implement a strict on-boarding process verifying device security requirements.

 Utilize MAC address ACLs on wireless infrastructure.
 Employ pre-admission scans via software agents (persistent or non-persistent).
 Implement network access control (NAC) at the network edge (e.g., 802.1x).
 Utilize ACLs on router interfaces for post-admission access control.
 Establish a well-defined off-boarding process for device access removal and data
cleanup.

Sceniro : A growing company is having wireless networking issues. An access point was recently added
near the window of one of the floors of building 1, in the hopes that their users in a building2 would also
be able to access the network. Unfortunately the access point not only failed to provide access for the
second building, but also caused many users in the first building to have degraded wireless service. The
technician has been called in to evaluate the problem and make recommendations.
 Isolate the Problematic AP: Powered off the newly added access point, which restored
service in Building 1, indicating it as the source of the immediate issue.
 Switch Port Verification: Checked the switch port configuration for the AP's connection,
confirming full-duplex and 100 Mbps.
 Fiber Cable Management: Noted and recommended organizing fiber optic cables in the
wiring closet onto cable trays to prevent damage.
 In-Band vs. Out-of-Band Management: Identified the use of in-band management and
recommended migrating switch VTY lines to the isolated out-of-band management network
for enhanced security.
 Secure Management Protocols: Advised against clear-text protocols (SNMPv1/v2, Telnet,
HTTP, FTP, TFTP) and recommended secure alternatives (SNMPv3, SSH, HTTPS, SFTP) or
using them within VPN tunnels.
 Network Hardening: Recommended disabling unnecessary and insecure network services
on all devices.
 AP Configuration Analysis (Maintenance Window):

 Discovered half-duplex configuration on the problematic AP's Ethernet interface.

 Verified omni-directional antenna suitability for Building 1 coverage.
 Confirmed consistent 802.11g protocol across APs.
 Identified overlapping channel (channel 11) with a nearby AP as the primary cause of
degradation.
 Changed the new AP's channel to channel 6 (non-overlapping).
 Conducted a wireless site survey (using a smartphone app) to confirm non-overlapping
channel assignments.

 Building 2 Wireless Extension:

 Determined the signal from Building 1's AP was insufficient for Building 2 due to
distance and building materials.
 Proposed using Yagi-Uda directional antennas on the exterior of both buildings as a
repeater link.
 Suggested a Layer 2 switch in Building 2 to connect the external antenna to a new AP
within Building 2.

 Wireless Technology Upgrade: Recommended considering upgrading APs to 802.11n

(MIMO) or 802.11ac (MU-MIMO) for increased throughput. Mentioned high-throughput (ht)
standards.
 Wireless LAN Controller (WLC) Implementation:

 Recommended a WLC for centralized management of access points (thin AP

architecture).
 Highlighted WLC benefits: user authentication, access control lists, and rogue AP
detection and mitigation (jamming).
 Explained the limitations of standalone ("fat" or "thick") AP configurations where each
AP handles authentication independently.
Scenerio:- A company just replaced most of their senior management team, and would like to hire an
outside consultants to come in and provide a thorough technical and security audit of the existing
network infrastructure and the servers and devices that are connected to it

 Firewall Deficiency: Absence of dedicated firewalls at Internet/WAN edge.

Recommendation: Implement routed or transparent (virtual wire) firewalls at each site,
internal firewalls for segmentation, leveraging stateful inspection, application inspection
(context awareness), and potentially UTM features.
 Cabling Issues:

 Non-standard UTP termination leading to cross-talk (NEXT, FEXT). Recommendation:

Re-crimp using EIA/TIA 568A standard.
 Incorrectly crimped crossover cables (functional but non-standard). Recommendation:
Use EIA/TIA 568A/B for crossover cables.
 Recommendation: Use Cat6 cabling and connectors for Gigabit Ethernet deployment.

 Cable Management and Physical Security: Poor cable management ("spaghetti").

Recommendation: Implement cable trays. Weak wiring closet security (no keys/passcodes).
Recommendation: Improve physical access controls.
 Lack of Change Control: Outages due to untested AP updates. Recommendation:
Implement a structured change control plan (documentation, change requests, rollback, impact
analysis, approval, maintenance windows, notification).
 Third-Party Connectivity Risks: Plans to connect to a third-party network without formal
agreement. Recommendation: Implement a Memorandum of Understanding (MOU) and
enforce minimum security requirements for interconnected systems.
 WAN/Internet Outages: Frequent WAN/Internet downtime. Recommendation: Obtain a
Service Level Agreement (SLA), explore secondary providers for redundancy, implement
traffic throttling for anomaly limitation, and traffic filtering/blocking for data leak prevention.
Request a Fair Access Policy.
 Absence of Intrusion Detection/Prevention: No IDS/IPS deployed. Recommendation:
Implement a network-based IPS to detect and prevent attacks like SYN floods (protocol
abuse) and flooding attacks.

 Missing Switch Port Security: Switch port security not enabled. Recommendation:
Implement DHCP snooping, ARP inspection, and switch port security to prevent ARP
poisoning. Implement user VLANs separate from server VLANs and use ACLs on router
interfaces for network segmentation and isolation.

Sceniro :- A user at PC3 (in site 2) has called the helpdesk, stating that PC6 (in site 3) can’t be accessed
over the WAN. The technician has been called in to identify the problem

Here are the troubleshooting steps and findings for the PC3 to PC6 connectivity issue, in short
and technical terms:

1. SW2 Port 3 Configuration: Verified correct VLAN (20) assignment for PC3's port.
2. SW2 Port 3 Status: Checked interface status; no errors, port is up and connected.
3. PC3 IP Configuration (ipconfig /all): Confirmed valid IP address, subnet mask,
default gateway (reachable via ping), DHCP server, and internal DNS server. Noted
single internal DNS server.
4. Default Gateway Reachability (Ping): Successful ping from PC3 to its default gateway.
5. LLDP/MAC Address Table (Neighbor Discovery): Mentioned LLDP for neighbor
verification; in its absence, suggested checking the switch's MAC address table for PC3's
MAC on port 3.
6. R2 Routing Table: Verified R2 has a default route and a specific route to Site 3
networks.
7. R2 WAN Interface Status: No errors found on R2's WAN interface.
8. Ping from R2 to PC6: Successful ping, confirming routing between Site 2 and Site 3 is
functional.
9. DNS Resolution (nslookup PC6): Successful resolution of PC6's hostname to its IP
address (10.35.2.45) using the internal DNS server.
10. Ping to PC6 by Name: Successful ping, confirming both IP connectivity and DNS
resolution.
11. Application Layer Details (RDP): User reported using Remote Desktop Protocol (TCP
port 3389).
12. PC6 RDP Configuration: Confirmed correct RDP configuration on PC6 (via phone).
13. Successful Technician RDP Session: Technician successfully established an RDP
session from PC3 to PC6.
14. Failed User RDP Session: User's attempt to connect via RDP failed.
15. Active Directory/Local Group Permissions: Investigation revealed the user lacked
membership in the necessary domain group (for Remote Desktop) and local groups on
PC6.
16. Root Cause: Insufficient user permissions for Remote Desktop access to PC6.

Here are the points the technician shared with the manager regarding WAN costs and Internet
access:

1. Internet/WAN Access Technologies: Listed DSL, Cable Modem, leased lines, packet-
switched networks (Frame Relay), Ethernet, Wireless, and analog modems (slowest).
2. Bit Rate vs. Baud Rate: Explained bit rate (bits per second) and baud rate (symbols per
second, often lower than bit rate).
3. Encapsulation and De-encapsulation: Defined the processes of adding headers and
trailers for network transmission and their removal upon reception.
4. Multiplexing and De-multiplexing: Explained the concept of combining multiple data
streams over a single link and their separation at the destination.
5. Binary Numbering System: Described the fundamental use of binary (base 2) and its
representation in decimal (IPv4), hexadecimal (IPv6), and octal.
6. Wireless Considerations: Noted the potential lower reliability of wireless compared to
wired and the inverse relationship between wavelength/frequency and distance.
7. Baseline for Bandwidth Needs: Emphasized the importance of creating a baseline (with
sufficient sampling) to determine required bandwidth and acceptable latency.
8. Cost-Saving Option: Suggested the possibility of sharing the existing internet
connection and allocating costs instead of procuring a separate connection.