perfsonar development work

[David Schmitz <>]

-- 

David Schmitz

Boltzmannstraße 1, 85748 Garching
Telefon:   +49 89 35831-8765
Fax:       +49 89 35831-9700
Leibniz-Rechenzentrum, Germany
Mail:  




---------- Forwarded message ----------
Date: Wed, 25 Jul 2007 14:34:49 +0200 (CEST)
From: David Schmitz 
<>
To: Nicolas Simar 
<>
Cc: Andreas Hanemann 
<>,
    David Schmitz 
<>,
    Szymon Trocha 
<>,
    Roman Lapacz 
<>,
 Nina Jeliazkova 
<>
Subject: Re: [Fwd: Schema for input errors and output drops]

Hi Nicolas,

> Thanks Szymon. Those sounds good to me.
> 
> Andreas or David, could you please proceed with the writing up of the schema
> (the MXL examples are needed for the end of this week so that Roman can
> implement them). It should take less than one hour.
Attached is a proposal for example XML message (adapted from utilization.xml) 
and 
and RNC specification (adapted from utilization.rnc).


> 
> 1. The metric that are needed are defined here:
> http://wiki.perfsonar.net/jra1-wiki/index.php/New_RRD_MA_SNMP_counters#Recommendation
>
At the moment the 4 basic frame metrics (ifInDiscards, ifOutDiscards,
ifInErrors, and ifOutErrors) are supported.
Others may later be added as necessary.

Concerning their specification by metdata,
my proposal is to distinguish their selection by different eventTypes
(including a wildcard eventType any for discards and errors) 
and by the direction element (*/in/out) in the subject.

Concerning their differentiation in the data elements,
I propose to add an additional attribute type (ifInErrors, ifOutErrors, etc.) 
in the datum element for specification of the specific type of frame metric
the datum element pertains.

> 2. To modify create the XML schema, you can follow the guideline defined by
> Jason. http://anonsvn.internet2.edu/svn/nmwg/trunk/nmwg/schema/README.txt
> His only inter-action is to say yes it is fine or could you please specify
> this.
> 
> 3. To get the schema, you can basically use the same message as the one used
> for utilisation (setupDataRequest, setupKeyRequest, setupDataResponse,
> SetupKeyResponse). There are very few things you would have to change is the
> eventType and the metrics being used.
I do not understand how to specify all message types separately
(setupKeyRequest, ...) as the example files for other metrics,
especially utilisation.xml
(http://anonsvn.internet2.edu/svn/nmwg/trunk/nmwg/schema/example_instances/utilization.xml)
 
contains only the single (template?) message type 'store'.

> 
> 4. Once the schema done, you can derive the rnc (used for documentation for
> different visualisation tools)
Can somebody experienced with the use of RNC files check my proposal?

> 
> Can you achieve this by the end of the week?


Best regards,
David

> 
> Cheers,
> Nicolas
> 
> Szymon Trocha wrote:
> > Hi all,
> > 
> > Roman Lapacz pisze:
> > 
> > > Szymon Trocha wrote:
> > >
> > > > Hi all,
> > > >
> > > > Nicolas Simar pisze:
> > > >
> > > > > Hi,
> > > > >
> > > > > I had a quick chat with Jason (Cc-ed) about the input errors and
> > > > > output drops schema. He thinks it will be failry the same as the one
> > > > > on link utilisation.
> > > > >
> > > > > What he basically needs to provide the rnc are:
> > > > > - the name of the metrics
> > > >
> > > >
> > > > As said earlier hopefully tomorrow I will provide the group with
> > > > selected SNMP counters.
> > 
> > 
> > Here they are:
> > http://wiki.perfsonar.net/jra1-wiki/index.php/New_RRD_MA_SNMP_counters
> > Based on general discussion on some input from other people I recommend
> > these 4 counters listed in Wiki.
> > 
> > > > > - from where they will be retrieved (e.g. related to an IP address)
> > > > > - the units
> > > > > - the value returned (number of drops reported by router counter, 
> > > > > the
> > > > > difference with the last 5 min or else).
> > > > > - in or out
> > > > >
> > > > > To know what information to provide, have a look at the examples for
> > > > > utilisation:
> > > > > http://anonsvn.internet2.edu/svn/nmwg/trunk/nmwg/schema/example_instances/utilization.xml
> > > > >  
> > > > >
> > > > >
> > > > > Once he got that, he will produce the rnc and Roman can derive the
> > > > > java classes from the link utilisation one.
> > > >
> > > >
> > > > Great!
> > > >
> > > > Roman - are you ok with it?
> > >
> > > I need example requests (I understand they will be very similar but I 
> > > need
> > > them to be sure we all have the same knowledge of it).
> > 
> > 
> > Sure. This is something the group has to work out now.
> > 
> > Regards,
> > Szymon
> 
> 

-- 

David Schmitz

Boltzmannstraße 1, 85748 Garching
Telefon:   +49 89 35831-8765
Fax:       +49 89 35831-9700
Leibniz-Rechenzentrum, Germany
Mail:  

# ##############################################################
# 
# File:         framemetric.rnc - Specialized schema for the 
#                                 measure of interface framemetric
# Version:      $Id$
# Purpose:      Describes specific elements to be used in the
#               representation and handling of interface 
#               framemetric
# Reference:    http://books.xmlschemata.org/relaxng/page2.html
#                         
# ##############################################################
        

# ##############################################################
# Namespace definitions
# ##############################################################
namespace nmwg = "http://ggf.org/ns/nmwg/base/2.0/";
namespace framemetric = 
"http://ggf.org/ns/nmwg/characteristic/framemetric/2.0/";
namespace nmwgr = "http://ggf.org/ns/nmwg/result/2.0/";


# ##############################################################
# Include additional functionality from other files
# ##############################################################
include "nmtopo.rnc"
include "nmtopo_ver3.rnc"
include "result.rnc"
include "nmbase.rnc" {
        Metadata |= framemetricMetadata
        Data |= framemetricData        
} 


# ##############################################################
# Metadata is the 'data' that describes physical measurements. 
# Metadata can be something such as a physical address, or 
# a geographical location; any form of static, re-usable 
# designation.  It is important to note that the subject
# namespace and parameters namespace MUST match (or the parameters
# can be a generic NMWG) or bad things will occur.
#
# Example: 
# 
# <nmwg:metadata id="REQUIRED_ID" 
#                metadataIdRef="OPTIONAL_REFERENCE_ID"
#                xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";>
# 
#   <!-- TBD OPTIONAL SUBJECT -->
# 
#   <!-- TBD OPTIONAL PARAMETERS -->
#
#   <!-- TBD OPTIONAL EVENTTYPE -->
# 
#   <!-- TBD OPTIONAL KEY -->
#  
#   <!-- ANY OPTIONAL (MULTIPLE) ELEMENT IN ANY NAMESPACE --> 
#
# </nmwg:metadata>
# 
# ##############################################################
        
framemetricMetadata = 
        element nmwg:metadata {
                Identifier &
                MetadataIdentifierRef? &
                framemetricMetadataContent
        }
          
framemetricMetadataBlock = 
        framemetricSubject? &
        (
                framemetricParameters |
                Parameters
        )?
        
framemetricMetadataContent = 
        (
                framemetricMetadataBlock |
                FilterMetadataBlock                
        ) &        
        EventType? &
        Key?        


# ##############################################################
# Redefined framemetric subject allows only an interface, and
# the two id attributes.    
#
# Example: 
# 
# <framemetric:subject id="REQUIRED_ID" 
#               metadataIdRef="OPTIONAL_REFERENCE_ID"
#               xmlns:nmwg="http://ggf.org/ns/nmwg/tools/framemetric/2.0/";>
# 
#   <nmwgtopo:interface xmlns:nmwgtopo="http://ggf.org/ns/nmwg/topology/2.0/";>
# 
#     <nmwgtopo:ipAddress type='REQUIRED_TYPE'> TEXT </nmwgtopo:ipAddress>
# 
#     <nmwgtopo:hostName> TEXT </nmwgtopo:hostName>
# 
#     <nmwgtopo:ifName> TEXT </nmwgtopo:ifName>
# 
#     <nmwgtopo:ifDescription> TEXT </nmwgtopo:ifDescription>
# 
#     <nmwgtopo:ifAddress type='REQUIRED_TYPE'> TEXT </nmwgtopo:ifAddress>
# 
#     <nmwgtopo:ifHostName> TEXT </nmwgtopo:ifHostName>
# 
#     <nmwgtopo:ifIndex> TEXT </nmwgtopo:ifIndex>
# 
#     <nmwgtopo:type> TEXT </nmwgtopo:type>
# 
#     <nmwgtopo:direction> TEXT </nmwgtopo:direction>
# 
#     <nmwgtopo:authRealm> TEXT </nmwgtopo:authRealm>
# 
#     <nmwgtopo:classOfService> TEXT </nmwgtopo:classOfService>
# 
#     <nmwgtopo:capacity> TEXT </nmwgtopo:capacity>
#  
#   </nmwgtopo:interface>
#  
# </framemetric:subject>
#
# ##############################################################

framemetricSubject =
        element framemetric:subject {
                Identifier &
                MetadataIdentifierRef? &                
                (
                        Interface |
                        BaseInterface |
                        L2Interface |
                        L3Interface
                )
        }


# ##############################################################
# This is simply the regular method of doing parameters with an
# enumeration to limit what 'names' are accepted and an outer
# framemetric: namespace for the parameters.
#
# Example: 
# 
# <framemetric:parameters id="REQUIRED_ID" 
#                   
xmlns:nmwg="http://ggf.org/ns/nmwg/tools/framemetric/2.0/";>
# 
#   <nmwg:parameter name="REQUIRED_ENUM_NAME" value="OPTIONAL_VALUE"
#                   xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";>
# 
#     <!-- ANY TEXT, (IF YOU DID NOT USE THE VALUE ATTRIBUTE) -->
# 
#   </nmwg:parameter>
#  
#   <!-- MORE PARAMETERS -->
#   
# </framemetric:parameters>
# 
# ##############################################################

framemetricParameters =
        element framemetric:parameters {
                Identifier &        
                framemetricParameter+
        }
        
framemetricParameter = 
        element nmwg:parameter { 
                attribute name { "interval" | "valueUnits" } &
                (
                        attribute value { text } |
                        text
                )
        }


# ##############################################################
# The data block is complex, and has the potential to contain
# many things.  The data block can be used to return a metadata
# block from a request, commonTime or datum elements, keys, 
# or something that we have perhaps not defined as of yet.  
#
# Example: 
# 
# <nmwg:data id="REQUIRED_ID" 
#            metadataIdRef="OPTIONAL_REFERENCE_ID" 
#            xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";>
# 
#   <!-- OPTIONAL (MULTIPLE) METADATA -->
# 
#           <!-- OR -->
#
#   <!-- TBD OPTIONAL (MULTIPLE) COMMON TIME ELEMENTS AND 
#        OPTIONAL (MULTIPLE) DATUM ELEMENTS-->
# 
#           <!-- OR -->
#  
#   <!-- TBD OPTIONAL (MULTIPLE) DATUM ELEMENTS -->
# 
#           <!-- OR -->
#  
#   <!-- OPTIONAL (MULTIPLE) KEY ELEMENTS -->
# 
#           <!-- OR -->
# 
#   <!-- ANY OPTIONAL (MULTIPLE) ELEMENT IN ANY NAMESPACE -->
#   
# </nmwg:data>
# 
# ##############################################################
   
framemetricData =
        element nmwg:data {
                Identifier &
                MetadataIdentifierRef? &
                (
                        (
                                Metadata* |
                                framemetricMetadata*
                        ) |
                        (
                                framemetricCommonTime+ & 
                                (
                                        framemetricDatum* |
                                        ResultDatum*
                                )
                        ) |
                        (
                                framemetricDatum* |
                                ResultDatum*
                        ) |
                        Key*
                )
        }


# ##############################################################
# CommonTime is used a a shortcut able to 'factor out' a frequently
# occurring time range that a bunch of datum (or other) elements
# might share, thus reducing complexity of XML representation.  
# CommonTime is similar to the other NMWG time stamps (from 
# nmtime.rnc) in its potential time representations.
#
# Example: 
# 
# <nmwg:commonTime type="REQUIRED_TYPE" value="OPTIONAL_VALUE"
#                  duration="OPTIONAL_DURATION" 
#                  inclusive="OPTIONAL_INCLUSIVE_FLAG"
#                  xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";>
# 
#   <!-- TBD OPTIONAL START TIME ELEMENT (USE END TIME OR DURATION) -->
#  
#   <!-- TBD OPTIONAL END TIME ELEMENT (ONLY WITH START TIME) -->
#  
#   <!-- TBD OPTIONAL TIME VALUE ELEMENT (USE IF NO VALUE ATTRIBUTE) -->
#  
#   <!-- TBD OPTIONAL (MULTIPLE) DATUM ELEMENTS -->
# 
#   <!-- ANY OPTIONAL (MULTIPLE) ELEMENT IN ANY NAMESPACE -->
# </nmwg:commonTime>
# 
# ##############################################################

framemetricCommonTime = 
        element nmwg:commonTime {
                Type &
                (
                        TimeStamp |
                        (
                                StartTime & 
                                (
                                        EndTime | 
                                        Duration 
                                )
                        )
                ) &
                (
                        framemetricDatum* |
                        ResultDatum*
                )
        } 


# ##############################################################
# These are the basic elements we would expect to see in the 
# specific iperf datum.
#
# Example: 
# 
# <framemetric:datum value="REQUIRED_VALUE"
#                    valueUnits="OPTIONAL_VALUE_UNITS"
#                    timeType="OPTIONAL_TIME_TYPE"
#                    timeValue="OPTIONAL_TIME_VALUE"
#                    
xmlns:nmwg="http://ggf.org/ns/nmwg/tools/framemetric/2.0/";>
# 
#   <!-- TIME ELEMENT (IF ATTRIBUTES NOT USED) -->
#  
# </framemetric:datum>
# 
# ##############################################################

framemetricDatum =
        element framemetric:datum {
                attribute type { xsd:string } &
                attribute value { xsd:float } &
                attribute valueUnits { xsd:string }? &        
                (
                        (
                                attribute timeType { xsd:string } & 
                                attribute timeValue { xsd:string }
                        ) |
                        Time
                )?                         
        }
<?xml version="1.0" encoding="UTF-8"?>
<nmwg:message type="store" 
              xmlns="http://ggf.org/ns/nmwg/base/2.0/";
              xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; 
              xmlns:netfram="http://ggf.org/ns/nmwg/characteristic/framemetric/2.0/";
              xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/";
              xmlns:nmtm="http://ggf.org/ns/nmwg/time/2.0/";
              xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/base/3.0/";
              xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/";
              xmlns:average="http://ggf.org/ns/nmwg/ops/average/2.0/";
              xmlns:nmwgr="http://ggf.org/ns/nmwg/result/2.0/";>

  <!-- Metadata using original topology schema -->              

  <nmwg:metadata id="iumeta1">
    <netfram:subject id="iusub1">
      <nmwgt:interface>
        <nmwgt:ipAddress type="v4">10.10.11.1</nmwgt:ipAddress>
        <nmwgt:hostName>dreadnought</nmwgt:hostName>
        <nmwgt:ifName>eth0</nmwgt:ifName>
        <nmwgt:ifDescription>gigE</nmwgt:ifDescription>
        <nmwgt:ifAddress type="ipv4">128.4.133.163</nmwgt:ifAddress>
        <nmwgt:ifIndex>0</nmwgt:ifIndex>
        <nmwgt:type>eth0</nmwgt:type>        
        <nmwgt:authRealm>someauth</nmwgt:authRealm>
<!--
        goes back to queueing strategy, could be
        more specifications?
        
        <classOfService>Best Effort</nmwgt:classOfService>
        <classOfService>Scavenger</nmwgt:classOfService>
        <classOfService>OSCARS</nmwgt:classOfService>
        <classOfService>All</nmwgt:classOfService>                                                
-->                                
        <nmwgt:classOfService>All</nmwgt:classOfService>                
<!--
        Can specify this up here, or use seperate metadata chains
        to describe.
        -->

        <nmwgt:direction>*</nmwgt:direction>
        <nmwgt:direction>in</nmwgt:direction>
        <nmwgt:direction>out</nmwgt:direction>        
 
      </nmwgt:interface>
    </netfram:subject>

    <!-- some alternatives: -->
    <netfram:eventType>http://ggf.org/ns/nmwg/characteristic/frames/2.0/any</netfram:eventType>
    <netfram:eventType>http://ggf.org/ns/nmwg/characteristic/frames/2.0/ifDiscards</netfram:eventType>
    <netfram:eventType>http://ggf.org/ns/nmwg/characteristic/frames/2.0/ifErrors</netfram:eventType>

    <!-- Any subsumes all available (frames) metrics, i.e. at the moment ifDiscards and ifErrors -->
    <!-- nmwgt:direction + netfram::eventType together determine which 
         actual frame counters are selected:

         e.g. direction=* + eventType=.../ifDiscards: ifInDiscards + ifOutDiscards selected,
         e.g. direction=in + eventType=.../any: ifInDiscards + ifInErrors selected,
         e.g. direction=out + eventType=.../ifErrors: ifOutErrors selected,

         so it is possible to get all available (frame) metrics for an ipAddress at once
    -->

    </netfram:eventType>
    
    <netfram:parameters id="param1">
      <nmwg:parameter name="interval">1</nmwg:parameter>
      <nmwg:parameter name="valueUnits">frames</nmwg:parameter>         
    </netfram:parameters>   
    
  </nmwg:metadata>

  <nmwg:metadata id="iumeta2" metadataIdRef="iumeta1">
<!--
    The metadataKey is nothing more than a file that is
    generated by tools like cricket that describes a 
    interface on a machine.  This file can be used in the
    future for queries and saves the time of needing to
    search on specific parameters.  
-->  
     
    <netfram:subject id="iusub2">
      <nmwgt:interface>
        <nmwgt:direction>in</nmwgt:direction>
      </nmwgt:interface>
    </netfram:subject>
  </nmwg:metadata>

  <nmwg:metadata id="iumeta3" metadataIdRef="iumeta1">
     
    <netfram:subject id="iusub3">
      <nmwgt:interface>      
        <nmwgt:direction>out</nmwgt:direction>
      </nmwgt:interface>
    </netfram:subject>
  </nmwg:metadata>


  <!-- Metadata(s) using new topology schema -->

  <nmwg:metadata id="iumeta4">
    <netfram:subject id="iusub4">

    <!-- we could use any of the specific interfaces from 
         topo as well ... (L2, L3) -->
         
      <nmwgtopo3:interface id="d1">     
        <nmwgtopo3:name type="string">dreadnought</nmwgtopo3:name>
        <nmwgtopo3:type>pc</nmwgtopo3:type>
        <nmwgtopo3:hostName>dreadnought.cis.udel.edu</nmwgtopo3:hostName>
        <nmwgtopo3:ifName>eth0</nmwgtopo3:ifName>
        <nmwgtopo3:ifDescription>gigE</nmwgtopo3:ifDescription>
        <nmwgtopo3:ifIndex>0</nmwgtopo3:ifIndex>
        <nmwgtopo3:capacity>1000000000</nmwgtopo3:capacity>
      </nmwgtopo3:interface>
    </netfram:subject>
    
    <netfram:parameters id="param4">
      <nmwg:parameter name="interval">1</nmwg:parameter>
      <nmwg:parameter name="valueUnits">frames</nmwg:parameter>         
    </netfram:parameters>   
    
  </nmwg:metadata>

     




  <!-- The following methods deal with a factored
       commonTime strategy.
  -->    

  <nmwg:data id="data1" metadataIdRef="iumeta1">   
    <nmwg:commonTime type="unix" value="1107492095">
      <netfram:datum type="ifInErrors" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifOutDiscards" value="234567890" valueUnits="frames"/>
    </nmwg:commonTime>
  </nmwg:data>

  <nmwg:data id="data2" metadataIdRef="iumeta1">
    <nmwg:commonTime type="unix">
      <nmtm:value>1107492095</nmtm:value>
      <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames"/>
    </nmwg:commonTime>
  </nmwg:data>
  
  <nmwg:data id="data3" metadataIdRef="iumeta1">   
    <nmwg:commonTime type="interval" duration="30">
      <nmtm:start type="unix" value="1107492095"/>
      <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifInErrors" value="234567890" valueUnits="frames"/>
    </nmwg:commonTime>
  </nmwg:data>
   
  <nmwg:data id="data4" metadataIdRef="iumeta1">
    <nmwg:commonTime type="interval" duration="30">
      <nmtm:start type="unix">
        <nmtm:value>1107492095</nmtm:value>
      </nmtm:start>
      <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames"/>
    </nmwg:commonTime>
  </nmwg:data>
    
  <nmwg:data id="data5" metadataIdRef="iumeta1">   
    <nmwg:commonTime type="range">
      <nmtm:start type="unix" value="1107492095"/>
      <nmtm:end type="unix" value="1107492395"/>
      <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames"/>
    </nmwg:commonTime>
  </nmwg:data>
   
  <nmwg:data id="data6" metadataIdRef="iumeta1">   
    <nmwg:commonTime type="range">
      <nmtm:start type="unix">
        <nmtm:value>1107492095</nmtm:value>
      </nmtm:start>
      <nmtm:end type="unix">
        <nmtm:value>1107492095</nmtm:value>
      </nmtm:end>
      <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames"/>
      <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames"/>
    </nmwg:commonTime>
  </nmwg:data>       


  <!-- Inline everything for single items (not really good for
       large groups) if you want to be compact.
  -->
  <nmwg:data id="data7" metadataIdRef="iumeta1">
    <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames" timeType="unix" timeValue="1021119880"/>
  </nmwg:data>
  
  
  <!-- If a commonTime is not applicable, and inlining time doesnt describe
       the time well enough, make a time element be a child of each datum.  It
       has a couple ways of being described
  -->
  <nmwg:data id="data8" metadataIdRef="iumeta1">    
    <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames">
      <nmtm:time type="unix" value="1021119880" />
    </netfram:datum>
  </nmwg:data>  

  <nmwg:data id="data9" metadataIdRef="iumeta1">   
    <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames">
      <nmtm:time type="unix">
        <nmtm:value>1021119880"</nmtm:value>
      </nmtm:time>
    </netfram:datum>
  </nmwg:data> 

  <nmwg:data id="data10" metadataIdRef="iumeta1">
    <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames">
      <nmtm:time type="interval" duration="30">
        <nmtm:start type="unix" value="1107492095"/>
      </nmtm:time>
    </netfram:datum>
  </nmwg:data> 

  <nmwg:data id="data11" metadataIdRef="iumeta1">    
    <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames">
      <nmtm:time type="interval" duration="30">
        <nmtm:start type="unix">
          <nmtm:value>1107492095</nmtm:value>
        </nmtm:start>  
      </nmtm:time>
    </netfram:datum>
  </nmwg:data> 

  <nmwg:data id="data12" metadataIdRef="iumeta1">   
    <netfram:datum type="ifOutErrors" value="234567890" valueUnits="frames">
      <nmtm:time type="range">
        <nmtm:start type="unix" value="1107492095"/>
        <nmtm:end type="unix" value="1107492395"/>
      </nmtm:time>
    </netfram:datum>
  </nmwg:data> 

  <nmwg:data id="data13" metadataIdRef="iumeta1">    
    <netfram:datum type="ifInDiscards" value="234567890" valueUnits="frames">
      <nmtm:time type="range">
        <nmtm:start type="unix">
          <nmtm:value>1107492095</nmtm:value>
        </nmtm:start>
        <nmtm:end type="unix">
          <nmtm:value>1107492395</nmtm:value>
        </nmtm:end>
      </nmtm:time>
    </netfram:datum>
  </nmwg:data>   

  <!-- result datum elements -->
  <nmwg:data id="data14" metadataIdRef="iumeta1">  
    <nmwgr:datum type="error.iu.mp">eth0: error fetching interface information: Device not found</nmwgr:datum>
  </nmwg:data> 
  
</nmwg:message>