if you take over the network for the first time, what information you want to know?
that must be included in your network documentation. Enter the information is clear and useful, and it will be available at the time the person concerned does not exist. That is the core documentation.
You should also prioritize documentation. Specify the information that must be recorded and the information you which ones can wait later. You can not do everything at once. Although each network has its own features, many common elements that can be documented.
This is usually done in the form of a diagram showing the 'node' major network, such as routers, switches, firewalls, and servers, and how they are all connected. Typically, printers and workstation are not included.
This is all the information on the server you will need to set up or take care of them, such as the name, function, IP address, disk configuration, OS and service pack, date and place of purchase, warranty and so on.
- Division of routers and switches port
This includes details of WAN configuration, VLAN, or port to the node distribution network through a patch panel.
- Configure the service network
Network services, such as DNS, WINS, DHCP, and RAS, is essential for network operations .. You should describe the complete structure. Although you can get this information by checking the server, the intention is to save time by documenting in a format that is easily broken.
- Domain policy and profiles
You can restrict the ability of a network user with Police Editor or Group Policies. You can also make roamingprofile that can be stored on the server rather than on your local computer. This configuration, if used, must be documented.
You must document how they are maintained, including what usually happens to them and how to solve the problem.
The procedure is basically the way we run the policy, and it can be quite long. For example, the policy "network must be secure from foreign users." However, it took a great effort to implement that policy. There is a procedure for firewalls, network protocols, passwords, physical security, and so on. You may also need procedures to handle network problems reported by users and for routine maintenance of the server.
read more reviews later on label
create network documentation
No comments:
Post a Comment