User talk:Pavels Gurskis - Revision history

Pavels Gurskis at 15:35, 23 December 2014

2014-12-23T15:35:30Z

← Older revision		Revision as of 15:35, 23 December 2014
Line 38:		Line 38:
	snmp = CreateSNMPTransport($node);		snmp = CreateSNMPTransport($node);
	ifName = SNMPGetValue(snmp,".1.3.6.1.2.1.2.2.1.2." . $1);		ifName = SNMPGetValue(snmp,".1.3.6.1.2.1.2.2.1.2." . $1);
			ifType = SNMPGetValue(snmp,".1.3.6.1.2.1.2.2.1.3." . $1);
	return %((ifType==6), $1, ifName);		return %((ifType==6), $1, ifName);

Pavels Gurskis at 09:31, 7 November 2014

2014-11-07T09:31:23Z

← Older revision		Revision as of 09:31, 7 November 2014
Line 39:		Line 39:
	ifName = SNMPGetValue(snmp,".1.3.6.1.2.1.2.2.1.2." . $1);		ifName = SNMPGetValue(snmp,".1.3.6.1.2.1.2.2.1.2." . $1);
	return %((ifType==6), $1, ifName);		return %((ifType==6), $1, ifName);

			{instance-name} in "Description" filed will be replaced with 3rd parameter returned from the filter script (ifName in that case).

	== Node interface ==		== Node interface ==

Pavels Gurskis at 09:29, 7 November 2014

2014-11-07T09:29:52Z

← Older revision		Revision as of 09:29, 7 November 2014
Line 20:		Line 20:

	PPS: Not sure if works everywhere... '''write mib-data''' might be needed as well		PPS: Not sure if works everywhere... '''write mib-data''' might be needed as well

			=== SNMP Instance Discovery ===

			Let's say we want to collect status of all interfaces on a node.

			Put OID of interest in "Parameter" field on "General" tab with {instance} suffix (.1.3.6.1.2.1.2.2.1.8.{instance}).

			Put something meaningful in "Description" filed on "General" tab, use {instance-name} macro to make this human-readable ("Interface status ({instance-name})").

			Go to "Instance Discovery" tab.

			Pick "SNMP Walk - Values" as discovery method.

			Pick proper base OID as described in [[Creating SNMP table DCI]] (.1.3.6.1.2.1.2.2.1.1).

			Add instance discovery filter script:
			snmp = CreateSNMPTransport($node);
			ifName = SNMPGetValue(snmp,".1.3.6.1.2.1.2.2.1.2." . $1);
			return %((ifType==6), $1, ifName);

	== Node interface ==		== Node interface ==

Pavels Gurskis at 15:49, 19 September 2014

2014-09-19T15:49:54Z

← Older revision		Revision as of 15:49, 19 September 2014
Line 40:		Line 40:

	Note, that different set of macros available for Activation and De-activation of alarms. For example, if you use unique DCI ID for alarm generation ('''%5'''), you should use different macro to de-activate this alarm ('''%3''')		Note, that different set of macros available for Activation and De-activation of alarms. For example, if you use unique DCI ID for alarm generation ('''%5'''), you should use different macro to de-activate this alarm ('''%3''')

			== NXSL scripting ==

			==== Referring scripts from Script Library ====
			Calling scripts from Script Library:
			myVariable=Name::In::Script::Library/functionName

			==== Event Processing Policy ====
			Calling Script Library scripts from Action in Event Processing Policy:
			%[Name::In::Script::Library/functionName]
			NB: you can not pass any parameters when calling scripts from EPP Actions, however you have access to $event and $node object

Pavels Gurskis at 10:33, 17 September 2014

2014-09-17T10:33:24Z

← Older revision		Revision as of 10:33, 17 September 2014
Line 18:		Line 18:

	PS: This might require entering command in interface (rather than global) context.		PS: This might require entering command in interface (rather than global) context.

	PPS: Not sure if works everywhere... '''write mib-data''' might be needed as well		PPS: Not sure if works everywhere... '''write mib-data''' might be needed as well

Pavels Gurskis at 10:33, 17 September 2014

2014-09-17T10:33:10Z

← Older revision		Revision as of 10:33, 17 September 2014
Line 18:		Line 18:

	PS: This might require entering command in interface (rather than global) context.		PS: This might require entering command in interface (rather than global) context.
			PPS: Not sure if works everywhere... '''write mib-data''' might be needed as well

	== Node interface ==		== Node interface ==

Pavels Gurskis at 05:42, 5 June 2014

2014-06-05T05:42:50Z

← Older revision		Revision as of 05:42, 5 June 2014
Line 16:		Line 16:
	While using ChildStatus to check status of the interface, keep in mind, that depending on the device/vendor object ID of the interface might change between the [[configuration polls]].		While using ChildStatus to check status of the interface, keep in mind, that depending on the device/vendor object ID of the interface might change between the [[configuration polls]].
	For Cisco switches there's way to preserve ifIndex for the interfaces using '''snmp-server ifindex persist''' command (read more about that on [http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/28420-ifIndex-Persistence.html Interface Index (ifIndex) Persistence])		For Cisco switches there's way to preserve ifIndex for the interfaces using '''snmp-server ifindex persist''' command (read more about that on [http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/28420-ifIndex-Persistence.html Interface Index (ifIndex) Persistence])

	PS: This might require entering command in interface (rather than global) context.		PS: This might require entering command in interface (rather than global) context.

Pavels Gurskis at 05:39, 5 June 2014

2014-06-05T05:39:52Z

← Older revision		Revision as of 05:39, 5 June 2014
Line 16:		Line 16:
	While using ChildStatus to check status of the interface, keep in mind, that depending on the device/vendor object ID of the interface might change between the [[configuration polls]].		While using ChildStatus to check status of the interface, keep in mind, that depending on the device/vendor object ID of the interface might change between the [[configuration polls]].
	For Cisco switches there's way to preserve ifIndex for the interfaces using '''snmp-server ifindex persist''' command (read more about that on [http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/28420-ifIndex-Persistence.html Interface Index (ifIndex) Persistence])		For Cisco switches there's way to preserve ifIndex for the interfaces using '''snmp-server ifindex persist''' command (read more about that on [http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/28420-ifIndex-Persistence.html Interface Index (ifIndex) Persistence])
			PS: This might require entering command in interface (rather than global) context.

	== Node interface ==		== Node interface ==

Pavels Gurskis at 15:58, 6 May 2014

2014-05-06T15:58:32Z

← Older revision		Revision as of 15:58, 6 May 2014
Line 31:		Line 31:
	=== SYS_* Events ===		=== SYS_* Events ===

	Please note, that '''no SYS_* events processed''' from the node after receiving SYS_NODE_DOWN ~~even~~, until SYS_NODE_NORMAL received from that node. However, custom events processed just fine even after SYS_NODE_DOWN event.		Please note, that as part of internal event correlation, '''no SYS_* events processed''' from the node after receiving SYS_NODE_DOWN event, until SYS_NODE_NORMAL received from that node. However, custom events processed just fine even after SYS_NODE_DOWN event.

	=== Macros for Event Processing ===		=== Macros for Event Processing ===

	Note, that different set of macros available for Activation and De-activation of alarms. For example, if you use unique DCI ID for alarm generation ('''%5'''), you should use different macro to de-activate this alarm ('''%3''')		Note, that different set of macros available for Activation and De-activation of alarms. For example, if you use unique DCI ID for alarm generation ('''%5'''), you should use different macro to de-activate this alarm ('''%3''')

Pavels Gurskis at 15:56, 6 May 2014

2014-05-06T15:56:42Z

← Older revision		Revision as of 15:56, 6 May 2014
Line 29:		Line 29:
	== Event Processing Policy ==		== Event Processing Policy ==

	=== ~~Missing~~ Events ===		=== SYS_* Events ===

	Please note, that '''no events processed''' from the node after receiving SYS_NODE_DOWN even, until SYS_NODE_NORMAL received from that node.		Please note, that '''no SYS_* events processed''' from the node after receiving SYS_NODE_DOWN even, until SYS_NODE_NORMAL received from that node. However, custom events processed just fine even after SYS_NODE_DOWN event.

	=== Macros for Event Processing ===		=== Macros for Event Processing ===

	Note, that different set of macros available for Activation and De-activation of alarms. For example, if you use unique DCI ID for alarm generation ('''%5'''), you should use different macro to de-activate this alarm ('''%3''')		Note, that different set of macros available for Activation and De-activation of alarms. For example, if you use unique DCI ID for alarm generation ('''%5'''), you should use different macro to de-activate this alarm ('''%3''')