Skip to Content
Last modified by Frank Fock on 2024/05/25 21:04
From version 7.1
edited by Frank Fock
on 2024/05/25 21:04
Change comment: There is no comment for this version
To version 6.2
edited by Admin
on 2024/02/07 22:10
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -How-to configure your own quotation for the ObjectNameAndDecodedIndex4RoundTrip OIDFormat?
1 +How to configure your own quotation for the ObjectNameAndDecodedIndex4RoundTrip OIDFormat?
Parent
... ... @@ -1,1 +1,1 @@
1 -SNMP4J.SNMP4J-SMI FAQ.WebHome
1 +SNMP4J.Home.SNMP4J-SMI FAQ.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.FRANKFOCK
1 +XWiki.Admin
Content
... ... @@ -1,13 +1,14 @@
1 1  The OIDFormat allows to parse and format OIDs with sub-index values as string values (instead of th well-known dotted numeric format {{code language="none"}}1.3.6{{/code}}) like for example {{code language="none"}}vacmAccessContextMatch."v3group"."".3.'noAuthNoPriv(1)'{{/code}}. With that format variable length sub-index values are enclosed with double quotes and fixed length or implied length sub-index values are enclosed with single quotes.
2 2  
3 -{{note title="**Warning**"}}
3 +{{note title="Warning"}}
4 4  If you use the same quotation character for fixed and variable length, you will not be able to parse OIDs properly if the MIB information for the corresponding table is not available/loaded!
5 5  {{/note}}
6 6  
7 -{{error title="**Always use a consistent escape character!**"}}
7 +{{error title="Always use a consistent escape character!"}}
8 8  The escaping charcater and the escape character used in the quote escape sequences for fixed and variable length sub-indexes must be identical! Otherwise, the format will not work.
9 9  {{/error}}
10 10  
11 +
11 11  
12 12  === Using Single Quotes Only ===
13 13