12 June 2012
24 May 2012
Cloud Distribution hires northern sales boss
MicroScope contributor
May 21, 2012 2:21 PM
May 21, 2012 2:21 PM
Cloud Distribution has appointed Tracey Hannan from telecom company KCOM to head up its sales operations in the North, writes Linda Endersby. Tracey will draw on her 15 years' experience in the industry to help lead, drive and manage sales as Cloud Distribution continues to expand.
"I am delighted to be working with Cloud Distribution," said Hannan. "The company is renowned for bringing innovative and disruptive technologies to market and it is a fast paced, agile and exciting organisation to work for."
Hannan will be based in the company's York offices and will report to sales director and co-founder, Greg Harris.
Said Harris: "Tracey is an excellent addition to the team. Right now we are experiencing great traction in the market and rapidly expanding. This is because we deliver a highly specialised and streamlined service based on our deep knowledge of the products, challenges and opportunities that exist within the cloud.
"Tracey's previous security experience combined with her product management and technical knowledge will help to strengthen our capabilities and we are looking forward to working with her," he added.
Hannan was propositions manager for KCOM and has worked as product marketing manager for MIS Corporate Defence Solutions, where she was responsible for products and vendor relationships. She has also served time with InTechnology, Check Point, and a number of other systems integrators.
23 April 2012
Optimize VoIP on your network with 3 easy clicks
It seems like it was just yesterday that we released a new product to our suite – the MS series Cloud managed switch. Many administrators deploy switches in a VoIP environment, so below are a few tips on how to configure a Meraki switch’s voice, QoS, and port mirroring features.
Voice VLAN
Using the power of cloud-managed networks, it is extremely easy to configure a voice VLAN on the MS series switch. What is a voice VLAN, you may ask? Often times, you may not have enough ports to connect each employee’s workstation and VoIP phone to your network. For this reason, most VoIP phone manufacturers add an extra port for workstations to connect to. However, your infrastructure may have a separate VLAN for data that the phone is not automatically configured for. In this scenario, configuring a voice VLAN may be crucial as it allows the switch to communicate with the VoIP phones and properly tag voice data.
The option to configure a voice VLAN is available in the pop-up menu to update the port(s). In the Configure > Switch Ports page, choose the ports to which you’d like to assign a voice VLAN, and then click “Edit selected items” button on the upper left corner. The menu shown below will appear, and this example assumes VLAN 200 is the voice VLAN.
Read more
http://www.meraki.com/blog/2012/04/optimize-voip-on-your-network-with-3-easy-clicks/
12 April 2012
Capital FM Arena Streamlines And Enhances Coverage With Cloud-Managed WiFi
Reading, UK, 11th April 2012 - Value Added Distributor, Cloud Distribution, announced today that Capital FM Arena Nottingham, the East Midlands premier entertainment venue, has implemented a Meraki Wireless LAN. Enabling anytime, anywhere network access via any mobile device, the new cloud-based network has simplified, streamlined and delivered increased network performance to the Arena’s wireless connections and WiFi access.
Through Cloud Distribution, the UK distributor for Meraki, the Arena has implemented 12 Meraki high performance 802.11n internal access points in total – three MR24s and a mixture of MR16s and MR12s. Each access point provides built-in enterprise-class features including a stateful policy firewall 802.1X/RADIUS support, Network Access Control, and Wireless Intrusion Detection and Prevention (WIDS/WIP).
12 March 2012
Meraki's WAN Optimization SAVES PARTNERS TIME & MONEY. Request a FREE TRIAL NOW
Here at Cloud Distribution we believe that WAN Optimization has become a technology which is far to complex for most end users to implement, manage and control. Meraki's MX range of Security Appliances collapse WANOP into the edge security device allowing you, the reseller, to sell it quickly saving time and money. Why sell a point solution which takes 60-90 days to sell when you can sell a complete edge device solution (including L7 Firewall, Packet Shaping, Content Filtering, VPN, NAC etc. etc.).
Here's how easy it is to enable WAN Optimization to a Meraki MX Security Appliance network:
Here's how easy it is to enable WAN Optimization to a Meraki MX Security Appliance network:
Figure 1: WAN optimization configuration
After that, the MXs that are part of the site-to-site VPN network will accelerate the FTP, HTTP, Windows file sharing (CIFS/SMB) and TCP-based traffic between them. There’s no additional cost to roll this out, and WAN optimization is available on the MX for customers with both the Enterprise and Advanced Security licenses.
Here’s a look at the WAN optimization of traffic between Meraki’s branches and San Francisco headquarters. At the time of this snapshot, the amount of data transfered across the WAN was reduced by 95.2%.
Figure 2: WAN optimization and bandwidth reduction
WAN optimization is available on all MX Cloud Managed Security Appliances. The MX80, MX90, and MX400 include a 1 TB hard drive for local caching, and the MX600 includes a 4 TB (RAID) drive. The MX60 doesn’t include an internal hard drive, but it still benefits from WAN optimization’s compression and protocol optimization.
By using WAN optimization technology built in to the Meraki MX, administrators can dramatically reduce bandwidth costs and accelerate application performance for traffic that flows between sites of a distributed network. Slow, high latency WAN links that connect branches can be accelerated, making the WAN feel like the LAN for users at remote sites.
17 February 2012
Meraki’s resilient out-of-band cloud management (or how to combat the FUD Aerohive push out..)
We recently had a great discussion with the networking gurus from wireless field day about our cloud managed architecture, and how it works under the covers. There was a lot of interest in our out-of-band cloud management: which parts of the network require connectivity to Meraki’s cloud, how customer networks are affected during a WAN failure, and what engineering advancements went into our design. We thought we’d recap the conversation for all of our customers:
At a 10,000 foot level, communication between your network and Meraki’s cloud is for management and configuration data, so if your connection to the cloud is interrupted, your network continues to function and end users won’t notice a difference. All of the features that affect data flow continue uninterrupted. For example:
- Users stay authenticated
- New users can authenticate
- Firewall policies continue to be enforced
- Data encryption/decryption is maintained
- Layer 7 traffic shaping rules continue to be enforced
- Wireless mesh routing operates with full functionality
- Users can roam between wireless APs
- VPN tunnels (site to site, teleworker, and client VPN) continue to operate
- RF features like Dynamic Frequency Selection (DFS) continue
- Performance remains at 100%
The traffic separation looks something like this:
Meraki runs multiple datacenters around the world, and every customer network is served by at least three independent datacenters. So if a natural disaster were to take out a datacenter that served your network, we’d simply fail over to another datacenter in a different part of the world. All of the configuration data, historical logs, etc. are mirrored in near-real time (at most 60-second lag, typically much less), so in these unlikely events, everything is the way you left it.
Of course, if you lose connectivity to Meraki’s cloud (say because your ISP has an outage), you will temporarily be unable to access reports or make config changes. But if your network is anything like ours, if your WAN link goes down, you’re in fire-fighting mode, not tweaking your wireless config.
As an aside, if you’re looking for a cost-effective way to improve your WAN availability, check out our MX security appliances – they’ve got built-in WAN link balancing and failover, so you can run 2 WAN connections into your network (e.g. cable + DSL, and even 3G) and the MX will balance traffic between them. If one goes down it’ll simply move all traffic to the healthy connection. Turns out this approach can save cost too…
If you do suffer a WAN outage, there are a small hand-full of end-user facing features on our wireless products that are affected if your connection to the cloud is lost. These are all convenience features, most of which you don’t get with a traditional wireless LAN. If you like the convenience and can tollerate limited functionality in the rare event of a WAN outage, enjoy them! If you’d prefer that there is zero end-user impact if your WAN connection is interrupted, don’t enable them (and use the alternatives listed below instead.) Features that are impacted by WAN failures include:
- Native Active Directory/LDAP integration (without RADIUS)
This is a handy feature that allows users to authenticate against your AD/LDAP server without running RADIUS. This is super-easy to configure, and is a feature that isn’t available with traditional solutions like Cisco.
This feature does require connectivity to the cloud, so if you want to integrate with AD or LDAP but not require cloud connectivity, simply use a traditional RADIUS configuration:
- Meraki-hosted splash pages and captive portal
Meraki hosts snazzy, mobile-friendly, and customizable splash pages that wireless users can click through (or sign on from) before accessing your network. Since these are hosted on Meraki’s servers, they are super-easy to deploy, without any additional infrastructure in your environment. Since they’re hosted by Meraki, they require WAN connectivity to function, but you can control how new user authentication will be handled in the event that you lose WAN connectivity:
- Built-in anti-virus scan (aka NAC)
While Meraki’s LAN-isolation firewall always ensures that untrusted clients cannot spread viruses or compromise your LAN, Meraki offers an extra layer of protection by optionally scanning clients for antivirus software before allowing them onto the network. If a client isn’t protected, they are placed in a quarantine, from which they can download AV software but can’t access any other parts of the network. This feature is unique to Meraki – no other wireless systems, cloud-managed or otherwise, offer it. We find that for many customers, a full-blown, dedicated NAC system is overkill (lots of configuration complexity, 5-6 figure price tag) but Meraki’s built-in solution offers 1-click peace of mind.
If you run Meraki’s NAC and lose WAN connectivity, you can choose how the network will behave: allow clients on without a scan, or block clients until WAN connectivity is restored. Clients already on the network will be unaffected, and other access control features remain in place (firewall rules, identity-based group policies, etc.) Most of our customers didn’t run NAC at all before they deployed Meraki, so rare interruptions aren’t a major issue. But if antivirus scans during WAN outages are mission-critical, we recommend a dedicated NAC appliance (also be sure to host a downloadable antivirus package behind the firewall, since users won’t be able to go out onto the network if they fail the scan.)
- Meraki-hosted RADIUS server
Most enterprise (and even SMB) environments already have a RADIUS server – Microsoft Active Directory, LDAP, FreeRADIUS etc. The vast majority of our customers who use RADIUS authentication (i.e. 802.1x) authenticate against their own server, so that they have one central user database for email, calendaring, wireless LAN authentication, etc. However, Meraki also offers a cloud-hosted RADIUS server for lightweight use. This requires connectivity to Meraki, so if access during a WAN outage is mission-critical, those user accounts should reside on your internal directory server.
There’s a lot of detail about what is affected by loss of connectivity, but in the scheme of Meraki’s features, this is a short list. Our customers find in practice that Meraki’s out of band management significantly improves the reliability and resilience of their networks, combining the centralized management of controller-based systems with the fault-tolerance of a distributed architecture. If you’re already a customer, how has Meraki’s out-of-band architecture benefited your network? What else would you like to know about how Meraki works under the covers? Let us know!
Subscribe to:
Posts (Atom)
