Re: Cisco MDS NTP problem
- From: Erik Freitag <erik.freitag@xxxxxxxxxxxxxx>
- Date: Tue, 26 Feb 2008 21:17:02 -0800
MdV wrote:
MDS9216i# sh ntp peer-status
Total peers : 1
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay
-----------------------------------------------------------
=10.193.136.42 0.0.0.0 16 64 0 0.00000
MDS9216i#
Why the local has 0.0.0.0 instead of my mgmt0 ip of 10.193.136.43?
I have...
ntp server 10.193.136.42 prefer
in my configuration. That's all.
Other switches ok, but not this.
Not sure if this helps but here's the output from a 9513 running 3.2(2c) -- you may be seeing a problem with SAN-OS 3.0(2a). I have also been caught once by forgetting the "ntp commit".
# show ntp peer-status
Total peers : 3
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay
-----------------------------------------------------------
*128.48.102.70 128.48.100.101 2 64 377 0.00027
=128.48.102.80 128.48.100.101 3 64 377 0.00024
=192.35.228.20 128.48.100.101 3 64 377 0.01384
# show ip int mgmt0
mgmt0 is up
Internet address is 128.48.100.101/24
Broadcast address is 255.255.255.255
# show runn | i ntp
ntp distribute
ntp server 128.48.102.70
ntp server 128.48.102.80
ntp server 192.35.228.20
ntp commit
.
- Follow-Ups:
- Re: Cisco MDS NTP problem
- From: Merv
- Re: Cisco MDS NTP problem
- References:
- Cisco MDS NTP problem
- From: MdV
- Cisco MDS NTP problem
- Prev by Date: Re: hsrp
- Next by Date: Re: Cisco MDS NTP problem
- Previous by thread: Re: Cisco MDS NTP problem
- Next by thread: Re: Cisco MDS NTP problem
- Index(es):
Relevant Pages
|
