Your sites, connected to where your systems run.
FajrFiber engineers the connection from your offices toward your data center or cloud environment, and operates the FajrFiber-managed portions of that path, with responsibility defined at every handoff.
Cloud and data-center capability comes through FajrCloud, within one ecosystem.
Cloud & Data Center Connectivity
The path is now part of the service.
Business systems increasingly run in data centers and cloud environments rather than in the office. Every user who depends on them now depends on the path in between.
That path often crosses more than one provider, and responsibility at each handoff is easy to leave undefined.
Who operates each part of the path.
Each part of the path has a named operator, and every handoff is defined.
- Your sites
Your network, beyond the FajrFiber handoff, unless a managed service is agreed.
- Access
Optical access, assessed per location.
- FajrFiber network
Enterprise routing across multiple uplinks.
- Handoff
Where responsibility passes to the environment provider.
- Environment
FajrCloud, your data center, or the cloud services you use.
Engineering detail
Cisco and Juniper routing and switching platforms.
Choose the path by what runs on it.
(a) Internet path to cloud services
- Suited to
- Cloud services and applications reached over the internet.
- What you decide
- The committed rate and how the site connects.
- Who operates it
- FajrFiber, up to the defined handoff.
One committed rate. No split between local and international traffic.
Static public IPv4 included; customer BGP where the design requires it.
(b) Direct connectivity to a data center
- Suited to
- Systems hosted in a data-center facility.
- What you decide
- Which facility, and the handoff at that facility.
- Who operates it
- FajrFiber, up to the defined handoff.
Direct fiber connectivity to multiple data-center environments in Dhaka and Chattogram, with high-capacity interconnection engineered for enterprise and cloud workloads.
FajrFiber operates the FajrFiber-managed transport to the facility handoff. The facility, and everything beyond its handoff, remains with the facility operator.
Point-to-point connectivity between sites, where available.
(c) Site-to-site interconnection
- Suited to
- Offices and branches that work as one network with your environment.
- What you decide
- Which sites connect, and the protection the topology needs.
- Who operates it
- FajrFiber, up to the defined handoff.
Secure interconnection between sites.
Engineering detail
Cryptographic transport protection is engineered according to the service topology, including MACsec with AES-256-GCM for suitable Layer-2 transport and IPsec with IKEv2/AES-256-GCM for routed WAN and Internet-based connectivity.
Where FajrCloud fits.
FajrFiber engineers the connection; FajrCloud provides cloud and data-center capability. Each is responsible for its own part, and the handoff between them is defined.
Addressing and routing toward your environment.
- Addressing
- Static public IPv4 included; customer BGP where the design requires it.
- IPv6
- Native IPv6 and customer BGP support are available for enterprise deployments, including customer-owned ASN and IPv6 prefix announcement.
- Routing
- Routing is governed by explicit engineering policy with defined preferred and secondary upstream behaviour.
Operated after it is delivered.
A human-operated Network Operations Center monitors the FajrFiber-managed portions of the path 24/7/365, and technical support is staffed around the clock.
Resilience is designed per site.
Enterprise connections are engineered with dual fiber paths as standard, with diverse PoP termination used to reduce single-path dependency.
What an engineer needs to start.
- Your sites.
- Where your systems run: a data center, FajrCloud or a cloud service.
- Which applications depend on the path.
- Your current addressing.
- Your existing providers.
- How much downtime the business can absorb.