Designing simple campus network based on best practices

Hello visitor,

If you are looking for something about designing stable and good network topology, see my figure.
This schema has been created by me based on CCNP - switch book. Genereal speaking If we need good network topology we have to thinking about redundancy and failover strategy.
I know that my topology is simple but is scalable also.

See my picture and I will try to describibe it:

Regarding Access layer - this layer is responsible for switching based on L2. Here we have one switch ber VLAN. This is good because if we have large segment we can use high density port switch. Or we can agregate switches together. Another switch another VLAN. Next level is distribution - it means that our L2 here is finished. And we are starting using L3 functionality. Here we have SVI per vlans for communication with L3 and HSRP for hight availability. HRSP allows us to have stable default gateway if one of distribution switch goes down or crash or other problem.

Redundancy looks good. If we cut one leg from yellow colour connection between access and distribution we still have connection to other L2 and core network (next internet, WAN, data center). If one from distribution switches goes down HSRP takes over default (next hop) gateway role for every VLANs.

Core is full mesh topology - means that we have connetion between all devices in core and distribution switches. There is L3 routing implemented. In my instance OSPF.  Because we need fast convergence time if any path failure. Between distribution and access layer switches we have trunk port connecitons.

For summarize:
Processing block can be adaptive. You can add next simillar block based on this topology. I hope that this figure help your understanding network designing. Regarding Spanning Tree there is limited only between access and distribution layer. Based on this VLAN ber switch approach we also have stable STP convergence because there is loop free topology.

Sorry If you find any english bugs here in this post but I'm writing all posts AD HOC without google translator support.

Good Day - networkers!

How does works? Smartphone and webbrowser - Packet Tracer 7.0

I decided to remaind something from PTv7. My idea was using new function from this tool. Smartphone it will be OK, cell tower sounds good, etc.

This is my proposition. Simple user want to browse webpage for instance "www.onet.pl". How he/she gets it from smartphobe by 3G/4G? See my project inside.

PT file will be added soon...

MPLS (MP-BGP and VRF) & OSPF Provider and Customer point of view

This will be simple structure of MPLS configuration (P & PE and also CE and C). I've created this structure based on other internet websites/blogs and modifyed some details.

First of all I gonna show you a figure where we see all network project:

P - it is provider backbone (this means that this devices must only transport packets)
PE - this is edge of provider where split MPLS service for many clients
CE - customer edge - place where customer can connect own devicec or use C
C- customer router (sometimes form ISP sometimes not)

Short description for this figure above:
Provider using OSPF for routing convergence and for simpler administration. MP-BGM must be because PE storing many routing tables (each client have one table) and must be exchanged with other PE.
Ready configuretion you will find here:

Configuration files will be soon ...