Flow Subscription MP/Configuration
From GEANT2-JRA1 Wiki
Flow subscription mp navigation
Contents |
[edit]
netflow configuration
you should configure a flow exporter (like a router) to export netflow data to the machine where the service is deployed. If you don't have a flow exporter you can use softflowd to generate your own netflow from ethernet.
[edit]
Service Configuration Options
Change the following should be enough:
- LS location where the service should register itself
- Add entries for all you flow exporters (examples are included).
Likely your are finished now, but maybe you need to modify any other things that are nog correct (for example zebedee path)
| Name | Description | Default value |
|---|---|---|
|
[edit] Service Type | ||
| service.r.type | mp | |
| service.r.service_type | mp | |
| service.r.service_name | Java flowSubscription MP | |
| service.r.ls_url | http://localhost:8080/XML-LS-1.1.2/services/LookupService | |
| service.r.access_point | http://sonar1.amsterdam.surfnet.nl:8080/flowsubscription-mp/services/flowsubscriptionMeasurementArchiveService | |
|
[edit] Measurement Archive general properties | ||
| service.mp.class_name | org.perfsonar.service.measurementPoint.flowsubscription.FlowTypeMPServiceEngine | |
| service.mp.message_types | SubscriptionRequest,UnSubscriptionRequest,SubscriptionKeepaliveRequest | |
| service.mp.conf_file | config.xml | |
|
[edit] Logger properties | ||
| service.log.log4j.config | /perfsonar/conf/log4j.properties | |
|
[edit] nmwg properties | ||
| service.sax_parser.config | /perfsonar/conf/objects.config | |
|
[edit] LS Registration properties | ||
| component.registrator.scheduler_component | ma_scheduler | |
| component.registrator.interval | 30000 | |
| service.ls.service_content_type | context | |
|
[edit] Authentication properties | ||
| service.as.authn_active | off | |
| service.as.authn_for_msg_types | SetupDataRequest | |
| service.as.point | http://homer.rediris.es:8080/perfSONAR-AS/services/AuthService | |
|
[edit] Flow properties | ||
| service.mp.flow.inPort | port (and up) that the zebedee client should receive data at | 11110 |
| service.mp.flow.betweenPort | port (and up) that the zebedee client should use for sending data (and listen for reverse connection setup from server) | 22220 |
| service.mp.flow.netflow_versions | which versions of netflow can we export | netflow_v9,netflow_v5,sflow |
| service.mp.flow.transport_protocols | what t.p. for netflow data do we support | udp,tcp,sctp,pr-sctp |
| service.mp.flow.sample_rate | at what rate is the netflow data sampled | 100 |
| service.mp.flow.max_conn | maximum client netflow subscriptions | 20 |
| service.mp.flow.router.0.name | flow exporter number 1 name | arthur |
| service.mp.flow.router.0.enabled | flow exporter number 1 enabled or not | true |
| service.mp.flow.router.0.address | flow exporter number 1 IP address | 145.145.127.1 |
| service.mp.flow.router.0.flowport | On what port is the exported flow data received | 29001 |
| service.mp.flow.router.0.interfaces | What interfaces does the flow exporter have | 1,2,3,4,5,6 |
| service.mp.flow.router.x.name | flow exporter number X name | ford |
| service.mp.flow.router.x.enabled | flow exporter number X enabled or not | true |
| service.mp.flow.router.x.address | flow exporter number X IP address | 145.145.127.2 |
| service.mp.flow.router.x.flowport | On what port is the exported flow data received | 29002 |
| service.mp.flow.router.x.interfaces | What interfaces does the flow exporter have | 1,2,3,4,5,6 |
| service.mp.flow.zebedee | /usr/bin/zebedee | |
| service.mp.flow.nfdump | /usr/local/bin/nfdump | |
| service.mp.flow.nfcapd | /usr/local/bin/nfcapd | |
| service.mp.flow.nfreplay | /usr/local/bin/nfreplay | |
