Part 1: Configuring the Radius Server
In this post we want to secure access to our devices and do so with a single authentication server. There are many reasons to do this; for example we can easily manage users and passwords without having to micromanage each device.
The topology is similar to the RSPAN post:
DLS1 VLAN 5 (MGT): 10.1.5.252
DLS2 VLAN 5 (MGT): 10.1.5.253
For this post we want to focus on capturing and analyzing traffic on DLS2 fa0/18 VLAN 10 that connects to PCC. In essence, we want to monitor the traffic to and from PCC using RSPAN (Remote Switched Port Analyzer). SRV will monitor the traffic using Wireshark. For the end test we will send a ping from PCB to PCC and see the ICMP packets on SRV running Wireshark.
Topology
While monitoring an analyzer using RSPAN, I was getting a bunch of packets that I don’t care about. I don’t really want to filter based on just one packet but instead would like to filter out the packets I don’t want. Here you can see STP and HSRP packets being exchanged on the switched port I’m analyzing:
So, you’re following along in a lab configuring BGP and your “show ip bgp” reveals a RIB-failure…
Topology
I have several config files (about 30) for each of 6 devices – that’s 180 configs files that I don’t want to manually move over. Not only would it be exhausting and error prone, I know it would take some time to do. I want to move these to the devices so I can quickly move through some TShoot labs without having to tftp each config file for each lab individually. Doing the later would also require each device to have connectivity to the tftp server at all times – it’s just not functional. So, instead, I’d rather have all the config files for each lab already installed in flash so I can quickly “configure replace” as I move through each lab.
From: GNS3 Vault (1) Thanks to Rene Molenaar for taking the time to post these practice labs on his site.
