Many schools decide to go to Portal certification, often starting with a complaint. One night, the dormitory block is out of reach, and the transport teacher is woken by telephone, and the switch logs are turned half a day, and it is not clear whether the authentication server is hanging or the bandwidth is full, and only the entire building’s network can be re-opened. The next day, leaders ask questions about which level the problem is.
Let's get this through to the current access.
Schools think they have little access, but not the same. One of the most confusing cases we've ever seen is that Internet certification alone has three parallels: early broadband dialling accounts are still in use, then unwired feeders are installed and a layer of web-based authentication has been added. Students often mix equipment with which to use, and they don’t know themselves when to print it. Before building it, at least we should list this information: what way teachers and students are connected to the Internet, where they come from, how their passwords change, how many historical accounts remain on the old system. This step seems to be trivial, but it directly determines how much data migration and consolidation will take place when the new system is online.
The list of equipment is harder to get than it thought.
The second pit is a lack of assets. Portal's handles who gets access to what equipment, so you have to know how many points of access, how many switches, and whether there are any management segments. In practical projects, it is often the case that a floor-level access switch type is too old to support standard authentication protocols, either it has to be replaced or it can only swim outside the certification system. There are network devices like door closures, surveillance, a cartoon terminal, which are all marked in advance as to where they are attached to an independent access strategy. We usually recommend schools first to produce a list of access points with a location, even if not accurate, that is more impressive than the one in their minds.
Authentication traffic and peaks are measured
The third is the capacity of the system, which can be easily decided by a head-capping. Some people estimate and send it directly by multiplying the number of students in school by two, and the results are completely inadequate because one student has a cell phone, a tablet, a notebook, an intelligent soundbox and a game machine in his dormitory, and each person has more than two online devices. It is more likely to pick a week to take a physical test, see how much the late peak request for certification is going to reach, and how high the flash point at which the start-up report will go.
The account's source must be figured out.
There is also a particularly easy point to ignore: where the teacher-student accounts come from. Some schools have teaching and learning systems that are made by two manufacturers, with their fields not being matched, and new certification systems either imported manually or connected. The most difficult thing we've ever experienced is that fresh data arrive before school starts, leaving many students without access to the Internet during the first two weeks, and complaints all over the network centre. So it is necessary to find out when the numbers will be received, in what format, who will ensure that these three things are correctly defined, so it is better to write them into the cooperative responsibility of the construction side rather than wait for the line to get back online.
History legacy system to separate
Many schools are not white paper, and most of them have used a pilot system with a broker's grant, or a manufacturer's trial system, where historical accounts and data are still in use, who is using them, and the bottom-up. We've seen old systems go down but the account numbers are still secret, and the new ones are running out of money and retroactive. So we need to figure out what we want to move, which to stop, and which to recognize.
The output of the status quo should be a list.
After all, the pre-construction mapping is not about reporting, but about making a thorough picture of all the decisions that follow. We are used to it as a three-fold deposit: an access mode with account number status table, a list of access devices with location, and a measured flow and peak log. These three sets together, and the selection of the back, capacity planning, and implementation schedule are justified. Without anything, project presumably gets stuck at a node, while when it's stuck, nobody remembers that the bottoming was never done, and it just makes the system look bad.
Don't think of touching as a factory job.
Finally, the school takes the lead. The manufacturers are willing to do your research, but they often do their research with an optimistic orientation and easily draw you on a programme that they are good at. A true neutral mapping should be first-hand data from the school network centre, where the manufacturer is responsible for giving it only on the basis of those data. This order should not be reversed; otherwise you think you are in the process of selecting it, which is actually chosen.