We are in process of configuring the syslog settings on Cisco routers so that syslog server receive the logs. The branch router is connected with HO router by MPLS.
HO Router 192.168.45.111
Branch Router 192.168.37.1
We have another switch placed at HO (192.168.45.2) which is a gateway of syslog server (192.168.45.70). The HO switch has the default routing pointing to HO firewall (192.168.45.111) and other remote sites static routes pointed towards to 192.168.45.111. The branch and HO machines can ping each other w/o problem. But when we do the ping from branch router (192.168.37.1) to syslog server (192.168.45.70) or HO Switch (192.168.45.2) then it doesn't ping even the HO Router (192.168.45.111) is getting ping.
This is completely strange issue for us and not able to solve this issue. If it could be routing issue then branch machines won't able to ping neither syslog server nor HO switch.
Thanks Glent for your response. The issue is now solved. Actually, when i use this command ping 192.168.45.70 source 192.168.37.1 then I found ping is working and for syslog logs, I added the following command with other config:
logging source-interface fastEthernet 0/1
After adding the above command, I started getting the syslogs from the internal IP of remote router. Earlier, it was sending the logs by taking serial interface (MPLS) as a source.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.