AdminGuide:Service:SNMP/en - Cronologia

Troccoli il 06:57, 28 giu 2022

2022-06-28T06:57:18Z

← Versione meno recente		Versione delle 06:57, 28 giu 2022
Riga 1:		Riga 1:
	<languages />		<languages />
	~~<div class="mw-translate-fuzzy">~~
	Return to [[AdminGuide:Service/en\|AdminGuide:Service]]		Return to [[AdminGuide:Service/en\|AdminGuide:Service]]
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	==Description==		==Description==
	===Protocol Operation===		===Protocol Operation===
Riga 12:		Riga 9:
	The server is the monitoring system that queries, while the SNMP agent is the service used to expose the data to a client that requests it.		The server is the monitoring system that queries, while the SNMP agent is the service used to expose the data to a client that requests it.
	SNMP involves the client requesting the agent to find out the value of the OID, and the agent returns the value.		SNMP involves the client requesting the agent to find out the value of the OID, and the agent returns the value.
	~~</div>~~

	The data within the agent is organized in the form of a tree. The data indicate, for example, the version of the primary and secondary firmware, information regarding telephone services, the size of virtual memory occupied by the process, and the total number of failed authentication attempts by SIP clients.		The data within the agent is organized in the form of a tree. The data indicate, for example, the version of the primary and secondary firmware, information regarding telephone services, the size of virtual memory occupied by the process, and the total number of failed authentication attempts by SIP clients.

	~~<div class="mw-translate-fuzzy">~~
	Objects are defined as an index of a leaf under a parent: a tree structure allows you to access by specifying the path address between the subtrees to the leaf, which is the object you want to monitor.		Objects are defined as an index of a leaf under a parent: a tree structure allows you to access by specifying the path address between the subtrees to the leaf, which is the object you want to monitor.
	SNMP provides:		SNMP provides:
Riga 22:		Riga 17:
	* Agent		* Agent
	* Protocol		* Protocol
	The representation of an OIP is done as a sequence of numbers, e.g., 1.3.6.1.2.1.4.6 is the path within the tree, and each point in the path has its textual correspondence.		The representation of an OIP is done as a sequence of numbers, e.g., 1.3.6.1.2.1.4.6 is the path within the tree, and each point in the path has its textual correspondence.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	==Configuration==		==Configuration==
	[[File:Impostazioni di sistema, SNMP.png\|destra\|300px]]		[[File:Impostazioni di sistema, SNMP.png\|destra\|300px]]
	To enable NSMP support, go to "System Settings > SNMP Settings" and hit the "Enabled" checkmark.		To enable NSMP support, go to "System Settings > SNMP Settings" and hit the "Enabled" checkmark.
	~~</div>~~

	The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.		The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.

	~~<div class="mw-translate-fuzzy">~~
	===System info===		===System info===
	[[File:Ireasoning.png\|350px\|destra]]		[[File:Ireasoning.png\|350px\|destra]]
	~~</div>~~

	The following information is mandatory; if it is not entered, the SNMP service cannot start.		The following information is mandatory; if it is not entered, the SNMP service cannot start.
Riga 47:		Riga 37:
	The MIBs file allows the software monitoring to know the single leaf that only knows by number what it is.		The MIBs file allows the software monitoring to know the single leaf that only knows by number what it is.

	~~<div class="mw-translate-fuzzy">~~
	===SNMP Access Settings===		===SNMP Access Settings===
	* '''Listening address''': e.g., by default 0.0.0.0 means it listens on all interfaces of the central unit. But, if we have a PBX with multiple network interfaces (some public and some private) and you want the SNMP service to be accessible from only one of these interfaces, you can put the IP address of the interface you want the service to be active. Then you can do a bind of the service on the IP entered; this must be one of the central unit's IPs (either one of its interfaces or that of the High Reliability in the case of a cluster). In the last case, in the case of HA, explicit monitoring should be done not pointing to the resource IP but the individual IPs of the two nodes.		* '''Listening address''': e.g., by default 0.0.0.0 means it listens on all interfaces of the central unit. But, if we have a PBX with multiple network interfaces (some public and some private) and you want the SNMP service to be accessible from only one of these interfaces, you can put the IP address of the interface you want the service to be active. Then you can do a bind of the service on the IP entered; this must be one of the central unit's IPs (either one of its interfaces or that of the High Reliability in the case of a cluster). In the last case, in the case of HA, explicit monitoring should be done not pointing to the resource IP but the individual IPs of the two nodes.
Riga 53:		Riga 42:
	* '''Community v1/v2''': these are the basic versions of SNMP supported by monitoring systems, SNMP v3 support is not yet enabled. The default value that is used is "public"		* '''Community v1/v2''': these are the basic versions of SNMP supported by monitoring systems, SNMP v3 support is not yet enabled. The default value that is used is "public"
	* '''ACL'''': Access Control List, is a restriction on which IP address the client must have for querying. If an SNMP request comes in outside the ACL, it is rejected.		* '''ACL'''': Access Control List, is a restriction on which IP address the client must have for querying. If an SNMP request comes in outside the ACL, it is rejected.
	~~</div>~~

	'''CAUTION:''' ACL 0.0.0.0/0 is not recommended, it is always good to restrict access only to authorized IPs		'''CAUTION:''' ACL 0.0.0.0/0 is not recommended, it is always good to restrict access only to authorized IPs

	~~<div class="mw-translate-fuzzy">~~
	===TRAP settings===		===TRAP settings===
	Traps are a reactive-type mechanism that SNMP agents have for notifying the occurrence of events.		Traps are a reactive-type mechanism that SNMP agents have for notifying the occurrence of events.
	Kalliope has not added specifications to the system, and basic ones are present:		Kalliope has not added specifications to the system, and basic ones are present:
	~~</div>~~

	* 0: ColdStart		* 0: ColdStart

Troccoli: Creata pagina con "Directions on the configuration of TRAPs:"

2022-06-21T15:26:58Z

Creata pagina con "Directions on the configuration of TRAPs:"

← Versione meno recente		Versione delle 15:26, 21 giu 2022
Riga 1:		Riga 1:
	<languages />		<languages />
			<div class="mw-translate-fuzzy">
	Return to [[AdminGuide:Service/en\|AdminGuide:Service]]		Return to [[AdminGuide:Service/en\|AdminGuide:Service]]
			</div>

			<div class="mw-translate-fuzzy">
	==Description==		==Description==
	===Protocol Operation===		===Protocol Operation===
Riga 9:		Riga 12:
	The server is the monitoring system that queries, while the SNMP agent is the service used to expose the data to a client that requests it.		The server is the monitoring system that queries, while the SNMP agent is the service used to expose the data to a client that requests it.
	SNMP involves the client requesting the agent to find out the value of the OID, and the agent returns the value.		SNMP involves the client requesting the agent to find out the value of the OID, and the agent returns the value.
			</div>

	The data within the agent is organized in the form of a tree. The data indicate, for example, the version of the primary and secondary firmware, information regarding telephone services, the size of virtual memory occupied by the process, and the total number of failed authentication attempts by SIP clients.		The data within the agent is organized in the form of a tree. The data indicate, for example, the version of the primary and secondary firmware, information regarding telephone services, the size of virtual memory occupied by the process, and the total number of failed authentication attempts by SIP clients.

			<div class="mw-translate-fuzzy">
	Objects are defined as an index of a leaf under a parent: a tree structure allows you to access by specifying the path address between the subtrees to the leaf, which is the object you want to monitor.		Objects are defined as an index of a leaf under a parent: a tree structure allows you to access by specifying the path address between the subtrees to the leaf, which is the object you want to monitor.
	SNMP provides:		SNMP provides:
Riga 17:		Riga 22:
	* Agent		* Agent
	* Protocol		* Protocol
	The representation of an OIP is done as a sequence of numbers, e.g., 1.3.6.1.2.1.4.6 is the path within the tree, and each point in the path has its textual correspondence.		The representation of an OIP is done as a sequence of numbers, e.g., 1.3.6.1.2.1.4.6 is the path within the tree, and each point in the path has its textual correspondence.
			</div>

			<div class="mw-translate-fuzzy">
	==Configuration==		==Configuration==
	[[File:Impostazioni di sistema, SNMP.png\|destra\|300px]]		[[File:Impostazioni di sistema, SNMP.png\|destra\|300px]]
	To enable NSMP support, go to "System Settings > SNMP Settings" and hit the "Enabled" checkmark.		To enable NSMP support, go to "System Settings > SNMP Settings" and hit the "Enabled" checkmark.
			</div>

	The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.		The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.

			<div class="mw-translate-fuzzy">
	===System info===		===System info===
	[[File:Ireasoning.png\|350px\|destra]]		[[File:Ireasoning.png\|350px\|destra]]
			</div>

	The following information is mandatory; if it is not entered, the SNMP service cannot start.		The following information is mandatory; if it is not entered, the SNMP service cannot start.
Riga 37:		Riga 47:
	The MIBs file allows the software monitoring to know the single leaf that only knows by number what it is.		The MIBs file allows the software monitoring to know the single leaf that only knows by number what it is.

			<div class="mw-translate-fuzzy">
	===SNMP Access Settings===		===SNMP Access Settings===
	* '''Listening address''': e.g., by default 0.0.0.0 means it listens on all interfaces of the central unit. But, if we have a PBX with multiple network interfaces (some public and some private) and you want the SNMP service to be accessible from only one of these interfaces, you can put the IP address of the interface you want the service to be active. Then you can do a bind of the service on the IP entered; this must be one of the central unit's IPs (either one of its interfaces or that of the High Reliability in the case of a cluster). In the last case, in the case of HA, explicit monitoring should be done not pointing to the resource IP but the individual IPs of the two nodes.		* '''Listening address''': e.g., by default 0.0.0.0 means it listens on all interfaces of the central unit. But, if we have a PBX with multiple network interfaces (some public and some private) and you want the SNMP service to be accessible from only one of these interfaces, you can put the IP address of the interface you want the service to be active. Then you can do a bind of the service on the IP entered; this must be one of the central unit's IPs (either one of its interfaces or that of the High Reliability in the case of a cluster). In the last case, in the case of HA, explicit monitoring should be done not pointing to the resource IP but the individual IPs of the two nodes.
Riga 42:		Riga 53:
	* '''Community v1/v2''': these are the basic versions of SNMP supported by monitoring systems, SNMP v3 support is not yet enabled. The default value that is used is "public"		* '''Community v1/v2''': these are the basic versions of SNMP supported by monitoring systems, SNMP v3 support is not yet enabled. The default value that is used is "public"
	* '''ACL'''': Access Control List, is a restriction on which IP address the client must have for querying. If an SNMP request comes in outside the ACL, it is rejected.		* '''ACL'''': Access Control List, is a restriction on which IP address the client must have for querying. If an SNMP request comes in outside the ACL, it is rejected.
			</div>

	'''CAUTION:''' ACL 0.0.0.0/0 is not recommended, it is always good to restrict access only to authorized IPs		'''CAUTION:''' ACL 0.0.0.0/0 is not recommended, it is always good to restrict access only to authorized IPs

			<div class="mw-translate-fuzzy">
	===TRAP settings===		===TRAP settings===
	Traps are a reactive-type mechanism that SNMP agents have for notifying the occurrence of events.		Traps are a reactive-type mechanism that SNMP agents have for notifying the occurrence of events.
	Kalliope has not added specifications to the system, and basic ones are present:		Kalliope has not added specifications to the system, and basic ones are present:
			</div>

	* 0: ColdStart		* 0: ColdStart

Troccoli: Creata pagina con "On the dashboard, the execution of the SNMP service is indicated by the green dot and the "Active" status. centro
"

2022-06-21T15:22:25Z

Creata pagina con "On the dashboard, the execution of the SNMP service is indicated by the green dot and the "Active" status. 500px|centro <br>"

← Versione meno recente		Versione delle 15:22, 21 giu 2022
Riga 25:		Riga 25:
	The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.		The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.

	===System ~~settings~~===		===System info===
	[[File:Ireasoning.png\|350px\|destra]]		[[File:Ireasoning.png\|350px\|destra]]

Riga 37:		Riga 37:
	The MIBs file allows the software monitoring to know the single leaf that only knows by number what it is.		The MIBs file allows the software monitoring to know the single leaf that only knows by number what it is.

	===SNMP ~~access settings~~===		===SNMP Access Settings===
	* '''Listening address''': e.g., by default 0.0.0.0 means it listens on all interfaces of the central unit. But, if we have a PBX with multiple network interfaces (some public and some private) and you want the SNMP service to be accessible from only one of these interfaces, you can put the IP address of the interface you want the service to be active. Then you can do a bind of the service on the IP entered; this must be one of the central unit's IPs (either one of its interfaces or that of the High Reliability in the case of a cluster). In the last case, in the case of HA, explicit monitoring should be done not pointing to the resource IP but the individual IPs of the two nodes.		* '''Listening address''': e.g., by default 0.0.0.0 means it listens on all interfaces of the central unit. But, if we have a PBX with multiple network interfaces (some public and some private) and you want the SNMP service to be accessible from only one of these interfaces, you can put the IP address of the interface you want the service to be active. Then you can do a bind of the service on the IP entered; this must be one of the central unit's IPs (either one of its interfaces or that of the High Reliability in the case of a cluster). In the last case, in the case of HA, explicit monitoring should be done not pointing to the resource IP but the individual IPs of the two nodes.
	* '''Listen port''': 161 is the standard port since SNMP uses the UDP transport protocol.		* '''Listen port''': 161 is the standard port since SNMP uses the UDP transport protocol.

Troccoli il 15:21, 21 giu 2022

2022-06-21T15:21:34Z

← Versione meno recente		Versione delle 15:21, 21 giu 2022
Riga 25:		Riga 25:
	The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.		The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.

	~~<div class="mw-translate-fuzzy">~~
	===System settings===		===System settings===
	[[File:Ireasoning.png\|350px\|destra]		[[File:Ireasoning.png\|350px\|destra]]
	~~</div>~~

	The following information is mandatory; if it is not entered, the SNMP service cannot start.		The following information is mandatory; if it is not entered, the SNMP service cannot start.

Troccoli: Creata pagina con "* '''TRAP send mode''': specify whether you want to send the trap in version 1 or 2. * '''TRAP destination address''': indicate IP address of the monitoring server to send TRA..."

2022-06-21T15:20:13Z

Creata pagina con "* '''TRAP send mode''': specify whether you want to send the trap in version 1 or 2. * '''TRAP destination address''': indicate IP address of the monitoring server to send TRA..."

← Versione meno recente		Versione delle 15:20, 21 giu 2022
Riga 65:		Riga 65:
	* '''TRAP destination port''': e.g. 162 is the standard one		* '''TRAP destination port''': e.g. 162 is the standard one

	~~Sulla~~ dashboard ~~viene indicata l’esecuzione del servizio~~ SNMP ~~tramite il pallino verde e lo stato “Attivo”~~.		On the dashboard, the execution of the SNMP service is indicated by the green dot and the "Active" status.
	[[File:Monitoraggio attivo.png\|500px\|centro]]		[[File:Monitoraggio attivo.png\|500px\|centro]]
	<br>		<br>

	~~È possibile fare un’interrogazione dell’agent su~~ Kalliope ~~tramite un qualunque~~ client ~~SNMP~~ (in ~~questo caso si utilizza il già sopracitato~~ iReasoning MIB Browser).		You can do an agent query on Kalliope via any SNMP client (in this case you can use the iReasoning MIB Browser).
	~~Bisogna indicare l’indirizzo~~ IP ~~a cui collegarsi e poi impostare~~		You need to indicate the IP address to connect to and then set up
	* '''Agent NSMP Version''': ~~i valori di~~ default ~~con cui fare la richiesta~~, ~~ovvero si può scegliere se farla~~ in ~~versione~~ 1 o 2		* '''Agent NSMP Version''': the default values with which to make the request, i.e. you can choose whether to make it in version 1 or 2
	* '''Agent Read Community''': ~~qual è la~~ community ~~di lettura per poter avere accesso ai dati~~		* '''Agent Read Community''': what is the read community in order to get access to the data
	* '''Agent Port''': ~~si può indicare la porta~~ standard, 161		* '''Agent Port''': you can indicate the standard port, 161
	* '''Agent Write Community''': ~~non è abilitata la possibilità di fare scrittura tramite~~ SNMP		* '''Agent Write Community'''': the ability to do write via SNMP is not enabled

	[[File:Impostazioni client.png\|400px]]		[[File:Impostazioni client.png\|400px]]

	~~Dopo aver effettuato l'interrogazione è possibile leggere il contenuto dell’albero che è presente su~~ Kalliope.		After making the query, it is possible to read the contents of the tree that is present on Kalliope.
	~~La lettura può essere fatta oggetto per oggetto~~:		The reading can be done on an object-by-object basis:
	~~Il sottoalbero~~ '''system''' ~~presente le seguenti informazioni tra cui il~~ sysContact, il sysName ~~e il~~ sysLocation.		The subtree '''system''' present the following information including the sysContact, sysName and sysLocation.

	[[File:System.png\|800px]]		[[File:System.png\|800px]]

	~~Il pannello~~ '''interfaces''' ~~restituisce le varie interfacce presenti e per ciascuna indica lo stato operativa e i byte scambiati~~ in ~~ingresso e uscita~~, ~~questo permette ai sistemi di monitoraggio di far vedere il grafico dell’occupazione~~:		The '''interfaces''' panel returns the various interfaces present and for each indicates the operational status and bytes exchanged in and out, this allows monitoring systems to show the occupancy graph:

	[[File:Interfaces.png\|800px]]		[[File:Interfaces.png\|800px]]

	~~Esempio del~~ kpbxNode:		kpbxNode example:

	[[File:KpbxNode.png\|800px]]		[[File:KpbxNode.png\|800px]]

	'''N.B.''~~' Il contatore delle autenticazioni fallite~~ (~~evidenziato~~ in ~~blu~~) ~~è un dato importante poiché nel momento~~ in ~~cui dovesse arrivare un burst di autenticazioni fallite~~, ~~probabilmente si tratterebbe di un attacco proveniente dall’esterno~~.		'''N.B.'' The counter of failed authentications (highlighted in blue) is essential data because if a burst of failed authentications comes in, it is likely to be an attack from outside.


	KalliopePBX ~~espone delle MIB che consentono il monitoraggio del funzionamento dell’apparato tramite il protocollo di comunicazione~~ standard ~~SNMP~~. <br>		KalliopePBX implements MIBs that allow you to monitor the functioning of the equipment through the SNMP standard communication protocol. <br>

	~~Le MIB SNMP consultabili su Kalliope sono~~:		The MIBs that can be consulted are:
	*MIB-~~II standard (RFC 1213) – Questa~~ MIB ~~definisce gli oggetti per la gestione e il monitoraggio di un apparato~~ in ~~una rete~~ TCP/IP~~, in particolare su Kalliope sono implementati i seguenti sottoalberi~~: system, interfaces, at, ip, icmp, tcp, udp, transmission, snmp OID: 1.3.6.1.2.1.1/2/3/4/5/6/7/10/11		*RFC1213-MIB - This MIB defines objects for managing and monitoring an entity in a TCP/IP network. On KalliopePBX the following subtrees are implemented: system, interfaces, at, ip, icmp, tcp, udp, transmission, snmp OID: 1.3.6.1.2.1.1/2/3/4/5/6/7/10/11
	https://datatracker.ietf.org/doc/rfc1213/		https://datatracker.ietf.org/doc/rfc1213/

	*Host ~~Resource~~ MIB ~~(RFC 2790)~~ - ~~Questa~~ MIB ~~definisce un insieme di oggetti contenenti la configurazione di host~~ (~~server~~/~~computer~~) ~~collegati ad una rete~~ TCP/IP ~~indipendentemente dal sistema operativo~~, ~~dai servizi di rete e dalle applicazioni~~ software ~~installate~~. OID: 1.3.6.1.2.1.25		*RFC 2790 Host Resources MIB - This MIB defines a set of objects containing the configuration of hosts (servers/computers) connected to a TCP/IP network independently of the operating system, the network services, and the installed software. OID: 1.3.6.1.2.1.25
	https://datatracker.ietf.org/doc/rfc2790/		https://datatracker.ietf.org/doc/rfc2790/

	*UCD-SNMP-MIB ~~– Questa~~ MIB ~~definisce gli oggetti per il monitoraggio delle~~ performance ~~di un~~ host (~~ad es~~. CPU /RAM / ~~occupazione dischi~~). OID: 1.3.6.1.4.1.2021		*UCD-SNMP-MIB - This MIB defines objects for monitoring the performance of a host (e.g. CPU /RAM / disk occupation). OID: 1.3.6.1.4.1.2021
	http://www.net-snmp.org/mibs/UCD-SNMP-MIB.txt		http://www.net-snmp.org/mibs/UCD-SNMP-MIB.txt

	*Kalliope MIB~~: questa~~ MIB ~~proprietaria fornisce informazioni aggiuntive sulla configurazione e il funzionamento dei servizi implementati sul nodo~~ Kalliope ~~come ad es. numero di account configurati o registrati~~, ~~chiamate contemporanee~~, ~~numero totale di chiamate~~. OID:1.3.6.1.4.1.33732		*Kalliope MIB - This proprietary MIB provides information on the configuration and the functioning of the services implemented on the Kalliope node, such as number of configured or registered accounts, simultaneous calls, total number of calls. OID:1.3.6.1.4.1.33732

	~~Scarica i file di definizioni delle~~ MIB:		Download the MIB definitions files:

	[[Media:Definizioni MIB.zip]]		[[Media:Definizioni MIB.zip]]

Troccoli: Creata pagina con "The data within the agent is organized in the form of a tree. The data indicate, for example, the version of the primary and secondary firmware, information regarding telephon..."

2022-06-21T15:16:30Z

Creata pagina con "The data within the agent is organized in the form of a tree. The data indicate, for example, the version of the primary and secondary firmware, information regarding telephon..."

Mostra modifiche

Troccoli: Pagina sostituita con '==Configuration=='

2022-06-21T15:09:29Z

Pagina sostituita con '==Configuration=='

← Versione meno recente		Versione delle 15:09, 21 giu 2022
Riga 23:		Riga 23:
	To enable NSMP support, go to "System Settings > SNMP Settings" and hit the "Enabled" checkmark.		To enable NSMP support, go to "System Settings > SNMP Settings" and hit the "Enabled" checkmark.

	~~Per gli esempi di configurazione è stato utilizzato il client~~ iReasoning MI Browser ~~che può fare interrogazioni~~ SNMP ~~e mostra l’organizzazione dei sottoalberi~~.		The iReasoning MI Browser client was used for the configuration examples, it can make SNMP queries and shows the subtree organization.

	*Kalliope MIB - This proprietary MIB provides information on the configuration and the functioning of the services implemented on the Kalliope node, such as number of configured or registered accounts, simultaneous calls, total number of calls. OID:~~1.3.6.1.4.1~~.~~33732~~		<div class="mw-translate-fuzzy">
			===System settings===
			[[File:Ireasoning.png\|350px\|destra]
			</div>

	~~Le seguenti informazioni sono obbligatorie e se non vengono inserite~~, ~~il servizio~~ SNMP ~~non può avviarsi~~.		The following information is mandatory; if it is not entered, the SNMP service cannot start.
	* '''sysName''': ~~è un particolare~~ OID ~~sotto l’albero~~ system (~~che è il primo figlio ed è indicato come~~ 1.3.1.2.1.1), sysName ~~è il nome della macchina ed è~~ 1.3.6.1.2.1.1.5.0 (lo 0 ~~in fondo poiché è di tipo scalare~~).		* '''sysName'''': is a particular OID under the system tree (which is the first child and is denoted as 1.3.1.2.1.1), sysName is the machine name and is 1.3.6.1.2.1.5.0 (the 0 at the bottom since it is scalar type).
	* '''sysLocation''' : ~~è la~~ location ~~fisica~~, ~~funge come una sorta di inventario~~		* '''sysLocation''' : is the physical location, it acts as a kind of inventory
	* '''sysContact''': ~~indirizzo mail del referente da contattare se c’è un’anomalia~~ in ~~quel determinato nodo~~		* '''sysContact''' : email address of the contact person to contact if there is an anomaly in that particular node

	Nelle impostazioni definite c’è l’albero delle MIB 2 e le host-resources (1.3.6.1.25) che sono i due che si espongono su Kalliope.		Nelle impostazioni definite c’è l’albero delle MIB 2 e le host-resources (1.3.6.1.25) che sono i due che si espongono su Kalliope.

Troccoli il 15:04, 21 giu 2022

2022-06-21T15:04:38Z

Mostra modifiche

S.vistoli il 13:11, 28 set 2018

2018-09-28T13:11:02Z

← Versione meno recente		Versione delle 13:11, 28 set 2018
Riga 5:		Riga 5:

	The MIBs that can be consulted are:		The MIBs that can be consulted are:
	*RFC1213-MIB - This MIB ~~defins objects~~ objects for managing and monitoring an entity in a TCP/IP network. On KalliopePBX the following subtrees are implemented: system, interfaces, at, ip, icmp, tcp, udp, transmission, snmp OID: 1.3.6.1.2.1.1/2/3/4/5/6/7/10/11		*RFC1213-MIB - This MIB defines objects for managing and monitoring an entity in a TCP/IP network. On KalliopePBX the following subtrees are implemented: system, interfaces, at, ip, icmp, tcp, udp, transmission, snmp OID: 1.3.6.1.2.1.1/2/3/4/5/6/7/10/11
	https://datatracker.ietf.org/doc/rfc1213/		https://datatracker.ietf.org/doc/rfc1213/

S.vistoli: Creata pagina con "Return to AdminGuide:Service"

2018-09-26T12:20:33Z

Creata pagina con "Return to AdminGuide:Service"

← Versione meno recente		Versione delle 12:20, 26 set 2018
Riga 1:		Riga 1:
	<languages />		<languages />
	~~Torna a~~ [[AdminGuide:Service]]		Return to [[AdminGuide:Service/en\|AdminGuide:Service]]

	KalliopePBX implements MIBs that allow you to monitor the functioning of the equipment through the SNMP standard communication protocol.		KalliopePBX implements MIBs that allow you to monitor the functioning of the equipment through the SNMP standard communication protocol.