Why Hotel Networks Need a Purpose-Built Switching Design

A hotel is one of the most demanding enterprise LAN environments because it combines high user turnover, large numbers of mobile devices, long operating hours, multiple revenue systems and a growing estate of powered edge devices. A typical floor may have guest-room access points, corridor access points, IP phones, IP cameras, door controllers, digital signage players, smart-room gateways, IPTV endpoints, service terminals and staff handheld devices. The lobby, ballroom, restaurants, meeting rooms and pool areas add sudden bursts of wireless demand. Back-office areas introduce ERP, PMS, finance, HR and management systems, while security teams depend on CCTV and access-control networks that must remain available even when guest traffic spikes.

The access switch therefore does much more than provide Ethernet ports. It determines whether powered devices receive enough energy, whether a busy floor can forward traffic without congestion, whether multicast video floods unnecessary ports, whether voice packets keep low latency, whether guests remain isolated from staff systems and whether faults can be located quickly. In hospitality, a switch that looks adequate by port count alone can be badly undersized once PoE budget, uplink capacity, traffic segmentation and redundancy are considered together.

Huawei’s current campus portfolio gives designers several useful building blocks. For conventional one-gigabit room and edge connectivity, CloudEngine S5735-L-V2 variants are available with 8, 16, 24 or 48 copper access ports, depending on model, while selected PoE models can power connected devices. Other variants add 10GE SFP+ uplinks. For higher-density wireless floors, Huawei also offers S5735-L-V2 2.5GE access models with 24 or 48 multi-gigabit copper ports, four 10GE SFP+ uplinks and PoE+ support. For value-focused sites, the eKitEngine S310 family includes managed 24-port switching with either Gigabit SFP or 10GE SFP+ uplinks, plus a PoE model intended for powered edge deployments. Exact availability, software release support and power budgets should always be confirmed against the chosen SKU and current UAE supply channel before quotation.

Recommended Hotel LAN Architecture in the UAE

A scalable hotel network is normally divided into access, aggregation and core or collapsed-core roles. Access switches sit in floor IDFs or service closets and connect endpoint devices. Aggregation switches collect uplinks from multiple floors, wings or buildings. The core connects aggregation blocks, firewalls, Internet edges, server networks, property-management platforms and any on-premises data-centre services. In smaller properties, aggregation and core functions can be combined. In a large resort, convention hotel or multi-building campus, keeping these functions separate creates clearer fault domains and allows independent growth.

For a typical guest-floor IDF, begin with the real endpoint schedule. Count access points, phones, cameras, room gateways, IPTV devices, maintenance terminals and spare ports. Then classify each device by speed requirement and PoE class. A 48-port PoE switch may appear efficient, but a pair of 24-port switches can sometimes provide a better failure domain because a single device failure affects fewer rooms. Conversely, two 48-port switches in a stack or logically unified access block may simplify a dense floor if the room count justifies it. The correct answer depends on room topology, riser cabling, cabinet space, UPS runtime, fibre pairs and service-level expectations.

Uplinks should be engineered around realistic aggregate demand rather than the number of copper ports. A floor with several modern Wi‑Fi access points can create far more northbound traffic than a floor dominated by IP phones and room-control devices. Huawei CloudEngine access platforms with 10GE SFP+ uplinks are particularly useful when the access layer must avoid a 1GE choke point. In designs with many high-throughput access points, 2.5GE downlinks can preserve wireless capacity between the AP and the wired network while 10GE uplinks carry aggregate traffic toward aggregation.

Fibre uplinks are strongly preferred between IDFs and the main equipment room because they provide electrical isolation, support longer runs and create a clean path for higher data rates. The number of fibres, optics type and redundancy method should be decided at design stage. A hotel refurbishment is the right time to reserve extra fibre strands; opening walls again later is far more expensive than provisioning additional fibre capacity during the initial project.

Huawei Switch Families That Fit Hospitality Deployments

Because the requested solution is “Huawei Network Switch for Hotels UAE” rather than one fixed SKU, the practical approach is to choose a model family by role. FourTeck can map the final part numbers after the floor plan, device count, PoE budget and uplink requirement are known. The following examples illustrate how different Huawei switching options fit common hotel scenarios; they are not a claim that every model has identical capabilities.

Designing the Wired Foundation for Modern Hotel Wi‑Fi

Wireless performance is inseparable from switching performance. A new access point may advertise multi-gigabit wireless capacity, but the guest experience can still be constrained if the AP connects to a 1GE switch port and then shares a congested 1GE uplink with many other APs. Hotels experience this problem during breakfasts, conferences, evening streaming peaks and large group arrivals because hundreds of guests can become active at nearly the same time.

For standard guest-room coverage, 1GE access may remain appropriate where radio designs, Internet bandwidth and expected client density do not justify multi-gigabit wired access. The important point is to decide based on traffic engineering rather than assumption. Ballrooms, meeting floors, exhibition halls, lobbies and premium public spaces often justify 2.5GE-capable switching because a smaller number of access points may serve many simultaneous clients and use wider wireless channels. Huawei’s published S5735-L-V2 2.5GE access models provide 24 or 48 2.5GE copper downlinks with four 10GE SFP+ uplinks, making them relevant to this type of high-density edge design.

AP placement also affects PoE and port planning. Ceiling-mounted units frequently return to the nearest floor IDF, while outdoor or pool-area units may use longer cable routes or protected pathways. Ensure the horizontal cabling category is appropriate for the intended speed and PoE load, especially if higher-power devices will be used. The cabling system, patch panels and terminations must support the same performance objective as the switch; upgrading only the active equipment does not correct poor structured cabling.

For hotel Wi‑Fi projects, FourTeck can integrate the switch design with the broader network architecture rather than quoting access switches in isolation. The FourTeck IT services team in the UAE can align cabling, VLANs, IP plans, wireless coverage, firewall policy and operational handover so the wired and wireless layers are engineered as one system.

VLAN Segmentation: Keep Guest, Staff and Building Systems Separate

A hotel should not operate as one flat broadcast domain. Segmentation reduces security exposure, keeps policy understandable and limits the impact of faults or noisy endpoints. A practical VLAN architecture might separate guest Internet access, staff corporate devices, voice, CCTV, access control, IPTV, building-management systems, POS terminals, guest-room IoT, management interfaces and network infrastructure. The exact number depends on the property and security policy, but the principle is consistent: devices with different trust levels or traffic behavior should not be mixed simply because they terminate on the same physical switch.

Huawei CloudEngine access switches support large VLAN counts and offer mechanisms such as voice VLANs and policy-driven VLAN assignment on appropriate models. That gives the designer flexibility to map endpoints to the correct logical segment while using a common physical switching estate. Dynamic access-control methods such as MAC authentication and 802.1X are also available on relevant Huawei models, allowing security policy to be tied more closely to the user or device rather than only to the wall port.

Guest traffic normally needs a direct, tightly controlled route to Internet security services without access to hotel operational systems. Staff devices may require PMS, file services, printers and internal applications. CCTV recorders may need camera reachability but no general access to corporate endpoints. Voice systems need call-control reachability and QoS but very limited lateral access. Building systems may be old, difficult to patch and therefore especially important to isolate. These are firewall and routing decisions as much as switch decisions, which is why the LAN should be designed alongside the security gateway.

For properties refreshing both switching and perimeter security, FourTeck can coordinate the access-layer VLAN plan with firewall zones and Internet policies. Visit the Firewall Dubai solution site for adjacent network-security services. This combined approach is more reliable than building a switch configuration first and trying to force the firewall design to match later.

Security Controls at the Access Layer

Hotel access networks face unusual endpoint diversity. Some devices are managed corporate computers, some are vendor-maintained appliances, some are guest-owned mobile devices, and others are embedded systems that may remain in service for many years. Access-layer security cannot assume every endpoint supports the same authentication method. A strong design therefore combines VLAN boundaries, port policies, authentication where appropriate, DHCP and ARP protections where supported, storm control, ACLs and disciplined management-plane access.

802.1X is useful for managed staff devices where credentials or certificates can be deployed centrally. MAC-based methods can be considered for devices that cannot perform 802.1X, but MAC identity should not be mistaken for strong cryptographic authentication because MAC addresses can be copied. Static port profiles may still be suitable for tightly controlled cameras, controllers or dedicated appliances. The goal is to choose the least permissive method that remains practical for each device class.

Management interfaces deserve special treatment. Switch administration should be reachable only from designated management networks, with role-based accounts, secure protocols and centralized logging. Default credentials should never survive handover. Unused switch ports should be disabled or placed in a restricted state, and temporary event ports should follow a documented activation process. These small operational controls matter in hotels because meeting spaces and service corridors can expose network outlets to many people over time.

The switch is one layer in a broader defense. Internet filtering, application control, VPN, threat prevention and inter-VLAN security normally reside on firewalls or other security platforms. The switch enforces local segmentation and access behavior; the security gateway decides what those segments are allowed to reach. Designing both together reduces policy gaps and makes troubleshooting easier for hotel IT teams.

10GE Uplinks, Fibre and Oversubscription

A hotel access switch with 24 or 48 copper ports rarely needs an uplink equal to the mathematical sum of all access-port line rates, because most devices do not transmit at maximum rate simultaneously. Some oversubscription is therefore normal. The engineering task is to choose an oversubscription ratio that is acceptable for the actual endpoint mix. A floor dominated by phones, room controls and cameras behaves very differently from a conference floor dominated by high-capacity Wi‑Fi.

Ten-gigabit uplinks are a strong baseline for many modern hotel floor designs because they provide substantial headroom over 1GE uplinks without making the aggregation architecture unnecessarily complex. Multiple 10GE links can be bundled where supported and appropriate, increasing capacity and providing link redundancy. The aggregation layer must then have enough port density and switching capacity to receive those floor uplinks without moving the bottleneck upward.

Fibre type should follow distance, existing infrastructure and future growth. Multimode fibre can be practical for many in-building runs, while single-mode fibre is often preferred for longer campus links, outdoor inter-building connections or designs that prioritize very long upgrade life. Optics should be matched at both ends and selected from supported compatibility lists. Avoid mixing undocumented transceivers simply because the connector fits; optical interoperability includes wavelength, encoding, transmit power, receiver sensitivity and device support considerations.

Resilience may use dual uplinks to separate aggregation devices, stack-based designs, link aggregation, spanning-tree mechanisms or routed access depending on the architecture and switch family. The right approach balances availability, operational simplicity and budget. Hotels with a full-time network team may adopt more advanced routed designs, while smaller properties often benefit from simpler Layer-2 access with carefully controlled redundancy.

Operations, Monitoring and Cloud Management

Operational visibility matters because hospitality networks are expected to run continuously. When a guest reports poor connectivity, the IT team needs to determine whether the problem is the room device, access point, switch port, VLAN, uplink, DHCP service, firewall or Internet circuit. Managed switching should therefore expose interface status, errors, utilization, MAC learning, PoE consumption, device logs and event history. Telemetry-capable models can provide deeper performance data to compatible management platforms.

Huawei eKitEngine S310 series switches are positioned with both cloud and on-premise management modes, which can be useful for smaller hospitality groups that need centralized visibility without building a large management stack at every property. Huawei’s CloudEngine campus portfolio can also integrate with Huawei management and analytics platforms in larger deployments. The management model should be chosen with the hotel operator’s real support process in mind: who receives alerts, who can change VLANs, who manages firmware, and how configuration backups are handled.

Configuration standardization is particularly valuable for hotel groups. If every property uses the same VLAN numbering logic, interface descriptions, uplink naming and monitoring conventions, remote support becomes faster and less error-prone. Templates should still allow local exceptions such as ballroom ports, outdoor access points or third-party building systems. Standardization should reduce arbitrary differences, not hide necessary site-specific engineering.

For customers looking for wider infrastructure support beyond switching, the FourTeck UAE main site covers enterprise IT and network services that can be coordinated with the hotel LAN project.

Hotel Switch Sizing Methodology

A reliable quotation starts with a sizing worksheet, not a catalogue page. First count endpoints by location and function. Guest-room devices should be separated from corridor devices, public-area devices and back-office devices because they may terminate in different cabinets. Include active endpoints plus planned spare ports. A reasonable project also reserves physical ports for maintenance laptops, temporary event use, replacement equipment and future room technologies.

Second, identify link speed. Many cameras, phones and controllers are satisfied with Fast Ethernet or Gigabit connectivity, but modern access points may warrant 2.5GE. Servers, storage, firewalls and aggregation links can require 10GE or more. Do not pay for multi-gigabit access on every port unless the endpoint plan justifies it; equally, do not force high-capacity APs through a 1GE bottleneck merely to standardize on the cheapest access SKU.

Third, calculate PoE. Use maximum supported draw for each powered endpoint, not only typical draw. Add growth headroom. Decide whether all devices must stay powered during switch restart and whether UPS backup covers the full PoE load. If a 48-port floor switch has enough interfaces but not enough PoE budget for the device set, select a higher-power configuration, split the load across multiple switches or reconsider the powered-device placement.

Fourth, calculate uplinks. Sum expected traffic classes and identify peaks. Wireless and CCTV usually dominate sustained bandwidth, while voice is low-bandwidth but delay-sensitive. Guest usage is bursty. IPTV can add significant multicast traffic depending on design. Translate the traffic estimate into an uplink target with resilience margin. If a floor requires more than one uplink for capacity, decide whether the links should be aggregated or split across resilient upstream devices.

Fifth, decide redundancy. Is one switch failure acceptable for a guest floor? Can an entire floor be offline during replacement? Should access switches be paired? Does the aggregation layer need device redundancy? Do critical services need alternate physical paths? The answers vary dramatically between a 40-room boutique hotel and a 700-room resort with conference facilities.

Sixth, verify feature requirements. Confirm VLAN scale, routing protocols, authentication method, QoS, multicast handling, stacking or virtualization, management platform compatibility, telemetry, logging, SNMP needs and software lifecycle. Never assume two switches in the same family have the same uplinks, PoE budget or software capabilities. Procurement should be based on the exact SKU and software support matrix.

Finally, validate physical deployment. Check cabinet depth, rack units, front-to-back clearance, fan direction, ambient temperature, power socket type, UPS capacity, earthing, fibre trays, patch-cord bend radius and service access. Many “network” problems discovered during installation are actually rack, cabling or power problems that could have been prevented during the survey.

Voice, IP Phones and Hospitality Telephony Integration

Hotels still depend heavily on voice even as guest calling habits change. Reception, concierge, housekeeping, engineering, security, reservations and emergency communication require reliable telephony. Guest-room handsets may also integrate with voicemail, wake-up calls and property-management workflows. The switching layer should therefore provide stable PoE, consistent voice VLAN assignment and QoS treatment from phone access ports through the aggregation path.

Where a phone provides a pass-through port for a workstation, the interface may need to carry both voice and data VLANs. This must be configured intentionally so the phone joins the correct voice segment while the attached computer remains in the appropriate staff segment. Do not treat the entire port as trusted merely because a phone is present; endpoint classification and policy should remain controlled.

For new-build or refresh projects that include PBX or handset work, switching and telephony should be coordinated. PoE budget, VLAN numbering, DHCP options, call server reachability and QoS are all shared dependencies. FourTeck’s IP phone solutions can be considered alongside the Huawei switching design where a hotel needs a combined voice-and-data modernization plan.

Emergency and service phones deserve special availability planning. Identify which phones must remain operational during local power failures and ensure the switch and call-control path share the required backup runtime. A handset powered by PoE has no independent wall adapter, so the UPS supporting the switch becomes part of the voice availability design.

UAE Deployment Considerations

Hotels in Dubai, Abu Dhabi, Sharjah, Ras Al Khaimah and other UAE locations can differ greatly in building age, riser design, room density and operating model, but several regional considerations recur. Equipment rooms may be exposed to high ambient heat if cooling is undersized or fails. Outdoor links between buildings may experience intense heat and dust. Refurbishment projects can reveal undocumented legacy cabling. New hotels may have excellent fibre infrastructure but aggressive opening schedules that compress staging and testing time.

For these reasons, a UAE hotel switching project should include a physical survey, cabinet inspection and path verification before final ordering. Confirm the number and condition of fibre pairs, copper category, grounding, patch-panel labeling, available rack space and UPS capacity. Where multiple contractors are involved, define ownership for optic installation, fibre testing, patching, switch configuration, firewall policy, AP commissioning and final documentation.

Local support strategy also matters. Keep spare optics, at least one compatible access switch for larger properties, and labeled configuration backups. Record serial numbers, software versions, rack positions and uplink destinations. A hotel network often operates for years across multiple staff changes; documentation reduces dependence on individual engineers and accelerates recovery during an incident.

FourTeck can support UAE procurement and deployment planning from design through handover, with final model selection based on confirmed technical requirements rather than a generic one-size-fits-all bill of materials.

Migration from Legacy Hotel Switching

Many hotel network upgrades must happen while the property remains operational. That changes the migration strategy. A “big bang” replacement of every floor may create unacceptable service risk, while an uncontrolled floor-by-floor swap can lead to inconsistent configurations. The preferred method is a documented migration template that defines VLANs, uplinks, management addresses, PoE expectations, spanning-tree behavior, authentication policy and test steps before the first live floor is changed.

Begin with a representative pilot area. Choose a floor or service zone that includes typical devices such as access points, phones, cameras and room systems. Build the new switch configuration, validate endpoint behavior, check PoE negotiation, confirm DHCP and DNS, test guest isolation, place calls, view camera streams and verify monitoring. Once the template is stable, repeat it across remaining floors with site-specific port mappings.

Legacy uplinks can be a hidden constraint. If existing IDFs use 1GE fibre and the new design calls for 10GE, confirm whether the fibre plant and optics can support the higher speed. If not, plan fibre remediation before switch cutover. Similarly, if existing AP cabling cannot support 2.5GE reliably, replacing the switch will not produce the desired wireless performance.

Maintain rollback capability. Keep the old switch configuration and patch map until the new floor passes acceptance. Schedule high-risk changes outside peak guest periods, coordinate with front office and security teams, and define who can authorize rollback. Technical migration is only one part of hotel change management; operational communication is equally important.

What to Verify Before Ordering a Huawei Hotel Switch

The part number matters. Huawei switch families include variants with different access-port counts, uplink interfaces, PoE capabilities, power supplies and performance characteristics. A quotation should therefore identify the exact model, not only the family name. Verify whether the proposed SKU supports PoE, the total PoE budget, the number and speed of uplinks, stacking or virtualization requirements, supported optics, power input, airflow and management features.

Software requirements should also be checked. Routing protocols, authentication, telemetry and advanced management features can depend on platform and release. Where the hotel has an existing NMS, RADIUS service, syslog platform or configuration management process, confirm interoperability before purchase. If a third-party support team will operate the network, agree the management protocol and access method during design.

Licensing should be evaluated at the solution level. Basic switch forwarding may not require the same licensing model as centralized campus management or analytics. The cost comparison should include any management platform, subscriptions, optics, stacking cables, power modules, rack accessories and spare units required to deliver the intended architecture. A low switch unit price can be misleading if the final design requires many additional components that were omitted from the initial quote.

For a broader view of FourTeck’s regional infrastructure capabilities and vendor-neutral enterprise services, see FourTeck Global. The hotel switching proposal itself can remain Huawei-focused while adjacent servers, security and communications are coordinated as part of one deployment plan.

Technical Sizing Example: 180-Room Business Hotel

Consider a 180-room business hotel with six guest floors, meeting facilities, lobby, restaurants and back-office areas. Assume each guest floor has twelve Wi‑Fi access points, eight corridor or service cameras, ten IP phones outside guest rooms and several controllers or service devices. The exact room-phone design is excluded from this example because some hotels still deploy a phone in every room while others use different arrangements. The purpose of the exercise is to show the sizing logic rather than prescribe quantities.

Each floor may easily exceed thirty powered endpoints once APs, phones, cameras and controllers are counted. A 48-port PoE+ switch could provide sufficient interfaces, but the PoE budget must be checked against the maximum draw. If the APs are high-performance models and cameras include heaters, IR illuminators or motorized functions, the required power can rise significantly. Two 24-port PoE switches may offer better failure isolation and additional power headroom, while a 48-port model may be more economical and simpler to manage. The decision belongs in the detailed bill of materials.

Suppose the twelve APs are capable of substantial aggregate wireless throughput. If the property expects conference traffic to spill into guest floors, one-gigabit AP links may be acceptable for ordinary floors while the meeting level receives 2.5GE switching. This mixed architecture is often more cost-effective than deploying multi-gigabit access everywhere. Each floor can then use one or two 10GE fibre uplinks toward redundant aggregation switches, depending on the availability target.

VLANs could include guest Wi‑Fi, staff Wi‑Fi, corporate wired, voice, CCTV, access control, building systems, IPTV and switch management. Inter-VLAN communication would be limited by firewall or routing policy. CCTV traffic might be routed only to recorders and management stations. Guest traffic would be isolated from internal resources. Voice would receive QoS treatment and reach only call-control services as required.

The aggregation and Internet edge would then be sized for the sum of floor uplinks, internal application traffic, firewall throughput and Internet capacity. This example shows why the appropriate “Huawei switch for a hotel” is actually a coordinated set of switches by role rather than one repeated model across the property.

Technical Sizing Example: Resort with Villas and Multiple Buildings

A resort presents a different problem. The network may stretch across a main hotel building, villas, restaurants, spa areas, outdoor bars, staff accommodation and engineering facilities. Copper Ethernet should remain local to each building or zone, while fibre forms the backbone between aggregation points. This reduces distance limitations and electrical exposure while creating a scalable path for higher uplink speeds.

Each remote building should be treated as a defined network block with its own access switching, UPS, environmental monitoring and fibre path. If business impact justifies it, provision two diverse fibre routes back to separate aggregation points. True path diversity is physical: two fibres installed in the same conduit do not protect against a single cable cut. Where civil works prevent complete diversity, document the limitation rather than implying full redundancy.

Outdoor Wi‑Fi and cameras may require surge protection, weather-rated enclosures and careful power planning. The Huawei switch itself should remain in an appropriate indoor or protected environment unless a specifically ruggedized platform is chosen. Long copper runs to outdoor devices should be avoided where they exceed structured-cabling limits or increase exposure to electrical events.

Resort networks also benefit from clear route summarization and site naming. Building and floor identifiers should appear consistently in switch hostnames, interface descriptions, IP subnets and monitoring dashboards. During an outage, support teams should be able to translate an alarm into a physical location immediately rather than guessing which anonymous switch serves which villas.

Acceptance Testing and Handover

A hotel switching project is complete only after structured acceptance. Start with physical verification: rack mounting, cable labeling, optic types, uplink destinations, redundant paths, power feeds and UPS connections. Then confirm the logical configuration: management IP addresses, VLANs, trunks, access ports, STP or equivalent topology controls, LACP groups, routing, DHCP relay, authentication and monitoring destinations.

Test PoE by sampling every device class and reviewing actual switch power consumption. Confirm that access points boot at the intended radio capability and have not reduced function because of insufficient negotiated power. Verify phone registration, camera streams, door-controller reachability and any smart-room gateway communication. Where perpetual PoE or fast PoE features are part of the design, test the intended maintenance behavior in a controlled window.

Performance tests should include uplink throughput, latency and error counters. A clean link should not accumulate physical errors under normal load. Fibre levels should be recorded where practical. For redundant designs, fail one uplink at a time and verify convergence, service continuity and monitoring alerts. A redundant topology that has never been failover-tested is only a diagram.

Security tests should confirm guest isolation, management-network restrictions and blocked lateral access between sensitive VLANs. Validate that unused ports are disabled or restricted. Check that only approved administration protocols are enabled. Confirm NTP, syslog and monitoring so event timestamps are useful during troubleshooting.

The final handover pack should include rack elevations, switch inventory, serial numbers, management IPs, software versions, VLAN table, uplink map, optic list, configuration backups, warranty information and escalation contacts. This documentation is especially valuable in hotels because ownership of the network often spans operator IT, property engineering, managed service providers and third-party application vendors.

Frequently Asked Technical Questions

Decision Recap: What the Right Huawei Hotel Switch Design Should Deliver

Quotation Input Checklist

To size the Huawei switching bill of materials accurately, provide as much of the following information as possible. FourTeck can work from drawings, a device schedule or a site survey when final counts are not yet available.

Plan a Huawei Switching Solution for Your UAE Hotel

FourTeck can turn room counts, floor drawings and device schedules into a practical Huawei switching architecture with exact access and aggregation models, PoE calculations, fibre uplinks, VLAN design, redundancy and implementation sequencing. The result is a bill of materials that reflects how the hotel actually operates rather than a generic switch list.

For a new hotel, involve the network team before structured cabling and IDF layouts are finalized. For an operating property, provide the existing switch inventory, floor-by-floor endpoint count, uplink topology and any known service problems. This allows the proposed Huawei solution to preserve what is usable, remove bottlenecks and phase migration around occupancy and operational windows.

The final recommendation can include standard Gigabit access where it is sufficient, multi-gigabit PoE access for high-density wireless areas, 10GE optical uplinks, resilient aggregation and a security policy aligned with the hotel’s firewall and Internet edge. Exact Huawei part numbers are confirmed only after the technical inputs are validated.