These few days i’ve learned the nature, concept of cisco switches and redundancy (topologies). how to create trunk ports, access ports, vlans, VTP, CDP, and last but not least, STP; which i believe more widely known as Spanning Tree Protocol. its sole objective is to detect and prevent any potential loop in switch environment as redundancies added in into the picture and business started to grow beyond boundaries..
i’ve created 4 trunking switches, placed each on its own management VLAN all in .1 subnet, 1 default gateway as router, and cloud represent my MS Loopback adapter. i’ve tried forcing down the root bridge both by priority, or root primary option through the terminal global config mode.. the STP took place by blocking the R3’s fast ethernet port 1/6 (fa1/6) when things are running in normal mode.. (i’ve opened a cmd window pinging from cloud to R4; through R1 as root bridge). and uh.. the simulation will took place at the root bridge, as i’m going to shut one of the port that connects R3 & R1 (fa1/4 to be exact). the traffic will be temporarily cut off, and fa1/6 will change its mode to LIS (listening), LRN (learning), and finally FWD (forwarding). well… what i’ve noticed is that the time gap between the consecutive pings on which it can reach up to 12-15 seconds.. and i presume it can made lots of things go haywire..
as things normalized (perform no shut command on the R1 fa1/4), the ICMP packets goes down / timeout again as normalized traffic flows through R1.. by knowing its limitation (and of course trying to appreciate it), i’ll advance into a deeper study about PSTP, RSTP and portfast in the next few weeks…