Re: Help explaining the (apparent) extra index seen in atPhysAddress?

2009/4/8 Fulko Hew <[email protected]>:
>> It's actually that CHOICE that introduces the .1 subidentifier.
>
> OK, thats what I thought, but, is it a '1', because:
>
> a) only one instance of the CHOICE was being returned, or
> b) because ipAddress is the first enumeration in the CHOICE?

I believe it's probably the latter.
But it has been years since I've looked at this, and I can't recall the details.
(All my SNMP books are at work, and it's too late to start searching the web)


>> > b) Are there any other situations where this occurs?
>>
>> No.
>> The atTable is the only place where NetworkAddress is used.
>>
>> It's obsolete - don't worry about it.
>
> That may very well be, but when I browse a system, both my OpenServer
> and Linux boxes respond with content... so I have to be able to cope with
> that.

Fair enough.
But atTable is the *only* MIB definition that I've come across that uses
NetworkAddress (and this table is officially deprecated).   And I can't recall
seeing any other syntax that uses CHOICE either.   I'm not sure whether
it's actually legal in any other context.   (Again - it's too late to
start chasing
that up - I've a 6am start tomorrow, and I need my bed!)
   So this isn't something you are likely to come across in any other situation.
It's specific to the atTable.   It's not worth wasting too much time on.

Dave

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
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