The network infrastructure of stock hotels has often been in operation for many years, and the introduction of hotel network audit gateways based on old exchanges, loose circuits, and missing files is a much more difficult task than new projects. Understanding these typical problems and developing response programmes ahead of time are the basis for successful implementation of the renovation project.
Could not close temporary folder: %s
One of the most common problems with old hotels is that there are no or no web-based topsaw files. The renovations have accumulated equipment from a variety of different manufacturers, and the connection to it is a mess. No one can tell what is connected to an exchange.
Core switch is too old to support port mirrors.
If the audit gateway is planned to be deployed by side mirrors, the core switch must support the port mirror function. Many older switches over 10 years either do not support the mirror at all or are supported with limited mirror speed (e.g. only mirrors can be used to reach 100 Mbps ports, whereas actual traffic is already in a gestation). In this case, several directions are taken: one is to replace the core switch (remodelling is most costly but most thorough); two is to deploy the audit gateway in a cascade (without relying on mirrors but introducing single fault lines); three are to meet and not core layers (some traffic may be missing and some integrity needs assessment). The choice of specific path depends on the hotel ' s budget and the requirements for network reliability.
The cabinet space is inadequate to accommodate new equipment
Many old hotels have weak electrical cabinets full and even overloaded.——Not only is the equipment full, but there are a lot of old cable piles in it, both occupying space and having security concerns. If we want to increase audit gateway equipment, first we need to clean up the cabinets, remove the used equipment and cables, and free space. This process requires extra care, since the cable markings in the old cabinets are often not clear, and the wrong wire can lead to accidental network break-ups.
Network address planning is a mess
The Internet site planning of the old hotel often has been extended several times on a temporary basis, and the same / 24 section may be mixed with various types of equipment such as residential devices, employee computers, surveillance cameras, door-block controls. This confusing segment planning poses great difficulties for auditing because the audit system cannot directly judge the type of user from an IP address. Ideally, the network should be standardized in synchronised.——The re-allocation audit strategy is detailed only for the user segments, but the network regularization is a major project that involves high risks if one-time changes are too wide. The actual projects can be phased in and VLAN will be independent before other devices are configured to follow.
Incompatibility of the certification system with the audit system
In this case, there are several options: replacing the certification system (with high costs of connecting to a single step), developing intermediates for format conversion (with medium technical difficulty and no low maintenance cost); and abandoning in-depth interfaces, allowing audit gateways to run independently and supplementing identification linkage records by other means (e.g. manual export of authentication logs to import auditing systems). The third option is a compromise formula, with audit records being compromised but sometimes the only viable option during the transition to old systems.
Operational impact control during construction
Hotels are a year-round operation, and network work must be carried out without compromising normal operations. Renovating is usually only scheduled at dawn, with limited windows per operation. This is a practical constraint on the progress of construction, which requires that the project plan plan complete all of the changes by completing one successive operation window ahead of schedule. Special attention needs to be paid to the need to confirm before each construction is completed that the network has been restored to normality and cannot leave a faulty network before dawn, otherwise there will be many complaints about the failure of a large number of customers to access the Internet during breakfast hours.
Altered acceptance and inspection standards
Once the old network has been remodeled, acceptance criteria should be stricter than new projects because the various temporary treatments introduced during the conversion process may leave a risk. The acceptance should cover whether all export flows are covered by audit, whether identity-related records are working properly, whether log capacity and retention cycles meet requirements, and whether equipment performance is stable at simulated peak loads."Looks normal."The remodeling project requires, inter alia, a complete receipt and inspection record that records the status comparison before and after the conversion as a reference base for subsequent transport.
The difficulty of retrofitting the old network is that there are too many unknowns and problems outside the plan will emerge.