Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya ASBE 10.1 - Second SBCE (Down)

Status
Not open for further replies.

BrianCosta

Systems Engineer
Oct 25, 2018
376
JO
Hi ...

I have Newly Installed Avaya ASBCE 10.1 HA on VMware Machines as follows:

VMWare 1 : ( 10.234.14.1)

Avaya IPO 11.1 Primary (10.234.11.1)
EMS: (10.234.13.1)
SBCE: (10.234.13.2) - Hostname:sbce

VMWare 2: ( 10.234.14.2)

Avaya IPO 11.2 Secondary (10.234.11.2)
SBCE (10.234.13.3) - Hostname: sbce

Each Server VMWare Machine has 4 NIC Cards as follows:

NIC 1: VMSwitch ( for Subnet 14 and Subnet 11)
NIC 2: for M1
NIC 3: Reserved for B1
NIC 4: M2 Duplication Link (crossover cable between 2 VM Servers)

when Adding Avaya SBCE devices as a High Availability to EMS, the first one is registered but the second management node is down (attached screenshot)
we tried to install sbce in different hostnames but nothing changed ( is the hostname for both should be unigue or not ) anyway in both cases nothing changed the first registered but the second did not.
all the networking IPs are pingable and reachable and I have no problems with them.
I know this is the first step in setup, but no one talking about this case if happened what should be done, it's the first step in the administration of the SBCE.



 
 https://files.engineering.com/getfile.aspx?folder=b6150d6f-3ab4-4775-a12c-722941d8268d&file=SBCE_HA.rar
I would go into the vmware console and take a look at the interface from there.

ifconfig, etc etc

also make sure the M1's are both pingable from the EMS itself not just your machine.

New England Communications
 
@JayNEC: Thanks, yes all it's pingable from VMWare Machine itself not from my PC.
also, I see from a document that:

Use Local WebLM Server An option to use a local WebLM server.
Virtualized EMSes cannot run on a local WebLM server.

I use local WebLM, is this causing the problems?
also should the hostname of both sbce is unigue or use the same name

Thanks
 
Are the M1 interfaces on a different subnet/VLAN to the A interfaces?

Go into linux on the servers do an IP A take a note of the MAC addresses and then confirm those interfaces are mapped to the correct vNICs and vSwitches etc in vmware.

Each server needs a unique hostname ems01, sbce01, sbce02 etc otherwise you'll have issues with DNS and ARP(hostnames)

Can IPO host sbce licences? if not install a standalone WebLM server for the licencing


Also found this

Avaya SBCE uses the Avaya Product Licensing and Delivery System (PLDS) to create licenses and download Avaya SBCE software. PLDS is not integrated with WebLM. Use PLDS to perform operations such as license activations, license upgrades, license moves and software downloads.

There are two licensed versions of Avaya SBCE:

Standard Services delivers non-encrypted SIP trunking.

Advanced Services adds Mobile Workspace User, Media Replication, and other features to the Standard Services offer.

Avaya Aura® Mobility Suite and Collaboration Suite licenses include Avaya SBCE.

Avaya SBCE uses WebLM version 8.0 or later for licensing requirements. You can install the Avaya SBCE license file on a primary Element Management System (EMS) using the Device Management page.

Important:
You must not enable the local WebLM option and install an Avaya SBCE license file on the secondary EMS if used in an active-active deployment. If you install a license file on a secondary EMS in an active-active deployment, the licensing system will always show that the secondary EMS is in Grace Period State.

Ensure that the license file of the WebLM server displays the product code Session Border Controller E AE. Before you configure the license file, you can view the License State, Grace Period State, and Grace Period Expiration Date fields on the Dashboard page. You have a 30-day grace period from the day of installation or upgrade to install the license. Avaya SBCE works normally during the grace period.

Important:
Licenses and a WebLM server are required for new installations or upgrades.

The license file contains the following information:

Product name

Supported software version

Expiration date

Host ID

The primary host ID of WebLM is used for creating the license file.

Licensed features

Licensed capacity

All hardware Avaya SBCE devices can use a local WebLM server for licenses. However, for mixed deployment environments with EMS on VMware and Avaya SBCE on hardware, use a WebLM server installed on VMware or System Manager WebLM.
 
@biglebowski :

Yes the M1 Interface is on Different VLAN of A1 Interface ( M1 - 13 ) - ( A1 - 11)

Thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top