Many schools, considering the wireless wifi system on-line campus, want to look at product functionality lists, price comparisons, and ask suppliers who have done similar projects. But practical experience tells me that if we do not get a clear picture of what the network infrastructure is, then the systems selected are probably out of tune with the actual environment, either rerouting them or running off the line.
Is the exit bandwidth enough? Let's count it first.
The wireless WiFi system at campus is governed by access certification and flow billing, which cannot be expanded by empty-handed export bandwidth. A 5,000-person school, assuming 2,000 equipment are simultaneously online during peak periods, allocates 2M bandwidth per person, requiring a minimum of 4G capacity for exports. If schools now have only 1 G in the bandwidth, students will complain about slowness after they have reached the billing system, but the problem is not on the side of the billing."The billing is not strong enough.", the export bandwidth assessment was skipped. It is proposed that during the selection start-up phase, the use of the export bandwidth peak and the use of free time for nearly three months be taken out, leaving real references to the bandwidth strategy design of the billing system.
Whether the existing AP and switchboard support VLAN and flow mirrors
The campus wireless WiFi system is to be fine-tuned by user, region and time, provided that network equipment is matched by sufficient control points. Does the core switchboard support 802.1Q VLAN? Does it support ACL based tactical route or flow mirrors? Is wireless AP supporting multiple SSIDs and separate VLANs per SSID? These capabilities directly determine whether the billing system can achieve a differentiated approach for accommodation, teaching, and office areas. Some schools use old switches without supporting flexible VLAN, which can only be considered as a whole with a large amount of grain and cannot be refined. The selection of these equipment capabilities is a much more useful list before they are selected than by looking directly at the product PPT.
Routers/AC co-operation capabilities for authentication
The campus WiFi system is usually certified in two mainstream programs: Portal and 802.1X. Portal certification requires export routers or wireless ACs to support the Portal protocol, redirecting uncertified users ' HTTP requests to the authentication page. 802.1X certification requires access to a switchboard or AP-supported 802.1X protocols to forward authentication requests to RADIUS servers. If the school has core equipment that does not support these agreements, either replace the equipment or the billing system can only do limited functions under the side mode. The advantage of the side-line model is that it does not need to be modified to the existing network structure, but control particle size is less than a straight mode. This choice is not for you by the supplier, and is determined by the current state of the school network.
Compatibility confirmation for RADIUS docking
Almost all campus wireless wifi systems use RADIFUS protocols for authentication and billing. But the extension properties of RADIUS vary greatly from one equipment manufacturer to another. The properties fields that are carried by H3C, sharp AC in the RADIUS report are not fully consistent, and the system needs to be tailored."Support for RADIUS"This general statement confirms that the system will be able to match the existing branding equipment of the school.——The core switch is H3C for China, the access to the APP.——That compatibility fits even more complex and requires a brand-by-brand confirmation.
The current network is so sophisticated that it's not possible to save the time.
The deployment of the campus wireless wifi system determines which traffic it can handle. Put it on the core switch, with a flow to the entire school export; put on the confluence level, and only to the corresponding area. If the school’s network is flat-tight (all AP straight line core switches), deployment is relatively simple; if there are multiple layers of assembly structures (the accommodation areas have their own convection switches and the teaching areas also have them), the system’s deployment points and the path to the next strategy must be reprogrammed. Many projects were problematic because the supplier had only seen rough pedals and had not been present to confirm the actual connection.
Flow attribution in a multi-export environment
A lot of schools have multiple operators exporting.——The wireless WiFi system on campus, in a multi-export environment, requires that user flows be attributed to the right export if they are to be accounted for separately by operators. This involves the configuration of strategic lines: when the system is certified, it sends out the user’s flow to the corresponding export. If the school’s export router does not support the strategic path based on the size of the user, the billing system cannot split the operator’s traffic.
I.P.V.6.
The university is one of the fastest-growing sites for IPv6. Many schools have already run double-store exports. If the campus wireless WiFi system only supports IPSAS4 billing and certification, there will be blind areas in a two-storey environment.——The choice of the system will determine whether the billing system supports IPv6 traffic recognition and counting, at least by achieving a single authentication entrance to an IPV4/IPv6. If the school has no IPv6 needs for the time being, it will also be necessary to spell out in the contract the support conditions and costs for subsequent IPv6 expansion so as not to be passive in the future.
Management of network equipment
The deployment of the campus wireless WiFi system will be accompanied by a combination of adjustments in core exchanges, ACs, and export routers. If the management authority for these equipment is relatively smooth, it will be smooth if it is done at the school information centre; if some of the equipment is managed by operators (e.g. operators are responsible for maintaining the export router), the cooperation will require the involvement of the operator, which will lead to an extended project cycle. Some schools have more rigid information centres and operators, so that the deployment of the billing system becomes a triad.
And the real pressure of the peaking scene.
The start-up season is the most stressful period for the wireless Wifi system on campus. On the day of the newbie report, thousands of devices were certified online simultaneously, and each request for certification was processed by a billing system. If the charge system ' s combined processing capability is configured to be daily mean, it will be stuck on the day of the start of school. When you select the model, the supplier gives actual test data for the joint release of authentication numbers, not the PPT values. And you have to confirm whether the billing system supports the queue and overtime protection of authentication requests at high speeds, avoiding full calibration breakpage due to single loads.
These assumptions are not just a selection. Each one may directly change the final deployment and system configuration. It takes two days to sort out this information, which is much less time than the project's midway re-engineering. The choice is not whether it can be more product-oriented, but whether the function of the product and the school network are actually right or not.