I am applying for a position for a Cisco Voice engineer - I have just recently passed my CCNA voice exam.
Basically, the post was asking for a ccnp voice engineer - but the salary was below what I expected for that qualification anyway; so I called and asked for their reasoning - at the same time explained that i had some experience as well as the ccna voice and now I have a telephone interview on wednesday evening this week - with the possibility of an in house/on site interview the following week.
I am stuck as to what to learn or recap for this interview - can someone provide me with some advice on what I can learn quickly or rather what should I really concentrate on for this interview??
It's impossible to predict what you will be asked during interview process, analyze the job posting requirements and make sure you can speak to those points. Interview is not an exam so don't look for specific questions/answers, but rather rely on what you know and what you can answer honestly.
I agree with Chris, I've been involved in many interviews for candidates and we determine what we're going to ask after reviewing the CV and after having the candidate give us a 10-15 minute talk about his experience, then we ask based on what he said was his experience and knowledge of the products. We set the bar just high enough for the role we're interviewing for, to be fair with the candidates.
As Chris says, honesty can get you far on interviews. If you don't know about a product or have limited experience, say so, there's nothing wrong with that. It's worse to tell them you're the master of some product and then be unable to answer the questions.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.