What is the Key to get help on this List?
And what is the reason to ignore my posts?

The ipv6 trap Receiver configutration use the wrong Port Nummer if configured 
via mib.

With regards
Claus

On 03.10.2013, at 11:37, Claus Klein <claus.kl...@arcormail.de> wrote:

> Hi,
> 
> what is the reason for different byteorder of port configuration with 
> snmpUDPDomain and transportDomainUdpIpv6 in snmpTargetAddrTable?
> 
> 
> with this configuration:
> 
> trapsess -v 3 -e 0x80001f88017f000001 -u trapuser -l noAuthNoPriv 
> udp:127.0.0.1:4660
> trapsess -v 3 -e 0x80001f88017f000001 -u trapuser -l noAuthNoPriv 
> udp6:[::ffff:127.0.0.1]:4660
> 
> I get this table entries:
> 
> snmptable -Cibw 99 localhost snmpTargetAddrTable
> SNMP table: SNMP-TARGET-MIB::snmpTargetAddrTable
> 
>         index                                       TDomain
> \'internal0\'                      SNMPv2-TM::snmpUDPDomain
> \'internal1\' TRANSPORT-ADDRESS-MIB::transportDomainUdpIpv6
> 
> SNMP table SNMP-TARGET-MIB::snmpTargetAddrTable, part 2
> 
>         index                                                  TAddress 
> Timeout RetryCount
> \'internal0\'                                      "7F 00 00 01 12 34 "    
> 1000          5
> \'internal1\' "00 00 00 00 00 00 00 00 00 00 FF FF 7F 00 00 01  34 12 "    
> 1000          5
> 
> SNMP table SNMP-TARGET-MIB::snmpTargetAddrTable, part 3
> 
>         index   TagList    Params StorageType RowStatus
> \'internal0\' internal0 internal0    readOnly    active
> \'internal1\' internal1 internal1    readOnly    active
> 
> 
> IMHO, the byteorder has to be network (big endian) for both transport Domains 
> at this mib table.
> 
> TransportAddressIPv6 ::= TEXTUAL-CONVENTION
>     DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x]0a:2d"
>     STATUS      current
>     DESCRIPTION
>         "Represents a transport address consisting of an IPv6
>          address and a port number (as used for example by UDP,
>          TCP and SCTP):
> 
>           octets       contents         encoding
>            1-16        IPv6 address     network-byte order
>           17-18        port number      network-byte order
> 
>          This textual convention SHOULD NOT be used directly in object
>          definitions since it restricts addresses to a specific format.
>          However, if it is used, it MAY be used either on its own or
>          in conjunction with TransportAddressType or TransportDomain
>          as a pair."
>     SYNTAX      OCTET STRING (SIZE (18))
> 
> It is not clear to me, which port number is really used with this 
> configuration.
> 
> 
> Can anyone please help?
> 
> Thanks in advance
> Best Regards
> Claus
> 
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
> _______________________________________________
> Net-snmp-coders mailing list
> Net-snmp-coders@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to