Network Management System and The Application in WiMAX

Network Management and Traffic Analysis for Wireless MANby Dedi Rahmawan Putra (95598052)Advisor: Dr. Kai-Wei Ke

July, 8 20081Network Management and Traffic Analysis for Wireless MAN1OutlineMotivations and ObjectivesSimple Network Management ProtocolThe Design of Network Management StationThe Implementation of Network Management Station WiMAX Network DeploymentNetwork Management DeploymentTraffic AnalysisRemaining Tasks, Conclusions, and Reference2Network Management and Traffic Analysis for Wireless MANJuly, 8 20082MotivationThe complexity of Wireless MAN system became higherThe need to maintain the functionality and the existence of each and between base station and subscriber stations.Reducing the manpower for monitoring purpose, simple maintenance, fault management, and extending the flexibility of management.To accurately model the traffic generated by each network elements in order to evaluate the performance of a system. In many real world cases, the traffic pattern is self-similar rather than Poisson.

3Network Management and Traffic Analysis for Wireless MANJuly, 8 2008To accomplish the WiMAX network deployment as a robust system and guarantee that the system will be performing as expected.

Since WiMAX defines several classifiers in its QoS implementation, the behavior would probably show the differences between each other.

3ObjectivesTo develop a Network Management Station (NMS) tool by using SNMP protocol. To integrate the developed Network Management Station (NMS) into WiMAX system in order to confidently characterize the network traffic behavior. To assess the self-similarity existence and its impact in WiMAX network traffic, comparing the past works which have proven that self-similarity exists in Ethernet traffic and Wireless LAN traffic. 4Network Management and Traffic Analysis for Wireless MANJuly, 8 2008This tool basically will be applicable to manage any devices with SNMP capability. However, this tool will be objected mainly in the deployment of fixed WiMAX system defined in IEEE Std. 802.16d.

Some scenario will be carried out and some sets of data recorded from the agents, based on their classifier and network load level, will be collected. Those sets of data then will be used as the source for traffic analysis purpose.

The traffic source coming from another devices associated to this system will be monitored simultaneously in order to figure out which aspects contributing the arising of self-similarity. We will use statistical approach to convince our conclusions.

4SNMPSimple Network Management Protocol5Network Management and Traffic Analysis for Wireless MANStandardPrinciple OperationObject terminologiesRetrieving Scalar ValueRetrieving Table ValueStandard Naming Tree

July, 8 20085StandardSMI (Structure of Management Information)Define how management information may look likeSMIv1: RFC 1155SMIv2: RFC2578 (currently used)MIBs (Management Information Bases)Tell what management information existsMIB-I: RFC1156MIB-II: RFC1213SNMP (Simple Network Management Protocol)Define how information is exchangedSNMPv1: RFC1157SNMPv2: RFC1901, 1905, 1906SNMPv3: RFC2571-2575July, 8 2008Network Management and Traffic Analysis for Wireless MAN6RFC1155 and RFC2578 are both full standard.A large number of additional MIB exist.SNMP terminology is commonly used to describe the whole things, used in a more general sense. In fact, its only a protocol for exchanging information.6Principle OperationJuly, 8 2008Network Management and Traffic Analysis for Wireless MAN7

NMSAgentMIBpollpollpollTRAPSGET/SETTransport SNMPv1 : unreliablev2/v3: reliable alternativesvariabletableMIBMIBAgentAgentThe protocol used for communication between agents and manager is SNMP.

Manager has to poll the agents continuously, because the agent itself cant check their own behavior if its still going well and cant inform the manager either.

However, if manager keeps polling the agents, it will take quite some time. Consequently, its relatively difficult to manage thousand of agents.

Polling also introduces lots of management traffics. So that scaleability is not very good.

There is a way where the agents can inform the manager if something important occurs called TRAPS.SNMPv1: limited number of TRAPS (only 7 situation where system can send the TRAPs), eg. System Start.SNMPv2/v3: more possibilities.

Transport mechanisms:SNMPv1: UnreliableSNMPv2/3: Reliable alternatives

MIB:-variable: IP address, number of packets has been sent, etc-table: routing table

A managed device is a network node that contains an SNMP agent and that resides on a managed network. An agent is a network-management software module that resides in a managed device.An NMS executes applications that monitor and control managed devices.

7Object TerminologiesObject: the definition of somethingInstance: something that has valueObject ID: the sequence of integers on the path leading from the root of the tree to a named objectScalar: an object with one instanceTable: an object with multiple instances (combination of scalars)

July, 8 2008Network Management and Traffic Analysis for Wireless MAN8Object-Type is the definition to the real variable of one leaf object.

In scalar, no distinction between object and instancesBut in terms of table, object may have multiple instances, multiple rows

To denote the instance, we need to add zero 0 after the ID of the object to get its value

Syntax can be one listed in the SMI Data Types. It is also possible to define a new type instead of using the available syntax we have shown before.

Max-Access: not about the right access. For example sysUpTime is read-only. That means only the system can change it, not the manager. In the example we could see that info is not-accessible.

Status: Current means it is currently used and this object should be implemented by everyone. Deprecated means it still should be implemented by the agent, but the manager should not use it because it will be outdated soon. Obsolete means it is there, but it is outdated.

Object naming: specify how the manager can identify an object in the agent.

8Retrieving Scalar ValueJuly, 8 2008Network Management and Traffic Analysis for Wireless MAN9

1.1.01.2.1.01.2.2.0Object OID: 1.1Instance OID: 1.1.0ValueGET 1.1.0 = 140.124.181.210ID of the object address: 1.1To get the real value of the address: GET 1.1.0 = 140.124.181.210If we use GET 1.1 = error, because the object itself doesnt have a value, but the instanceGET 1.2 = errorGET 1.2.0 = error (no value, theres no instance)We may also use GET 1.info.name.0 = printer19

Retrieving Table Entries ValueJuly, 8 2008Network Management and Traffic Analysis for Wireless MAN10X.C.I = OidOfTable.ColumnNumber.IndexValue new-MIB.routeTable.next.8 = 3destination1.3.2.8 = 3next is an object with 6 instances.To identify which instance is needed, put the instance number behind the object.

SNMP uses the element values within a specific column. We use dest column for this example to index the table.Note that the index value should be unique. If there are 2 routes to one destination, we have to do something in addition.

GET 1.3.1.5 = 5GET 1.3.2.5 = 2GET 1.3.1.9 = 9GET 1.3.2.9 = 3GET 1.3.2.7 = 2GET 1.3.1.1 = errorGET 1.3.2.1 = error

X.C.I = OID of table.Column Number.Index Value

10Standard Naming TreeJuly, 8 2008Network Management and Traffic Analysis for Wireless MAN11

Ensuring that each variable gets a unique namefor internet peoplefor company or universityStandard naming tree is used to ensure that each variable gets a unique name, since the various MIBS may be defined by different people

If we are in the internet world want to define a new variable, we have to define under root.iso.org.dod.internet.mngt.mib-2 or 1.1.3.6.1.2.1.x

If we are from a company or even university, we have to define under root.iso.org.dod.internet.private.enterprise or 1.1.3.6.1.4.1.x11The Design of Network Management Station (NMS)12Network Management and Traffic Analysis for Wireless MAN NMS OverviewSystem Context DiagramFeature RefinementJuly, 8 2008NMS OverviewA comprehensive web-based system utilizing SNMP protocol dedicated to network management system.Planned to be integrated with the deployment of fixed WiMAX system Provides easy management tools to manage several agents within the network area of interest.Deliver user friendly menus to access the functional pagesProvide object registration, agent registration, and their interaction.It polls the agents periodically to accomplish the dynamic monitoring.July, 8 200813Network Management and Traffic Analysis for Wireless MANAn object has attributes to be defined, and they shall be matched with the object-types definition in Management Information Base (MIB). The MIB may come from standardized MIB, private MIB, or user-defined MIB. Wrongly defined object attributes, especially the object ID and syntax, may cause failures in retrieving the management data instances.

User can only include the objects that have been registered in the system previously into an agent. An agent may have the same objects with another agent. If we cannot find the object we need, we should register it first before included into any agent. Once we finish the object inclusions for an agent,

Monitored objects are presented based on their retrieval method in 2 categories: static and dynamic monitoring. Static object is displayed in value, and dynamic object is represented in time-series chart (histogram or line-chart).

We may also modify the object or agent properties while the monitoring procedure is running. However, some policies may be applied to ensure the stability and correctness of the system performance.

13System Context DiagramJuly, 8 200814Network Management and Traffic Analysis for Wireless MAN

NMS uses a distributed multitier application model for enterprise application to perform a monitoring mechanism.

The Business Logic is the core application where the implementation classes reside.

The Presentation Logic is responsible to receive user inputs and formulate how to present the information to the clients, including the user interface, layout styles, button events, session controls, form processing, and charting formats

SNMP Tools is the one which is responsible to execute SNMP commands as requested by Business Logic

Database Driver is a Java API called Java Database Connectivity (JDBC). This driver serves as the interface to the Database Server. The request comes from Business Logic, activated when the system wants to access the Database Server as the Enterprise information System (EIS), either storing or retrieving information.14Feature RefinementJuly, 8 200815Network Management and Traffic Analysis for Wireless MANFeaturesSatisfied RequirementsOperationAdministrationMaintenanceProvisioningFunctionsObject RegistrationxxObject SummaryxAgent RegistrationxxAgent SummaryxAgent object ManagementxxxAgent Status ControlxxxStatic MonitoringxxxDynamic MonitoringxxGrouped MonitoringxxManager System ControlxxAgent Management StructurexxAdmin Login ControlxxxServer TimexxPing ToolxxxGet ToolxxxSet ToolxxxxLogs of ActivitiesxxOperation deals with keeping the network up and running smoothly. It includes monitoring the network to spot problems as soon as possible, ideally before users are affected.

Administration deals with keeping track of resources in the network and how they are assigned. It includes the entire tasks that are necessary to keep the network under control.

Maintenance is concerned with performing repairs and upgrades - for example, when equipment must be replaced, when a device needs a patch, when a new device is added to a network. Maintenance also involves corrective and preventive measures to make the managed network run better, such as adjusting device configuration parameters.

Provisioning is concerned with configuring resources in the network to support a given service. For example, this might include setting up the network so that a new user can receive voice service.

Functions that are performed as part of network management accordingly include controlling, planning, allocating, deploying, coordinating, and monitoring the resources of a network, network planning, frequency allocation, predetermined traffic routing to support load balancing, cryptographic key distribution authorization, configuration management, fault management, security management, performance management, bandwidth management, and accounting management.15Object Registration UIJuly, 8 200816Network Management and Traffic Analysis for Wireless MAN

displaying hidden field16Object Registration FieldsJuly, 8 200817Network Management and Traffic Analysis for Wireless MANObject IDObject NameSyntax: the object data typeMax-Access: the maximum possible accessDescriptionMake Default for New agent: special field intended to distinguish which objects should be included in a newly-registered agent by default. Syntax: Octet-String, Object-Identifier, Integer32, Unsigned32, Gauge32, Counter32, TimeTicks Counter64, IpAddress, Bits, and MacAddress.17Syntax EnumerationJuly, 8 200818Network Management and Traffic Analysis for Wireless MAN

meaningless status value for human readablemore understandable meaning 18Once: retrieved once when the monitoring starts. Eg: SystemDescription, systemName.Continuously-Updated-Value: retrieved and updated regularly. Eg: systemUpTime.

Line-Chart: retrieved regularly, the previously retrieval data will be kept. Bar-Chart: basically similar with Line-Chart one, but using bar-chart or histogram to illustrate the monitored object.Object Retrieval MethodJuly, 8 200819Network Management and Traffic Analysis for Wireless MAN

newly appeared fieldOnce This method is used for an object which is assumed to be fixed or never be changed for a quite long period.

Continuously-Updated-Value The latest-retrieving value will replace the old one. So at any given time, only one value exists. This method is aimed for an object which is changed regularly and the older data is not needed anymore like systemUpTime.Line-Chart also means the object will be retrieved regularly, but the previously retrieval data will be kept for monitoring purpose. Once you select this option method, the hidden field for selecting the Interval Time will be shown as well. This method is aimed to monitor the value changes of an object instance from time to time, represented as a line chart. However, to avoid the data explosions in the Database Server, a number of retrieval data will be limited.Bar-Chart method is basically similar with Line-Chart one. The only difference is how the data is being represented. This method is using bar-chart or histogram to illustrate the monitored object.19Agent Registration UIJuly, 8 200820Network Management and Traffic Analysis for Wireless MAN

hidden by defaultshow hidden fieldITU-T = International Telecommunication Union Telecommunication Division20Agent Registration FieldsJuly, 8 200821Network Management and Traffic Analysis for Wireless MANIP AddressAgent nameDevice type: the level position in the WiMAX network deployment hierarchy: WiMAX-BS, WiMAX-SS, AP, CLIENT Upper level gateway: which upper gateway the device belongs to.SNMP version : which compatible SNMP standard the device agent is designed for: v1, v2c, v3Read Community: community string for read access.Write Community: community string for write access.SNMP PortThere are 4 types of device being defined here: WiMAX-BS, WiMAX-SS, Access Point, and Client.21Agent Object ManagementJuly, 8 200822Network Management and Traffic Analysis for Wireless MAN

Need confirmation: monitoring in progress? restartObject naming convention: name + index for Table instances22Agent Status ControlJuly, 8 200823Network Management and Traffic Analysis for Wireless MAN

OKNeed AttentionNot Performed23Static MonitoringJuly, 8 200824Network Management and Traffic Analysis for Wireless MAN

Used for: Once and Continuously-Updated-Value24Dynamic MonitoringJuly, 8 200825Network Management and Traffic Analysis for Wireless MAN

Line-ChartObject NameBar-Chart(Histogram)25Grouped Monitoring SettingJuly, 8 200826Network Management and Traffic Analysis for Wireless MAN

This feature is given to help the user to precisely figure out the relationships or differences between the monitored objects so they can make further decisions or conclusions.26Grouped MonitoringJuly, 8 200827Network Management and Traffic Analysis for Wireless MAN

ITU-T = International Telecommunication Union Telecommunication Division27Agent Management StructureJuly, 8 200828Network Management and Traffic Analysis for Wireless MAN

ITU-T = International Telecommunication Union Telecommunication Division28Simple Management ToolsJuly, 8 200829Network Management and Traffic Analysis for Wireless MAN

ITU-T = International Telecommunication Union Telecommunication Division29The Implementation of Network Management Station30Network Management and Traffic Analysis for Wireless MANImplementation Class DiagramImplementation ArchitectureGUI LayoutImportant Functional implementationJuly, 8 2008Implementation Class DiagramJuly, 8 200831Network Management and Traffic Analysis for Wireless MAN

ITU-T = International Telecommunication Union Telecommunication Division31Implementation ArchitectureJuly, 8 200832Network Management and Traffic Analysis for Wireless MAN

ITU-T = International Telecommunication Union Telecommunication Division32GUI LayoutJuly, 8 200833Network Management and Traffic Analysis for Wireless MAN

Containers and contents are implemented using JSPITU-T = International Telecommunication Union Telecommunication Division33July, 8 200834Network Management and Traffic Analysis for Wireless MAN

Ping functionThis function is aimed to detect the device status. Ping utilizes isReachable() function call provided by Java. This function call will test whether that address being specified is reachable. Best effort is made by the implementation to try to reach the host, but firewalls and server configuration may block requests resulting in an unreachable status while some specific ports may be accessible. A typical implementation will use ICMP ECHO REQUESTs if the privilege can be obtained, otherwise it will try to establish a TCP connection on port 7 (Echo) of the destination host.The timeout value, in milliseconds, indicates the maximum amount of time the try should take. If the operation times out before getting an answer, the host is deemed unreachable. A negative value will result in an IllegalArgumentException being thrown. Get functionGetRequest is one of the SNMP commands defined in SNMPv1, which is implemented using Stateless Session Bean within EJB container. This function will be called to perform the value retrieval from a specific object ID in the MIB agent. To do Get function, we utilize an open source SNMP library for Java called Snmp4j. It is used for monitoring feature and simple Get feature. Set functionSetRequest is one of the SNMP commands defined in SNMPv1. It is implemented using Stateless Session Bean within EJB container. This function is used in simple Set tool feature. To execute a Set command, we also utilize Snmp4j library. The following steps mention the preparation of how to accomplish this function. Timer Interval function is necessary to schedule a sequence of actions by giving a certain delay in between. It is also implemented using Stateless Session Bean within EJB container. This timer interval function is basically constructed by 3 sub functions: initiating the timer, cancelling the timer, and providing the timeout actions. Timeout actions in practical can be divided into 2 categories. The first one is, after the first timeout occurs, the system will do the action and then cancel the timer immediately. Static monitoring with Once retrieval method uses this timeout action category. The second one is, after the first timeout occurs, the system will do the action and restarting the timer again and resume for the next timeout, and so on. Timer will be cancelled by executing cancelling timer function. Static monitoring with Continuously-Updated-Value retrieval method, dynamic monitoring, and auto-ping will be the feature using this Timer Interval function.Chart Generator functionChart generator generates the chart presentations on monitoring procedure. This function is implemented in 2 places. The static PNG image is implemented using Servlet within web container, and the real-time monitoring mechanism is implemented using Applet within Applet Class library. The generated chart is a time series domain chart drawn against the retrieval value. We utilize an open source library for Java to draw chart called JFreeChart. There are two kinds of charting presentation available: bar or histogram time series chart, and line time series chart. Chart generator function is constructed by 3 sub functions: one chart generator main method, and 2 private methods. The following description explains chart generator function, together with the code snippets to offer more understanding about its implementation.34Functional Implementation35Network Management and Traffic Analysis for Wireless MANPing functionGet functionSet functionTimer Interval FunctionChart Generator functionJuly, 8 2008PingJuly, 8 200836Network Management and Traffic Analysis for Wireless MANaimed to detect the device statusutilizes isReachable() function call provided by Java.Implemented using Stateless Session Bean within EJB Container.This function call will test whether that address being specified is reachable. Best effort is made by the implementation to try to reach the host, but firewalls and server configuration may block requests resulting in an unreachable status while some specific ports may be accessible. A typical implementation will use ICMP ECHO REQUESTs if the privilege can be obtained, otherwise it will try to establish a TCP connection on port 7 (Echo) of the destination host.The timeout value, in milliseconds, indicates the maximum amount of time the try should take. If the operation times out before getting an answer, the host is deemed unreachable. A negative value will result in an IllegalArgumentException being thrown. 36GetJuly, 8 200837Network Management and Traffic Analysis for Wireless MANUsed for monitoring feature and simple Get feature. Implemented using Stateless Session Bean within EJB container.To perform the value retrieval from a specific object ID in the MIB agent.Utilizing Snmp4j library to create SNMP PDU and execute Get command.37SetJuly, 8 200838Network Management and Traffic Analysis for Wireless MANImplemented using Stateless Session Bean within EJB container.Used for simple Set tool featureTo create SetRequest-PDU and execute Set command, we also utilize Snmp4j library.Set functionSetRequest is one of the SNMP commands defined in SNMPv1. It is implemented using Stateless Session Bean within EJB container. This function is used in simple Set tool feature. To execute a Set command, we also utilize Snmp4j library. The following steps mention the preparation of how to accomplish this function. Timer Interval function is necessary to schedule a sequence of actions by giving a certain delay in between. It is also implemented using Stateless Session Bean within EJB container. This timer interval function is basically constructed by 3 sub functions: initiating the timer, cancelling the timer, and providing the timeout actions. Timeout actions in practical can be divided into 2 categories. The first one is, after the first timeout occurs, the system will do the action and then cancel the timer immediately. Static monitoring with Once retrieval method uses this timeout action category. The second one is, after the first timeout occurs, the system will do the action and restarting the timer again and resume for the next timeout, and so on. Timer will be cancelled by executing cancelling timer function. Static monitoring with Continuously-Updated-Value retrieval method, dynamic monitoring, and auto-ping will be the feature using this Timer Interval function.Chart Generator functionChart generator generates the chart presentations on monitoring procedure. This function is implemented in 2 places. The static PNG image is implemented using Servlet within web container, and the real-time monitoring mechanism is implemented using Applet within Applet Class library. The generated chart is a time series domain chart drawn against the retrieval value. We utilize an open source library for Java to draw chart called JFreeChart. There are two kinds of charting presentation available: bar or histogram time series chart, and line time series chart. Chart generator function is constructed by 3 sub functions: one chart generator main method, and 2 private methods. The following description explains chart generator function, together with the code snippets to offer more understanding about its implementation.38Timer IntervalJuly, 8 200839Network Management and Traffic Analysis for Wireless MANTo schedule a sequence of actions by giving a certain delay in between.Implemented using Stateless Session Bean within EJB container.Constructed by 3 sub functions: initiating timer, cancelling timer, timeout actions. Used for dynamic monitoring and Auto-ping feature.Timeout actions in practical can be divided into 2 categories. The first one is, after the first timeout occurs, the system will do the action and then cancel the timer immediately. Static monitoring with Once retrieval method uses this timeout action category. The second one is, after the first timeout occurs, the system will do the action and restarting the timer again and resume for the next timeout, and so on. Timer will be cancelled by executing cancelling timer function. Static monitoring with Continuously-Updated-Value retrieval method, dynamic monitoring, and auto-ping will be the feature using this Timer Interval function.39Chart GeneratorJuly, 8 200840Network Management and Traffic Analysis for Wireless MANGenerates the chart presentations on monitoring procedure.Utilizing JFreeChart library. Two kinds of charting presentation available: bar or histogram time series chart, and line time series chart. Implemented in:Servlet within web container: for Static PNG imageApplet within Applet Class Library: for real monitoringThe chart is a time series domain chart drawn against the retrieval valueChart generator function is constructed by 3 sub functions: one chart generator main method, and 2 private methods. 40WiMAX System Deployment and Management 41Network Management and Traffic Analysis for Wireless MANWiMAX Network DeploymentManagement ScenarioNetwork Element RegistrationMIB ExtractionTraffic Generation PlanNMS Demonstration

July, 8 2008WiMAX Network DeploymentJuly, 8 200842Network Management and Traffic Analysis for Wireless MAN

It comprises a WiMAX Base Station (WiMAX-BS) connecting with 2 WiMAX Subscriber Station (WiMAX-SS). WiMAX-BS is connected to the outside Internet world through its Ethernet interface. The connection between BS and SS is using Wireless MAN channel medium based on IEEE 802.16. Each WiMAX-SS is connected through cable to one Access Point 802.11. Access Point may have a number of 802.11 subscriber stations like notebooks. NMS would be installed in a PC Server. NMS through this PC polls the MIB-SNMP agent on every network element for network management and monitoring purpose.42Network Element RegistrationJuly, 8 200843Network Management and Traffic Analysis for Wireless MANDevice TypeDevice NameIP AddressUpper Level GatewayWiMAX-BSProxim-BS140.124.183.210None WiMAX-SSProxim-SS1140.124.183.212140.124.183.210WiMAX-SSProxim-SS2140.124.183.214140.124.183.210APLinksys-AP1140.124.183.216140.124.183.212APLinksys-AP2140.124.183.217140.124.183.214ClientUser Client140.124.144.216NoneClientLab-NB1-1140.124.183.xxx140.124.183.216ClientLab-NB1-2140.124.183.xxx140.124.183.216ClientLab-NB2-1140.124.183.xxx140.124.183.217ClientLab-NB2-2140.124.183.xxx140.124.183.217Our WiMAX network main system comprises a WiMAX Base Station (WiMAX-BS) connecting with 2 WiMAX Subscriber Station (WiMAX-SS). WiMAX-BS is connected to the outside Internet world through its Ethernet interface. The connection between BS and SS is using WiMAX signal based on IEEE 802.16. Each WiMAX-SS is connected through cable to one Access Point 802.11. So there are two access points deployed in this scenario, and both may have a number of 802.11 subscriber stations like notebooks. Our NMS would be installed in a PC Server. NMS through this PC polls the MIB-SNMP agent on every network element for network management and monitoring purpose.43MIB-IIJuly, 8 2008Network Management and Traffic Analysis for Wireless MAN44

OID: 1.3.6.1.2.1wmanIfMib is defined under this branchWe see that we miss branch no. 9. It was originally defined in MIB-I reserved for CMOT (OSI management over TCP) group. But as we know that CMOT is now historic.

Transmission group (10) is just a placeholder. It doesnt have any variable. But It allows us to put transmission MIBs under.

SNMP (11) was new in the MIB-II.44MIB-II Groups in a Protocol StackJuly, 8 2008Network Management and Traffic Analysis for Wireless MAN45

SYSTEMTRANSMISSIONINTERFACESAT (Address Translation) is ARP: mapping IP address with MAC address.Interfaces are abstraction of transmission protocol below, and just count the generic things like no. of packets coming in and no. of packets going out. Not count the collision.45IEEE Std 802.16f-2005 MIBJuly, 8 200846Network Management and Traffic Analysis for Wireless MANwmanIfMib = 1.3.6.1.2.1.10.184wmanIfMibObjects = 1.3.6.1.2.1.10.184.1wmanIfBsObjects (1)wmanIfSsObjects (2)wmanIfCommonObjects (3)wmanIfBsPacketCswmanIfBsCpswmanIfBsPkmObjectswmanIfBsNotificationwmanIfBsPhywmanIfSsPkmObjectswmanIfSsNotificationwmanIfSsPhy

wmanIfCmnPacketCswmanIfCmnCpswmanIfCmnPkmObjects

wmanIfMibConformance = 1.3.6.1.2.1.10.184.2wmanIfMibGroups (1)wmanIfMibCompliances (2)Our WiMAX network main system comprises a WiMAX Base Station (WiMAX-BS) connecting with 2 WiMAX Subscriber Station (WiMAX-SS). WiMAX-BS is connected to the outside Internet world through its Ethernet interface. The connection between BS and SS is using WiMAX signal based on IEEE 802.16. Each WiMAX-SS is connected through cable to one Access Point 802.11. So there are two access points deployed in this scenario, and both may have a number of 802.11 subscriber stations like notebooks. Our NMS would be installed in a PC Server. NMS through this PC polls the MIB-SNMP agent on every network element for network management and monitoring purpose.46MIB ExtractionJuly, 8 200847Network Management and Traffic Analysis for Wireless MANObject IDObject NameSyntaxMax-AccessApplicability1.3.6.1.2.1.2.2.1.2.x1ifDescrOCTET-STRINGREAD-ONLYAll1.3.6.1.2.1.2.2.1.5.x1ifSpeedGauge32READ-ONLYAll1.3.6.1.2.1.2.2.1.10.x1ifInOctetsCounter32READ-ONLYAll1.3.6.1.2.1.2.2.1.11.x1ifInUcastPktsCounter32READ-ONLYAll1.3.6.1.2.1.2.2.1.12.x1ifInNUcastPktsCounter32READ-ONLYAll1.3.6.1.2.1.2.2.1.14.x1ifInErrorsCounter32READ-ONLYAll1.3.6.1.2.1.2.2.1.16.x1ifOutOctetsCounter32READ-ONLYAll1.3.6.1.2.1.2.2.1.17.x1ifOutUcastPktsCounter32READ-ONLYAll1.3.6.1.2.1.2.2.1.18.x1ifOutNUcastOctetsCounter32READ-ONLYAll1.3.6.1.2.1.4.9ipInDeliversCounter32READ-ONLYAll1.3.6.1.2.1.4.10ipOutRequestsCounter32READ-ONLYAll1.3.6.1.2.1.6.10tcpInSegsCounter32READ-ONLYAll1.3.6.1.2.1.6.11tcpOutSegsCounter32READ-ONLYAll1.3.6.1.2.1.7.1udpInDatagramsCounter32READ-ONLYAll1.3.6.1.2.1.7.4udpOutDatagramsCounter32READ-ONLYAllOur WiMAX network main system comprises a WiMAX Base Station (WiMAX-BS) connecting with 2 WiMAX Subscriber Station (WiMAX-SS). WiMAX-BS is connected to the outside Internet world through its Ethernet interface. The connection between BS and SS is using WiMAX signal based on IEEE 802.16. Each WiMAX-SS is connected through cable to one Access Point 802.11. So there are two access points deployed in this scenario, and both may have a number of 802.11 subscriber stations like notebooks. Our NMS would be installed in a PC Server. NMS through this PC polls the MIB-SNMP agent on every network element for network management and monitoring purpose.47Management ScenarioJuly, 8 200848Network Management and Traffic Analysis for Wireless MAN

48Traffic GenerationJuly, 8 200849Network Management and Traffic Analysis for Wireless MANQoS Service Class: UGS, rtPS, nrtPS, Best EffortModulation: BPSK, QPSK, 16QAM, 64QAMDestination: Unicast, Broadcast/MulticastTraffic Intensity: light load, heavy loadData flow: Uplink (UL), Downlink (DL)Data Traffic:UGS: VoIP, T1/E1 orATM CBRrtPS: MPEG video, VoIP, video conferencenrtPS: video and audio streamingBE: internet application(web browsing), email, FTP

UGS: Efektif utk layanan yang sensitif terhadap througput, latency dan jitter seperti layanan pada TDM (Time Division Multiplexing).rtPS: Efektif untuk layanan yang sensitif terhadap throughput dan latency namun dengan toleransi yang lebih longgar bila dibandingkan dengan UGS.nrtPS: Efektif untuk aplikasi yang membutuhkan throughput yang intensif dengan garansi minimal pada latency-nya. BE: Untuk trafik yang tidak membutuhkan jaminan kecepatan data (best effort) dan tidak ada jaminan (requirement) pada rate atau delay-nya.

49NMS Demonstration50Network Management and Traffic Analysis for Wireless MANJuly, 8 2008Remaining TasksJuly, 8 200851Network Management and Traffic Analysis for Wireless MANCarry out the traffic generation planTraffic analysis for self-similar existence in our test-bed networkImproving the Network Management Station (NMS)Our WiMAX network main system comprises a WiMAX Base Station (WiMAX-BS) connecting with 2 WiMAX Subscriber Station (WiMAX-SS). WiMAX-BS is connected to the outside Internet world through its Ethernet interface. The connection between BS and SS is using WiMAX signal based on IEEE 802.16. Each WiMAX-SS is connected through cable to one Access Point 802.11. So there are two access points deployed in this scenario, and both may have a number of 802.11 subscriber stations like notebooks. Our NMS would be installed in a PC Server. NMS through this PC polls the MIB-SNMP agent on every network element for network management and monitoring purpose.51ConclusionNetwork Management Station (NMS) has been developed successfully. However some features has not yet been implemented. NMS provides configurable system to extend the management flexibility.NMS can be deployed appropriately into our test-bed network.Traffic generation plan has been defined and ready to carry on.Traffic analysis will come out later after the data traffic collection.July, 8 2008Network Management and Traffic Analysis for Wireless MAN5252ReferencesHwang, You-Sun. Kim, Eung-Bae. An Architecture of SNMP-based Network Management of the Broadband Wireless Access System. IEEE, 2003Kantorovitch, J. Mahonen, P. Case Studies and Experiments of SNMP in wireless Networks. IEEE, 2002Ke, Kai-Wei. Wu, Ho-Ting. Tsai, Chen-Nien. Lin, Wen-Chi. WLAN Self-Similar Traffic and Impact to CSMA/CA Performance. National Science Council, 200XLeland, Will E. Taqqu, Murad S. Willinger, Walter. Wilson, Daniel V. On the Self-Similar Nature of Ethernet Traffic. Proceeding of ACM SIGCOMM 94, 1993Aiko Pras, (2000). Internet Management Protocol, http://www.simpleweb.org . Centre for Telematics and Information Technology, University of Twente, Netherland.Gilbert Held, (2000). Managing TCP/IP Networks: Technique, Tools and Security Consideration. John Wiley&Sons Ltd.http://java.sun.com/javaee/5/docs/tutorial/doc/July, 8 200853Network Management and Traffic Analysis for Wireless MANITU-T = International Telecommunication Union Telecommunication Division53User

Data

+getId() : Long+setId(in id : Long) : void+getIpAddress() : String+setIpAddress(in ipAddress : String) : void+getName() : String+setName(in name : String) : void

-id : Long-ipAddress : String-name : String-type : String-deviceStatus : Boolean-monitorStatus : Boolean-snmpVersion : int-snmpPort : int-communityWrite : String-communityRead : String

AgentEntity+getId() : Long+setId(in id : Long) : void+getName() : String+setName(in name : String) : void+getSyntax() : String+setSyntax(in syntax : String) : void

-id : Long-oid : String-name : String-syntax : String-maxaccess : String-description : String-retrievalMethod : String-asDefault : Boolean-intervalRetrieval : int-enumeration : Boolean

ObjectEntity+getId() : Long+setId(in id : Long) : void+equals(in object : Object) : Boolean

-id : Long

AgentObjectEntity+getId() : Long+setId(in id : Long) : void+getInstanceValue() : int+setInstanceValue(in value : int) : void+getMeaning() : String+setMeaning(in meaning : String) : void

-id : Long-instanceValue : int-meaning : String

EnumInstanceEntity+getId() : Long+setId(in id : Long) : void+getMoment() : Long+setMoment(in moment : Long) : void+getInstanceValue() : String+setInstanceValue(in value : String) : void

-id : Long-moment : Long-retrievalValue : String

MonitoringEntity

-agentEntity

0..*

1

0..*

-objectEntity

1

1

-gateway

0..1

1

-objectEntity

0..*

-agentObjectEntity

0..*

1

Data

Browser

Database

Session Beans

Entity Beans

Servlets

JSP Pages

Java EE Server

Web Container

EJB Container

Client

Applets

Class Library

Header

Footer

Content

Content

Menu

Content

Content