The EX controller works differently to 'normal' MiVB physical machines.
It's a single board Linux PC in the box running Linux and KVM (Kernel-based Virtual Machine)
That Linux OS initially runs a virtual deployment server (called deployment tool) that lets you deploy the virtual MiVB machine and then shuts down the deployment server.
All three machines will have different IP addresses - and have different web interfaces.
It does all make sense once you understand what's going on, but does take a while to get the hang of it.
Once MiVB is up and running it should be familiar to you.
There are some new hardware cards (DSP, T1/E1 cards, FXS/FXO cards) that have placement rules but are then largely configured from MiVB.
**From install doc**
•Slot numbers are displayed on the front, left-bottom corner of the controller.
•Cards must be installed from slot 1 sequentially, without leaving empty slots between the cards.
•There must not be any empty slot between cards.
•Install all PRI card(s) first, sequentially starting from slot 1.
•If you have an FXO or FXS card to install, then install a DSP card.
•Install a DSP card in the first slot available after the PRI card(s) or in the next slot available after the FXO or FXS card.
•If there is no PRI card, then install the DSP card in slot 1.
•Install FXO and FXS cards in the next available slots after the DSP card.
•If there are no PRI or DSP cards, then all the slots must remain empty
There is a good guide on the Mitel Doc Center: "EX Controller Installation and Administration Guide Release 9.0 & Later Issue 1.0"
It explains how the Deployment Tool works, gets it's initial IP address and how to connect.
This should let you deploy the MiVB and get going.
I would advise updating the deployment tool software itself before trying to deploy the latest MiVB software.
It does all work well once you get it going! I would prefer an MXe any day though.
yeah i agree - confused me until i understood what was going on i think they were trying to be too clever and have HW that would support multiple platforms
- we only have 3 that are resilient endpoints - NO TDM stuff at all
I believe some of the trunk stuff is done from outside the MiVB interface
If I never did anything I'd never done before , I'd never do anything.....
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.