Creating SNMP table DCI - Revision history

AlexKirhenshtein: Text replacement - "^" to "{{deprecated}}"

2022-09-13T16:13:18Z

Text replacement - "^" to "{{deprecated}}"

← Older revision		Revision as of 16:13, 13 September 2022
Line 1:		Line 1:
	SNMP table DCI defined by two parts - base OID and column definitions. Base OID is used to scan all possible instances (rows). Instance is considered a suffix obtained during walk on base OID. For example, for interface table (.1.3.6.1.2.1.2.2) you should select ifIndex (.1.3.6.1.2.1.2.2.1.1) as base OID. Walk will provide instances like .1, .2, .3 and so on. Then you can set base OIDs for columns in a way that after concatenation with discovered instance values they render into valid OID. For example, for interface description column from ifTable you should use .1.3.6.1.2.1.2.2.1.2 - it will be concatenated with interface index and became correct OID.		{{deprecated}}SNMP table DCI defined by two parts - base OID and column definitions. Base OID is used to scan all possible instances (rows). Instance is considered a suffix obtained during walk on base OID. For example, for interface table (.1.3.6.1.2.1.2.2) you should select ifIndex (.1.3.6.1.2.1.2.2.1.1) as base OID. Walk will provide instances like .1, .2, .3 and so on. Then you can set base OIDs for columns in a way that after concatenation with discovered instance values they render into valid OID. For example, for interface description column from ifTable you should use .1.3.6.1.2.1.2.2.1.2 - it will be concatenated with interface index and became correct OID.

	'''NB:''' base OID should return at least some values (shouldn't be empty row)		'''NB:''' base OID should return at least some values (shouldn't be empty row)

Pavels Gurskis at 19:04, 4 November 2014

2014-11-04T19:04:35Z

← Older revision		Revision as of 19:04, 4 November 2014
Line 1:		Line 1:
	SNMP table DCI defined by two parts - base OID and column definitions. Base OID is used to scan all possible instances (rows). Instance is considered a suffix obtained during walk on base OID. For example, for interface table (.1.3.6.1.2.1.2.2) you should select ifIndex (.1.3.6.1.2.1.2.2.1.1) as base OID. Walk will provide instances like .1, .2, .3 and so on. Then you can set base OIDs for columns in a way that after concatenation with discovered instance values they render into valid OID. For example, for interface description column from ifTable you should use .1.3.6.1.2.1.2.2.1.2 - it will be concatenated with interface index and became correct OID.		SNMP table DCI defined by two parts - base OID and column definitions. Base OID is used to scan all possible instances (rows). Instance is considered a suffix obtained during walk on base OID. For example, for interface table (.1.3.6.1.2.1.2.2) you should select ifIndex (.1.3.6.1.2.1.2.2.1.1) as base OID. Walk will provide instances like .1, .2, .3 and so on. Then you can set base OIDs for columns in a way that after concatenation with discovered instance values they render into valid OID. For example, for interface description column from ifTable you should use .1.3.6.1.2.1.2.2.1.2 - it will be concatenated with interface index and became correct OID.

			'''NB:''' base OID should return at least some values (shouldn't be empty row)

	Below is screenshots of working interface table configuration:		Below is screenshots of working interface table configuration:

Victor: Created page with "SNMP table DCI defined by two parts - base OID and column definitions. Base OID is used to scan all possible instances (rows). Instance is considered a suffix obtained during ..."

2014-08-14T08:17:43Z

Created page with "SNMP table DCI defined by two parts - base OID and column definitions. Base OID is used to scan all possible instances (rows). Instance is considered a suffix obtained during ..."

New page

SNMP table DCI defined by two parts - base OID and column definitions. Base OID is used to scan all possible instances (rows). Instance is considered a suffix obtained during walk on base OID. For example, for interface table (.1.3.6.1.2.1.2.2) you should select ifIndex (.1.3.6.1.2.1.2.2.1.1) as base OID. Walk will provide instances like .1, .2, .3 and so on. Then you can set base OIDs for columns in a way that after concatenation with discovered instance values they render into valid OID. For example, for interface description column from ifTable you should use .1.3.6.1.2.1.2.2.1.2 - it will be concatenated with interface index and became correct OID.

Below is screenshots of working interface table configuration:

[[File:snmp_tables_screen01.png]]

[[File:snmp_tables_screen02.png]]

[[File:snmp_tables_screen03.png]]