WS-6 + DHCP + NTP = No Time

[Dawizman]

As the title says, I have multiple WS-6-Mini switches at client sites. They get a management IP from our NMS via DHCP. We set an internal NTP server and Time Zone in the switches. With this configuration, the switched will never get time from NTP. I don't ever see NTP starting in the logs. If I set the exact same IP statically, it works immediately. Firmware is 1.5.2.

[Stephen]

I will investigate this. Would you post the logs?

[Dawizman]

Code: Select all

Jan 1 00:00:09 netonix: 1.5.2 on WS-6-MINI

Jan 1 00:00:13 system: Setting MAC address from flash configuration: EC:13:B2:92:3B:5A

Jan 1 00:00:16 admin: adding lan (eth0) to firewall zone lan

Dec 31 17:00:36 udhcpc[1005]: udhcpc (v1.19.4) started

Dec 31 17:00:36 udhcpc[1005]: Sending discover...

Dec 31 17:00:39 Port: link state changed to 'up' (1G) on port 6

Dec 31 17:00:39 udhcpc[1005]: Sending discover...

Dec 31 17:00:39 STP: msti 0 set port 2 to discarding

Dec 31 17:00:39 STP: msti 0 set port 5 to discarding

Dec 31 17:00:39 STP: msti 0 set port 6 to discarding

Dec 31 17:00:40 Port: link state changed to 'up' (1G) on port 3

Dec 31 17:00:40 STP: MSTI0: New root on port 2, root path cost is 20000, root bridge id is 32768.78-8A-20-FD-64-5C

Dec 31 17:00:40 STP: msti 0 set port 2 to learning

Dec 31 17:00:40 STP: msti 0 set port 2 to forwarding

Dec 31 17:00:40 STP: msti 0 set port 3 to discarding

Dec 31 17:00:42 STP: msti 0 set port 3 to learning

Dec 31 17:00:42 STP: msti 0 set port 3 to forwarding

Dec 31 17:00:42 STP: msti 0 set port 6 to learning

Dec 31 17:00:42 STP: msti 0 set port 6 to forwarding

Dec 31 17:00:42 udhcpc[1005]: Sending discover...

Dec 31 17:00:42 STP: msti 0 set port 5 to learning

Dec 31 17:00:42 STP: msti 0 set port 5 to forwarding

Dec 31 17:00:43 udhcpc[1005]: Sending select for 10.105.3.204...

Dec 31 17:00:43 udhcpc[1005]: Lease of 10.105.3.204 obtained, lease time 864000

Dec 31 17:00:43 dropbear[1212]: Running in background

Dec 31 17:00:46 switch[1276]: Detected warm boot

Dec 31 17:00:46 admin: adding lan (eth0.15) to firewall zone lan

Dec 31 17:00:48 STP: msti 0 set port 2 to discarding

Dec 31 17:00:48 STP: msti 0 set port 3 to discarding

Dec 31 17:00:48 STP: msti 0 set port 5 to discarding

Dec 31 17:00:48 STP: msti 0 set port 6 to discarding

Dec 31 17:00:49 STP: MSTI0: New root on port 2, root path cost is 20000, root bridge id is 32768.78-8A-20-FD-64-5C

Dec 31 17:00:49 STP: msti 0 set port 2 to learning

Dec 31 17:00:49 STP: msti 0 set port 2 to forwarding

Dec 31 17:00:52 STP: msti 0 set port 6 to learning

Dec 31 17:00:52 STP: msti 0 set port 6 to forwarding

Dec 31 17:00:52 STP: msti 0 set port 5 to learning

Dec 31 17:00:52 STP: msti 0 set port 5 to forwarding

Dec 31 17:00:52 STP: msti 0 set port 3 to learning

Dec 31 17:00:52 STP: msti 0 set port 3 to forwarding

Dec 31 17:36:26 UI: Configuration changed by admin (::ffff:10.105.1.1)

Dec 31 17:36:26 UI: IPv4_Mode: changed from 'DHCP' to 'Static'

Dec 31 17:36:26 UI: IPv4_Address: changed from '10.105.0.200' to '10.105.3.204'

Dec 31 17:36:30 admin: removing lan (eth0.15) from firewall zone lan

Dec 31 17:36:36 admin: adding lan (eth0.15) to firewall zone lan

Dec 31 17:36:36 system: starting ntpclient

May 29 16:16:15 monitor: restarting vtss_appl

May 29 16:16:16 STP: msti 0 set port 2 to discarding

May 29 16:16:16 STP: msti 0 set port 3 to discarding

May 29 16:16:16 STP: msti 0 set port 5 to discarding

May 29 16:16:16 STP: msti 0 set port 6 to discarding

May 29 16:16:17 system: time set by NTP server

May 29 16:16:18 STP: MSTI0: New root on port 2, root path cost is 20000, root bridge id is 32768.78-8A-20-FD-64-5C

May 29 16:16:18 STP: msti 0 set port 2 to learning

May 29 16:16:18 STP: msti 0 set port 2 to forwarding

May 29 16:16:20 STP: msti 0 set port 6 to learning

May 29 16:16:20 STP: msti 0 set port 6 to forwarding

May 29 16:16:20 STP: msti 0 set port 5 to learning

May 29 16:16:20 STP: msti 0 set port 5 to forwarding

May 29 16:16:20 STP: msti 0 set port 3 to learning

May 29 16:16:20 STP: msti 0 set port 3 to forwarding

May 29 16:16:36 UI: Configuration changed by admin (::ffff:10.105.1.1)

May 29 16:16:36 UI: IPv4_Mode: changed from 'Static' to 'DHCP'

May 29 16:16:44 udhcpc[4078]: udhcpc (v1.19.4) started

May 29 16:16:44 udhcpc[4078]: Sending discover...

May 29 16:16:44 udhcpc[4078]: Sending select for 10.105.3.204...

May 29 16:16:44 udhcpc[4078]: Lease of 10.105.3.204 obtained, lease time 864000

May 29 16:16:45 STP: msti 0 set port 2 to discarding

May 29 16:16:45 STP: msti 0 set port 3 to discarding

May 29 16:16:45 STP: msti 0 set port 5 to discarding

May 29 16:16:45 STP: msti 0 set port 6 to discarding

May 29 16:16:46 STP: MSTI0: New root on port 2, root path cost is 20000, root bridge id is 32768.78-8A-20-FD-64-5C

May 29 16:16:46 STP: msti 0 set port 2 to learning

May 29 16:16:46 STP: msti 0 set port 2 to forwarding

May 29 16:16:47 STP: msti 0 set port 2 to discarding

May 29 16:16:47 STP: msti 0 set port 3 to discarding

May 29 16:16:47 STP: msti 0 set port 5 to discarding

May 29 16:16:47 STP: msti 0 set port 6 to discarding
 

[Stephen]

Could you send a screenshot of the top right corner of the UI?

The line:

Code: Select all

May 29 16:16:17 system: time set by NTP server


Seems to imply that the NTP service found the time.

[Dawizman]

Could you send a screenshot of the top right corner of the UI?

The line:

Code: Select all

May 29 16:16:17 system: time set by NTP server


Seems to imply that the NTP service found the time.

Yes, but that was right after I changed from DHCP to static.

[Stephen]

Ah you're right,
I'll test this and see if I can replicate it. However, in the mean time, are there other static ip's assigned in the network where the dhcp server is functioning? Could there be any addresses assigned twice because of this?

A good test to get an idea of this would be to allow the WS-6 to acquire a DHCP address and then ping out of the network in the tools tab to see if it has been assigned a functional address.

[Dawizman]

Nothing in this range is statically assigned, and I have multiple Netonix switches exhibiting this behaviour. If I change the IP to static, and use the exact same IP settings that were received dynamically, NTP works right away. As you can see in the log, NTP does not appear to start unless the address is static. Seems like a fairly minor bug, and easy to find and correct i would guess.

Replication of the issue is easy. Set the switch to DHCP with a functioning NTP server and reboot it. It will not start NTP.

[jakematic]

I can confirm on 1.5.3rc1 that NTP does not start when set to DHCP even though NTP is enabled and server IP is entered.

Interestingly it did set the time though - suspect because there is an NTP directive in my server dhcpd.conf

Code: Select all

option domain-name-servers 208.67.222.222, 208.67.220.220, 8.8.8.8, 8.8.4.4;
option ntp-servers 192.168.0.19, 192.168.0.42;
next-server 192.168.0.19;


Code: Select all

Dec 31 19:00:06 netonix: 1.5.3rc1 on WS-6-MINI
Dec 31 19:00:10 system: Setting MAC address from flash configuration: EC:13:B2:91:AD:16
Dec 31 19:00:11 udhcpc[523]: udhcpc (v1.19.4) started
Dec 31 19:00:12 udhcpc[523]: Sending discover...
Dec 31 19:00:15 udhcpc[523]: Sending discover...
Dec 31 19:00:15 udhcpc[523]: Sending select for 192.168.0.36...
Dec 31 19:00:15 udhcpc[523]: Lease of 192.168.0.36 obtained, lease time 86400
Jun 4 07:26:40 Port: link state changed to 'down' on port 2
Jun 4 07:26:40 Port: link state changed to 'down' on port 3
Jun 4 07:26:40 Port: link state changed to 'down' on port 4
Jun 4 07:26:42 Port: link state changed to 'up' (100M-F) on port 2
Jun 4 07:26:42 STP: msti 0 set port 2 to discarding
Jun 4 07:26:42 Port: link state changed to 'up' (100M-F) on port 3
Jun 4 07:26:42 STP: msti 0 set port 3 to discarding
Jun 4 07:26:42 STP: msti 0 set port 2 to discarding
Jun 4 07:26:42 STP: msti 0 set port 3 to discarding
Jun 4 07:26:43 Port: link state changed to 'up' (1G) on port 4
Jun 4 07:26:43 STP: msti 0 set port 4 to discarding
Jun 4 07:26:43 Port: link state changed to 'up' (1G) on port 1
Jun 4 07:26:43 STP: msti 0 set port 1 to discarding
Jun 4 07:26:43 STP: MSTI0: New root on port 1, root path cost is 30000, root bridge id is 32768.80-2A-A8-1F-E9-F5
Jun 4 07:26:43 STP: msti 0 set port 1 to learning
Jun 4 07:26:43 STP: msti 0 set port 1 to forwarding
Jun 4 07:26:45 STP: msti 0 set port 4 to learning
Jun 4 07:26:45 STP: msti 0 set port 4 to forwarding
Jun 4 07:26:45 STP: msti 0 set port 3 to learning
Jun 4 07:26:45 STP: msti 0 set port 3 to forwarding
Jun 4 07:26:45 STP: msti 0 set port 2 to learning
Jun 4 07:26:45 STP: msti 0 set port 2 to forwarding
Jun 4 07:26:46 dropbear[810]: Running in background
Jun 4 07:26:49 switch[837]: Detected warm boot
Jun 4 07:32:40 UI: Configuration changed by admin (::ffff:192.168.0.141)
Jun 4 07:32:40 UI: IPv4_Mode: changed from 'DHCP' to 'Static'
Jun 4 07:32:44 admin: removing lan (eth0) from firewall zone lan
Jun 4 07:32:51 admin: adding lan (eth0) to firewall zone lan
Jun 4 07:32:52 system: starting ntpclient
Jun 4 07:32:52 monitor: restarting vtss_appl
Jun 4 07:32:54 STP: msti 0 set port 1 to discarding
Jun 4 07:32:54 STP: msti 0 set port 2 to discarding
Jun 4 07:32:54 STP: msti 0 set port 3 to discarding
Jun 4 07:32:54 STP: msti 0 set port 4 to discarding
Jun 4 07:32:55 STP: MSTI0: New root on port 1, root path cost is 30000, root bridge id is 32768.80-2A-A8-1F-E9-F5
Jun 4 07:32:55 STP: msti 0 set port 1 to learning
Jun 4 07:32:55 STP: msti 0 set port 1 to forwarding
Jun 4 07:32:58 STP: msti 0 set port 4 to learning
Jun 4 07:32:58 STP: msti 0 set port 4 to forwarding
Jun 4 07:32:58 STP: msti 0 set port 3 to learning
Jun 4 07:32:58 STP: msti 0 set port 3 to forwarding
Jun 4 07:32:58 STP: msti 0 set port 2 to learning
Jun 4 07:32:58 STP: msti 0 set port 2 to forwarding


[Stephen]

Been able to confirm as well. This bug has been added to the list of items to be fixed/added for the next release.