I've been experimenting with implementing TCP syslog with multiple devices in my network, and I've come across a few instances where it stops and doesn't recover. For instance, there was an extended maintenance where we reloaded one of our routers and it never seemed to restart the TCP syslog.
The server is up but was unreachable for a time. However, I am concerned that once the link is down, it seems to stay down and there are no outward signs that it has tried to reconnect. On at least one other device, removing and readding the host worked, but that's not something I want to continuously test and alert on.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...