[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MIB-DOCTORS] [IPFIX] AD review of draft-ietf-ipfix-mib-05.txt (ipfixExportEntry)
Dear Atsushi,
You propose to split ipfixExportMemberType from -06 into two objects
ipfixExportGroupType and ipfixExportMemberType with several
interdependencies specified in the description clauses.
At first sight, this does not seem to be easier to understand than the
table structure in -06.
Regards,
Gerhard
Atsushi Kobayashi wrote:
> Dear Thomas, Benoit, Gerhard and all,
>
> Sorry for late reply.
>
> I have concerns about the modification for the following comment.
> The MIB draft -06 was modified for the ipfixExportIndex to be located at
> the end of indexes. But, I wonder the order of these indexes is
> difficult to represent the Transport Session group.
>
> I prefer to keep the order of 3 tuple indexes
> (ipfixMeteringProcessCacheId, ipfixTemplateObservationDomainId,
> ipfixExportGroupIndex) in order to understand easily the result of
> snmpwalk, even if the MIB structure changes a little bit.
>
>>> T16. ipfixExportEntry leads to a warning in the smicng compilation
>>>
>>> W: f(ipfix.mi2), (676,12) Row "ipfixExportEntry" does not have a
>>> consistent indexing scheme - index items from current table must come
>>> after index items from other tables
>>>
>> Since I have only libsmi (which does not catch this) I did not realize it.
>> Fixed.
>
> I propose to add ExportGroupTable as follows. What do you think about it?
>
> --------------------------------------------------------------------
> -- 1.1.5: Export Group Table
> --------------------------------------------------------------------
> ipfixExportGroupTable OBJECT-TYPE
> SYNTAX SEQUENCE OF IpfixExportGroupEntry
> MAX-ACCESS not-accessible
> STATUS current
> DESCRIPTION
> "This table lists all export groups.
> On Collectors this table is not needed."
> ::= { ipfixMainObjects 5 }
>
> ipfixExportGroupEntry OBJECT-TYPE
> SYNTAX IpfixExportGroupEntry
> MAX-ACCESS not-accessible
> STATUS current
> DESCRIPTION
> "Defines an entry in the ipfixExportGroupTable"
> INDEX {
> ipfixMeteringProcessCacheId,
> ipfixTemplateObservationDomainId,
> ipfixExportGroupIndex
> }
> ::= { ipfixExportGroupTable 1 }
>
> IpfixExportGroupEntry ::=
> SEQUENCE {
> ipfixExportGroupIndex Unsigned32,
> ipfixExportGroupType INTEGER
> }
>
> ipfixExportGroupIndex OBJECT-TYPE
> SYNTAX Unsigned32 (1..4294967295)
> MAX-ACCESS not-accessible
> STATUS current
> DESCRIPTION
> "Locally arbitrary, but unique identifier of an entry in
> the ipfixExportGroupTable. The value is expected
> to remain constant from a re-initialization of the entity's
> network management agent to the next re-initialization.
>
> A common ipfixExportGroupIndex between two entries from ipfix
> Export table expresses that there is a relationship between the
> Transport Sessions in ipfixTransportSessionIndex. The type
> of Trasport Session group is expressed by the value of
> ipfixExportMemberType."
> ::= { ipfixExportGroupEntry 1 }
>
> ipfixExportGroupType OBJECT-TYPE
> SYNTAX INTEGER {
> unknown(0),
> failover(1),
> duplicate(2),
> loadBalancing(3)
> }
> MAX-ACCESS read-only
> STATUS current
> DESCRIPTION
> "The type of a Transport Session group
> (identified by the value of ipfixExportGroupIndex,
> ipfixObservationDomainId and ipfixMeteringProcessCacheId).
> The following values are valid:
>
> unknown(0)
> This value MUST be used if the status of the group
> membership cannot be detected by the equipment. This
> value should be avoided as far as possible.
>
> failover(1)
> This value is used for a group member that is used as
> the primary or secondary target of an Exporter.
> This value MUST also be specified if the Exporter does
> not support Transport Session grouping. In this case the
> group contains only one Transport Session.
>
> duplicate(2)
> This value is used for a group member that is used for
> duplicate exporting i.e., all group members identified
> by the ipfixExportIndex are exporting the same Records
> in parallel. This implies that all group members MUST
> have the the same membertype duplicate(3).
>
> loadBalancing(3)
> This value is used for a group member that is used as
> as one target for load-balancing. This means that a
> Record is sent to one of the group members in this
> group identified by ipfixExportIndex.
> This implies that all group members MUST have the same
> membertype load-balancing(4)."
> ::= { ipfixExportGroupEntry 2 }
>
>
> --------------------------------------------------------------------
> -- 1.1.6: Export Table
> --------------------------------------------------------------------
> ipfixExportTable OBJECT-TYPE
> SYNTAX SEQUENCE OF IpfixExportEntry
> MAX-ACCESS not-accessible
> STATUS current
> DESCRIPTION
> "This table lists all exports of an IPFIX device.
>
> On Exporters this table contains all exports grouped by
> Transport Session, Observation Domain Id, Template Id and
> Metering Process represented by the
> ipfixMeteringProcessCacheId. Thanks to the ipfixExportGroupIndex
> the exports can group one or more Transport Sessions to
> achieve a special functionality like failover management,
> load-balancing etc. The entries with the same
> ipfixExportGroupIndex, the same ipfixObservationDomainId
> and the same ipfixMeteringProcessCacheId define a Transport
> Session group. If the Exporter does not use Transport
> Session grouping then each ipfixGroupExportIndex contains a
> single ipfixMeteringProcessCacheId and thus a singe
> Transport Session and this session MUST have the member
> type primary(1). Transport Sessions referenced in this
> table MUST have the ipfixTransportSessionMode exporting(1).
>
> On Collectors this table is not needed."
> ::= { ipfixMainObjects 6 }
>
> ipfixExportEntry OBJECT-TYPE
> SYNTAX IpfixExportEntry
> MAX-ACCESS not-accessible
> STATUS current
> DESCRIPTION
> "Defines an entry in the ipfixExportTable"
> INDEX {
> ipfixMeteringProcessCacheId,
> ipfixTemplateObservationDomainId,
> ipfixExportGroupIndex,
> ipfixTransportSessionIndex,
> ipfixTemplateId
> }
> ::= { ipfixExportTable 1 }
>
> IpfixExportEntry ::=
> SEQUENCE {
> ipfixExportMemberType INTEGER
> }
>
> ipfixExportMemberType OBJECT-TYPE
> SYNTAX INTEGER {
> unknown(0),
> primary(1),
> secondary(2)
> }
> MAX-ACCESS read-only
> STATUS current
> DESCRIPTION
> "The type of a member Transport Session in a Transport
> Session group (identified by the value of ipfixExportIndex,
> ipfixObservationDomainId and ipfixMeteringProcessCacheId).
> The following values are valid:
>
> unknown(0)
> If the Transport Session group uses duplicate or load
> balancing, the type of a member Transport Session MUST
> have the member type unknown(0).
>
> primary(1)
> This value is used for a group member that is used as
> the primary target of an Exporter. Other group members
> (with the same ipfixExportIndex and
> ipfixMeteringProcessCacheId) MUST NOT have the value
> primary(1) but MUST have the value secondary(2).
>
> secondary(2)
> This value is used for a group member that is used as a
> secondary target of an Exporter. The Exporter will use
> one of the targets specified as secondary(2) within the
> same Transport Session group when the primary target is
> not reachable."
>
> ::= { ipfixExportEntry 1 }
>
> ---
> Atsushi KOBAYASHI <akoba at nttv6.net>
> NTT Information Sharing Platform Lab.
> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
>
> _______________________________________________
> IPFIX mailing list
> IPFIX at ietf.org
> https://www.ietf.org/mailman/listinfo/ipfix
--
Dipl.-Ing. Gerhard Münz
Chair for Network Architectures and Services (I8)
Department of Informatics
Technische Universität München
Boltzmannstr. 3, 85748 Garching bei München, Germany
Phone: +49 89 289-18008 Fax: +49 89 289-18033
E-mail: muenz at net.in.tum.de WWW: http://www.net.in.tum.de/~muenz