Telnet Hikvision NVR a simple guide

DaveP

DaveP

Getting the hang of it
Nov 18, 2014
270
57
Dumfriesshire
Telnet is a very sharp tool, and as with all sharp tools... you can poke your eye out

(Ok you can't really poke your eye out,
but telling telnet to do bad things may result in a very very bricked nvr thats only use will be as a door stop)

So... assuming a windows pc and the nvr is on the same ip 'range', do the following.

1. You have changed your admin password away from the default 12345
2. In your browser, go to your nvr address and enable telnet in the nvr (if you don't have the advanced option, then maybe you are still using the default password, so change that first)

attachment.php


3. Save and close.

4. Open a command prompt on your PC

attachment.php


5. Which should give...

attachment.php



6. Type the following.. (using the ipaddress of your own nvr, not mine !!) telnet 192.168.1.250
then press the enter key.

7. All going well you will see

attachment.php


8. Enter this user name ... root
then press the enter key

9. The screen will then ask you for your password (this is the same as your nvr admin password.
Hint... the screen does not echo / show your password as you type it, which can be confusing for the newbie, so don't look
at the screen, just type your password and press the enter key.

10. If you managed so far, you will get

attachment.php


11. Now the good bit, type... top
then press the enter key

12. Yayyyyyyyyyyyy, you can now see the cpu usage / load and load averages and the screen updates it self in real time.

attachment.php


13. When you have finished, the nice way to exit this screen is to hold the Ctrl key and press c
you will still be connected to the nvr and able to issue other commands, but you don't want to do that, do you :(
so now close the command prompt window by pressing the X in the top right corner.

14. More info can be found about top on the internettywebby, http://bit.ly/1xwJgSM

15. If you need or have or want to use telnet for other reasons on your nvr, then my advice (unless you have sysop experience) is don't.


:D
 

Attachments

  • ScreenHunter_28 Jan. 05 11.46.jpg
    ScreenHunter_28 Jan. 05 11.46.jpg
    48.5 KB · Views: 1,841
  • ScreenHunter_29 Jan. 05 11.54.jpg
    ScreenHunter_29 Jan. 05 11.54.jpg
    32.3 KB · Views: 1,787
  • ScreenHunter_30 Jan. 05 11.55.jpg
    ScreenHunter_30 Jan. 05 11.55.jpg
    31.1 KB · Views: 1,783
  • ScreenHunter_31 Jan. 05 11.58.jpg
    ScreenHunter_31 Jan. 05 11.58.jpg
    15.2 KB · Views: 1,828
  • ScreenHunter_32 Jan. 05 12.03.jpg
    ScreenHunter_32 Jan. 05 12.03.jpg
    31.3 KB · Views: 1,787
  • ScreenHunter_34 Jan. 05 12.06.jpg
    ScreenHunter_34 Jan. 05 12.06.jpg
    145.5 KB · Views: 1,768
  • Like
Reactions: anishjp, Killswitch, Mike and 6 others
My DS-7608NI-SE / P on firmware V2.3.9 build 140704 no longer gives a telnet option.

attachment.php


But telnet is still functional.

attachment.php
 

Attachments

  • 24wc7xe.jpg
    24wc7xe.jpg
    91.1 KB · Views: 1,696
  • 2ldg67m.jpg
    2ldg67m.jpg
    108.4 KB · Views: 1,693
Last edited by a moderator:
  • Like
Reactions: DaveP
Thank you for that information catseyenu :), maybe the later firmware virtual host option switches telnet on... or maybe its just on by default.

For our avid readers, The easy way to see if the telnet port is indeed open is to try and telnet to the nvr ip address, if it connects then its open :laugh:
 
thanks for this - had to turn the Telnet function on in Windows (relatively easy, google it).

which columns are we actually looking out for? Obviously cpu% is cpu load; what is VSZ etc?
 
Hi thestooge

VSZ is kinda deeper than intended for this, but its to do with virtual memory size and may give an incorrect answer, depending on which version of busybox that the nvr is runing,

An answer from the internettywebby says (and I believe it, lol)
It looks like busybox top calculates %MEM as VSZ/MemTotal instead of RSS/MemTotal. The latest version of busybox calls that column %VSZ to avoid some confusion
Click to expand...

The most relevant bits (pun intended) for our purposes are the lines showing the cpu (although that % number can be misleading) and load averages 1 minute, 5 minute, 15, minute.

Further reading if required.. http://www.linuxjournal.com/article/9001?page=0,0
 
  • Like
Reactions: catseyenu
Dave, trying to understand why mine doesn't display CPU... have you upgraded your Busybox?
My NVR is running BusyBox v1.2.1.
 
Mines is as it was in the box v1.16.1 and was sourced from China so ??????

But 1.16 isn't new as it dates back to 2010, the latest version is 1.21 from 2013, so 1.2.1 doesn't seem quite right.. Version:1.2.1 Released: 2006-10-23

ho hum, lol
 
Last edited by a moderator:
hi my friend please help me
i need have nvr 7616 the language chain
but i need change to English i have firmware but cannot upgrade
( Language version mismatch )
 
Hey Guys, what is the command to see memory and cpu usage?
Also if anyone has a list of commands, that would be overmuch appreciated.
 
'top' shows the running processes sorted in CPU usage, with a useful summary breakdown at the top. 'q' or Control-C to quit.
A very simple view of RAM memory is 'free', or storage is 'df'.
And if you want to struggle with the intricacies of Linux memory allocation then 'cat /proc/meminfo'
But best check Wikipedia for interpretation - it's not easy!
'ps' is also useful to list running processes
To get a fair proportion of the available commands, 'busybox'. But be careful - you could easily break the NVR.
 
Perfect, thanks @alastairstevenson Is there a way to reset the memory. not sure if it is resetting or not after reboot. Here is one of my issues i am having. I have 5- DS-9664NI-RH at a site. they are all connected to one main core switch where all other switches from multiple IDF rooms interconnect to. All switches bandwidth is fine, 10% of usage of Brocade ICX6450. The issues i am having is while viewing live feed, the image is very choppy, it jumps/freezes every 5-seconds. But playback is smooth as butter. Reloaded all FW to all devices. Reset al devices, NVR,Cameras , switches, workstations etc. Even when logging directly into the cameras web interface, the image is smooth. I dialed down all bitrate to avoid over usage of bandwidth. Also i put one of the NVRs and one camera on its own switch, still issue persists. Weird. Any suggestions. I'm attaching captures. FYI this NVR is running Fedora14.1 not busy box. thanks
or telnet session
attachment.php
attachment.php
 

Attachments

  • Screen Shot 2015-06-22 at 11.16.36 AM.png
    Screen Shot 2015-06-22 at 11.16.36 AM.png
    36.1 KB · Views: 1,421
  • Screen Shot 2015-06-22 at 11.17.03 AM.png
    Screen Shot 2015-06-22 at 11.17.03 AM.png
    73.8 KB · Views: 1,406
Last edited by a moderator:
Hmm.. not sure if I have any useful suggestions.
The processor(s) don't seem maxed out, nor does RAM.
RAM will be initialised on every startup, I don't think that could have a bearing on the problem.
Presumably the problem is with Live View over the web access, and occurs with more than one machine to view with, and with different browsers?
I don't know about this NVR, but for Live View under web access, there are usually some performance settings that can be changed in Local Configuration to drive the plugin differently, do these have any effect on the problem?
Does the problem vary with the number of channels being viewed? And are you viewing the same number of channels in Playback?
How is Live View via the VGA/HDMI output?
 
Viewing the live feed via web interface is good. There are 5 workstations, and when viewing 1 or 16 cameras at a time, still the same results. This is in a casino. When attaching a monitor directly on the NVR, via vga/hdmi, the results are the same, the LiveView is very choppy and jumpy but the playback is smooth as butter. I think the decoding part is ok since playback is fine. The weird thing is, i took one whole NVR out and one IP camera and a brand new switch, and localized it for trouble shooting, and sure enough it is still with the same outcome. I have my engineers at Hik working on it but as you know its a procedure with them no matter what. I will copy some stats here.
If you have any other useful commands please let me know. if you have a command that gives me live or actually incoming/outgoing bandwidth, that would be great.

[root@localhost ~]# netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:30960 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN
tcp 0 0 10.10.100.4:38591 10.10.200.130:554 ESTABLISHED
tcp 0 0 10.10.100.4:51520 10.10.200.112:8000 ESTABLISHED
tcp 0 0 10.10.100.4:36852 10.10.200.115:554 ESTABLISHED
tcp 0 0 10.10.100.4:50254 10.10.200.140:8000 ESTABLISHED
tcp 0 0 10.10.100.4:51922 10.10.200.145:8000 ESTABLISHED
tcp 0 0 10.10.100.4:32865 10.10.200.128:554 ESTABLISHED
tcp 0 0 10.10.100.4:60756 10.10.200.120:554 ESTABLISHED
tcp 0 0 10.10.100.4:23 10.10.1.11:51051 ESTABLISHED
tcp 0 0 10.10.100.4:58643 10.10.200.110:8000 ESTABLISHED
tcp 0 0 10.10.100.4:45765 10.10.200.101:554 ESTABLISHED
tcp 0 0 10.10.100.4:33716 10.10.200.103:554 ESTABLISHED
tcp 0 0 10.10.100.4:49228 10.10.200.118:554 ESTABLISHED
tcp 0 0 10.10.100.4:59714 10.10.200.121:8000 ESTABLISHED
tcp 0 0 10.10.100.4:36010 10.10.200.112:554 ESTABLISHED
tcp 0 0 10.10.100.4:35390 10.10.200.145:554 ESTABLISHED
tcp 0 0 10.10.100.4:49524 10.10.200.129:8000 ESTABLISHED
tcp 0 0 10.10.100.4:57669 10.10.200.117:554 ESTABLISHED
tcp 0 0 10.10.100.4:43248 10.10.200.130:8000 ESTABLISHED
tcp 0 0 10.10.100.4:48691 10.10.200.128:8000 ESTABLISHED
tcp 0 0 10.10.100.4:34707 10.10.200.122:554 ESTABLISHED
tcp 0 0 10.10.100.4:32817 10.10.200.129:554 ESTABLISHED
tcp 0 0 10.10.100.4:39824 10.10.200.122:8000 ESTABLISHED
tcp 0 0 10.10.100.4:43880 10.10.200.113:8000 ESTABLISHED
tcp 0 0 10.10.100.4:53051 10.10.200.123:554 ESTABLISHED
tcp 0 0 10.10.100.4:49544 10.10.200.110:554 ESTABLISHED
tcp 0 0 10.10.100.4:55712 10.10.200.140:554 ESTABLISHED
tcp 0 0 10.10.100.4:58298 10.10.200.111:554 ESTABLISHED
tcp 0 0 10.10.100.4:57673 10.10.200.117:554 ESTABLISHED
tcp 0 0 10.10.100.4:43435 10.10.200.121:554 ESTABLISHED
tcp 0 0 10.10.100.4:46921 10.10.200.104:8000 ESTABLISHED
tcp 0 0 10.10.100.4:37178 10.10.200.120:8000 ESTABLISHED
tcp 0 0 10.10.100.4:36388 10.10.200.102:8000 ESTABLISHED
tcp 0 0 10.10.100.4:43998 10.10.200.117:8000 ESTABLISHED
tcp 0 0 10.10.100.4:35925 10.10.200.126:554 ESTABLISHED
tcp 0 0 10.10.100.4:46119 10.10.200.116:8000 ESTABLISHED
tcp 0 0 10.10.100.4:32813 10.10.200.129:554 ESTABLISHED
tcp 0 0 10.10.100.4:35505 10.10.200.119:554 ESTABLISHED
tcp 0 0 10.10.100.4:35394 10.10.200.145:554 ESTABLISHED
tcp 0 0 10.10.100.4:44537 10.10.200.126:8000 ESTABLISHED
tcp 0 0 10.10.100.4:56327 10.10.200.111:8000 ESTABLISHED
tcp 0 0 10.10.100.4:52351 10.10.200.125:554 ESTABLISHED
tcp 0 0 10.10.100.4:36006 10.10.200.112:554 ESTABLISHED
tcp 0 0 10.10.100.4:59835 10.10.200.101:8000 ESTABLISHED
tcp 0 0 10.10.100.4:50428 10.10.200.125:8000 ESTABLISHED
tcp 0 0 10.10.100.4:43439 10.10.200.121:554 ESTABLISHED
tcp 0 0 10.10.100.4:40645 10.10.200.113:554 ESTABLISHED
tcp 0 0 10.10.100.4:49224 10.10.200.118:554 ESTABLISHED
tcp 0 0 10.10.100.4:49540 10.10.200.110:554 ESTABLISHED
tcp 0 0 10.10.100.4:38587 10.10.200.130:554 ESTABLISHED
tcp 0 0 10.10.100.4:57217 10.10.200.106:554 ESTABLISHED
tcp 0 0 10.10.100.4:57333 10.10.200.108:554 ESTABLISHED
tcp 0 0 10.10.100.4:53495 10.10.200.102:554 ESTABLISHED
tcp 0 0 10.10.100.4:57221 10.10.200.106:554 ESTABLISHED
tcp 0 0 10.10.100.4:36069 10.10.200.114:554 ESTABLISHED
tcp 0 0 10.10.100.4:37526 10.10.200.109:554 ESTABLISHED
tcp 0 0 10.10.100.4:57337 10.10.200.108:554 ESTABLISHED
tcp 0 0 10.10.100.4:35921 10.10.200.126:554 ESTABLISHED
tcp 0 0 10.10.100.4:53527 10.10.200.107:8000 ESTABLISHED
tcp 0 0 10.10.100.4:50110 10.10.200.107:554 ESTABLISHED
tcp 0 0 10.10.100.4:50099 10.10.200.107:554 ESTABLISHED
tcp 0 0 10.10.100.4:40622 10.10.200.103:8000 ESTABLISHED
tcp 0 0 10.10.100.4:38965 10.10.200.105:554 ESTABLISHED
tcp 0 0 10.10.100.4:33720 10.10.200.103:554 ESTABLISHED
tcp 0 0 10.10.100.4:34703 10.10.200.122:554 ESTABLISHED
tcp 0 0 10.10.100.4:53022 10.10.200.114:8000 ESTABLISHED
tcp 0 0 10.10.100.4:44304 10.10.200.116:554 ESTABLISHED
tcp 0 0 10.10.100.4:38969 10.10.200.105:554 ESTABLISHED
tcp 0 0 10.10.100.4:54234 10.10.200.115:8000 ESTABLISHED
tcp 0 0 10.10.100.4:53491 10.10.200.102:554 ESTABLISHED
tcp 0 0 10.10.100.4:36856 10.10.200.115:554 ESTABLISHED
tcp 0 0 10.10.100.4:33578 10.10.200.118:8000 ESTABLISHED
tcp 0 0 10.10.100.4:60760 10.10.200.120:554 ESTABLISHED
tcp 0 0 10.10.100.4:52347 10.10.200.125:554 ESTABLISHED
tcp 0 0 10.10.100.4:42409 10.10.200.106:8000 ESTABLISHED
tcp 0 0 10.10.100.4:45769 10.10.200.101:554 ESTABLISHED
tcp 0 0 10.10.100.4:36065 10.10.200.114:554 ESTABLISHED
tcp 0 0 10.10.100.4:35506 10.10.200.119:554 ESTABLISHED
tcp 0 0 10.10.100.4:37530 10.10.200.109:554 ESTABLISHED
tcp 0 0 10.10.100.4:58302 10.10.200.111:554 ESTABLISHED
tcp 0 0 10.10.100.4:50100 10.10.200.123:8000 ESTABLISHED
tcp 0 0 10.10.100.4:51615 10.10.200.105:8000 ESTABLISHED
tcp 0 0 10.10.100.4:40658 10.10.200.113:554 ESTABLISHED
tcp 0 0 10.10.100.4:32861 10.10.200.128:554 ESTABLISHED
tcp 0 0 10.10.100.4:55704 10.10.200.140:554 ESTABLISHED
tcp 0 0 10.10.100.4:43882 10.10.200.104:554 ESTABLISHED
tcp 0 0 10.10.100.4:42488 10.10.200.108:8000 ESTABLISHED
tcp 0 0 10.10.100.4:53052 10.10.200.123:554 ESTABLISHED
tcp 0 0 10.10.100.4:40752 10.10.200.119:8000 ESTABLISHED
tcp 0 0 10.10.100.4:43878 10.10.200.104:554 ESTABLISHED
tcp 0 0 10.10.100.4:34353 10.10.200.109:8000 ESTABLISHED
tcp 0 0 :::23 :::* LISTEN
tcp 0 0 :::8000 :::* LISTEN
tcp 0 0 :::554 :::* LISTEN
tcp 0 0 :::80 :::* LISTEN
tcp 0 0 :::6000 :::* LISTEN
tcp 0 0 ::ffff:10.10.100.4:8000 ::ffff:10.10.1.11:49172 ESTABLISHED
tcp 0 0 ::ffff:10.10.100.4:554 ::ffff:10.10.2.5:61023 ESTABLISHED
tcp 0 0 ::ffff:10.10.100.4:8000 ::ffff:10.10.2.5:61009 ESTABLISHED
udp 0 0 0.0.0.0:7001 0.0.0.0:*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 1673 @ISCSIADM_ABSTRACT_NAMESPACE
unix 2 [ ACC ] STREAM LISTENING 3419 /tmp/.X11-unix/X0
unix 2 [ ACC ] STREAM LISTENING 4117 /var/systemCmd.socket
unix 2 [ ACC ] STREAM LISTENING 4875 /var/cmd.socket
unix 2 [ ACC ] STREAM LISTENING 3418 @/tmp/.X11-unix/X0
unix 2 [ ] DGRAM 220 @/org/kernel/udev/udevd
unix 3 [ ] STREAM CONNECTED 6158 @/tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 6157
unix 3 [ ] STREAM CONNECTED 4942 @/tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 4877
unix 3 [ ] DGRAM 225
unix 3 [ ] DGRAM 224

..


[root@localhost ~]# ifconfig
bond0 Link encap:Ethernet HWaddr 00:40:48:DF:9A:08
inet addr:10.10.100.4 Bcast:10.10.255.255 Mask:255.255.0.0
inet6 addr: fe80::240:48ff:fedf:9a08/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:1212576325 errors:0 dropped:0 overruns:0 frame:0
TX packets:3143788157 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1737919622 (1.6 GiB) TX bytes:3042303014 (2.8 GiB)


eth0 Link encap:Ethernet HWaddr 00:40:48:DF:9A:08
UP BROADCAST RUNNING SLAVE MTU:1500 Metric:1
RX packets:3158848788 errors:0 dropped:0 overruns:0 frame:0
TX packets:1567622987 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2283585416 (2.1 GiB) TX bytes:1109390598 (1.0 GiB)
Interrupt:17 Base address:0x6000


eth1 Link encap:Ethernet HWaddr 00:40:48:DF:9A:09
UP BROADCAST RUNNING SLAVE MTU:1500 Metric:1
RX packets:2348694837 errors:0 dropped:0 overruns:0 frame:0
TX packets:1576165170 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3749304546 (3.4 GiB) TX bytes:1932912416 (1.8 GiB)
Interrupt:16 Base address:0x2000


lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:858 errors:0 dropped:0 overruns:0 frame:0
TX packets:858 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:72280 (70.5 KiB) TX bytes:72280 (70.5 KiB)
 
I've been trying to figure out how to get a current operating temp from the NVR so I can monitor it. Is telnet possibly my answer? Anyone know a way to get temp information?
 
I'd like to fool around with this but I can't find the option to enable telnet on my DS-7608NI-I2/8P. In Network/Advanced/Other there is Alarm Host IP, Alarm Host Port, Multicast Address, Enable Virtual Host (which I've enabled) and Enable Flow Control. I changed the password from default long ago. I'm running V3.4.90 build 160926, is this setting somewhere else or did Hik disable it? TIA
 
You must log in or register to reply here.
Top Bottom