Thanks Dave. Really appreciate your help spending time on my issues.
Best Regards,
--- On Thu, 15/4/10, Dave Shield <d.t.shi...@liverpool.ac.uk> wrote:
From: Dave Shield <d.t.shi...@liverpool.ac.uk>
Subject: Re: Regarding string as index for tables
To: "phani kumar" <kumarc...@yahoo.co.uk>
Cc: net-snmp-users@lists.sourceforge.net
Date: Thursday, 15 April, 2010, 11:28
On 15 April 2010 11:14, phani kumar <kumarc...@yahoo.co.uk> wrote:
> Just to wind things for the day, this is the last one trust me.
>
> 1) So taking this logic to table with ip address as the index....
> then the walk should yield :
>
> c1.1.2.3.4
> c1.1.2.4.4
> c1.1.3.4.5
> c1.10.3.4.5
Exactly.
The reason that I've been hanging off discussing IP addresses
is that these are defined as fixed-size, so are automatically handled
as IMPLIED strings and hence do not include the size subidentifier.
This happens automatically - you don't need to define the index
object as IMPLIED for a fixed-length string. It's implied IMPLIED
(even when it's not the last index object - which you can't do
with the explicit IMPLIED token)
> If I am correct , in the case of c1.1.2.3.4 and c1.1.2.4.4
> as both the first two octets are same the next lexicographical
> one to that is 3. So all this is comparing octets and finding
> out which is next/greater to the current one ?
Zigactly!
> 2) This is about ip address representation in the MIB. I remember we got
>
> IpAddress TC from SMIv2 and we can use it. But then there is some new
> discussion
> came across saying, the IpAddress TC is old and there is new one and
> more precise which people are using now-a-days !!
The issue with the IpAddress TC is that it is explicitly designed for IPv4.
It cannot handle IPv6 addresses.
It's therefore being deprecated in favour of an (InetAddressType,InetAddress)
pair, which can handle both IPv4 and IPv6 addresses (plus other types as well).
But note that InetAddressType is *not* fixed-length, so isn't automatically
treated as IMPLIED.
> I am not sure this i a new TC or donno
These are defined in INET-ADDRESS-MIB.
For examples of their use, see (e.g.) UDP-MIB or TCP-MIB.
Try comparing the tables defined here, with the equivalent
ones in RFC1213.
Dave
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
