BCM 400 disk problems

[MasterCommDave]

Was recently trying to initialize BCM 400 3.6. After initialization was able to access BCM thru putty using the default ethernet IP, but was not able to connect using Intenet Explorer. I could ping the unit also.Has any one ever had this happen? If so what was the cause and what can be done to correct it? Thanks

 

[biv343]

You need the SSL certificate fix tool. The issue is with the SSL certificate not being valid if platform initialization occured after 1/1/2008, or maybe it was 1/1/2007, don't remember which.

I haven't looked to see if the SSL fix tool made it to the Avaya support site or not. You can change the date on the system to something before 2007, such as January 1 2006, then re-run the platform initialization. You can change the date from the DOS command line. Go to the command line, and type date 1-1-2006, then hit enter. Go back to the initialization menu, run the universal profile again and you'll be set.