This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
extensions:teemip-network-mgmt-extended [2020/11/27 12:31] – [Network Device Virtual Interface] cnaud | extensions:teemip-network-mgmt-extended [2023/12/14 09:33] – [Network Management Extended] cnaud | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{ classicon_clusternetwork.png}} | + | {{ picto_networkmanagementextended.png}} |
====== Network Management Extended ====== | ====== Network Management Extended ====== | ||
---- dataentry summary ---- | ---- dataentry summary ---- | ||
name : Network management extended | name : Network management extended | ||
- | description_wiki | + | description_wiki |
index_hidden | index_hidden | ||
level_hidden | level_hidden | ||
- | version | + | collector_hidden |
- | release_dt | + | version |
- | TeemIp | + | release_dt |
+ | TeemIp | ||
+ | iTop : 3.1+ | ||
code : teemip-network-mgmt-extended | code : teemip-network-mgmt-extended | ||
+ | localization | ||
state : stable | state : stable | ||
diffusion_hidden | diffusion_hidden | ||
- | product_hidden | + | product_hidden |
module-lists_hidden : | module-lists_hidden : | ||
keyword_tags | keyword_tags | ||
- | dependencies_s | + | dependencies_s |
- | download_wiki | + | download_wiki |
- | git hub_wiki | + | github_wiki |
+ | php-max | ||
---- | ---- | ||
- | FIXME - wiki page under construction | + | This extension adds to TeemIp data model a few advanced classes dedicated to the network world. |
< | < | ||
Line 27: | Line 31: | ||
===== Revision History ===== | ===== Revision History ===== | ||
- | ^ Version | + | ^ Version |
- | | 1.0.0 | | + | | |
+ | | | ||
+ | | 3.1.0 | 2023-06-21 | ||
+ | | 3.0.1 | 2022-09-09 | ||
+ | | 3.0.0 | 2022-01-11 | ||
+ | | 1.1.0 | 2021-04-01 | Obsolete | ||
+ | | 1.0.0 | 2020-12-11 | ||
===== Features ===== | ===== Features ===== | ||
- | + | With TeemIp Network Management Extended: | |
- | FIXME | + | * Group interfaces together through Aggregate Links, |
+ | * Manage high availability, | ||
+ | * Add components like power supplies, management boards... to network devices, | ||
+ | * Use topological object to manage speeds, layer 2 protocols and connectors on your IP Interfaces. | ||
===== Licensing ===== | ===== Licensing ===== | ||
- | The TeemIp Network Management Extended extension is licensed under the terms of the GNU Affero General Public License Version 3 as published by the Free Software Foundation. This gives you legal permission to copy, distribute and/or modify TeemIp under certain conditions. Read the ’license.txt’ file in the TeemIp distribution. TeemIp is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY, | + | The TeemIp Network Management Extended extension is licensed under the terms of the GNU Affero General Public License Version 3 as published by the Free Software Foundation. This gives you legal permission to copy, distribute and/or modify TeemIp |
===== Limitations ===== | ===== Limitations ===== | ||
Line 43: | Line 56: | ||
There is no specific requirement with that extension. TeemIp Network Management Extended is anyway already embedded in TeemIp standalone starting with TeemIp 2.7. | There is no specific requirement with that extension. TeemIp Network Management Extended is anyway already embedded in TeemIp standalone starting with TeemIp 2.7. | ||
- | When installed on an iTop application, | + | When installed on an iTop application, |
Line 57: | Line 70: | ||
===== Aggregate Link ===== | ===== Aggregate Link ===== | ||
- | {{classicon_aggregatelink.png }} | + | {{icons8-bursts-48.png }} |
Should you need to group several physical interfaces on your network device to model trunking in the HP world or Ether Channel in the Cisco one, the Aggregate Link class will allow you to do so. | Should you need to group several physical interfaces on your network device to model trunking in the HP world or Ether Channel in the Cisco one, the Aggregate Link class will allow you to do so. | ||
Line 69: | Line 82: | ||
| Status| Possible values: Active, Inactive | | Status| Possible values: Active, Inactive | ||
| Device | Foreign key to a(n) Network Device | Yes | | | Device | Foreign key to a(n) Network Device | Yes | | ||
+ | | Device-> | ||
+ | | Device-> | ||
+ | | Peer aggregate | Foreign key to a(n) peer aggregate | No | | ||
| Description | Multiline character string | | Description | Multiline character string | ||
Line 78: | Line 94: | ||
In the Overview menu of the Configuration Management module, find the Network group and the Aggregate Link dashlet within that group. Click on it and select the item you are interested in: | In the Overview menu of the Configuration Management module, find the Network group and the Aggregate Link dashlet within that group. Click on it and select the item you are interested in: | ||
- | {{ classdisplay_aggregatelink.png }} | + | {{ classdisplay_aggregatelink3x.png }} |
+ | <note tip> | ||
+ | TeemIp will handle the relation with a peer aggregate like a 1:1 relation. When the link is set on one Aggregate Link, it is automatically set on the other side and when it is removed, it is automatically removed from the other side as well. | ||
+ | </ | ||
===== Cluster Network ===== | ===== Cluster Network ===== | ||
- | {{classicon_clusternetwork.png }} | + | {{icons8-stack.png }} |
This class allows you to group network devices together to create a high availability, | This class allows you to group network devices together to create a high availability, | ||
Line 97: | Line 116: | ||
| **Dates** ||| | | **Dates** ||| | ||
| Move to production date | Date (year-month-day) | No | | | Move to production date | Date (year-month-day) | No | | ||
+ | | Replacement date | Date (year-month-day) | No | | ||
| **Other information ** ||| | | **Other information ** ||| | ||
| Description | Multiline character string | | Description | Multiline character string | ||
Line 105: | Line 125: | ||
| Documents | All the documents linked to this configuration item | | | Documents | All the documents linked to this configuration item | | ||
| Application solutions |All the application solutions for this configuration item | | | Application solutions |All the application solutions for this configuration item | | ||
- | | Nodes | List of all network devices within the cluster | | + | | Nodes | List of all network devices within the cluster |
| IP Addresses | List of all IP addresses used by the cluster | | | IP Addresses | List of all IP addresses used by the cluster | | ||
- | | Devices | List of all the devices connected to this cluster network | | + | | Devices | List of all the devices connected to this cluster network |
+ | |||
+ | < | ||
+ | * (1) The role (Ative or Standby) that appears on the link between a node and the cluster is defined at the node side. | ||
+ | * (2) This list is actually automatically computed from the list of CIs connected to each of the nodes of the cluster. The list doesn' | ||
+ | </ | ||
=== Creating a new Cluster Network === | === Creating a new Cluster Network === | ||
Click on the “New CI” menu, then select “Cluster Network” in the form below: | Click on the “New CI” menu, then select “Cluster Network” in the form below: | ||
- | {{ classcreate_clusternetwork_selectionform.png }} | + | {{ classcreate_clusternetwork_selectionform3x.png }} |
And click “Apply” to display the Cluster Network creation form: | And click “Apply” to display the Cluster Network creation form: | ||
- | {{ classcreate_clusternetwork.png }} | + | {{ classcreate_clusternetwork3x.png }} |
When listing the nodes, redundancy parameters can be set so that impact analysis can take availability of all cluster members into consideration. | When listing the nodes, redundancy parameters can be set so that impact analysis can take availability of all cluster members into consideration. | ||
- | {{ classcreate_clusternetwork_ha.png }} | + | {{ classdisplay_clusternetwork_ha3x.png }} |
+ | |||
+ | <note warning> | ||
+ | The extension changes a bit the way impact analysis on network devices is done. If a network device belongs to a cluster, then the CIs attached to it will not be directly impacted by it any more but through the cluster. This is what highlights the picture below. | ||
+ | </ | ||
+ | |||
+ | {{ classdisplay_clusternetwork_impact3x.png }} | ||
===== Network Device Component ===== | ===== Network Device Component ===== | ||
- | {{classicon_networkdevicecomponent.png }} | + | {{icons8-slave-48.png }} |
Network devices may be made of different components: power supplies, management board... That class allow you to register them in TeemIp' | Network devices may be made of different components: power supplies, management board... That class allow you to register them in TeemIp' | ||
Line 157: | Line 188: | ||
In the Overview menu of the Configuration Management module, find the Network Device Component dashlet, click on it and select the item you are interested in: | In the Overview menu of the Configuration Management module, find the Network Device Component dashlet, click on it and select the item you are interested in: | ||
- | {{ classdisplay_networkdevicecomponent.png }} | + | {{ classdisplay_networkdevicecomponent3x.png }} |
+ | ===== Network Device ===== | ||
+ | {{icons8-switch.png | ||
+ | This class of CIs is brought by iTop CMDB. It models any type of network device: router, switch, hub, load balancer, firewall… TeemIp Network Management Extended enriches it with additional attributes and relations as shown below. | ||
+ | === Network Device additional Properties === | ||
+ | ^ Name ^ Type ^ Mandatory? | ||
+ | | **General Information** ||| | ||
+ | | Cluster network | Foreign key to a(n) Cluster Network | No | | ||
+ | | Cluster role | Possible values: Active, Standby | No | | ||
+ | | **More Information** ||| | ||
+ | | SNMP Credentials | Foreign key to a(n) SNMP Credentials | No | | ||
+ | | **Dates** ||| | ||
+ | | Replacement date | Date (year-month-day) | No | | ||
+ | |||
+ | === Tabs === | ||
+ | ^ Tab ^ Description | ||
+ | | Components | List of all network device components attached to this device | | ||
+ | | Aggregat links | List of all aggregate links attached to this device | | ||
+ | |||
+ | === Displaying a Network Device === | ||
+ | In the Overview menu of the Configuration Management module, find the Network Device dashlet, click on it and select the item you are interested in: | ||
+ | |||
+ | {{ classdisplay_networkdevice_extended.png }} | ||
+ | |||
+ | ===== Network Flow ===== | ||
+ | |||
+ | {{icons8-flow.png | ||
+ | |||
+ | Network Flows will help you to document the key flows that go through your network and to visualize them in a diagram. | ||
+ | |||
+ | === Network Flow Properties === | ||
+ | ^ Name ^ Type ^ Mandatory? | ||
+ | | **General Information** ||| | ||
+ | | Common Name | Alphanumeric string | Yes | | ||
+ | | Organization | Foreign key to a(n) Organization | Yes | | ||
+ | | Status| Possible values: Implementation, | ||
+ | | Business criticality | Possible values: Low, Medium; High | No | | ||
+ | | Move to production date | Date (year-month-day) | No | | ||
+ | | Description | Multiline character string | ||
+ | | **Flow Details** ||| | ||
+ | | Protocol | Possible values: UDP, TCP, UDP/TCP, Other | No | | ||
+ | | Source CI| Foreign key to a(n) FunctionalCI | No | | ||
+ | | Source port | Alphanumeric string | No | | ||
+ | | Destination CI | Foreign key to a(n) FunctionalCI | No | | ||
+ | | Destination port | Alphanumeric string | No | | ||
+ | | Capacity | Foreign key to a(n) Flow Capacity | No | | ||
+ | |||
+ | < | ||
+ | Name of the object is automatically computed as the concatenation of Protocol - Name of the Source CI / Source port - Name of the Destination CI / Destination port | ||
+ | </ | ||
+ | <note tip> | ||
+ | Access to this class of objects is protected by the [[extensions: | ||
+ | </ | ||
+ | |||
+ | === Displaying a Network Flow === | ||
+ | In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Network Flow dashlet, click on it and select the item you are interested in: | ||
+ | |||
+ | {{ classdisplay_networkflow.png }} | ||
+ | |||
+ | |||
+ | === Outgoing Flow === | ||
+ | Once network flows between CIs are documented, the logical path that connects them all can be visualized through the menu **Outgoing Flow…** displayed under the **Other Actions** menu of Network Flow or Functional CI (see above). | ||
+ | |||
+ | {{ network_outgoingflow1.png }} | ||
+ | {{ network_outgoingflow2.png }} | ||
+ | |||
+ | <note tip> | ||
+ | Only outgoing flows, i.e. flows from a source CI to a destination CI can be documented. Incoming flows cannot be drawn. | ||
+ | </ | ||
+ | ===== VLAN ===== | ||
+ | {{icons8-hierarchy.png | ||
+ | TeemIp Network Management Extended alters and enhances the Virtual LAN class properties but leaves the tabs unchanged. | ||
+ | |||
+ | === VLAN Properties === | ||
+ | ^ Name ^ Type ^ Mandatory? | ||
+ | | Tag | Integer | Yes | | ||
+ | | Name | Alphanumeric string | No | | ||
+ | | Organization | Foreign key to a(n) Organization | Yes | | ||
+ | | Status | Possible values: Reserved, Unused, Used | No | | ||
+ | | Type | Possible values: MAC address based, Network based, Port based, Protocol based | No | | ||
+ | | Description | Multiline character string | No | | ||
+ | |||
+ | === Tabs === | ||
+ | ^ Tab ^ Description | ||
+ | | Subnets | Subnets (v4 or v6) which are part of this VLAN | | ||
+ | | Physical network interfaces | Physical interfaces which are part of this VLAN | | ||
+ | | Logical network interfaces | Logical interfaces which are part of this VLAN | | ||
+ | | Interfaces' | ||
+ | | DHCP Options | Shared Network DHCP Option pointing to the VLAN (1) | | ||
+ | |||
+ | < | ||
+ | * (1) This tab is brought by the [[extensions: | ||
+ | </ | ||
+ | |||
+ | === Displaying a VLAN === | ||
+ | In the Overview menu of the Configuration Management module, find the Network group, click on it and select the item you are interested in the list: | ||
+ | |||
+ | {{ classdisplay_vlan3x.png }} | ||
+ | |||
+ | |||
+ | <note warning> | ||
+ | When migrating from version **1.0.0**, the extension will copy the old 'VLAN tag' attribute in the name and will preset the tag to ' | ||
+ | </ | ||
+ | |||
+ | ===== SNMP Credentials ===== | ||
+ | {{icons8-switch-48-lock.png | ||
+ | This class allows you to document the different SNMP credentials that are used within your organization. | ||
+ | |||
+ | === SNMP Credentials Properties === | ||
+ | ^ Name ^ Type ^ Mandatory? | ||
+ | | **General Information** ||| | ||
+ | | Name | Alphanumeric string | Yes | | ||
+ | | Organization | Foreign key to a(n) Organization | Yes | | ||
+ | | Description | Multiline character string | ||
+ | | **SNMP V1 / V2c** ||| | ||
+ | | Community | Alphanumeric string | (*) | | ||
+ | | **SNMP V3** ||| | ||
+ | | Security level | Possible values: None, NoAuthNoPriv, | ||
+ | | Security name | Alphanumeric string | (*) | | ||
+ | | Authentication protocol | Possible values: MD5, SHA | (*) | | ||
+ | | Authentication passphrase | Encrypted alphanumeric string | (*) | | ||
+ | | Privacy Protocol | Possible values: DES, AES | (*) | | ||
+ | | Privacy Passphrase | Encrypted alphanumeric string | (*) | | ||
+ | | Context name | Alphanumeric string | No | | ||
+ | |||
+ | (*) The mandatory nature of the attribute actually depends on the Security level value. [[extensions: | ||
+ | |||
+ | === Tabs === | ||
+ | ^ Tab ^ Description | ||
+ | | Devices | List of all the devices using these credentials | | ||
+ | |||
+ | <note tip> | ||
+ | Access to this class of objects is protected by the [[extensions: | ||
+ | </ | ||
+ | |||
+ | === Creating new SNMP Credentials === | ||
+ | From the listing view or from any create action of a SNMP Credentials badge, click on the {{2_x: | ||
+ | |||
+ | {{ classcreate_snmpcredentials.png }} | ||
+ | |||
+ | According to the selected value for the Security level, the attributes that are relevant for this level become mandatory : | ||
+ | ^ Security level ^ Attributes | ||
+ | | None | Community | Basic SNMP V1 / V2C | | ||
+ | | NoAuthNoPriv | Security name | Basic SNMP V3 | | ||
+ | | AuthNoPriv | Security name \\ Authentication protocol, Authentication passphrase | SNMP V3 with authentication only | | ||
+ | | AuthPriv | Security name \\ Authentication protocol, Authentication passphrase \\ Privacy protocol, Privacy passphrase | SNMP V3 with authentication and privacy | | ||
===== Typology Elements ===== | ===== Typology Elements ===== | ||
- | {{classicon_network_typology.png }} | + | {{icons8-new-item-48.png }} |
- | Three new typological elements are brought by the extension: | + | Four new typological elements are brought by the extension: |
^ Name ^ Description | ^ Name ^ Description | ||
- | | Interface Connector | Physical connector used on a physical interface | Name, Description, | ||
- | | Layer 2 Protocol | Layer 2 protocol used on a network interface | Name, Description, | ||
| Interface Speed | Speed available on a network interface | Name, Description, | | Interface Speed | Speed available on a network interface | Name, Description, | ||
+ | | Layer 2 Protocol | Layer 2 protocol used on a network interface | Name, Description, | ||
+ | | Interface Connector | Physical connector used on a physical interface | Name, Description, | ||
+ | | Flow Capacity | Capacity provided by a network Flow | Name, Description, | ||
The extension groups network specific typological elements in a dedicated dashlet. | The extension groups network specific typological elements in a dedicated dashlet. | ||
- | {{ overview_group_network_typology.png }} | + | {{ overview_group_network_typology3x.png }} |
These typological elements change the different interfaces as follows: | These typological elements change the different interfaces as follows: | ||
==== Logical Interface ==== | ==== Logical Interface ==== | ||
+ | * Speed attribute (string) is replaced by a foreign key toward a Interface Speed, | ||
+ | * Foreign key toward Layer 2 Protocol is added | ||
+ | |||
+ | {{ classdisplay_logicalinterface3x.png }} | ||
+ | |||
Line 186: | Line 367: | ||
* Foreign key toward Layer 2 Protocol is added | * Foreign key toward Layer 2 Protocol is added | ||
- | {{ classdisplay_networkdevicevirtualinterface.png }} | + | {{ classdisplay_networkdevicevirtualinterface3x.png }} |
==== Physical Interface ==== | ==== Physical Interface ==== | ||
+ | * Speed attribute (string) is replaced by a foreign key toward a Interface Speed, | ||
+ | * Foreign key toward Layer 2 Protocol is added | ||
+ | * Foreign key toward Connector is added | ||
+ | Note that the extension adds as well a foreign key toward an Aggregate Link. | ||
+ | {{ classdisplay_physicalinterface3x.png }} | ||
+ | ===== Network Security Manager profile ===== | ||
+ | Next to the CIs described here above, the extension brings a new User Profile: **Network Security Manager** which enables R/W access to Flow capacity, Network flow and SNMP Credentials objects. All persons in charge of network security should endorse this profile. | ||
+ | <note tip> | ||
+ | Not that the profile mus be used in conjunction with **Configuration Manager** profile. | ||
+ | </ |