wiki:Old/WiMAX/17
close Warning: Can't synchronize with repository "(default)" (/common/SVN/wimax does not appear to be a Subversion repository.). Look in the Trac log for more information.

Version 20 (modified by seskar, 8 years ago) ( diff )

9. WiMAX RF Aggregate Manager Service

wimaxrf is an Aggregate Manager (AM) that is used to configure and control WIMAX (Basestation) RF Section.

WiMAX RF Aggregate Manager

    Installation

       apt-get install omf-wimaxrf-aggmgr-5.2
    

    Please confirm that the most current packages of the software are installed. You can check it
    with the following commands.

    dpkg -l | egrep 'omf-|asn-gw|click'
    

    Current version for omf-common-5.2 is 4 and
    Current version for omf-aggmgr-5.2 is 6

    ii  omf-aggmgr-5.2                      ubuntu6                                  OMF Aggregate Manager
    ii  omf-common-5.2                      ubuntu4                                  Common ruby classes for OMF
    

    In case of wrong version please remove the two packages and reinstall them.

    apt-get --purge remove omf-aggmgr-5.2 omf-common-5.2
    apt-get install omf-aggmgr-5.2
    dpkg -l | grep omf-
    

    Configuration

    The configuration file for wimxrf AM is in the same location as for all the other OMF AM services in /etc/omf-agggr-5.2/available/wimaxrf.yaml. The configuration file consists of multiple section sections relating to different components of the services.

    Default parameter values are shown in []; Bold font indicates mandatory parameters.

    wimaxrf:
    

    Databasee section

      database:
       dbFile: '/db/wimaxrf.db'
      reset:
       file: '/defaults/reset.xml'
    
    • file: location of the default configuration [none]. The file is an XML file that containes default BS parameters and is used with /default wimaxrf service

    asngw: Section

      asngw:
       if: eth1
       ip: 10.3.0.71
       rcvport: 54321
       sndport: 54321
       id: ASNGW000
       tecnh: 3
       dsc: IP-Config-Mgmt
    

    bs: section

      bs: 
       ip: 10.3.0.1
       mask: 255.255.0.0
       bsid: 44:51:DB:00:00:01 
       frequency: 2590000
       stats:
         localoml:
           :omlServer: oml.orbit-lab.org
           interval: 10
         globaloml:
           :omlServer: oml.orbit-lab.org
    

    localoml section is used to specify OML server that will receive client related measurements while globaloml server section is used to configure parameters that are used by global GENI-wide logging process (should point at oml.orbit-lab.org until GENI gmoc takes over reporting function). Both are configured with two parameters:

    • :omlServer:: value is the hostname of your OML server. If you wish to install the oml2 server on your host
      locally, please do so by the following commands.
        apt-get install oml2-server 
      

    and then point the omlServer value to your localhost.

    • interval:: collection itnerval in seconds (defaults: [10] for localoml and [300] for globaloml)

    datapath: section

    Default interface for datapath outside endpoint:

      datapath:
        datapathif: eth0
    

    Each of the sections in this file should be modified to reflect your deployment configuration (please keep in mind that this is a YAML file and that it depends heavily on spaces and not TABs). Once the configuration file is ready, you have to enable the service by creating the symbolic link in /etc/omf-aggmgr-5.2/enabled:

    ln -s ../available/wimaxrf.yaml
    

    and restarting the OMF aggregate manager service:

    /etc/init.d/omf-aggmgr-5.2 restart
    

    Logging

    OMF aggregate managers have quite extended logging capabilities. Log messages from all of the enabled services are stored in /var/log/omf-aggmgr-5.2.log

    Note: See TracWiki for help on using the wiki.