There is no excerpt because this is a protected post....
Read More
1 Minute
Protected: Build your security network
There is no excerpt because this is a protected post....
Read More
2 Minutes
Protected: Build the Backbone
There is no excerpt because this is a protected post....
Read More
4 Minutes
vPC vs VSS
Si l’objectif “historique” est le même : s’affranchir de la limitation de STP (blocage de ports pour prévenir les boucles), de l’usage des FHRP (HSRP, VRRP) pour équilibrer les liens, d’augmenter les performances en...
Read More
2 Minutes
Drive healing methods… that work!
The MBR table before: and after: Now the drive is recognized in diskmgmt.msc and in File Explorer and back usable again! TestDisk has well analyzed the disk Writing this new structure to the previous...
Read More
Windows : Drive healing from scratch
Lab setup: PC + USB to SATA adapter + Seagate 1T HDD run>msinfo32, shows: Lets gather some information on this drive? msinfo32 is shows nothing! disk management (diskmgmt.msc) is shows nothing! Fault in system...
Read More
Multicast: RPF… Part 6
In our test network R1, R2 and R3 are in the same RIP routing domain All these routers are configured for a PIM-SM mode operation The RP address is set to R3’s fa1/0 interface...
Read More
Multicast: rather than dense, sparse it and let’s meet at rendez-vous point… Part 5
Client1 is configured to join multicast destined for group 226.0.0.1 and sent from Server1 Instead of PIM-Dense (flood and prune) we use PIM-Sparse to build the forwarding path from the server to the client...
Read More
I’am not a good gateway… set redirection!
In this lab PC1 tries to communicate with PC2 R1, R2 and R3 are in the same network Static routing is configured on routers R1, R2 and R3 such as At R2, PC-2 network...
Read More
Multicast: Hold ASM for a moment, let’s do SSM!… Part 4
IGMPv3 (RFC 4607) allows the receivers to specify the source they wish in additiont the multicast group trafic By default we use the 232.0.0.0/8 range for SSM In our lab setup We configure Client1...
Read More
Is it sufficient split-horizon rule to prevent RIP loops?
Per the split-horizon rule, don’t send an update back on the interface it was received on What is the challenge here? In addition to bandwidth usage and system resources consumption, Split horizon helps prevent...
Read More
RIP: do not split it then… and unleach the power of the “network” command
In RIP domain routers R1 and R2 exchange information about loopback 0 and 1 networks Router RIP command “network 0.0.0.0” hints routers to add all ip enabled interfaces to the update list and include...
Read More