show voice port - Tecnológico de Costa Rica
show voice port - Tecnológico de Costa Rica show voice port - Tecnológico de Costa Rica
Managing System Performance This chapter describes the basic tasks that you can perform to manage the general system performance. For a complete description of the performance management commands in this chapter, refer to the “Performance Management Commands” chapter of the Configuration Fundamentals Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online. System Performance Management Task List Perform any of the tasks in the following sections to manage system performance: • Set the Interval for Load Data • Limit TCP Transactions • Configure Switching and Scheduling Priorities • Establish Queueing and Congestion Strategies • Configure Generic Traffic Shaping • Modify the System Buffer Size In addition, most chapters in this guide include performance tasks specific to the chapter content, and the Internetworking Design Guide includes detailed information on performance issues that arise when designing a network. See the “Performance Management Examples” section at the end of this chapter for examples. Set the Interval for Load Data You can change the period of time over which a set of data is used for computing load statistics. Decisions, such as dial backup decisions, are dependent on these statistics. If you decrease the load interval, the average statistics are computed over a shorter period of time and are more responsive to bursts of traffic. To change the length of time for which a set of data is used to compute load statistics, perform the following task in interface configuration mode: Task Command Set the length of time for which data is used for load calculations. load-interval seconds Managing System Performance FC-357
Limit TCP Transactions Limit TCP Transactions When using a standard TCP implementation to send keystrokes between machines, TCP tends to send one packet for each keystroke typed, which can use up bandwidth and contribute to congestion on larger networks. John Nagle’s algorithm (RFC 896) helps alleviate the small-packet problem in TCP. The first character typed after connection establishment is sent in a single packet, but TCP holds any additional characters typed until the receiver acknowledges the previous packet. Then the second, larger packet is sent, and additional typed characters are saved until the acknowledgment comes back. The effect is to accumulate characters into larger chunks, and pace them out to the network at a rate matching the round-trip time of the given connection. This method is usually good for all TCP-based traffic. However, do not enable the Nagle slow packet avoidance algorithm if you have XRemote users on X Window sessions. By default, the Nagle algorithm is not enabled. To enable the Nagle algorithm and thereby reduce TCP transactions, perform the following task in global configuration mode: Task Command Enable the Nagle slow packet avoidance algorithm. service nagle Configure Switching and Scheduling Priorities The normal operation of the network server allows the switching operations to use as much of the central processor as is required. If the network is running unusually heavy loads that do not allow the processor the time to handle the routing protocols, you might need to give priority to the system process scheduler. To do so, perform the following task in global configuration mode: Task Command Define the maximum amount of time that can scheduler interval milliseconds elapse without running the lowest-priority system processes. To change the amount of time that the CPU spends on fast switching and process level operations on the Cisco 7200 series and Cisco 7500 series, perform the following task in global configuration mode: Task Command For the Cisco 7200 series and Cisco 7500 series, change the default time the CPU spends on process tasks and fast switching. Caution Cisco recommends that you do not change the default values of the scheduler allocate command. FC-358 Configuration Fundamentals Configuration Guide scheduler allocate network-microseconds process-microseconds
- Page 137 and 138: Configuring FXS Interfaces Configur
- Page 139 and 140: Configuring FXS Interfaces 18 Voice
- Page 141 and 142: Configuring FXS Interfaces Wild Car
- Page 143 and 144: Configuring FXS Interfaces 22 Voice
- Page 145 and 146: Configuring FXO Interfaces Configur
- Page 147 and 148: Configuring E&M Interfaces Configur
- Page 149 and 150: Configuring E&M Interfaces 28 Voice
- Page 151 and 152: List of Terms List of Terms This se
- Page 153 and 154: Cisco Connection Online Cisco Conne
- Page 155 and 156: CHAPTER Configuring Voice over IP f
- Page 157 and 158: Prerequisites Tasks Prerequisites T
- Page 159 and 160: Configuration Tasks To configure Vo
- Page 161 and 162: Configure RSVP for Voice Enable RSV
- Page 163 and 164: You should configure Multilink PPP
- Page 165 and 166: Enable RTP Header Compression on a
- Page 167 and 168: Frame Relay for Voice over IP Confi
- Page 169 and 170: Table 2-1 Sample Number Expansion T
- Page 171 and 172: Figure 2-5 Outgoing Calls from the
- Page 173 and 174: Configure POTS Peers To configure t
- Page 175 and 176: Configure VoIP Peers Verify Tips Co
- Page 177 and 178: • Call progress tone using the cp
- Page 179 and 180: Fine-Tune FXO and FXS Voice Ports T
- Page 181 and 182: Validation Tips Step Command Purpos
- Page 183 and 184: Step Command Purpose Fine-Tune E&M
- Page 185 and 186: Configure CODEC and VAD for Dial Pe
- Page 187: Step 8 Click the Up button until th
- Page 191 and 192: Establish Queueing and Congestion S
- Page 193 and 194: Establish Queueing and Congestion S
- Page 195 and 196: Establish Queueing and Congestion S
- Page 197 and 198: Modify the System Buffer Size To di
- Page 199 and 200: Performance Management Examples The
- Page 201 and 202: 4-2 • output attenuation • port
- Page 203 and 204: Command Syntax Conventions Command
- Page 205 and 206: acc-qos 4-6 Example The following e
- Page 207 and 208: answer-address 4-8 Example The foll
- Page 209 and 210: comfort-noise comfort-noise 4-10 To
- Page 211 and 212: cptone cptone 4-12 To configure a v
- Page 213 and 214: description description To include
- Page 215 and 216: destination-pattern 4-16 Related Co
- Page 217 and 218: dial-peer voice dial-peer voice 4-1
- Page 219 and 220: echo-cancel coverage echo-cancel co
- Page 221 and 222: echo-cancel enable echo-cancel enab
- Page 223 and 224: fax-rate fax-rate 4-24 To establish
- Page 225 and 226: icpif icpif 4-26 To specify the Cal
- Page 227 and 228: input gain input gain To configure
- Page 229 and 230: ip udp checksum ip udp checksum 4-3
- Page 231 and 232: non-linear non-linear 4-32 To enabl
- Page 233 and 234: operation operation To select a spe
- Page 235 and 236: port port 4-36 To associate a dial
- Page 237 and 238: eq-qos req-qos 4-38 To specify the
Limit TCP Transactions<br />
Limit TCP Transactions<br />
When using a standard TCP implementation to send keystrokes between machines, TCP tends to<br />
send one packet for each keystroke typed, which can use up bandwidth and contribute to congestion<br />
on larger networks.<br />
John Nagle’s algorithm (RFC 896) helps alleviate the small-packet problem in TCP. The first<br />
character typed after connection establishment is sent in a single packet, but TCP holds any<br />
additional characters typed until the receiver acknowledges the previous packet. Then the second,<br />
larger packet is sent, and additional typed characters are saved until the acknowledgment comes<br />
back. The effect is to accumulate characters into larger chunks, and pace them out to the network at<br />
a rate matching the round-trip time of the given connection. This method is usually good for all<br />
TCP-based traffic. However, do not enable the Nagle slow packet avoidance algorithm if you have<br />
XRemote users on X Window sessions.<br />
By <strong>de</strong>fault, the Nagle algorithm is not enabled. To enable the Nagle algorithm and thereby reduce<br />
TCP transactions, perform the following task in global configuration mo<strong>de</strong>:<br />
Task Command<br />
Enable the Nagle slow packet avoidance<br />
algorithm.<br />
service nagle<br />
Configure Switching and Scheduling Priorities<br />
The normal operation of the network server allows the switching operations to use as much of the<br />
central processor as is required. If the network is running unusually heavy loads that do not allow<br />
the processor the time to handle the routing protocols, you might need to give priority to the system<br />
process scheduler. To do so, perform the following task in global configuration mo<strong>de</strong>:<br />
Task Command<br />
Define the maximum amount of time that can scheduler interval milliseconds<br />
elapse without running the lowest-priority system<br />
processes.<br />
To change the amount of time that the CPU spends on fast switching and process level operations on<br />
the Cisco 7200 series and Cisco 7500 series, perform the following task in global configuration<br />
mo<strong>de</strong>:<br />
Task Command<br />
For the Cisco 7200 series and Cisco 7500 series,<br />
change the <strong>de</strong>fault time the CPU spends on<br />
process tasks and fast switching.<br />
Caution Cisco recommends that you do not change the <strong>de</strong>fault values of the scheduler allocate<br />
command.<br />
FC-358 Configuration Fundamentals Configuration Gui<strong>de</strong><br />
scheduler allocate network-microseconds<br />
process-microseconds