The reset command when executed using the peer name resets all the tunnels, even if the peer exists the error says no peer or tunnel found.
vyos@vyos:~$ reset vpn ipsec-peer Possible completions: right Reset all tunnels for given peer vyos@vyos:~$ reset vpn ipsec-peer right Possible completions: <Enter> Execute the current command tunnel Reset a specific tunnel for given peer vti Reset the VTI tunnel for given peer vyos@vyos:~$ reset vpn ipsec-peer right Peer or tunnel(s) not found, aborting
It allows to reset the tunnel when the tunnel number is specified
vyos@vyos:~$ reset vpn ipsec-peer right tunnel 0
closing CHILD_SA right-tunnel-0{70} with SPIs ca7a571f_i (0 bytes) cf540b3a_o (0 bytes) and TS 10.0.0.0/24 === 10.20.0.0/24
sending DELETE for ESP CHILD_SA with SPI ca7a571f
generating INFORMATIONAL request 744 [ D ]
sending packet: from 1.2.3.3[4500] to 1.2.3.4[4500] (80 bytes)
received packet: from 1.2.3.4[4500] to 1.2.3.3[4500] (80 bytes)
parsed INFORMATIONAL response 744 [ D ]
received DELETE for ESP CHILD_SA with SPI cf540b3a
CHILD_SA closed
CHILD_SA {70} closed successfully
establishing CHILD_SA right-tunnel-0{72}
generating CREATE_CHILD_SA request 745 [ SA No KE TSi TSr ]
sending packet: from 1.2.3.3[4500] to 1.2.3.4[4500] (320 bytes)
received packet: from 1.2.3.4[4500] to 1.2.3.3[4500] (320 bytes)
parsed CREATE_CHILD_SA response 745 [ SA No KE TSi TSr ]
selected proposal: ESP:AES_CBC_256/HMAC_SHA2_256_128/ECP_384/NO_EXT_SEQ
CHILD_SA right-tunnel-0{72} established with SPIs c13a90fb_i cc856f3c_o and TS 10.0.0.0/24 === 10.20.0.0/24
connection 'right-tunnel-0' established successfully
Peer reset result: success