Project

General

Profile

Actions
Copy link

Bug #480

closed

Monitor IP config upgrade doesn't work

Added by Chris Buechler over 14 years ago. Updated over 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Gateways
Target version:
2.0
Start date:
04/04/2010
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

After upgrading a 1.2.x config to 2.0, if the configured monitor IP is anything other than the gateway IP, it is not converted properly. OPT1's monitor IP ends up in 

<opt1> 
...
<monitorip>1.2.3.4</monitorip>
</opt1>

Which does nothing. the gateway_item entry after converted is missing the monitor tag entirely. It should convert that monitor IP not to the interface config as shown above, but to:

<gateway_item>
...
<monitor>1.2.3.4</monitor>
</gateway_item>

Related issues

Related to Bug #771: Gateway upgrade code is broken.Resolved07/30/2010

Actions
Actions
Copy link
 #1

Updated by Ermal Luçi over 14 years ago

Please provide an example.

Actions
Copy link
 #2

Updated by Perry Mason over 14 years ago

Can confirm the problem.

Actions
Copy link
 #3

Updated by Ermal Luçi over 14 years ago

Please provide the sample from 1.2.x config to be upgraded

Actions
Copy link
 #4

Updated by Chris Buechler over 14 years ago

I already sent you my config for this Ermal.

Actions
Copy link
 #5

Updated by Ermal Luçi over 14 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Chris Buechler over 14 years ago

  • Status changed from Feedback to Resolved

fixed

Actions
Copy link

Also available in: Atom PDF