[Query] mib of type TransportAddress

Hi,

 

I have a scalar MIB defined for some ServerAddress which is R/RW & is of
type TransportAddress which intern is again OctetString as defined by
RFC-3419.

 

What is the value Manager is expects the agent to produce?  [The default
value defined for this mib is 000000000000].  

 

When the Manager requests a snmp get on this mib 

The output display is:

 

 # snmpget -v2c -c motrw 127.0.0.1 clSnmpBootstrapServerAddress.0

CNEOMI-LITE-BOOTSTRAP-MIB::clSnmpBootstrapServerAddress.0 = STRING:
"000000000000"

 

But what value should Manager pass when he has to do a snmp set on this?

For example:

# snmpset -v2c  -c motrw 127.0.0.1 clSnmpBootstrapServerAddress.0 =
100874cf00a2

CNEOMI-LITE-BOOTSTRAP-MIB::clSnmpBootstrapServerAddress.0 = Hex-STRING:
00 00 00 00 00 00 00 00 00 00 00 00

 

 

The equivalent of the above hex is 10.8.127.192:162

 

Now from my example, the input manager is trying to write on that mib is
it proper?

 

Please help me to know what is the valid Values that are possible on a
MIB of type TransportAddress, I don't have much awareness on this
data-type.

 

Also let me know which api & which variable will get me this value which
I can take & assign to this mib after doing the required validations.

 

Any help will be Highly appreciated.

 

Below is from RFC3419 which speak about the TransportAddress

 

 

>From RFC 3419 :

 

TransportAddress ::= TEXTUAL-CONVENTION

    STATUS      current

    DESCRIPTION

        "Denotes a generic transport address.

 

         A TransportAddress value is always interpreted within the

         context of a TransportAddressType or TransportDomain value.

         Every usage of the TransportAddress textual convention MUST

         specify the TransportAddressType or TransportDomain object

         which provides the context. Furthermore, MIB authors SHOULD

         define a separate TransportAddressType or TransportDomain

         object for each TransportAddress object. It is suggested that

         the TransportAddressType or TransportDomain is logically

         registered before the object(s) which use the

         TransportAddress textual convention if they appear in the

         same logical row.

 

         The value of a TransportAddress object must always be

         consistent with the value of the associated

         TransportAddressType or TransportDomain object. Attempts

         to set a TransportAddress object to a value which is

         inconsistent with the associated TransportAddressType or

         TransportDomain must fail with an inconsistentValue error.

 

         When this textual convention is used as a syntax of an

         index object, there may be issues with the limit of 128

         sub-identifiers specified in SMIv2, STD 58. In this case,

         the OBJECT-TYPE declaration MUST include a 'SIZE' clause

         to limit the number of potential instance sub-identifiers."

    SYNTAX      OCTET STRING (SIZE (0..255))

 

TransportAddressIPv4 ::= TEXTUAL-CONVENTION

    DISPLAY-HINT "1d.1d.1d.1d:2d"

    STATUS      current

    DESCRIPTION

        "Represents a transport address consisting of an IPv4

         address and a port number (as used for example by UDP,

         TCP and SCTP):

 

          octets       contents         encoding

           1-4         IPv4 address     network-byte order

           5-6         port number      network-byte order

 

 

 

Regards,

Sudhir P


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users