All MIBs › SIEMENS-PN-MIB › hicomSQLsessionIdGenerator
hicomSQLsessionIdGenerator
Module: SIEMENS-PN-MIB
OID (symbolic): SIEMENS-PN-MIB::hicomSQLsessionIdGenerator
OID (numeric): 1.3.6.1.4.1.231.7.2.1.8.1
Node type: OBJECT-TYPE
Type: TestAndIncr
Access: read-write
Description: hicomSQLsessionIdGenerator is used to create and assign unique SQL session identifiers to concurrent manager applications. hicomSQLsessionIdGenerator shall be used in accordance to the semantics of TestAndIncr specified in Textual Conventions (RFC1903).
A GET on hicomSQLsessionIdGenerator returns a new SQL session ID. This value shall be confirmed/claimed by a manager application by setting the hicomSQLsessionIdGenerator variable to the value which was returned by the previous GET. If the SET on hicomSQLsessionIdGenerator succeeds (error status 'noError' is returned), the SQL session ID value is uniquely assigned to the requesting manager application. Further, the agent did create a corresponding entry in the hicomSQLsessionTable having hicomSQLsessionId set to the SQL session ID value used with the SET.
If the SET on hicomSQLsessionIdGenerator fails (error status 'inconsistenValue' is returned) the same value was read by another manager and this one just claimed his SQL session ID by performing successfully a SET. In this case no entry is created in the hicomSQLsessionTable. To get and claim a unique SQL session ID, the manager application has to redo the GET and SET operation cycle on hicomSQLsessionIdGenerator.
NOTE: using this and other hicomSQL objects is reserved for Siemens internal use ONLY. No documentation on this interface is available for customers.
What is hicomSQLsessionIdGenerator?
TestAndIncr object used to hand out unique SQL session IDs to concurrent managers: a GET returns a new ID and the manager claims it by SETting that value back, which creates its session row. If the SET fails with inconsistentValue another manager claimed it first, so repeat GET and SET. The source notes the SQL objects are for Siemens internal use only with no customer documentation.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.231.7.2.1.8.1 snmpwalk -v2c -c public <target> SIEMENS-PN-MIB::hicomSQLsessionIdGenerator
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.231.7.2.1.8.1.1 snmpget -v2c -c public <target> SIEMENS-PN-MIB::hicomSQLsessionIdGenerator.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.231.7.2.1.8.1.1 s <value>
Start monitoring Siemens Hicom 300 PBX, Siemens UNITY telephony system (topology/alarm/system-change status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SIEMENS-PN-MIB::hicomSQLsessionIdGenerator OID value, configure state conditions and alerts, and monitor any Siemens Hicom 300 PBX, Siemens UNITY telephony system (topology/alarm/system-change status) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.231 | sni | AN-MIB |
| 1.3.6.1.4.1.231.7 | siemensUnits | AN-MIB |
| 1.3.6.1.4.1.231.7.2 | pn | H150E-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.231.7.2.1 | hicomMib | SIEMENS-PN-MIB |
| 1.3.6.1.4.1.231.7.2.1.8 | hicomSQL | SIEMENS-PN-MIB |
| 1.3.6.1.4.1.231.7.2.1.8.1 | hicomSQLsessionIdGenerator | SIEMENS-PN-MIB |