Deployed Avaya EMS+SBC 8.1

[fondog2]

Hello to all,
I currently deployed the above and in doing so I made sure that the OVA configs were set to EMS for deployment configuration, Set the M1, M2, A1, A2, B1 and B2 for the NIC's. I also set the Appliance type to EMS+SBCE and EMS Instance Type to Primary (this could be my issue but not sure). After the deployment finished I am able to login and I see the EMS but no SBCE so I can't configure it. I also have the not connecting to WebLM but I can't ping the System Manager IP and have network looking at the firewall rules. From what I'm seeing the EMS deployed and is using the management IP instead of the SBCE and I should have set the EMS instance to secondary or none. Has anyone seen this before or can tell me what I did or didn't do? The doc for this is like the rest of Avaya's very vague.

Thank you,

 

[kyle555]

I feel like you nailed it. Can't remember off hand, if you paste the info around that field I'd know for sure, but there's definitely one that's "not for single box deployments"

I know it's weird

And then, when you're done, if you enable all the interfaces and do ifconfig and get the MACs for A1 A2 B1 B2 M1 M2 you'll notice they do not align at all with what you put in VMware. At least that's what I consistently get on vCenter deployments.

 

[fondog2]

kyle555,
You are correct on those NIC's you have to go by mac addresses. None of them are up they all show down at this time which could be part of my issue still dealing with Network and firewall rules as this is a brand new deployment and not a migration. New firewall equipment too. Hopefully the two pics can be viewed.

 

[kyle555]

OK. A EMS gets 3 CPU, a SBC gets 4

So you pick SBC on the first radio button

And then I think it's NONE for EMS Instance Type because that's for "EMS Install Type" which is only if you picked the first radio button for an EMS if you want primary or secondary

 

[fondog2]

OK so what do you pick for both? The doc sucks. Redeploy as an SBC then appliance type EMS+SBC, EMS instance Primary?

 

[fondog2]

Maybe I'm not explaining correctly. I want an EMS+SBC combo. So I would think deploy as EMS and then EMS+SBC but that didn't seem to work.

 

[fondog2]

Or I am misunderstanding you all together. Which is possible considering I have deployed this dang thing 4 times today.

 

[kyle555]

only 4? Amateur

I'd deploy as SBC with type EMS+SBC and EMS type none

 

[fondog2]

Thanks Kyle I will give it a shot and let you know the outcome.

 

[fondog2]

kyle555,
So I redeployed, patched and have it talking to the WebLM. But still no joy on seeing the SBC as an option when you go up to Device: EMS drop down box. I may have to reach out to Avaya and see what they say.

 

[fondog2]

Kyle555,
It is working now and the SBC showed up. 2 things. One the NIC's got out of order so I matched the MAC addresses to set them. Second I had to reboot the box before it showed up. Thank you for your help on this.

 

[kyle555]

 

[fondog2]

One last thing. I did a typo on the host name. Instead of SBC3 it was SBC2. I tried the command from root which is SBCEConfigurator.py change-hostname SBC2 and it stated command not found. Do you know if the 8.1 SBC has a newer command?

 

[fondog2]

I got it. I was able to do it through VI.