Connect. Secure. Manage.
Cisco IGMP Snooping
Configure Cisco IGMP snooping and querier behaviour to control multicast on switched networks without interrupting legitimate receivers.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Cisco IGMP snooping helps switches direct IPv4 multicast traffic to ports with interested receivers rather than treating every stream as traffic for the whole VLAN. Correct operation depends on membership reports, multicast-router ports and querier behaviour. MCI Network Services configures and troubleshoots IGMP snooping in Cisco access and distribution networks, particularly where receivers lose traffic intermittently or multicast is consuming bandwidth on ports that do not need it.
Cisco-focused engineering
Design around the platform, traffic and failure behaviour you actually operate.
Change with evidence
Use pre-checks, acceptance criteria and a documented route back.
Operational handover
Keep the configuration, diagrams and responsibilities understandable after delivery.
Understand the receiver segment
We start with the devices connected to the VLAN and the way they join multicast groups. A receiver may be a dedicated appliance, a virtual machine, a host running several applications or a downstream switch carrying many endpoints. Those arrangements affect how membership changes should be interpreted at an individual switch port.
The review includes group addresses, IGMP versions, the expected source and the application lifecycle. A device may join only when a service starts or after a user selects a stream. Testing a quiet network without exercising that behaviour can produce an incomplete picture of the required forwarding state.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Establish who sends membership queries
Receivers need an appropriate querying arrangement so membership remains known over time. Depending on the topology, this may be provided by a multicast router or a supported snooping querier. We identify the intended querier and check its relationship with the rest of the multicast design.
A missing or inconsistent querier can make a service appear to work initially and then fail as state ages. Conversely, adding querier settings without understanding existing devices can introduce unnecessary complexity. We review the live election and query behaviour rather than assume that a configured address is the device actually performing the role.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Distinguish snooping from multicast routing
IGMP snooping controls forwarding within a switched domain. It does not, by itself, create multicast delivery between separate subnets. Where sources and receivers sit across routed boundaries, the network also needs a supported routing design and appropriate source reachability.
We inspect the interface facing the multicast router, the receiver ports and any switch-to-switch trunks. The goal is to confirm that membership information and data follow the intended paths. For routed services, our Cisco PIM multicast design work addresses the additional control-plane dependencies rather than trying to solve every problem with access-switch settings.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Use fast-leave behaviour carefully
A port may carry more than one receiver even when only one physical cable is attached. A downstream switch, access point or virtualisation host can aggregate several interested systems. Removing the port from a group immediately after one leave message can therefore interrupt other legitimate receivers if the chosen feature assumes a single host.
We verify the platform’s supported leave behaviour and the actual attachment model before enabling it. Faster removal is not automatically better than waiting for confirmation that no receivers remain. The right setting balances timely pruning with continuity for the devices sharing the connection.
Review unknown traffic and static exceptions
Different platforms and configurations handle unknown multicast and router-port discovery differently. We establish what should happen before membership is learned and what observations indicate a problem. A change intended to reduce flooding should not silently prevent a receiver from discovering or joining its service.
Static memberships or forwarding exceptions can be justified for a specific requirement, but they need ownership and documentation. They should not become the default response to an unexplained dynamic membership failure. Otherwise, the network may continue forwarding unnecessary streams while the underlying querier or host issue remains unresolved.
Test membership changes and topology events
Acceptance testing follows a receiver joining, receiving and leaving a group. Where several receivers share a port or downstream segment, we verify that one receiver leaving does not remove traffic from the others. We also inspect forwarding after an approved uplink or topology change.
The evidence combines switch membership state with packet observations at useful points. We check whether reports are sent by the receiver, reach the relevant switch and produce the expected forwarding entry. This helps distinguish an application that never joins from a network that fails to honour a valid membership request.
Keep the settings understandable
The handover records VLANs, querier arrangements, router-facing ports, exceptional static settings and receiver assumptions. Monitoring should help identify unexpected multicast load or changes to important membership behaviour, while recognising that not every legitimate receiver remains joined continuously.
MCI can review a Cisco network with intermittent multicast reception, unexplained flooding or problems after a switch replacement. We provide a defined investigation and configuration scope, with tests tied to the actual receiver population rather than a generic recommendation to enable or disable snooping across the entire estate.
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.