Connect. Secure. Manage.
Cisco Fibre Channel Zoning
Plan and implement Cisco storage-fabric zoning with clear initiator and target mappings, change approval and checks with the storage platform owners.
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 Fibre Channel zoning controls which initiators and targets are permitted to communicate through an MDS fabric. Accurate zoning is important both for access control and for predictable operation, but it does not replace storage-side permissions. MCI Network Services plans, reviews and implements zoning changes with the host and storage owners, using verified identifiers and an approved connectivity specification.
Workload-led design
Start with application, compute and storage dependencies rather than the switch model.
Clear failure domains
Understand which links, devices and sites can fail together.
Operational clarity
Make fabrics, external routing and management responsibilities supportable.
Verify the intended host-to-storage relationship
A zoning request should identify the host, its relevant initiator ports, the target ports and the business purpose of the connection. We confirm the appropriate World Wide Port Names rather than assuming that a copied identifier belongs to the correct adapter or storage interface. Similar device names can conceal very different physical paths.
The storage team confirms which resources will be presented and how access is controlled beyond the fabric. A permitted Fibre Channel connection does not establish that the right volumes are visible or that an unintended host cannot access them. Those checks remain part of joint acceptance rather than being inferred from successful login state.
Standards & partnerships
Confidence in the team behind your network.
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
Review the existing fabric policy
Before adding a zone, we examine the active and configured zoning information and the naming convention already in use. We identify the relevant fabric or VSAN and check whether the requested endpoints are already represented. This reduces the risk of creating duplicate or inconsistent objects during routine growth.
The selected zoning method must be supported for the platform and endpoint design. Conventional zoning, supported Smart Zoning arrangements and other features have different operational implications. We follow the applicable vendor guidance and customer standard rather than presenting one membership pattern as universally correct for every storage system.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Keep the change narrow and reviewable
The proposed configuration includes only the relationships needed for the approved request. We avoid broad zones that make future access difficult to reason about. Naming should identify purpose and ownership without exposing unnecessary customer information in records shared outside the operating team.
Changes are independently reviewable against the connectivity specification. The review checks identifiers, membership, fabric placement and the intended active set. It also considers whether an apparently unused zone is genuinely obsolete or still supports a recovery path that is not normally active.
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 ↗Coordinate both independent fabrics
A resilient host commonly depends on more than one fabric or path. We plan the required changes on each side and confirm that the identifiers belong to the appropriate connections. Copying one fabric’s membership without checking physical mapping can leave the host with less independence than the diagram suggests.
The sequence is agreed with the storage team so that existing access is protected. Where a change touches an active relationship, we establish the expected effect and a rollback method before activation. Redundancy should be verified, not assumed merely because a host has two adapters or the switches have different names.
Validate after activation
We inspect the resulting fabric state and ask the host and storage owners to verify the expected paths and presented resources. The checks distinguish visibility from usable application access. A host may discover a target while still lacking the correct storage configuration or multipath behaviour.
We also confirm that the change has not introduced unwanted connectivity. Negative checks are selected according to the agreed scope and performed safely. The acceptance record links the final configuration to the authorised request, making it possible to explain later why a particular relationship exists.
Remove obsolete access carefully
Decommissioning requires as much care as addition. We establish that the host or storage relationship is no longer required, including backup and recovery uses, before removing it. Stale aliases and zones can then be cleaned up without silently disrupting a service that only runs during a failure or periodic operation.
The process retains enough change history to investigate future questions. If a connection has been removed as part of a migration, the records should identify the replacement path and the point at which rollback is no longer intended. This is more useful than leaving old access indefinitely because its purpose is uncertain.
Keep zoning part of a controlled service
MCI can support an individual change, review a large inherited configuration or help establish a repeatable zoning standard. The deliverable includes the approved mapping, applied changes, verification results and any unresolved dependency owned by another team. Credentials and complete storage configurations are handled through an agreed secure channel.
Our Cisco storage networking services remain focused on the fabric and its integration. We coordinate with storage administrators rather than replacing their responsibility for resource presentation and data protection. That separation makes the work safer and gives the customer clear ownership from the initial request through acceptance.
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.