Re: smidump -f smiv1 output
Hi and thanks for the feedback. For example, we have the following SMIv2 MIB object:
ibmMvsTcpListenerLocalAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address type of the ibmMvsTcpListenerLocalAddr object." ::= { ibmTcpipMvsTcpListenerEntry 2 }
In the SMIv1 output from smidump, we thought this object would have been defined as:
ibmMvsTcpListenerLocalAddrType OBJECT-TYPE SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16) } ACCESS read-only STATUS mandatory DESCRIPTION "The IP address type of the ibmMvsTcpListenerLocalAddr object." ::= { ibmTcpipMvsTcpListenerEntry 2 }
Thanks,
Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com
Hi!
Kristine Adamson writes:
Kristine> Hi and thanks for the feedback. For example, we have the Kristine> following SMIv2 MIB object:
Kristine> ibmMvsTcpListenerLocalAddrType OBJECT-TYPE Kristine> SYNTAX InetAddressType Kristine> MAX-ACCESS read-only Kristine> STATUS current Kristine> DESCRIPTION Kristine> "The IP address type of the Kristine> ibmMvsTcpListenerLocalAddr object." Kristine> ::= { ibmTcpipMvsTcpListenerEntry 2 }
Kristine> In the SMIv1 output from smidump, we thought this object Kristine> would have been defined as:
Kristine> ibmMvsTcpListenerLocalAddrType OBJECT-TYPE Kristine> SYNTAX INTEGER { Kristine> unknown(0), Kristine> ipv4(1), Kristine> ipv6(2), Kristine> ipv4z(3), Kristine> ipv6z(4), Kristine> dns(16) Kristine> } Kristine> ACCESS read-only Kristine> STATUS mandatory Kristine> DESCRIPTION Kristine> "The IP address type of the Kristine> ibmMvsTcpListenerLocalAddr object." Kristine> ::= { ibmTcpipMvsTcpListenerEntry 2 }
Such a change is not necessary. The SMIv1 output as it is produced now is valid and reflects more closely what the original SMIv2 defines.
-frank
participants (2)
-
Frank Strauss -
Kristine Adamson