No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


On the AR3260 Running V200R007C00SPCb00, the Zabbix Is Used to Run a Script and Obtain the Ping Result. However, the Results Are Non-consecutive

Publication Date:  2019-04-15 Views:  148 Downloads:  0

Issue Description

The Zabbix is used to run a script to ping the peer end directly connected to the AR3260 through a private line. The results are non-consecutive. In scenarios of high concurrency, a timeout occurs, and the result fails to be obtained.
The script content is as follows:

CMD_PATH=`dirname $0`
`expect $CMD_PATH/ > $CMD_PATH/log`
sleep 1
a=` cat $CMD_PATH/log | grep loss | awk '{split($0,str,"[%]");print str[1]}'`
echo $a
set timeout 10
spawn ssh -l read_yyyw
expect ": "
send "read_yyyw\r"
expect ">"
send "ping -c 5 -t 1000\r"
expect ">"
send "q\r"

The interface values are as follows:

Handling Process

1. Perform an extended ping test. It is found that no packet is lost. Therefore, a device hardware fault is ruled out. It is suspected that the fault is caused by configurations on the device.

2. Check the script and find that it is executed every minute. During each execution, six SSH connections, ping, and logout operations are performed concurrently. Check the SSH implementation mechanism on the AR and find that the AR does not support the preceding high-concurrency SSH login scenarios.

Root Cause

The AR does not support the high-concurrency SSH login scenarios.


Modify the shell script and use SSH for login in non-concurrent mode. The fault is rectified.


The AR supports a maximum of five concurrent SSH connections. (One account uses the same IP address to log in to devices using SSH.)