Merge Failed @ 99%

[bigjohn8210]

I have just done a name change on a system and when i merged the config it failed at 99%

I turned up onsite thinking the box would have just defaulted

but found the box in a reboot cycle

I have tried the Manager BootP process to see if it would load the bin file to the unit with no luck

Any idea if anyone has had this before why it happend because i don't want to have to go through this again.


Currently awaiting a new box to arrive onsite

 

[aarenot]

What release, and did the manager, and IPO firmware release match?

 

[bigjohn8210]

Manager Used 4.0(5)

Systems Managed 3.1 (65)



I have made changes to many software levels

 

[SuperJenks]

Its likely the unit was not upgraded properly. If the 3.0.99 and 3.1.99 was not used, or didnt upgrade as it should, the memory space available for the .bin and running config will not have enough space to hold the data. This would explain why 99% of the config is being saved. Try down grading to 3.0.99, then 3.1.99 and finally 3.1.65. Try that. Ill check back for more questions.

 

[Infinity306]

I would try using 3.1 manager first, while the new versions of manager are supposed to be backward compatible it's possible that they are not 100% compatible but just 99% compat. I know I had problems with 3.2 manager when i was running 3.1 on the IPoffice... we h ad an extended power outage and the UPS on the IPoffice didn't last long enough, so the ipoffice rebooted and wouldn't pull config from 3.2.. I had to manually send config back to it..

 

[tlpeter]

@bigjohn8210

with what kind of connection you where sending the config ?
you should be connected straight on to the ip office
dial in is straight on it but vpn is not and can cause this kind of trouble


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[aarenot]

If using VPN to admin, remote desktop to a local machine that has manager on it, and go from there. To the VMPRO server works fine.

 

[bigjohn8210]

I connected in via the PRI on the system using isdn 2


We had to use the DTE process on the system and default it the upload a backup config.