IP500 V2 SD card problem 3

[Lodde]

Hi

I am hoping that anyone else also has experinced a problem with the SD card in the 500v2.

It can all of a sudden loose the config of the IPO and that is really bad.

Does anyone know if Avaya is working on the problem or if there is a PB for it ?

regards Lodde

 

[littlelily]

Last news: release 6.0.14 hasn't yet solved crackling noise problem...
Any hint?

 

[tlpeter]

There is a pb for it.
Raise a case for it and tell them that 6.0.14 does not solve the problem.

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[littlelily]

I called distributor support...

 

[tlpeter]

I just received an email that it is in the Q4 release.
So it did not make it into Q3.



Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[amriddle01]

We will get it next month then, that's Q4

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[tlpeter]

Q4 is most of the times the end of November or begin of December or am i mistaken.



Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[amriddle01]

Indeed, I am working on the old 16 month year again, that's how it feels sometimes

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[AvayaSpec]

I have a SD CARD version 6.0.14. The licens suddenly get Invalid. Rebooting does't help. Tried to delete them and back on still invalid?

 

[tlpeter]

Remove the card and put it in a card reader.
Then uncheck "read only" on the folder "system"


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[SCNIPOffice]

Just upgrading a 6.0.14 to 6.0.18 and experienced this mid-upgrade on one out of five IP offices. In upgradewiz, only the name of the IP office appears (not the files that normally appear underneath). The system in upgradewiz shows 6.0.18, however upgradewiz did not act like it had been upgraded correctly.

Sysmon shows the SD card going into read only mode. I was able to restart the IP office a number of times and it eventually came back as read/write, however when attempting the upgrade again, it failed with some scary looking messages:

254964mS PRN: Merge from NAND Done
254964mS PRN: Attempt merge of call log from file...
254965mS PRN: Config Write Wake Up
255465mS PRN: Updates IO list size 0 updated list size 4
255465mS PRN: Config Write Completed
262060mS PRN: WhoIsTCPSession: created
262319mS RES: Tue 12/10/2010 21:31:47 FreeMem=70224160(1) CMMsg=2 (4) Buff=200 963 1000 7463 5 Links=1942
262319mS RES2: IP 500 V2 6.0(18) Tasks=40 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=44 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
275130mS PRN: WhoIsTCPSession: created
275319mS RES: Tue 12/10/2010 21:32:00 FreeMem=70224160(1) CMMsg=2 (4) Buff=200 963 1000 7463 5 Links=1942
275319mS RES2: IP 500 V2 6.0(18) Tasks=40 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=44 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
284319mS RES: Tue 12/10/2010 21:32:09 FreeMem=60398696(1) CMMsg=2 (4) Buff=200 963 1000 7463 5 Links=1941
284319mS RES2: IP 500 V2 6.0(18) Tasks=40 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=44 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
372434mS PRN: LoadCountControl: Marked As Successful Boot1
372819mS RES: Tue 12/10/2010 21:33:37 FreeMem=60398264(1) CMMsg=2 (4) Buff=200 962 1000 7463 5 Links=1933
372819mS RES2: IP 500 V2 6.0(18) Tasks=40 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=43 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
373062mS PRN: Read/Write Sector: memcmp failed
373070mS PRN: LoadControl: Marked For NAND Boot Already
373070mS PRN: WARNING:
373071mS PRN: Card verification: Write to System SD Card directories FAILED, raising an alarm
373071mS PRN:
373071mS PRN: \system\backup failed
373071mS PRN: \system\lvmail failed
373071mS PRN: \system\dynamic\lvmail failed
522927mS PRN: Config Write Wake Up
523427mS PRN: Updates IO list size 0 updated list size 1
523427mS PRN: Config Write Completed
543474mS PRN: Config Write Wake Up
543974mS PRN: Updates IO list size 0 updated list size 1
543974mS PRN: Config Write Completed

 

[tlpeter]

Remove the card and put it in a card reader.
Then go to properties of the folder system.
Then uncheck read only and apply for all folders.

Then put it back in and try again.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[SCNIPOffice]

Thanks tlpeter,

I'll try this as soon as I can get someone on site tomorrow. If that doesn't work, is there a guide for reformatting the SD card? Looks like there's an option in Manager that will do it to an SD card in a local SD reader, but there are different options (A-Law, U-Law, ...).

What would be my next step?

 

[tlpeter]

It depends on where you are located.
We only have A-law but i am in Europe where there is only A-law.
The US has U-law.

Formatting the card can be a dangerous job if it is in read only mode.
Somehow it ends up not being recognized anymore.
I have had this a couple of times and i needed to format it with Windows while the docs say don't do that.
But if there is no other choice then take the gamble.
Only do a quick format and right after that a format with manager.
Sometimes it will not do the job the first time and you have to try that again.
It took me 10 times on a certain card but it is still up and running


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[SCNIPOffice]

Apparently the SD card is SDHD format, which wasn't readable by the on-site SD card readers. The act of ejecting and reinserting the card seems to have made it writable again. I was able to see the card come up without being in read only mode through sysmon and have run upgradewiz once against it where I see all of the bin files listed under the IPO:

IP 500 V2 Version: 6.0(14) Available: 6.0(18)
avpots16.bin
dvppots.bin
nas0-16.bin
nadcp-16.bin
nadcpV2.bin
naatm16.bin

After running the upgrade once, the upgradewiz reported a successful upgrade, however the system did not reboot. I rebooted and it came back up as 6.0(14). System status shows that the IPO is reading the config off of the SD card. I'm running the upgrade process again to see what happens.

I'll keep all posted.

 

[SCNIPOffice]

After another run of the upgrade process, it appears that the IPO has been successfully upgraded to 6.0.18 with all errors gone. Thanks for the pointers!

 

[hibroth]

From the Global Tech Bull #124 released with the 6.0(18):

2.1 Upgrading an IP500v2 System to this Maintenance Release
If the system is to be upgraded remotely and is an IP500v2 platform please check the size of the IP Office configuration file (config.cfg) held on the system SD card before upgrading to this release. The config.cfg file can be found in the “Primary” folder of the System SD card. For further information please refer to “Viewing the Card Contents” in the “SD Card Management” section of the IP Office Installation Manual.
If it is determined that the IP Office configuration file stored on the System SD card has a zero byte size it is likely that the issue documented in CQ105039 “SD Card - Config periodically defaulting following a system restart” has occurred. In this instance the IP500v2 system will potentially restart with a default configuration. In this instance it is recommended that the following procedure to upgrade the IP500v2 system is performed when connected to the customer’s LAN:
1) Using Manager, take a copy of the System configuration and store on the local Administration PC.
2) Connect to the IP Office’s LAN and perform a System Restart using Manager.
3) When the system has restarted use Manager to send the backup of the customer’s system configuration file to the IP500v2.
4) Restart the system and recheck the size of the IP Office configuration in the System SD card.
5) Upgrade the IP500v2 system to the 6.0(18) GA release.