Overview
This guide is devised to help setup your new Express for Lync appliance.
Express for Lync 3.0 Roles
Express for Lync 3.0 is designed to be your primary Lync device. A user can configure the following roles and services on their Express for Lync appliance:
Lync Server 2013 Standard Edition Front End Server/Pool with a collocated Mediation Server
Lync Server 2013 Edge Server
Microsoft Windows Active Directory Server
Active Directory Federated Services 3.0 Server
Microsoft Office Web Apps Server
Reverse Proxy Server using Internet Information Services (IIS) Application Request Routing (ARR)
TDM Gateway using NetBorder Express VoIP Gateway
Session Border Controller using the Vega SBC
In some environments, not all roles are required as they may already be deployed. See the examples below:
if an organization already has an existing Active Directory infrastructure, the Domain Controller role does not need to be activated. Express for Lync can interface with the existing AD infrastructure to configure Lync Server.
If an organization currently has Microsoft Exchange running with OWA active, they have most probably deployed a reverse proxy server and the domain controller. They would not need to activate these roles on Express for Lync.
Windows Logon Information
Upon first boot of the appliance, use the credentials below to login:
Username: administrator
Password: sangoma1!
NOTE: All virtual machines within the Express for Lync appliance use the above credentials. It is recommended, for security purposes, that the above password be changed from defaults.
Networking
There are 7 ports on the Express for Lync appliance. Each port has their own specific functions as outlined below:
Port 0 - LAN Management
Port 1 - LAN Front End and Edge
Port 2 - LAN AD, OWA, RP, SBC
Port 3 - Unused
Port 4 - WAN SBC
Port 5 - WAN Reverse Proxy
Port 6 - WAN Edge Proxy
IPMI Interface
This is the interface used to monitor and manage the Express for Lync appliance. This must be connected in order to be able to setup the appliance for the first time.
Management Interface
Port 0 of the appliance is considered the management interface. This interface is not attached to any of the virtual machines on the appliance, and can be used to connect to the host. Within Windows, it is dubbed "Ethernet 7". Only this interface should get an IP address. All other Hyper-V interfaces should be disabled.
Front End and Edge Internal Interface
Port 1 of the appliance connects to the internal interfaces of both the Lync Front End server and the Lync Edge server. The IP address to these VMs is applied from within their respective VMs.
AD, OWAS, Reverse Proxy and SBC Internal Interface
Port 2 of the appliance connects to the internal interfaces of the Active Directory, Office Web Apps, SBC, and the Reverse Proxy Servers. If any of these VMs are going to be enabled, you must connect this interface. The IP address to these VMs is applied from within their respective VMs.
SBC External
This interface is used to connect the Session Border Controller (SBC) to the external world. It can be connect to either a DMZ (De-Militerized Zone) or directly to the internet. If you are not planning on using the SBC externally, this interface is not required and does not need to be connected.
Reverse Proxy External
This interface is used to connect the Reverse Proxy server to the external world. It can be connect to either a DMZ (De-Militerized Zone) or directly to the internet. If you are not planning on using the Reverse Proxy server, you do not need to connect this interface. It is also important to note that if you are not using the Reverse Proxy server, you should not even power on the virtual machine.
Edge External
This interface is used to connec the Lync Edge Server to the external world. It can be connect to either a DMZ (De-Militerized Zone) or directly to the internet. If you are not planning on using the Lync Edge Server, you do not need to connect this interface. It is also important to note that if you are not using the Lync Edge Server, you should not even power on the virtual machine.
Appliance First Time Setup Infromation
There are two methods of connecting to the Express for Lync interface:
IPMI Connection
Remote Desktop
In order to connect for the first time, it is recommended that the IPMI interface gets setup. This will allow you to configure the appliance without the need for remote desktop. Once you have configured the IP address of the management interface, you can proceed to connect via Remote Desktop.
Sangoma IPMI User Guide
This user guide applies to all Sangoma products that use the Carrier hardware platform.
NetBorder Carrier SBC
NetBorder SS7 Gateway
Express for Lync 3.0
Sangoma-NetBorder-IPMI-UserGuide.pdf
Sangoma IPMI Firmware
Latest Sangoma IPMI firmware is:
Aug 2015 |