Keeping track of the current status of pipelines is important,
because if a pipeline is down, part of the system is down. Many organizations
check pipelines through the Pipeline Status tab in
the Configuration Console, because it displays the latest pipeline status
and statistics based on an automatic system poll every 60 seconds. But you
can use a command line to check the status of a particular pipeline or all
pipelines on a particular pipeline node. (The command line check provides
only pipeline status, not pipeline performance statistics.)
Before you begin:
- An SNMP agent must be installed and configured on the pipeline node running
the pipeline.
- The SNMP agent must be started and running on the pipeline node, using
the same port number as configured during pipeline installation. This SNMP
agent port number is system-wide, not per pipeline node. The default SNMP
port number is 13516, but you can locate the SNMP agent port number configured
in the server.xml file located on each pipeline node.
Procedure:
- From a command line on the pipeline node, complete one of the following
steps:
- To check the status of all pipelines on this pipeline node, type the
following commandpipeline -l
- To check the status of a particular pipeline on this pipeline node,
type the following command pipeline -n pipelinename -l
where pipelinename is the unique name of the pipeline
you want to check. Note: The name you type must match the name used to start
the pipeline.
- Press Enter.
The system returns one of the following statuses for each pipeline:
- Running for each currently active
pipeline.
- Stopped for each currently inactive
pipeline.
For example, to check the status of pipeline08, you would
type the following command: pipeline -n pipeline08 -l
What to do next:
If the status of a pipeline is unexpectedly listed as Stopped,
you may want to use the troubleshooting topics to discover the reason.