1. Home
  2. Cisco Systems
  3. Cisco MDS NTP problem

Cisco MDS NTP problem

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.

Reply to
MdV
Loading thread data ...
  1. is the address 10.193.136.43 reachable ?

  1. are NTP packets being exchanged - debug ntp packets

  2. check ouput fo other NTP debugs

debug ntp events ` debug ntp validity debug ntp sleect debug ntp sync

  1. what is software version - post output of sh version
Reply to
Merv

Additional info:

MDS9216i# sh ntp statistics peer ipaddr 10.193.136.42 remote host: 10.193.136.42 local interface: 7.0.0.0 time last received: 89055s time until next send: 24s reachability change: 89055s packets sent: 1391 packets received: 0 bad authentication: 0 bogus origin: 0 duplicate: 0 bad dispersion: 0 bad reference time: 0 candidate order: 0 MDS9216i#

Notice that the local interface is 7.0.0.0, this is really strange.

MDS9216i# sh ip int mgmt0 is up Internet address is 10.193.136.43/24 Broadcast address is 255.255.255.255

MDS9216i#

  1. is the address 10.193.136.43 reachable ?

Yes

  1. are NTP packets being exchanged - debug ntp packets

This is a Cisco MDS, no debug ntp packets, but debug ntp errors and debug ntp Info. It says update ack.

2008 Feb 27 03:38:41.173570 ntp: NTP: Updating LC 33619968 with TIME_OF_DAY 2008 Feb 27 03:38:41.173711 ntp: NTP: Updating LC 33685504 with TIME_OF_DAY 2008 Feb 27 03:38:41.173995 ntp: Sending Time of day upd to standby 2008 Feb 27 03:38:51.653852 ntp: Sending tstamp update 0x8e5b92d to LC 2 2008 Feb 27 03:38:51.654055 ntp: Sending tstamp update 0x8e5b92d to LC 1 2008 Feb 27 03:38:51.654163 ntp: timestamp update ack SUCCESS from LC 2 2008 Feb 27 03:38:51.657329 ntp: timestamp update ack SUCCESS from LC 1 2008 Feb 27 03:39:31.753846 ntp: Sending tstamp update 0x8e5c8d7 to LC 2 2008 Feb 27 03:39:31.754047 ntp: Sending tstamp update 0x8e5c8d7 to LC 1 2008 Feb 27 03:39:31.754147 ntp: timestamp update ack SUCCESS from LC 2 2008 Feb 27 03:39:31.757316 ntp: timestamp update ack SUCCESS from LC 1

  1. check ouput fo other NTP debugs

debug ntp events debug ntp validity debug ntp sleect debug ntp sync

No such debugs.

  1. what is software version - post output of sh version

MDS9216i# sh ver Cisco Storage Area Networking Operating System (SAN-OS) Software TAC support:

formatting link
(c) 2002-2006, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software are covered under the GNU Public License. A copy of the license is available at
formatting link
Software BIOS: version 1.1.0 loader: version 1.2(2) kickstart: version 3.0(2a) system: version 3.0(2a)

BIOS compile time: 10/24/03 kickstart image file is: bootflash:/m9200-ek9-kickstart-mz.

3.0.2a.bin kickstart compile time: 5/4/2006 21:00:00 [06/30/2006 18:17:39] system image file is: bootflash:/m9200-ek9-mz.3.0.2a.bin system compile time: 5/4/2006 21:00:00 [06/30/2006 18:36:14]

Hardware cisco MDS 9216i ("2x1GE IPS, 14x1/2Gbps FC/Supervisor") Intel(R) Pentium(R) III CPU with 963836 kB of memory. Processor Board ID JAE10244H6N

bootflash: 250368 kB slot0: 0 kB

MDS9216i kernel uptime is 270 days 12 hours 22 minute(s) 50 second(s)

Last reset Reason: Unknown System version: Service:

MDS9216i#

Reply to
MdV

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

Reply to
Erik Freitag

The output if this command indicates the no NTP packets are being received

I would suggest you open a case with Cisco TAC

Reply to
Merv

it appears that the ntp commit command is related to the ntp distribute command.

As can be seen from the OP posting the MDS is sending ntp packet to the configured NTP server, but no receiivng any packets in response

question is what source IP address is being used in the NTP packet that is transmitted ???

OP may want to capture the NTP packets been trasnsmitted to make that determination.

Another question is what is the NTP server 10.193.136.42 - is it a Cisco router or switch ?

Reply to
Merv

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.