But recently its noted that the ntp is not synchronizing properly in some access switches after the reboot,
Are you saying that before the reboot the NTP sync was available? If this is so, then it will depend on your IOS. 15.0(1)SE, SE1, SE2, takes exactly 10 minutes before NTP to sync. Older IOS takes less time. I don't know why this is so.
but its detecting the ntp server.
No it's not. The IP Addresses of Core 1 and Core 2 have a "~" prefexing them. This means that the NTP addresses are configured but are not or have not synchronized.
No, the issue shows as some access switches reloaded after the power outage.
Sorry, but can you explain this further?
In our network, our access switches (per site) gets NTP from the site distro. The site distro gets their NTP from the core. So when the site goes out due to power, the access swithces take 20 long minutes for the NTP to get sync. This is because the distro takes 10 minutes for the NTP to sync. During this stage the access switch NTP goes into insane. 10 minutes after the power outage the distro gets NTP sync but the access switch still doesn't get sync until a further 10 minutes.
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...