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

Reminder

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

upgrade
Knowledge Base

fast-connect configuration removed after reboot

Publication Date:  2012-07-27  |   Views:  2  |   Downloads:  0  |   Author:  Carlos Thompson  |   Document ID:  EKB0000273763

Contents

Issue Description

When fast-connect is configured in a voip entity, and the system is rebooted (e.g. after a power failure), fast-connect configuration is lost.
This has been tested in VRP 3.40 release 0109P17 but has been reported in other 0109Pxx releases.

Alarm Information

Null

Handling Process

This is the configuration in VRP 3.40 r0109P17:
<Quidway>system-view
System View: return to User View with Ctrl+Z.
[Quidway]voice-setup
[Quidway-voice]dial-program
[Quidway-voice-dial]entity 10 voip
[Quidway-voice-dial-entity10]match-template 10
[Quidway-voice-dial-entity10]fast-connect
                             ^
 % Unrecognized command found at '^' position.
[Quidway-voice-dial-entity10]f?
   fax
[Quidway-voice-dial-entity10]address ip 1.2.3.4
[Quidway-voice-dial-entity10]f?
   fast-connect
   fax
[Quidway-voice-dial-entity10]fast-connect
[Quidway-voice-dial-entity10]display this
#
entity 10 voip
  fast-connect
  match-template 10
  address ip 1.2.3.4
#
return
[Quidway-voice-dial-entity10]return
<Quidway>
If saved and then rebooted, the system reads *fast-connect* when no *address ip* command has been issued and therefore ignores the command.
This problem does not happen in VRP 3.40 release 0201, where the same sequence would show:
[Quidway-voice-dial-entity10]display this
#
entity 10 voip
  match-template 10
  address ip 1.2.3.4
  fast-connect
#
When saved and rebooted, the command will not be ignored.
Note that if the configuration script is manually edited so that *fast-connect* command be after *address ip* command, the command will not be ignored in neither release 0109p17 nor 0201.
However, if a later change is done and saved, manual editting will be lost, and the problem will rise again.

Root Cause

*fast-connect* command must be issued after *address ip* command.  However the system orders  *fast-connect*  before  *address ip*, and saves the configuration file in this order.
When the system reboots, it reads *fast-connect* when there is no IP address in the voip entity and therefore ignores this command.
The command is lost for *display current-configuration* (and not working), but it is still there in *display saved-configuration*.

Suggestions

1. Upgrade to VRP 3.40 release 0201 or later.
2. Edit manually the startup configuration file.