I'm working on setting up RIPv2 on several L3 switches and ASA's as our network is growing and static routing has become too cumbersome to manage.
The question I have is what is the best method to advertise a loopback address 192.168.210.xxx/32 into RIPv2? It looks like we could add "network 192.168.210.0" for the loopback subnet, this does advertise the /32 into RIP, but this network statement would be the same on all of the devices. Not sure if that would cause an issue since on each device it only advertises the specific /32 host address. Then there is "redistribute connected" which also works, but seems redundant just for the purpose of advertising the loopback. Or add a static and "redistribute static". Any advice on this would be most appreciated.
I would suggest that a network statement under router rip would be the best way. Having the network statement on each router should not cause an issue. And with a network statement the loopback would be advertised as an internal route and it avoids possible complications that sometimes come up when you use redistribution.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...