| Skip Navigation Links | |
| Exit Print View | |
|
Using Virtual Networks in Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Using Virtual Networks in Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
1. Network Virtualization and Resource Management in Oracle Solaris
2. Creating and Administering Virtual Networks in Oracle Solaris
3. Managing Network Resources in Oracle Solaris
4. Monitoring Network Traffic and Resource Usage in Oracle Solaris
Overview of Network Traffic Flow
Commands for Monitoring Traffic Statistics
Gathering Statistics About Network Traffic on Links
Obtaining Network Traffic Statistics on Network Devices
Obtaining Network Traffic Statistics on Lanes
Obtaining Network Traffic Statistics on Link Aggregations
You can use the extended accounting facility to set up network accounting on the system. Network accounting involves capturing statistics about network traffic in a log file. In this manner, you can maintain records of traffic for tracking, provisioning, consolidation, and billing purposes. Later, you can refer to the log file to obtain historical information about network use over a period of time.
To set up network accounting, you use the extended accounting facility's acctadm command. After you have completed setting up network accounting, you use the flowstat command to record traffic statistics.
This section describes the following procedures:
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.
# acctadm [process | task | flow | net]
The extended accounting facility can enable four types of accounting. The optional operands of the acctadm command correspond to these accounting types. You use an operand with the command to configure a specific type of accounting.
Note - Network accounting also applies to flows that are managed by the flowadm and flowstat commands as discussed in Managing Resources on Flows. Therefore, to set up accounting for these flows, use the net option with the acctadm command. Do not use the flow option, which enables flow accounting for IPQoS configurations.
Specifying net displays the status of network accounting. If net is not used, then the status of all four accounting types is displayed.
# acctadm -e extended -f filename net
where filename includes the full path of the log file that will capture network traffic statistics. The log file can be created in any directory that you specify.
# acctadm net
Example 4-4 Setting Up Network Accounting on the System
This example shows how to configure network accounting to capture and display historical traffic information on the system.
First, view the status of all accounting types as follows:
# acctadm
Task accounting: inactive
Task accounting file: none
Tracked task resources: none
Untracked task resources: extended
Process accounting: inactive
Process accounting file: none
Tracked process resources: none
Untracked process resources: extended,host
Flow accounting: inactive
Flow accounting file: none
Tracked flow resources: none
Untracked flow resources: extended
Network accounting: inactive
Network accounting file: none
Tracked Network resources: none
Untracked Network resources: extended
The output shows that network accounting is not active.
Next, enable extended network accounting.
# acctadm -e extended -f /var/log/net.log net
# acctadm net
Net accounting: active
Net accounting file: /var/log/net.log
Tracked net resources: extended
Untracked net resources: none
After you have enabled network accounting, you can use the dlstat and flowstat commands to extract information from the log file. This procedure describes the steps.
Before You Begin
You must enable extended accounting for the network before you can display historical data about the network. Further, to display historical data about traffic on flows, you must first configure flows on the system as explained in Managing Resources on Flows.
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.
# dlstat show-link -h [-a] -f filename [-d date] [-F format] [-s start-time] [-e end-time] [link]
Displays a summary of historical information about resource usage by incoming and outgoing packets on datalinks.
Displays resource usage on all datalinks, including those that have already been deleted after the data capture.
Specifies the log file that was defined when network accounting was enabled with the acctadm command.
Displays logged information for the specified date.
Displays the data in a specific format that can then be plotted for analysis. Currently, gnuplot is the only supported format.
Displays available logged information for a specified date and time range. Use the MM/DD/YYY,hh:mm:ss format. The hour (hh) must use the 24-hour clock notation. If you do not include the date, then data for the specified time range for the current date is displayed.
Displays historical data for a specified datalink. If you do not use this option, then historical network data for all configured datalinks is displayed.
# flowstat -h [-a] -f filename [-d date] [-F format] [-s start-time] [-e end-time] [flow]
Displays a summary of historical information about resource usage by incoming and outgoing packets on configured flows.
Displays resource usage on all configured flows, including those that have already been deleted after the data capture.
Specifies the log file that was defined when network accounting was enabled with the acctadm command.
Displays logged information for the specified date.
Displays the data in a specific format. Currently, gnuplot is the only supported format.
Displays available logged information for a specified date and time range. Use the MM/DD/YYY,hh:mm:ss format. The hour (hh) must use the 24-hour clock notation. If you do not include the date, then data for the specified time range for the current date is displayed.
Displays historical data for a specified flow. If you do not use this option, then historical network data for all configured flows is displayed.
Example 4-5 Displaying Historical Information About Resource Usage on Datalinks
The following example shows historical statistics about network traffic and its use of resources on a specified datalink:
# dlstat show-link -h -f /var/log/net.log net0 LINK DURATION IPACKETS RBYTES OPACKETS OBYTES BANDWIDTH net0 80 1031 546908 0 0 2.44 Kbps
Example 4-6 Displaying Historical Information About Resource Usage on Flows
The following examples show different ways of displaying historical statistics about network traffic on a flow and its use of resources.
The following example displays historical statistics of resource usage by traffic on a flow:
# flowstat -h -f /var/log/net.log FLOW DURATION IPACKETS RBYTES OPACKETS OBYTES BANDWIDTH flowtcp 100 1031 546908 0 0 43.76Kbps flowudp 0 0 0 0 0 0.00Mbps
The following example displays historical statistics of resource usage by traffic on a flow over a given date and time range:
# flowstat -h -s 02/19/2008,10:39:06 -e 02/19/2008,10:40:06 \ -f /var/log/net.log flowtcp FLOW START END RBYTES OBYTES BANDWIDTH flowtcp 10:39:06 10:39:26 1546 6539 3.23 Kbps flowtcp 10:39:26 10:39:46 3586 9922 5.40 Kbps flowtcp 10:39:46 10:40:06 240 216 182.40 bps flowtcp 10:40:06 10:40:26 0 0 0.00 bps
The following example displays historical statistics of resource usage by traffic on a flow over a given date and time range. The information is displayed by using the gnuplot format.
# flowstat -h -s 02/19/2008,10:39:06 -e 02/19/2008,10:40:06 \ -F gnuplot -f /var/log/net.log flowtcp # Time tcp-flow 10:39:06 3.23 10:39:26 5.40 10:39:46 0.18 10:40:06 0.00
|