Direct answer: what is the Cisco Meraki MS130-24?

The Cisco Meraki MS130-24 is a fixed-configuration, cloud-managed Layer 2 access switch in the MS130 family. It is primarily used to connect wired endpoints such as desktop computers, printers, servers, non-PoE network devices and downstream network equipment at the access layer. Organizations that value centralized Meraki Dashboard administration, remote visibility and consistent configuration across branches should consider it, especially when 24 copper Gigabit Ethernet ports are enough for the local device count.

The most important factor to confirm is power delivery. The MS130-24 is the non-PoE member of the 24-port group, so it does not power access points, VoIP phones, cameras or other powered devices over Ethernet. If those endpoints need PoE from the switch, compare the MS130-24P. If the design also requires multigigabit access ports and 10 GbE SFP+ uplinks, compare the MS130-24X.

FourTeck can help determine whether the MS130-24 has the right port count, uplink type, licensing approach, rack position and migration fit for the intended Dubai or UAE site, and can identify when a PoE or higher-bandwidth model is the safer procurement choice.

Why the MS130-24 exists in a modern Meraki access design

A switch purchase often looks straightforward when the requirement is described only as “24 Gigabit ports.” In practice, the correct model is determined by more than port count. Power delivery, uplink bandwidth, management architecture, licensing, rack constraints, thermal conditions and the expected mix of endpoints all influence whether a switch will still make sense after installation. The Cisco Meraki MS130-24 occupies a clear position: it is designed for access environments that need 24 standard 1 GbE copper ports, four 1 GbE SFP uplinks and Meraki cloud management, but do not require PoE on the access ports.

That distinction is useful in offices where desktops, printers, appliances, local servers, storage interfaces, building systems with their own power supplies and other conventional Ethernet devices dominate the port count. In these networks, buying a PoE switch can add unnecessary hardware cost and power capacity that may never be used. A non-PoE switch can therefore be the more disciplined choice when the endpoint plan is known and power is handled independently. The MS130-24 also uses a fanless design, which can be attractive in sound-sensitive communications rooms or offices where the rack is close to occupied space, although the rack still needs appropriate ventilation and environmental control.

The model is not intended to replace every 24-port access switch requirement. Its four uplinks are 1 GbE SFP rather than 10 GbE SFP+, and its access ports are standard Gigabit Ethernet rather than multigigabit. If a site expects dense Wi-Fi 6/6E access points, high-throughput aggregation, extensive PoE demand or rapidly increasing east-west traffic, the design should be reviewed against higher-bandwidth or PoE-capable alternatives. The value of the MS130-24 is strongest when its simple hardware profile matches the actual edge requirement.

Cloud management is the other defining part of the product. The Meraki Dashboard is used to claim the switch, add it to the appropriate network, configure ports and VLAN-related settings, monitor status, receive firmware updates and use remote troubleshooting tools. For organizations already operating Meraki security appliances, wireless access points or switches, the MS130-24 can fit into a familiar operational model and reduce the number of separate management systems the IT team has to maintain.

Verified MS130-24 hardware profile

Specifications above are based on Cisco Meraki’s published MS130 documentation. Optics, licenses, installation services and other dependencies should be confirmed for the final quotation.

Seven capabilities that shape the buying decision

The non-PoE decision deserves special attention

The MS130-24 should be selected only when the endpoint power plan is clear. A typical business network can contain a mixture of powered and non-powered devices: desktop computers and printers normally have local power, while access points, VoIP phones, door controllers and surveillance cameras often depend on power delivered through Ethernet. If the same access switch is expected to serve both groups, a non-PoE model can create immediate deployment friction.

External PoE injectors can solve individual cases, but using many injectors often makes power and cable management more complicated. Each injector adds another device, another power connection and another point to document. For a site with only one unusual powered endpoint, an injector may still be reasonable. For a floor with many powered devices, a PoE switch is usually a cleaner architecture. The MS130-24P exists precisely for organizations that want the same basic 24-port access density with integrated power delivery.

The MS130-24X is a different comparison. It combines PoE support with six 2.5 GbE access ports and four 10 GbE SFP+ uplinks, which can be important when the network edge must support higher-speed wireless infrastructure or larger uplink demands. That added capability should be justified by the design rather than purchased automatically. Standard office endpoints that remain at 1 GbE and do not require PoE can make the MS130-24 the more efficient option.

A practical procurement exercise is to classify every planned endpoint by three attributes: required Ethernet speed, required switch-supplied power and expected traffic profile. Once that list is complete, the right MS130 variant usually becomes much clearer.

Port planning: how to decide whether 24 ports are enough

Port count should be based on the patching plan rather than the number of people in the office. One employee can use multiple network connections, while some employees may use only Wi-Fi. Printers, meeting-room equipment, access-control interfaces, AV systems, building-management gateways, local servers, uplinks to specialist appliances and temporary test devices all consume switch ports. The safest approach is to map physical outlets and fixed devices, then reserve additional capacity for changes.

For example, a 20-person office may appear to fit easily on a 24-port switch. If 16 desks are wired, two network printers are connected, two meeting rooms have wired AV endpoints, one local server is present and one port is reserved for an appliance, 22 ports are already committed. That leaves very little flexibility for an extra workstation, a new meeting-room device or troubleshooting. In that situation, a 48-port model or a second access switch may provide a cleaner growth path depending on rack space, cabling and redundancy objectives.

The four SFP uplinks are separate from the 24 copper access interfaces, which gives the design more flexibility than a simple 24-port total might suggest. However, those uplinks are still part of the switching architecture and should be assigned intentionally. One may connect upstream to a distribution switch, another may serve a secondary fibre path, and others may remain unused initially. The actual topology should reflect redundancy goals and the capabilities of the upstream network.

Port planning is also a migration issue. When replacing an existing switch, collect the current port map before the change. Identify trunks, access VLANs, disabled interfaces, special security settings, nonstandard speed or duplex requirements and any endpoints that depend on a particular port assignment. A cloud-managed platform makes configuration easier to standardize, but it does not eliminate the need to understand what the old switch was doing.

Uplink design: four SFP ports do not automatically mean high-speed aggregation

A common purchasing error is to focus on the number of uplink cages without checking their speed. The MS130-24 provides four 1 GbE SFP interfaces. This can be entirely appropriate for a branch where most traffic is headed toward an internet connection well below 1 Gbps or where the upstream design deliberately uses Gigabit fibre. It can be restrictive in a busy campus access layer where many simultaneous users are expected to push large volumes of traffic toward servers, storage or other internal networks.

The 56 Gbps switching capacity describes the internal switching capability, but application performance still depends on where traffic flows. Twenty-four endpoints can communicate locally at the edge, yet traffic leaving the switch must traverse the configured uplinks. If most traffic is northbound, the uplink design becomes the practical bottleneck long before the number of access ports is exhausted. This is why uplink speed should be sized using expected traffic patterns rather than by assuming the internal switch capacity will be available end to end.

Fibre type also matters. Cisco Meraki lists compatible 1 GbE SFP accessories such as SX, LX10 and copper SFP options for the family. The correct optic depends on the cable plant, connector type, fibre mode, distance and the interface on the device at the far end. Existing optics should not be assumed compatible solely because they physically fit an SFP cage. Confirm supported module type and both ends of the link before ordering.

Where a branch has only one upstream connection today, the additional SFP interfaces can still be useful for future topology changes or separate infrastructure links. They should not, however, be treated as a substitute for 10 GbE uplinks when the traffic forecast genuinely requires 10 GbE. That is a model-selection issue rather than a configuration setting.

Meraki Dashboard operations and what the cloud model changes

The MS130-24 is designed around Cisco Meraki Dashboard management. During initial setup, the device is claimed into a Meraki organization, added to a Dashboard network, physically connected so it can reach the Meraki cloud, allowed to check in and update as needed, and then configured through Dashboard. If the environment requires a static IP for initial connectivity, the local status page can be used for that purpose. This workflow is materially different from buying a traditional standalone switch and administering it primarily through a local command line.

For distributed businesses, the operational advantage is consistency. Network teams can use the same interface to inspect port status, apply configuration, review events and use remote tools across multiple locations. This can simplify branch rollout because a switch can be pre-claimed and associated with the intended organization before a local installer connects it. A standardized template and documented port plan are still necessary, but the management plane does not need to be recreated separately at every site.

The cloud model also creates dependencies that should be acknowledged during design. The switch needs appropriate connectivity to communicate with the Meraki cloud, and the organization must maintain the applicable licensing arrangement. Change control should account for the platform’s firmware process and for any network policies that could prevent cloud communication. In heavily restricted environments, those dependencies should be reviewed early rather than discovered during commissioning.

Remote packet capture and event information can be valuable when troubleshooting intermittent issues, but they should be used as part of a structured diagnostic process. A remote view can show that a link is flapping or that a port is seeing unexpected traffic, yet physical issues such as damaged cabling, poor patch-panel termination or local power problems may still require on-site testing. Cloud management improves visibility; it does not eliminate the physical layer.

Organizations moving from locally managed switching should also consider operational ownership. Decide who can administer the Meraki organization, how administrator permissions are assigned, how changes are approved, who receives alerts and how configurations are documented. The technology becomes easier to manage when the governance model is equally clear.

Access-layer controls and segmentation considerations

These controls are most effective when implemented as part of an end-to-end architecture. The MS130-24 is an access switch, not a complete security system. Internet edge protection, inter-VLAN policy, secure remote access, endpoint security and identity services may involve other products or platforms. For UAE organizations reviewing both switching and network-security requirements, the Firewall Dubai by FourTeck resource can be used alongside the switching consultation to coordinate the edge and security layers.

Licensing: treat it as part of the switch architecture, not an afterthought

Meraki switching is licensed. The exact licensing mode and SKU should be confirmed for the customer’s organization and purchasing model. Cisco documents both co-termination and subscription approaches. Under classic co-termination licensing, MS licenses are model-specific and include Enterprise and Advanced tiers for supported models. Cisco also offers subscription licensing, where the MS130-24 is mapped within the MS100 Medium class. The commercial route used in a quotation should match the customer’s existing Meraki organization and licensing strategy rather than being selected in isolation.

This matters during migrations and expansions. An organization that already operates Meraki switches may have an established licensing model, renewal date and administrative process. Adding a new MS130-24 can affect how the team plans renewals and budgets future operations. A first-time Meraki customer needs to consider the license from the beginning because Dashboard operation is integral to the product experience.

Feature-tier decisions should be based on required functionality. Cisco notes that Advanced licensing is available for MS130, but not every advanced capability listed across the broader MS platform applies equally to the MS130. For example, Cisco’s licensing documentation states that Encrypted Traffic Analytics and NetFlow v10 are not supported on MS130. Buyers should therefore avoid assuming that a higher tier automatically delivers every feature associated with other switch families.

License term is also a commercial decision. A longer term can reduce renewal frequency and may align with a hardware lifecycle plan, while a shorter term may better match a temporary site, project horizon or budgeting preference. The right choice depends on procurement policy, not simply on the lowest initial purchase figure.

Before a quotation is finalized, provide the existing Meraki organization details if applicable, the desired license term, the current licensing model, the number of new switches and any planned future expansion. That information helps prevent a hardware-only quote that does not reflect the full operational requirement.

Sizing the MS130-24 for real traffic

Switch sizing should begin with traffic flows. A group of ordinary office users browsing cloud applications may place relatively modest sustained demand on a local access switch, even when every desktop has a 1 GbE link. A design supporting large local file transfers, virtualization hosts, production media workflows or dense wireless aggregation can create much heavier traffic. The same port count can therefore produce very different uplink requirements.

The MS130-24 offers 56 Gbps of switching capacity, which is appropriate for its intended access role, but the 1 GbE uplinks define how much traffic a single uplink can carry to an upstream device. Multiple uplinks can be used within supported network designs, yet aggregation and redundancy behavior must be planned correctly at both ends. Do not assume that four physical uplink ports automatically provide a simple 4 Gbps path in every topology; configuration and upstream compatibility determine what can be achieved.

Application sensitivity matters as much as raw throughput. Voice, video and interactive cloud applications can be affected by congestion, latency and packet loss even when average bandwidth appears low. Cisco Meraki lists voice and video QoS capability for the platform. A good access design classifies and prioritizes traffic only where there is a clear policy, and it also ensures that congestion is not being created by an undersized uplink or WAN circuit.

Growth should be modelled over the expected service period. If a branch currently uses 12 wired ports but is expected to double headcount, the MS130-24 may still be adequate if the final device count and uplink load remain within the design. If the same branch is also adding higher-speed wireless, cameras and IP phones, the future requirement may point toward a PoE or multigigabit model instead. Buying only for today’s endpoint list can force an early replacement.

The sizing discussion should therefore cover device count, power needs, uplink speed, typical application traffic, local server usage, expected growth and redundancy. These inputs are more useful than a generic recommendation based solely on company size.

Where the MS130-24 is a strong fit

When the MS130-24 may be the wrong choice

A balanced product page should make unsuitable scenarios clear. The MS130-24 is not the right default when a site expects the switch to power many endpoints. Access points, desk phones and cameras are common reasons to choose the MS130-24P or another PoE-capable switch instead. The decision should be based on the total powered-device count and power budget, not merely whether one PoE device exists.

It may also be underspecified when access or uplink speeds need to exceed 1 GbE. The MS130-24X adds six 2.5 GbE access ports and four 10 GbE SFP+ uplinks. Those capabilities can materially improve fit for higher-throughput wireless and aggregation designs, although they are unnecessary for many conventional office networks. If the switch will sit below a 10 GbE distribution layer and is expected to move large internal data volumes, 1 GbE SFP uplinks deserve careful scrutiny.

A 24-port switch may be too small where growth is predictable. Running at nearly full physical port occupancy from the beginning leaves little room for moves, adds and changes. A 48-port model can reduce the need for a second chassis, though it also changes rack space, power and failure-domain considerations. In other cases, two 24-port switches may be preferable because they create operational separation. There is no universal rule; the topology and growth plan decide.

The product should also not be treated as a Layer 3 core switch simply because it supports enterprise access features. It is positioned as a Layer 2 access switch. If the project requires substantial routing, aggregation, high availability or core functionality, select the architecture first and then choose a switch family that fits that role.

Finally, organizations that cannot meet cloud-management or licensing requirements should evaluate whether Meraki is the right operational model. The strongest reason to buy an MS130-24 is not just the port hardware; it is the combination of that hardware with Meraki’s management approach.

MS130-24 vs MS130-24P vs MS130-24X

The most important lesson from this comparison is that the model suffix changes the network design materially. “24” alone does not identify the right product. A quotation request should specify the exact model or, if the model is not yet decided, describe the endpoint and uplink requirements so the correct variant can be selected.

Deployment journey for a Dubai or UAE site

Migration from an existing switch

Replacing a switch is not merely a hardware swap. The existing device contains operational knowledge in its configuration: which ports are trunks, which VLAN each endpoint uses, where authentication is enforced, which ports are administratively disabled, which interfaces connect to infrastructure and which devices behave differently from the standard template. A successful migration captures that information before the old switch is removed.

Start with an inventory of the current connections. Trace uplinks and important endpoints physically where possible. Export or document the existing configuration, port descriptions and VLAN assignments. Record whether any link aggregation is used, whether the upstream equipment expects a specific native VLAN or tagged VLAN list, and whether legacy devices require unusual settings. The goal is not to copy every old configuration line mechanically; it is to preserve the intended network behavior in the Meraki design.

Then translate the design into Dashboard configuration. Standardize names and descriptions so the new switch is easier to support. If the migration introduces 802.1X or other new access controls, consider phasing those changes rather than combining every policy transformation into the hardware cutover. A migration window is easier to troubleshoot when the number of simultaneous variables is limited.

Plan rollback. Keep the old switch configuration and cable map available until validation is complete. Define the point at which the team will revert if a critical dependency fails. For a remote branch, ensure local hands are available if cables need to be moved back. Dashboard visibility can help the remote engineer, but someone may still need to touch the physical rack.

After cutover, validate more than basic ping tests. Confirm business applications, authentication, printing, local servers, voice or video services using separately powered devices, remote monitoring and any dependent appliances. A switch can appear healthy while one VLAN or specialized endpoint remains incorrectly configured.

Rack, power and environmental planning in the UAE

The MS130-24 is a 1U rack-mount switch measuring approximately 44 cm wide and 25 cm deep. That depth is compact compared with many enterprise devices, but rack fit should still be checked against patch panels, horizontal cable managers, rear power distribution units and door clearance. Fibre patch cords also need appropriate bend radius and strain relief, particularly when the rack is shallow.

The switch uses an internal fixed power supply and accepts 100–240 V AC. UPS protection is commonly appropriate for network infrastructure because a brief power interruption can disconnect an entire group of users even when endpoints have their own power. The UPS should be sized for the full communications rack, not for the switch alone, and runtime targets should reflect business continuity requirements.

Cisco specifies an operating temperature range of 0°C to 45°C for the model. Dubai and wider UAE conditions make environmental control especially important. A fanless switch produces relatively little power draw, but it still relies on the surrounding environment to remove heat. Do not interpret “fanless” as permission to place the unit in an outdoor cabinet, ceiling void or poorly ventilated room where ambient temperature can exceed the supported range.

Dust and cable congestion also affect maintainability. Keep the rack organized so technicians can identify ports without disturbing neighboring connections. Label both ends of important cables and maintain a port schedule. In multi-tenant or shared communications rooms, secure the cabinet and document who has physical access.

For organizations that want installation, structured handover or wider network support, FourTeck IT Services UAE can be referenced when the requirement extends beyond product supply into deployment and operational support.

Optics, accessories and compatibility checks

The switch’s SFP uplinks are useful only when the selected transceivers and cabling match the network. Cisco Meraki lists 1 GbE accessories including MA-SFP-1GB-SX, MA-SFP-1GB-LX10 and MA-SFP-1GB-TX among compatible options in the MS130 family documentation. The correct module depends on whether the link uses multimode fibre, single-mode fibre or copper, as well as the required distance and the interface supported by the upstream device.

Do not order optics based solely on connector appearance. Fibre patch leads can use different connector types, existing building fibre may be multimode or single-mode, and long-distance requirements can exceed the reach of a short-range optic. Existing third-party modules should be reviewed against current compatibility guidance if reuse is planned. A procurement list should state the exact optic model and quantity rather than leaving “SFP” as a generic line item.

Rack accessories also need to be considered. The MS130-24 uses integrated 1U rack mounting, but the full installation can still require cage nuts or rack hardware appropriate to the cabinet, patch leads, cable managers, labels and UPS capacity. The physical bill of materials should reflect the actual site instead of treating the switch as the only item needed for deployment.

Compatibility extends beyond hardware. The switch must integrate with the upstream VLAN design, DHCP architecture, identity services where 802.1X is used, logging or monitoring systems where SNMP/syslog integration is required and any Meraki organization conventions already in place. Those dependencies should be documented before the device arrives.

For a new site, supplying a simple network diagram with the quotation request is often the fastest way to eliminate ambiguity. Mark the internet edge, firewall, upstream switch or router, expected fibre links, access switches and key endpoint groups. The diagram does not need to be elaborate; it needs to make the intended traffic and connection paths clear.

Procurement questions that prevent expensive mistakes

Is the exact model MS130-24, not MS130-24P or MS130-24X? The model suffix determines PoE capability and uplink speed. A small naming mistake can produce a materially different device. Put the full model name on the request and purchase order.

How many ports are needed now and at the end of the planned service period? Include infrastructure and spare capacity, not just employee desktops. If the forecast is close to 24 ports, compare the cost and operational impact of a 48-port model or an additional access switch.

Do any endpoints need PoE? If yes, count them, identify their power classes or expected draw, and decide whether they belong on a separate powered switch. Do not assume injectors will be operationally convenient at scale.

What uplink media and speed are required? The MS130-24 has four 1 GbE SFP uplinks. If the distribution layer expects 10 GbE, choose a model designed for that speed instead of trying to solve the mismatch with optics.

Which licensing model and term will be used? Existing Meraki customers should align the new switch with their current organization and renewal strategy. New customers should include licensing in the project budget from the beginning.

Are optics included? Hardware quotations often separate transceivers from the switch. Specify fibre type, distance, connector environment and upstream interface so the correct modules can be priced.

Who will install and configure the switch? Product supply and deployment are different scopes. Clarify whether the project includes rack installation, patching, Dashboard configuration, VLAN migration, testing, documentation and after-hours cutover.

What support outcome is expected after handover? Some organizations have an internal network team; others need ongoing assistance. Define the expected operational model so responsibilities are clear after commissioning.

Operational lifecycle and support planning

A switch remains in service for years, so the buying decision should consider ongoing operations as well as initial installation. Document administrator ownership, licensing, network naming, alert recipients, maintenance windows and escalation contacts. The Meraki Dashboard can centralize many operational tasks, but the surrounding process determines whether those capabilities translate into faster support.

Firmware is one example. Automatic and cloud-coordinated update processes simplify lifecycle management, yet businesses should still understand their maintenance policy and application sensitivity. A branch with ordinary office traffic may accept a standard maintenance approach, while a production environment may require tighter change planning. The switch should be grouped and scheduled according to the organization’s operational risk profile.

Monitoring should focus on actionable signals. Port status, errors, unusual link changes, event logs and upstream availability can help identify developing issues. SNMP and syslog integration are available in the platform for organizations that use external monitoring or logging. Avoid creating alert noise that no one owns; every important alert should have an expected response.

Capacity should be reviewed periodically. A switch purchased with eight spare ports can become full after a few office changes. Uplink utilization can also grow as cloud applications, backups and collaboration traffic increase. Reviewing port occupancy and traffic trends can indicate when to add capacity before congestion or physical port shortage becomes an urgent problem.

Lifecycle planning also includes documentation for eventual replacement. Keep the device inventory, rack location, serial information, license details, uplink map and port plan current. When the switch is later upgraded, accurate records reduce migration risk and shorten the discovery phase.

Dubai and UAE availability guidance

For a Dubai or UAE quotation, provide the required quantity, delivery location, licensing requirement, optics list and whether installation is included. Product availability can vary with distribution stock, project quantity and license term, so a current commercial quote should be used rather than relying on a historical online price.

Multi-site projects should identify each location and the number of switches per site. This makes it easier to plan staging, labeling, Dashboard organization, shipping and installation. If branches have different endpoint profiles, do not force one switch model across every site purely for standardization. Standardization is valuable only when the hardware still fits the requirement.

UAE buyers may also need a coordinated scope covering firewall, switching, wireless, structured cabling and support. That broader design should be resolved as one network architecture because choices at the access layer affect uplinks, VLANs, power and security policy. General company and regional information is available through FourTeck, while UAE-focused procurement and infrastructure discussions can be coordinated through the local FourTeck team.

For an accurate MS130-24 proposal, the most useful starting point is a short requirement list rather than a generic request for “best price.” Quantity, port use, PoE need, uplink design, licensing term, optics, rack location and deployment scope give the quotation enough context to be technically meaningful.

Frequently asked buyer questions

A deeper buyer checklist before approving the model

First, verify the physical endpoint list. Count every required connection and decide which devices genuinely need a wired port. Do not use desk count as a substitute for the port schedule. Reserve reasonable spare capacity for growth, temporary equipment and troubleshooting.

Second, classify power demand. If the access switch must power phones, cameras or wireless devices, record quantity and expected power needs. If powered devices are concentrated in another part of the network, keeping this MS130-24 as a non-PoE switch may still be an efficient design.

Third, validate uplinks against the distribution layer. Confirm whether the upstream interface is copper or fibre, whether it is 1 GbE or 10 GbE, which transceiver type is supported, the fibre distance and whether redundancy or link aggregation is part of the topology. A mismatch here can prevent commissioning even when the access ports are correct.

Fourth, confirm the logical network design. List VLANs, trunk requirements, management addressing, DHCP locations, authentication services and any access controls that the switch must participate in. For a replacement project, compare these requirements with the old configuration and resolve inconsistencies before cutover.

Fifth, decide how the switch will be operated. Identify Dashboard administrators, licensing ownership, alert recipients, firmware/change policy and documentation standards. A technically successful installation can still become difficult to support if administrative ownership is unclear.

Sixth, review the rack. Confirm 1U availability, power outlets, UPS capacity, patch management, cabinet depth and environmental control. In the UAE, give special attention to cooling and any communications spaces that may be affected by air-conditioning shutdowns or high ambient heat.

Seventh, define the deployment scope. Product supply, pre-staging, installation, patching, configuration, migration, testing and support are separate activities. A precise scope avoids disputes over what is included and makes quotations easier to compare.

Eighth, challenge the model choice one final time. If the requirement has drifted toward PoE, multigigabit access, 10 GbE uplinks or more than 24 ports, update the bill of materials before approval. The cheapest time to correct a switch selection is before the purchase order is issued.

Decision recap

What FourTeck needs for an accurate MS130-24 quotation

For UAE company information and broader infrastructure requirements, visit FourTeck UAE. A complete requirement allows the commercial proposal to reflect the actual network rather than a generic hardware line item.

Confirm the right Meraki access switch before you order

The Cisco Meraki MS130-24 is a strong fit when your Dubai or UAE network needs 24 standard Gigabit access ports, four 1 GbE SFP uplinks, fanless 1U hardware and centralized Meraki management without PoE. If the project needs powered endpoints, multigigabit access, 10 GbE uplinks or more physical ports, those requirements should change the model selection before procurement.