I-Series NVR having network LAN dropping out

[Yorkie]

Hi all,
I have a DS-7716NI-I4/16P which I am in the process of testing with the intention of using it to upgrade from a fully functional 7700 E-series, however I am noticing an issue with it.

After the system is started it will connect to the network fine and will run on the network for 12-16 hours with no problems, then for a few hours it will keep dropping the LAN connection for notable periods of time with the occasional uptime before dropping again.

I did a full reset to factory defaults when I got the system, and since have assigned a static IP address which is not used by anything else on the network. The IPv4 gateway, subnet mask, and the primary DNS server are all set to the exact same values as the E-series NVR currently on the network. I have the I-series plugged in to a Hikvision 8-port switch which is connected to the primary router and is also connected to 3 Hikvision IP cameras - I have currently only linked the NVR to one of those cameras, because if I link the other two up it then sets them to H265 encoding which the E-series doesn't like. When the LAN link is up the feed from the linked camera is working fine, so I know the network connection is fine..... when the link goes down the orange network detect light on the 8-port switch goes out, with the occasional sporadic blink or double blink - this corelates to the NVR sending a small packet of a few bytes every now and then as I have watched it on the network traffic page of the GUI whilst it then receives 0 bytes in return

Is this likely to be something that a firmware update would resolve, or could there be something else going on?

Firmware version
V4.60.005 build 220108

Encoding version
V5.0 build 211130

Hardware version
0100054105000000

HTTP port 80
RTSP port 554
HTTPS port 443
Server port 8000
Enhanced Service port 8443
IoT port 30999

 

[Yorkie]

Update:- the system now disconnects itself from the network and fails to reconnect at all once the GUI is loaded. There are two green LED's on the motherboard which relate to the network connection and these are now permanently off...... if I interrupt the system boot and go into U-Boot mode then these green LED's are lit. I can use the setenv command to put the device IP address and gateway onto the correct subnet for my network, yet if I then ping another device on the network it will eventually time out and restart.

It comes up with the "bad CRC" error, and upon restarting if I go into U-boot again it will list the IP adress and gateway back at their default values as if having not saved the settings I entered - given my network is on subnet 4 and cannot be changed, I am wondering if this resetting to subnet 0 is what is causing the network failure problem.... if so is there a way to fix it or to somehow re-route network traffic using the internal NIC ports....?

HKVS # printenv
bootcmd=tftp 0x42000000 $(bootfile);bootm 0x42000000;
default=y2mount /nand;y2rdm /nand/uImage 0x42000000;
sec=tftp 0x42000000 Ky2015-1-H3536-uImage_sec;bootm 0x42000000;
phyaddr1=7
bootdelay=1
baudrate=115200
ipaddr=192.0.0.64
serverip=192.0.0.128
gatewayip=192.0.0.1
netmask=255.255.255.0
bootfile=uImage
mdio_intf=rgmii
bootargs=mem=1148M console=ttyS0,115200
ethaddr=4c:bd:8f:8a:cc:6b
stdin=serial
stdout=serial
stderr=serial
verify=y
ver=U-Boot 2010.06-svn (Dec 28 2015 - 10:42:45)[V1.2.1]

Environment size: 495/4092 bytes
HKVS # setenv ipaddr 192.168.4.4
HKVS # setenv gatewayip 192.168.4.1
HKVS # setenv netmask 255.255.252.0
HKVS # printenv
bootcmd=tftp 0x42000000 $(bootfile);bootm 0x42000000;
default=y2mount /nand;y2rdm /nand/uImage 0x42000000;
sec=tftp 0x42000000 Ky2015-1-H3536-uImage_sec;bootm 0x42000000;
phyaddr1=7
bootdelay=1
baudrate=115200
serverip=192.0.0.128
bootfile=uImage
mdio_intf=rgmii
bootargs=mem=1148M console=ttyS0,115200
ethaddr=4c:bd:8f:8a:cc:6b
stdin=serial
stdout=serial
stderr=serial
verify=y
ver=U-Boot 2010.06-svn (Dec 28 2015 - 10:42:45)[V1.2.1]
ipaddr=192.168.4.4
gatewayip=192.168.4.1
netmask=255.255.252.0

Environment size: 498/4092 bytes
HKVS # ping 192.168.4.1
timeout for link [4999]!
MAC:   4C-BD-8F-8A-CC-6B

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again

ARP Retry count exceeded; starting again
�

U-Boot 2010.06-svn (Dec 28 2015 - 10:42:45)[V1.2.1]

Protected at offset: 0x0, size:0x40000 Protection status:[0x22f]=>[0x22f].
*** Warning - bad CRC, using default environment

 

[sportster]

I doubt I can help you with your primary, underlying issue. I suspect your h/w issues are bigger than the typo I think you've introduced.

HKVS # setenv netmask 255.255.252.0

I imagine the 252 is a typo & you really meant to use a mask of 255.255.255.0.

FWIW & from what I recall, HIK applies the mask to ALL network interfaces, such that the POE ports now get 255.255.252.0 as well (whether you like it or not )..... effectively giving you something like:

• LAN interface -- 192.168.4.4 has a range of 192.168.4.1 --> 192.168.7.254
• POE Ports ------ 192.168.254.1 has a range of 192.168.252.1 --> 192.168.255.254

A 255.255.252.0 mask ...... probably not what you want.

 

[TomThumb]

Also, I wouldn't have thought this was correct either;

ipaddr=192.0.0.64
serverip=192.0.0.128
gatewayip=192.0.0.1

as these are public addresses (not private class C).

my network is on subnet 4

means nothing, the (IPv4) subnets are determined by the network mask.
If you are saying that you've built a network with four subnets you'd best give all the information (each subnet, mask, gateway etc.).

 

[Yorkie]

means nothing, the (IPv4) subnets are determined by the network mask.
If you are saying that you've built a network with four subnets you'd best give all the information (each subnet, mask, gateway etc.).

The primary gateway is 192.168.4.1 which was set by the ISP, so everything coming off that has to be 192.168.4.x

 

[Yorkie]

the U-Boot feedback from a normal startup shows the connection dropping out and retrying

U-Boot 2010.06-svn (Dec 28 2015 - 10:42:45)[V1.2.1]

Protected at offset: 0x0, size:0x40000 Protection status:[0x22f]=>[0x22f].
Hit ctrl+u to stop autoboot:  0
Mounting yaffs2 mount point/partnum: nand/0
Configures yaffs mount nand success!
Copy /nand/uImage to 0x42000000...      [DONE]
timeout wait for link failed!
## Booting kernel from Legacy Image at 42000000 ...
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] need to Authorization
[    2.599303] init(1) called reboot syscall, cmd: 0x0.
[   16.552579] libphy: 1:07 - Link is Up - 100/Full
[   18.552578] libphy: 1:07 - Link is Down
[   45.552566] libphy: 1:07 - Link is Up - 100/Full
[   47.552563] libphy: 1:07 - Link is Down
[   54.692323] libphy: STMMAC FIXED MII:01 - Link is Up - 1000/Full
[  107.442696] libphy: 1:07 - Link is Up - 100/Full
[  109.442671] libphy: 1:07 - Link is Down
[  110.442685] libphy: 1:07 - Link is Up - 100/Full
[  112.442679] libphy: 1:07 - Link is Down
[  113.442673] libphy: 1:07 - Link is Up - 100/Full
[  115.442783] libphy: 1:07 - Link is Down
[  125.446358] [APP]dvr_main_sc1885<2066>: tty unauthorized
[  125.463967] [APP]dvr_main_sc1885<2066>: !!!!!!!!!!!!!!!sc_hicore is start ok time[1787121780]!!!!!!!!!!!!!!!!
[  126.442677] libphy: 1:07 - Link is Up - 100/Full
[  128.442711] libphy: 1:07 - Link is Down
[  129.442583] libphy: 1:07 - Link is Up - 100/Full
[  131.442779] libphy: 1:07 - Link is Down
[  159.452693] libphy: 1:07 - Link is Up - 100/Full
[  161.452691] libphy: 1:07 - Link is Down
[  175.452662] libphy: 1:07 - Link is Up - 100/Full
[  176.452693] libphy: 1:07 - Link is Down
[  178.452704] libphy: 1:07 - Link is Up - 100/Full
[  180.452675] libphy: 1:07 - Link is Down

- with that "link is up", "link is down" repeating a few times per minute

.... the line of code "[ 54.692323] libphy: STMMAC FIXED MII:01 - Link is Up - 1000/Full" has caught my attention, as I have seen that bad MII commands can cause network dropouts.... I'm not sure if the serverip variable needs to be changed from 192.0.0.128