Application Scenarios
Independent Deployment
In smaller data centers such as hospitals and schools, where customers only need one or two appliances to meet the demand for network visibility, a standalone deployment is most suitable for them.
Spine-Leaf Architecture
In medium to large data centres such as financial institutions, operator’s core data centres, and cloud service providers, NPB networks can achieve highly scalable, flexible and high-performance data centre traffic monitoring solutions by adopting the Spine-Leaf architecture.
This architecture is especially suitable for large and fast-growing data center environments. Customers just need to tell us the number of ports to be captured and the size of the traffic, as well as the number of ports for the monitoring and analysis tools, and we can instantly figure out the number of Leafs that need to be captured and analysed, and select the right Spine NPB such as PX532P-T and PX564P-T to meet the customer’s possible future expansion needs.
Data Center Interconnect
NPB networking in data centre interconnection scenarios is a complex but important topic. In this scenario, NPBs not only need to handle traffic within a single data centre, but also need to manage and analyse traffic across data centres.
- Local NPB deployment
Deploy a separate NPB system in each data centre to handle local traffic and perform initial analysis.
- Centralised Management Platform
Deploy a centralised management platform to unify the management of NPBs in all data centres and provide global view and policy management.
- Cross-data center data synchronisation
Cross-data center synchronisation of critical monitoring data is achieved by using WDM equipment or dedicated carrier lines
Cross-vendor Networking
In actual deployments, it is a common situation to use equipment from multiple NPB vendors for network visibility. This may be due to historical reasons, specific functional requirements, cost considerations, or to avoid vendor lock-in.