Issue with 6.3 Template install

[lopes1211]

I'm doing a fresh install of 6.3 on an s8300D. System Plat installs fine and the web interface shows DOM and CDOM running.

Domain-0 6.3.0.0.18002 192.168.1.33 512.0 MB 1 8m 22s Running N/A
services_vm 2.0.0.0.15 192.168.1.32 512.0 MB 1 3m 15s Running Stopped
cdom 6.3.0.0.18002 192.168.1.34 512.0 MB 1 7m 17s Running N/A

I'm following the June 2014 6.3 manual and after inserting the template DVD, the manual says:

5. Click Virtual Machine Management > Templates in the navigation pane.
The system displays the Search Local and Remote Template page. Use this page to select
the template to install on System Platform.
6. Click Install, and then, in the Install Template From field, select the location of the template
to be installed.

When I click "install", nothing happens. I do not get any type of dropdown or popup to ask me to select "from" usb/dvd/http/plds as the manual implies. I've reloaded Sys Plat several times and it behaves the same every time. Am I doing something wrong, missing a step, or maybe have some bad hw/sw?

-CL

 

[kyle555]

Probably browser related from the sounds of it. Otherwise, it should prompt for options to look from local file system (if you copy all the files into /vsp-template, it looks there by default), but you normally have options to pop a DVD in the portable DVD drive, or download from PLDS (which I've never actually seen work). Maybe try a different System Platform disc/download it again/burn it again slowly, otherwise, what browser are you using? I'm usually good with Chrome or Firefox

 

[wpetilli]

Yea, make sure you select the right medium for the system to search off. Did you burn the SP and templates on the same DVD? Maybe separate them? I've only used original AVAYA discs to do this, that were separate. I've not had any issues with the browsers... the only thing is there's a point where you need to turn off pop up blocker to get past a certain step in the template install, but it's after it launches.

 

[Sean5150]

I have run into this issue into the past and the fix was a system platform patch provided by Avaya.