Statistics monitoring using JMS

Overview

An OSS performance management application can use a JMS interface to communicate with the NFM-P server for monitoring statistics events. The OSS needs to subscribe to the NFM-P-topic-xml for all JMS topics including statistics events or to the NFM-P-topic-xml-stats JMS topic for events related to statistics collection. See Chapter 4, Event monitoring using JMS for more information about connecting to the JMS event stream and subscribing to JMS topics.

For scheduled accounting or performance statistics collection, JMS StatsEvent notifications are generated to display the beginning and end of polling of an NE for accounting or performance statistics. The JMS StatsEvent indicates statistics collection activity. The following table describes the parameters in the scheduled performance statistics collection StatsEvent output.

Table 14-4: JMS StatsEvent parameters

Parameter	Description	Values
<state>	Marks the start or end of polling for an NE	begin end
<statsType>	Statistics type	polling accounting
<networkElement>	NE identifier	Site ID of the NE
<time>	Collection time	Unix Epoch time, in milliseconds

Figure 14-17: StatsEvent output example, scheduled performance statistics collection

<?xml version="1.0" encoding="UTF-8"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

   <SOAP:Header>

      <header xmlns="xmlapi_1.0">

         <eventName>StatsEvent</eventName>

         <ALA_category>STATISTICS</ALA_category>

         <ALA_OLC>0</ALA_OLC>

         <ALA_isVessel>false</ALA_isVessel>

         <ALA_allomorphic/>

         <MTOSI_osTime>1333998300824</MTOSI_osTime>

         <MTOSI_NTType>ALA_OTHER</MTOSI_NTType>

         <MTOSI_objectName/>

         <ALA_clientId>JMS_client@n</ALA_clientId>

         <MTOSI_objectType>StatsEvent</MTOSI_objectType>

         <ALA_eventName>StatsEvent</ALA_eventName>

      </header>

   </SOAP:Header>

   <SOAP:Body>

      <jms xmlns="xmlapi_1.0">

         <statsEvent>

            <state>begin</state>

            <networkElement>198.51.100.57</networkElement>

            <statsType>polling</statsType>

            <time>1333998300824</time>

         </statsEvent>

      </jms>

   </SOAP:Body>

</SOAP:Envelope>

For on-demand statistics collection, an ObjectCreationEvent or AttributeValueChangeEvent notification is generated to display the statistics class that is polled and the attributes and values of the class. When a statistic is first collected, there is an ObjectCreationEvent sent for the new current data record. When subsequent records are collected, the current data record is updated so an AttributeValueChangeEvent is sent. The following figure shows sample on-demand statistics collection ObjectCreation output.

Figure 14-18: ObjectCreation output example, on-demand statistics collection

<?xml version="1.0" encoding="UTF-8"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

   <SOAP:Header>

      <header xmlns="xmlapi_1.0">

         <eventName>ObjectCreation</eventName>

         <ALA_category>STATISTICS</ALA_category>

         <ALA_OLC>0</ALA_OLC>

         <ALA_isVessel>false</ALA_isVessel>

         <ALA_allomorphic>equipment.InterfaceStats</ALA_allomorphic>

         <MTOSI_osTime>1334089752549</MTOSI_osTime>

         <MTOSI_NTType>NT_OBJECTCREATION</MTOSI_NTType>

         <MTOSI_objectName>logger:real-time|equipment.InterfaceStats|network_198.51.100.57_shelf-1_cardSlot-1_card_daughterCardSlot-1_daughterCard_port-1</MTOSI_objectName>

         <ALA_span>:0:</ALA_span>

         <ALA_clientId>JMS_client@n</ALA_clientId>

         <MTOSI_objectType>equipment.InterfaceStats</MTOSI_objectType>

         <ALA_eventName>ObjectCreation</ALA_eventName>

      </header>

   </SOAP:Header>

   <SOAP:Body>

      <jms xmlns="xmlapi_1.0">

         <objectCreationEvent>

            <equipment.InterfaceStats>

               <receivedOctets>144677782</receivedOctets>

               <receivedOctetsPeriodic>0</receivedOctetsPeriodic>

               <receivedUnicastPackets>637046</receivedUnicastPackets>

               <receivedUnicastPacketsPeriodic>0</receivedUnicastPacketsPeriodic>

               <receivedPacketsDiscarded>0</receivedPacketsDiscarded>

               <receivedPacketsDiscardedPeriodic>0</receivedPacketsDiscardedPeriodic>

               <receivedBadPackets>0</receivedBadPackets>

               <receivedBadPacketsPeriodic>0</receivedBadPacketsPeriodic>

               <receivedUnknownProtocolPackets>0</receivedUnknownProtocolPackets>

               <receivedUnknownProtocolPacketsPeriodic>0</receivedUnknownProtocol

PacketsPeriodic>

               <transmittedOctets>198584536</transmittedOctets>

               <transmittedOctetsPeriodic>0</transmittedOctetsPeriodic>

               <transmittedUnicastPackets>553327</transmittedUnicastPackets>

               <transmittedUnicastPacketsPeriodic>0</transmittedUnicastPacketsPeriodic>

               <outboundPacketsDiscarded>0</outboundPacketsDiscarded>

               <outboundPacketsDiscardedPeriodic>0</outboundPacketsDiscardedPeriodic>

               <outboundBadPackets>0</outboundBadPackets>

               <outboundBadPacketsPeriodic>0</outboundBadPacketsPeriodic>

               <timeCaptured>1334089752528</timeCaptured>

               <periodicTime>0</periodicTime>

               <monitoredObjectClass>equipment.PhysicalPort</monitoredObjectClass>

               <monitoredObjectPointer>network:198.51.100.57:shelf-1:cardSlot-1:card:daughterCardSlot-1:daughterCard:port-1</monitoredObjectPointer>

               <alarmedObjectClass>equipment.PhysicalPort</alarmedObjectClass>

               <alarmedObjectPointer>network:198.51.100.57:shelf-1:cardSlot-1:card:daughterCardSlot-1:daughterCard:port-1</alarmedObjectPointer>

               <logRecordClass>equipment.InterfaceStatsLogRecord</logRecordClass>

               <displayedName>Port 1/1/1</displayedName>

               <monitoredObjectSiteId>198.51.100.57</monitoredObjectSiteId>

               <monitoredObjectSiteName>sim20_57</monitoredObjectSiteName>

               <suspect>false</suspect>

               <createdOnPollType>SelectiveResync</createdOnPollType>

               <updatedOnPollType>SelectiveResync</updatedOnPollType>

               <historyCreated>false</historyCreated>

               <deploymentState>0</deploymentState>

               <objectFullName>logger:real-time|equipment.InterfaceStats|network_198.51.100.57_shelf-1_cardSlot-1_card_daughterCardSlot-1_daughterCard_port-1</objectFullName>

               <name>Port 1/1/1</name>

               <selfAlarmed>false</selfAlarmed>

               <children-Set/>

            </equipment.InterfaceStats>

         </objectCreationEvent>

      </jms>

   </SOAP:Body>

</SOAP:Envelope>