Network
From i-doit documentation
This Paper will discuss some background information about the network model inside i-doit and how it can be used to document different network configurations.
The Network category is one of the more complex categories inside the i-doit Framework. The design process focused on covering the most used network configurations in a wide variety of devices with a single model. In this terms a device can be any component with a network communication port. The model is independent of topologies (for instance: Ethernet, ATM, TokenRing - yes, some of you still use it...), protocols (IP, AT, IPX - same as before ;-) or used link layer like PPP, 802.x, etc. Also VLAN configurations or virtual network connections like load balancing or fault tolerant settings can be documented in a clear and logical way.
Contents |
Introduction
The Network category consists of three parts. There are an Interface, a log. interface (log. stands for logical...) and a Port entry. An Interface can host ports and a Port can be connected with other ports. A log. Interface can be seen as a logical representation of one or more ports in one or more interfaces of the same device. That can be used to document things like management address, link aggregation or VLAN configuration. But more later. Let's begin with a more detailed view on the concept behind all that stuff.
Concept
The Interface represents a physical entity where network ports "sit on". As an analogy you can think of interfaces as containers for network ports. For the documentation of a single-port network interface controller (NIC) this seems to be overloaded, because you first have to define the interface itself and afterwards the corresponding ports. But already with a second port on the NIC this distinction makes more sense. And when you think of chassis based switching systems with lots of modules (interfaces) and different ports you will soon begin to love the way, i-doit handles this task.
A Port is, as we have seen, part of an interface. The database model allows you to document different vlaues to describe the characteristics. Also, you can attach logical information to a port. Primarily the protocl information (e.g. IP) will be used, but there are also dynamic settings for WiFi, QoS, STP and more. Furthermore the port is a connector object. That means, it is possible to construct connections between ports.
The logcial Interface is something between a port and an interface. And aside from this, it's a whole new ballgame. You can use logical interfaces to document - yeah, you have guessed - advanced logical configurations of interfaces/ports. For example:
Usage
Interface
Clicking the Network folder in the left menu tree opens a list view of currently recorded interfaces. You can use the New button located in the content area to create a new interface definition. Screenshot
The first field awaiting your input here is the Title. What is a good value for this? Well, it depends. - Mostly on the object type you are documenting.
