Is there a system to inventory and describe the structure of the network?
Are there some system for the technical description of communication networks?
Ie is conventionally the network, it in the Central node have the hardware, you need to keep a bug tracker on it, to indicate all the actions that was accomplished, the equipment, store the configs, the settings knowledge base for the repeated reproduction of the structure.
In short, there are hardware and software. Need to go somewhere else and do the same, without reference to the people. This should be a description, configs, sources for reproduction and so There is something for these purposes?
P. S. Monitoring, as such, are not interested in (Zabbix, with this excellent cope). Clean warehouse with inventory numbers, quantity of units etc. are also not the same. Detail even more. There is a kind of medium: different kind of iron which is connected to each other programmatically and physically, there are settings of this iron. The composition of iron, and settings can vary. Doing this a collective image, may it be a man, is the super specialist. You must log all changes (hardware structure, switching between iron, composition FOR, its relationship between itself and its settings). Order of probation to go, and to do the same by introducing this any other regular specialist. Those same web developers is, for example, any Vagrant with ansible, puppet. The analogy might be inaccurate, but you get the idea. Need backlog management and manual for this economy. I.e., its current state, which can easily be reproduced (to fetch iron, mentor programmes and work) and change history.
CMS on the Wiki + Zabbix + straight arm and thinking that it is all describe and configure
luther91 answered on March 23rd 20 at 19:08
You can look towards systems like Cisco Prime.
mila answered on March 23rd 20 at 19:10
GLPI + FusionInventory plugin free, pearl and page... :(
Keeps the inventory information about the consumables, vendors, information about components, there is no ticket system, better use something else.
Kodik store recommend in networks that allow you automatically through networks-ci to collect configs from glands and versioned this stuff automatically, there it's pretty easy to do. Wiki it is also possible in md(MarkDown) to write. kanban Board will help to organize the work in principle even for the ticket system works.
dahlia_Stroman answered on March 23rd 20 at 19:12
Any option from Notepad to the wiki, or specialized ServiceDesk systems.
The latter is, on the basis of 1C is quite useful.