The first question asked after the decision to go on to the Portal certification is often "How does the equipment fit in?" The access is a fear of breaking the network, and the bypasses are not stopped. The deployment model and network structure of V7 in the knowledge base, together with NE-80's bridge or route mode, can make this architecture clear.
Network Portal AuthenticationFour deployment models for Portal services
The knowledge base lists the deployment patterns of V7: sidewalking, cloud end deployment, local deployment, and distribution. The benefits of side paths deployment are low; local deployment is appropriate for single projects to put equipment and systems locally; cloud end deployment is suitable for multi-project centralization; distributed deployment is appropriate for large projects to separate control and storage.
Bridges and routeways to pre-barrel
NE-80 asNetwork Portal AuthenticationThe network is a bridge with a transparent chain of equipment in the network, single or multiple bridges (up to 8 routes), which minimizes changes to existing networks; the route mode allows the gateway to export itself and to do NAT, multiple exports, and application. If you want to add Portal without moving it, the bridge will be more stable; if you want to follow the exit path and bandwidth distribution, the router model is better.Network Portal AuthenticationThe docking is done on this level.
The V7 can be supplemented by a standard RADIUS protocol for domestic manufacturers such as China, Central H3C, sharp, Shine, Sense, Mikrotik, Behaive, Panabit, and other foreign firms such as Cisco, Juniper, Arba, Ruckus. So when selecting the Portal certified deployment structure, we will first identify what type of AC or BRAS is on the current network, then decide where Portalserver should be placed, how Radius should be connected, rather than looking for equipment.
Where should Portal put it and who do we connect with?
The knowledge base's network architecture: V7 supports any dynamic IP access, with different GNSS devices available for cloud public networks to deploy; the interface includes bras from China, Brass from Central, NatShell gateways, third party AC, routers etc. Interception occurred in the jump of authentication equipment (AC or BRAS or gateway), and Portal page was provided by V7 to verify Radius Server, as stated earlier in this link.
How to make a trade-off between the sidewalk and the string?
Give a practical judgement: if the existing network is not moving, if single points are feared to fail, priority by-pass and bridge is given to the most dangerous break; if export equipment is supposed to be changed, flow control and route selections are done, route modes are put in place. In either case, certification equipment and V7 Radius are guaranteed to stabilize their connection, or no page can be played out or any link to it is blocked. The NE-80 hardware side-by-side protection link is the back way left to the serial mode: automatic side roads when the equipment is unusual, do not kill the entire school traffic.
Distributional deployments are typical: multi-branch, multi-school areas need to centralize their control surfaces and separate storage from single point failures and data loss. Cloud end deployments are appropriate for headquarters to concentrate on the country’s doorways. Local side roads tend to be most convenient for single-point locations. The network Portal certification structure is not “best” but only the one best suited to your current network and its support capabilities. So the network Portal certified deployment, with Portal services assigned to V7, pre-net access bridges or routers, determines whether it should be bypassed or in combination.
The NE-80 hardware sideways are also emphasized: when the equipment is abnormal (power outages, dead machines) under a serial mode, the physical side of the bridge is physically accessible and traffic does not cut off the entire building network. This is a direct response to clients who fear "links out of the net." Network Portal certifies that there can be a safe exit from the string, provided it is supported by a switch on the hardware side roads. When structure is cut-off, counting this saving capability is no longer an option.
The models are designed to be a carrier: the roadside plus is most cost-effective for local deployment, and distribution and cloudy requirements for transport. Network Portal certification does not have a universal structure, so that the architecture is naturally reduced by making clear the three things: current network assets, number of branches, and operators.