Cisco Enterprise Switching
OSPF, VLANs and EtherChannel
New Brunswick Community College · Moncton, Canada
Project overview
Design and configure a simulated campus switching environment using segmentation, Layer 3 routing, link aggregation and secure device administration.
Technical problem
Connect distinct VLANs while maintaining logical segmentation, resilient uplink design and secured management access.
Architecture and objectives
Conceptual illustration of the documented scope, not a recovered topology or proof of connectivity.
- Work with PP-L3-2 and PP-L2-1 and VLANs 60, 61, 62 and 63.
- Allocate five access ports per VLAN and use SVIs for inter-VLAN routing.
- Configure OSPF scope, 802.1Q trunks and LACP EtherChannel on uplink ports 47/48.
- Practice SSHv2, RSA 2048-bit keys, local administrative login and secured VTY access.
Environment and configuration
| Area | Documented scope |
|---|---|
| Access VLANs | 60 / 61 / 62 / 63 |
| Access-port allocation | Five per VLAN in assignment scope |
| Uplinks | LACP EtherChannel; ports 47 and 48 |
| Routing | SVIs and OSPF |
| Management | SSHv2, RSA 2048-bit and local authentication |
Configuration reference
Design and diagnostic reference; not a verbatim successful execution log.
! Verification commands; no successful output is implied
show vlan brief
show ip interface brief
show interfaces trunk
show etherchannel summary
show ip ospf neighbor
show ip route
show ip sshTroubleshooting
Compare VLAN membership, trunk allowed-VLAN lists and port-channel consistency. Investigate OSPF adjacency and route installation separately from Layer 2 reachability.
Security considerations
Prefer SSHv2 over Telnet, secure VTY authentication, review administrative permissions and keep passwords and keys out of published configurations.
Evidence and verified outcomes
The supplied technical history documents the switch environment and configuration scope. Local Packet Tracer coursework exists, but the exact PP-L3-2/PP-L2-1 topology and retained successful show-command output have not been matched. Adjacency, port-channel and inter-VLAN acceptance outcomes remain unverified.
Historical academic work. No current cloud service, production deployment, performance metric or certification is implied.
Skills demonstrated in the documented scope
Screenshot evidence
Original coursework and configuration evidence remain under review. No unreviewed screenshots are published here.
Source and validation notes
Based on the owner-supplied NBCC technical portfolio history and the bounded local evidence described above. Raw submissions and configuration exports are withheld from public download pending review for credentials, personal information and publication suitability.
View additional technical labs →Technical implementation and illustrative configuration
Recovered scope: PP-L3-2 / PP-L2-1, VLANs 60–63, five access ports per VLAN, SVIs, OSPF, LACP on ports 47/48 and SSHv2 with RSA 2048-bit keys. Exact interface names, gateway addresses and router IDs were not recovered.
Illustrative pattern only — placeholders are not final settings or recovered running configuration.
ip routing
vlan 60
interface vlan 60
ip address <gateway-ip> <subnet-mask>
no shutdown
interface range <uplink-47>, <uplink-48>
channel-group <group-id> mode active
interface port-channel <group-id>
switchport mode trunk
router ospf <process-id>
network <network> <wildcard-mask> area <area-id>
ip ssh version 2Compare member/port-channel settings and allowed VLANs, then validate LACP, SVIs and OSPF independently. April 7 logs name other devices; partial connectivity there does not validate this topology. A matched .pkt, running configuration and successful show outputs remain missing.