Team connectivity
Define the connections required by staff and equipment, then select Cisco capabilities suited to the existing network while checking ports, capacity and licence requirements for each exact product reference under consideration.
Cisco
Cisco networks for SMEs in French-speaking Switzerland: choose equipment, segment access, manage licences and prepare network changes with Sunitech.
Suitable tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais

A Cisco network can connect computers, Wi-Fi access points, servers and multiple locations. An SME's requirements extend beyond socket counts: calls, remote applications and backups place different demands on the network. We start by identifying necessary traffic, areas to separate and equipment whose failure would stop operations. This avoids replacing hardware without addressing the organisation of the network.
Define the connections required by staff and equipment, then select Cisco capabilities suited to the existing network while checking ports, capacity and licence requirements for each exact product reference under consideration.
Plan separation between users, visitors, servers and specialist equipment on the Cisco network, documenting permitted traffic and testing the applications that must continue to work across the relevant network boundaries.
Review the management mode available for the Cisco equipment involved, the permissions required and associated dependencies, without assuming that every model uses the same console, subscription arrangement or operational procedures.
Decide who may view or change Cisco configurations, how their accounts will be protected and where the information needed to take over network management will remain available after a team change.
Prepare Cisco changes with a configuration backup, an agreed intervention window and acceptance criteria, so that required communications can be checked and a rollback can be organised if the change fails.
Collect Cisco product references, installed versions and available contracts, then plan updates and replacement around network dependencies, business continuity needs and the time required to prepare a controlled transition between configurations.
From initial scoping to ongoing support, the agreed work and each party’s responsibilities are defined with you before implementation.
Identify sites, equipment, traffic and dependencies before defining priorities.
Prepare changes, test configurations and organise commissioning.
Assess usage, coverage areas and mobility needs. The required measurements are agreed during scoping.
Separate uses, restrict traffic and define access rules with the people responsible.
Agree monitoring checks, updates and incident-handling arrangements.
Document the network and plan its next developments with your teams.
We start with your teams’ needs, business applications and organisational constraints.

Share client files between colleagues, with appropriate access and documents that are easy to find.

Keep tills and connections working, including across multiple shops.

Protect patient records and maintain the tools needed for consultations.

Connect the office and the workshop, secure equipment and prepare for recovery after an incident.
Tools alone are not enough. Ongoing management, access and documentation need to remain clear over time.
Defined areas and needs, with coverage to be checked on site.
Traffic rules and separate access according to usage.
Inventoried equipment and checks suited to the required service.
Updates and changes prepared with the people involved.
Useful documentation for planning replacements and new requirements.
Uses, limitations and frequently asked questions: the points to clarify when preparing your project.
Local or cloud management options depend on the product family, model and licences. Certain Catalyst devices can be managed through Meraki in documented configurations; this does not automatically apply to an entire fleet. We check model references, software versions and existing entitlements. An IT audit helps prepare the decision, especially when administrator accounts and contracts are spread across several contacts.
The project covers addressing, separate networks, traffic rules and power requirements for connected devices. Configurations are backed up before intervention. We agree a change window and rollback method, then test the affected printers, applications, telephony and remote access. Cybersecurity completes this preparation by reviewing administrator access, updates and permitted traffic between network areas.
A central dashboard does not remove cabling, service provider or power constraints. Features and the consequences of licence expiry must be checked for the chosen offering. We identify who receives alerts and who authorises an intervention. Managed IT can cover that follow-up within a defined scope, without presenting an available catalogue feature as a service already included in your agreement.
Can we keep equipment from other manufacturers? Yes, where interfaces and required functions are compatible. Administration may remain distributed across several tools.
Does all management need to move to the cloud? No. The decision depends on your constraints, hardware compatibility and licensing. Changing the management mode should be prepared as a migration, with a reference configuration and tests before wider rollout.
The Cloud Management with IOS XE documentation specifies relevant models and prerequisites. The Meraki licensing guide describes the different subscription models. Compare these references with your inventory before selecting an architecture.
Review of your needs, comparison of options and clearly explained priorities.
Preparation, configuration, testing and coordination with the relevant providers.
Agreed support scope, documentation, licences and next steps.
A project? A question?
An initial conversation to understand your situation and decide on the next steps together.
Contact us