- Collaboration & Conferencing
- Cloud Services
- Contact Solutions
- Internet of Things
Network and security
VIRTUAL SERVER SPECIFICATIONS
Easily change these configurations to quickly respond to business demands. You can scale up to eight CPUs and 64GB RAM.
While a virtual server is in ‘Powered off’ or ‘Suspended’ mode, you won’t accrue usage of CPU or RAM attributed to that virtual server.
Adjust your cloud solution by adding or removing data disks from your virtual servers at any time – from a minimum of 10GB to a maximum of 1,000GB in size.
Through the management console, you can create up to 15 virtual disks per virtual server.
You can also remove or increase the size of a data disk, but can't reduce it.
The system disk, which contains the operating system, can't be removed nor resized.
The system disk size depends on the operating system you choose:
|Operating system||System disk size|
|Microsoft® Windows® Server 2003||20GB|
|Microsoft Windows Server 2008||40GB|
|Microsoft Windows Server 2012||60GB|
Telstra will allocate a public IP address to each virtual server facing the internet in your network configuration.
You'll assign your own private IP addresses for the virtual servers connected to your private network. Both public and private IP addresses are static.
Configure up to two virtual network interface cards (vNICs) per virtual server.
Our virtual servers can only be delivered using our pre-defined operating system templates.
You can pick the one you need and we'll install it for you.
|CentOS® 5.x (32/64-bit)|
|CentOS 6.x (32/64-bit)|
|Red Hat® Enterprise Linux|
|Red Hat Enterprise Linux 5.x (32/64-bit)|
|Red Hat Enterprise Linux 6.x (32/64-bit)|
|SUSE® Linux Enterprise|
|SUSE Linux Enterprise 10 (32/64-bit)|
|SUSE Linux Enterprise 11 (32/64-bit)|
|Microsoft Windows Server 2003 - Enterprise R2 (32*/64-bit)|
|Microsoft Windows Server 2008 - Enterprise SP2 (32*/64-bit)|
|Microsoft Windows Server 2008 - Enterprise R2 (64-bit)|
|Microsoft Windows Server 2008 - Web R2 (64-bit)|
|Microsoft Windows Server 2012 - Datacenter (64-bit)|
|Microsoft Windows Server 2012 - Datacenter R2 (64-bit)|
Note: *32-bit versions of Microsoft Windows Server 2003 and 2008 do not currently support virtual servers running 8CPUs.
You're responsible for configuring and monitoring your operating system and ensuring that it's up to date by installing updates.
We don't provide support for any of these operating systems.
Contact your vendor directly if you have any issues:
Our combination of software and networks create a total cloud solution. Confidently access the software you need from your office, home or a client's site.
- With no up-front costs and reduced ongoing IT demands, you can request software on a new virtual server with a virtual server (shared) or managed virtual server (dedicated) service.
- Our business applications provide access to enterprise-grade software for an easy monthly fee. This means any business can gain the same software advantages as their biggest competitor.
- Enterprise applications combine the strengths of our alliance partners with local hosting in our secure data centres plus access via the Telstra Next IP® network for added security.
Business applications and enterprise applications are only available to our customers based in Australia. Contact our customer service team or your Telstra representative.
Use your existing Microsoft software licences on our cloud servers.
Thanks to our status as a Microsoft-authorised licence mobility partner, if you're a Microsoft Volume Licensing customer covered by Microsoft Software Assurance you may be able to use your eligible software licences on our cloud servers.
Licence mobility enables you to leverage your existing Microsoft licence investment on our cloud servers, thereby making it easier to move to our cloud services.
The eligible application software licences are:
- Microsoft Dynamics® CRM Server
- Microsoft Exchange Server
- Microsoft Lync® Server
- Microsoft SharePoint® Server
- Microsoft SQL Server®
Note: Microsoft Windows Server and desktop apps are ineligible. We don't support customer-supplied operating systems or virtual hard disks – you must select one of our pre-packaged operating systems.
HOW TO APPLY
STEP 1 – DETERMINE WHICH OF YOUR LICENCES ARE ELIGIBLE
Simply view your licence status by logging in to the Microsoft Volume Licensing Service Centre and note which of the above eligible applications you're licensed for. Typically, your IT or procurement department can access your licensing agreement details.
STEP 2 – VERIFY YOUR LICENCES WITH MICROSOFT
Under the Authorised Mobility Partner section of the form, you'll need to write 'Telstra Corporation Limited' as your mobility partner and include our URL www.telstra.com and licensing email firstname.lastname@example.org. From there, wait for signed notification* from Microsoft before installing your software. This usually takes a few business days.
STEP 3 – INSTALL YOUR APPLICATION SOFTWARE
*If your licence(s) are eligible, Microsoft will email a counter-signed copy of the form both to you and us. If your licences can't be verified, Microsoft will return the verification form to you explaining why. You can make any necessary revisions and resubmit the form as many times as needed.
Remember, it's up to you to have the right licences to install and run software applications on your virtual servers. See ourResponsibilities Guide and Our Customer Terms.
For all the details, see Microsoft Volume Licensing Software Assurance.
If you configure back-up on your virtual servers, we'll create daily backups of your system and data, and storing them off-site.
Our backup retention options are:
|7 daily copies
1 month of daily copies
3 months of daily copies
|3 months of daily copies
3 months of daily copies
|12 monthly copies
84 monthly copies
You can restore selected individual or all files from a data disk from virtual server backups. We don't support full system restore from backups, only from snapshots.
Virtual server snapshots help you roll back to a system configuration up to 24 hours from the moment you created it.
You can only have one snapshot at a time for each virtual server. If you create a new one, you automatically delete the earlier snapshot.
ABOUT NETWORK AND SECURITY ADD-ONS
Virtual servers can be connected to the internet and/or a private cloud network. You can connect one or more IP subnets to your private cloud network.
There are two options for connecting to virtual servers through a permanent, private network - the Telstra Next IP® network or an IPsec VPN network tunnel. Both can be requested through the management console.
A Telstra Next IP® network connection can reach all your IP subnets in your private cloud network.
IPsec VPN network tunnels connect only to the IP subnets you specify.
REMOTE ACCESS TO VIRTUAL SERVERS
You can remotely access and manage virtual servers through SSL VPN technology – a secure client-to-site network tunnel used to remotely access your cloud solution from the internet. You access it over HTTPS, using a web browser. Once authenticated, you have direct access to virtual servers. All the network traffic will be transmitted securely.
Once you've established a VPN connection, you'll be able to use tools such as Remote Desktop Services or Secure Shell to manage your virtual server – just as if you were sitting in front of it.
To be reachable by IPsec VPN, a virtual server needs to be connected to a private cloud network.
Connect up to three IPsec VPN network tunnels at one time. Add and remove tunnels any time.
Specify one or more source subnets at a single office site and multiple destination subnets in your private cloud network – all within a single network tunnel. Use firewall rules to restrict access to selected virtual servers.
You choose the encryption and authentication protocols that secure your IPsec VPN connection, from the options below.
IPsec VPN security phase
Phase 2 Perfect forwarding secrecy (PFS)
Migrate virtual servers or create a hybrid cloud by extending VLANs between your on-premises infrastructure and our virtual data centre, sharing an IP subnet across both environments.
Connection is through a point-to-point VLAN Extension tunnel, over a Telstra Next IP® network.
VLAN Extension can extend subnets between Telstra cloud infrastructure and any site connected to your Telstra Next IP®network, including third-party data centres or co-location facilities.
To use our VLAN Extension service you'll need:
- A Telstra cloud infrastructure virtual data centre in Australia
- A Telstra Next IP® network connection
- Any Telstra cloud infrastructure compute service
- Virtual Server (Shared)
- Virtual Server (Dedicated)
- Managed virtual server (dedicated)
- A terminating device compatible with our VLAN Extension service
- Cisco CSR 1000V AppX Bundle
- Cisco Nexus 3172 (available from late October 2014)
VLAN Extension cannot be used to connect two Telstra virtual data centres.
To accommodate VXLAN protocol encapsulation overhead, ensure your terminating device and any other inpath devices in your on-premises infrastructure have an MTU size of at least 1600 bytes.
First hop redundancy protocols such as HSRP (Hot Standby Router Protocol), VRRP (Virtual Router Redundancy Protocol) and GLBP (Gateway Load Balancing Protocol) are not supported by our VLAN Extension add-on.
VLAN Extension can be configured in either a redundant or a non-redundant format. Redundancy of the communication connection is achieved by supporting the VLAN Extension tunnel with an identical second compatible terminating device at your on-premises end of the tunnel.
VLAN Extension enables you to progressively relocate servers across a shared subnet. It also allows you to migrate a server in a compatible format (e.g. OVF) to or from a virtual server (dedicated) service in cloud infrastructure. Note that VMware vMotion cannot be used for this purpose.
As part of your device set up, you'll need to create firewall rules to allow communication between VTEP IP endpoints on UDP port 4789.
For each extended subnet, you can control your traffic flow by locating your gateway either on our cloud platform, or in your on-premises infrastructure.
Whenever the gateway is located in our cloud infrastructure, for configuration purposes we require the first three useable IP addresses of each extended subnet.
Changing gateway location may disrupt access to your servers, and require configuration by both you and Telstra. Your service will be disrupted during a gateway change if your IP subnet is routed to both your on-premises infrastructure and cloud infrastructure environment.
A gateway change is available in two service levels, including a scheduled gateway change. A service level comparison is shown below.
|Service feature||Gateway change||Scheduled gateway change|
|Timing of our configuration||
Occurs at a Telstra selected time between 1PM and 8PM on any day up to 3.5 business days from time of request.
We'll email you when our configuration has started.
Once started, our configuration will take approximately 30 minutes. We will notify you once complete.
You nominate your preferred and alternative date and 1 hour time window (select from limited options – no earlier than 3 business days from time of request).
We'll email you to confirm the successfully scheduled time window, within 24 hours of your request.
Once started, our configuration will take approximately 30 minutes. We will notify you once complete.
|Timing of your configuration||Any time. We recommend you do this as close as possible to our configuration, to minimise service disruption.||Any time. We recommend you do this as close as possible to our configuration, to minimise service disruption.|
|Support||Device related technical support available from Cisco.||Device related technical support available from Cisco.|
All outbound email traffic originating from mail servers operating within the cloud must be sent through our SMTP mail relay service. SMTP mail relay is charged based on the number of email messages sent.
Configure your application using our SMTP mail relay details (which we send to you when your cloud solution is up and running). You're automatically charged for any emails sent through our servers.
Want to optimise your virtual server and network performance? Request load balancers for your private and public networks and control traffic between multiple virtual servers.
For more complex network configurations, you have the flexibility to customise the load balancer algorithm to divert particular traffic to different directions. The load balancer health check redirects traffic to other load-balanced servers if one of your virtual servers is not responding.
If your load balancer is facing the internet, we allocate a public IP address. If it's located in your private network, you assign your own private IP address.
Our cloud infrastructure is fully redundant. We protect you from a single point of failure for all the features in our architecture.
We also perform regular penetration testing of our platform using a third party.
Our cloud infrastructure is also monitored by an assurance tool that sends alerts to our support team if something goes wrong.
Our virtual servers on shared compute are backed by the following service level agreements to help ensure maximum availability and performance.
|Service support coverage hours||24/7|
Measured on a yearly basis.
|99.9% of the service year|
|Recovery point objective
The maximum rollback point in time to which your data is restored.
|Recovery time objective
The time taken to restore or reconfigure your equipment and commence the uploading of data to the target systems during the restoration process.