4.412 rept-stat-iptps
Use this command to display current and peak IPTPS usage for each IPSG / IPGWx linkset in the system or for each link in the IPSG / IPGWx linkset.
Parameters
- history
- This parameter specifies whether to report the history of IP TPS usage data on IPSG linksets for the last 60 seconds.
- link
- The link on the card specified in the loc parameter.
- Range:
- a, a1-a63, b, b1-b63
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have assigned signaling link ports.
- loc
- The IPSG card location for which IP TPS usage data is to be reported.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
rept-stat-iptps
rept-stat-iptps:lsn=lsgw1101
rept-stat-iptps:peakreset=yes
rept-stat-iptps:lsn=lsm2pa1:tpscost=yes
rept-stat-iptps:loc=1305:tpscost=yes
rept-stat-iptps:loc=1305:history=yes
rept-stat-iptps:loc=1305:link=a3:history=yes
Dependencies
If the linksets are not IPGWx or IPSG, then this command cannot be entered.
The specified linkset name must exist in the database.
The history, link, loc, and tpscost parameters can be specified for only IPSG cards.
If the history parameter is specified, then the loc parameter must be specified.
If the tpscost parameter is specified, then the loc or lsn parameter must be specified.
If the loc parameter is specified, then the tpscost, history, or peakreset parameter must be specified.
Only one of the history, tpscost, and peakreset parameters can be specified in the command.
The loc and lsn parameters cannot be specified together in the command.
The specified linkset must be type IPSG.
Notes
Traffic peak data are stored only in OAM memory and are not preserved when the card that is running the OAM boots, or in the case of an active/standby switchover.
IPSG linksets have SLKTPS linksets configured rather than IPTPS. SLKTPS configures the transactions per second for each link assigned to the IPSG linkset as opposed to IPTPS which configures the combined transactions per second for the entire IPGW linkset. For an IPSG linkset, the calculated IP TPS value (shown under the 'CONFIG' column in the report) is made up of the aggregate calculated SLKTPS of all of the provisioned links in the linkset. Non-IPSG hosted links are not counted in the calculation as they do not support SLKTPS.
If a linkset contains a mixture of IPLIMx M2PA and IPSG-M2PA links, then the command does not report any data below the TPS header or raise alarms.
For IPSG-M3UA and IPGWx-M3UA links, the rept-stat-iptps command also counts the received DAUD messages and transmitted SNMs in response to DAUD audits (along with the other transmitted SNMs).
The process of updating the IP TPS counts for DAUD and DAUD response SNMs is:
- Rcv IP TPS count is updated with the total number of valid DAUD messages that are successfully queued for response processing based on the combination of RCs (Routing Contexts) and APCs (Affected Point Codes) received in the M3UA DAUD message.
- In reply to DAUD, based on the response generated (DUNA or (DAVA/DRST + SCON)), Tx IP TPS counts are updated for each RC/APC combination (either the same as the Rcv counts or twice the Rcv counts respectively).
- If no RC is present, then the Tx/Rcv IP TPS is incremented for the associated link corresponding to the lowest PORT ID for IPSG-M3UA links for the same association.
- For IPGWx-M3UA links, Tx/Rcv IP TPS are always incremented on the default PORT Index (since only one link can be configured in IPGWx GPL).
- For IPGWx-M3UA links, Rcv IP TPS count are also updated with the number of valid and non discarded Deviated DAUD message received (since Deviated DAUD always contains single RC and APC combination).
All of the transmitted SNMs are pegged in IPTPS Tx counts and are considered in the TPS algorithms.
Output
The rept-stat-iptps command reports on IPSG and IPGWx
linkset IP TPS. The report includes the following information for the system and for
each IPSG or IPGWx linkset:
- Configured IP TPS alarm threshold
- Configured IP TPS
- Current IP TPS transmit and receive usage for 15 seconds
- Peak IP TPS transmit and receive usage and timestamp for all 15 second periods since last reset
rept-stat-iptps command is enhanced to report derived IP TPS usage
for IPSG linksets.
- Current derived IP TPS transmit and receive usage over a window of 15 seconds
- Peak IP TPS transmit and receive usage and timestamp for all 15 second periods since last reset
- 60 seconds history of the IP TPS transmit and receive usage
- The specified card location indicates an E5-ENET-B/SLIC IPSG card or the links in the specified linkset are hosted on E5-ENET-B or SLIC card,
- the E5-ENET-B IPSG High Throughput feature is turned ON,
- the actual traffic rate running on the ISPG card > 6500 TPS and
- the network configuration or traffic characteristics exceeds optimal configuration limits as shown in Table 4-53.
Table 4-53 Baseline Configuration Changes for the E5-ENET-B Card
| E5-ENET-B Card Baseline Configuration | E5-ENET-B IPSG High Throughput feature OFF | E5-ENET-B IPSG High Throughput feature ON |
|---|---|---|
| TPS | 6500 | 9500 |
| Max RTT (ms) | 120 | 50 |
| Avg. MSU size (bytes) | 0-272 | 0-120 |
| Number of associations/links | 16 | 4 |
| Protocol | M2PA and M3UA | M2PA |
For all other conditions, including the use instead of an E5-ENET-B card, the derived IP TPS values is invalid and is denoted by dashes (---) in the Derived TPS and column.
The following table shows values for Max rsvdslktps and Max maxslktps:
Table 4-54 MaxTPS Per Card
| E5-ENET-B IPSG High Throughput FAK | Max RSVDSLKTPS | Max MAXSLKTPS | ||||
|---|---|---|---|---|---|---|
| E5-ENET-A | E5-ENET-B | SLIC | E5-ENET-A | E5-ENET-B | SLIC | |
| FAK is OFF | 5000 | 6500 | 10000 | 5000 | 6500 | 10000 |
| FAK is ON. | 5000 | 9500 | 10000 | 5000 | 9500 | 10000 |
If the linkset is specified, then the command reports the same information for the individual links in the linkset.
If the peakreset=yes parameter is specified, then the command resets all the stored peak values to the current actual usage for each link, and recalculates linkset and system peaks before reporting usage.
If the linkset is specified with the peakreset=yes parameter, then the command recalculates peaks for the specified linkset and resets all the stored peak values to the current actual usage for each link contained in the linkset before reporting usage.
The peaks for transmit and receive, and for link, and linkset IP TPS may all occur at different times.
The IP TPS value shown in the command may contain one extra MSU if the linkset is specified. Because the alarm calculations are implemented using integer math, rounding may occur at each entity (link, linkset) if the IP TPS value for the entity is not evenly divisible by 15. This could occur when performing an IPTPS report for a linkset that has more than one link configured.
For mixed IPLIMx-M2PA and IPSG-M2PA linksets, the command does not report any data or raise alarms.
IPGW linksets display dashes in the CONFIG/MAX column.
Asterisk sign indicates that parameter (CONFIG/RSVD or CONFIG/MAX) is used to generate TPS alarm for IPSG links/linkset.
This example shows the output for an IPGW linkset:
rept-stat-iptps:lsn=ls1307a
eagle10212 10-04-03 09:38:48 EST EAGLE 42.0.0
IP TPS USAGE REPORT
THRESH CONFIG/ CONFIG/ TPS PEAK PEAKTIMESTAMP
RSVD MAX
--------------------------------------------------------------------------
LSN
ls1307a 100% 10000 --- TX: 4800 5000 03-05-05 09:49:09
RCV: 4850 5000 03-05-05 09:49:09
--------------------------------------------------------------------------
LOC LINK
1307 A 80% 2500 ---- TX: 2399 2500 03-05-05 09:49:09
RCV: 2428 2500 03-05-05 09:49:09
This example shows the output when IPSG and IPGW linksets are included:
rept-stat-iptps
rlghncxa03w 11-03-13 16:20:46 EST EAGLE 44.0.0
IP TPS USAGE REPORT
THRESH CONFIG/ CONFIG/ TPS PEAK PEAKTIMESTAMP
RSVD MAX
--------------------------------------------------------------------------
LSN
ls1303a 100% 500* 500 TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
ls1305a 100% 2500* 5000 TX: 0 10 11-02-29 12:46:37
RCV: 0 10 11-02-29 12:57:52
ls1305i 100% 0* 0 TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
lsitunaa 100% 0* 0 TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
lsitunbb 100% 0* 0 TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
lsituis 100% 0* 0 TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
lsituns 100% 0* 0 TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
lsm2pa1 100% 2500* 6500 TX: 0 10 11-02-29 12:56:07
RCV: 0 10 11-02-29 12:58:07
ls1307a 100% 100 --- TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
ls1315a 100% 4000 --- TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
ls1317i 100% 4000 --- TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
lgipgw 100% 4000 --- TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
lgipgw2 100% 4000 --- TX: 0 0 00-00-00 00:00:00
RCV: 0 0 00-00-00 00:00:00
--------------------------------------------------------------------------
Command Completed.
This example shows the output for an IPSG M3UA linkset:
rept-stat-iptps:lsn=ipsgm3ua
rlghncxa03w 10-04-03 16:20:46 EST EAGLE 42.0.0
IP TPS USAGE REPORT
THRESH CONFIG/ CONFIG/ TPS PEAK PEAKTIMESTAMP
RSVD MAX
---------------------------------------------------------------------------
LSN
IPSGM3UA 100% 4000 10000* TX: 3700 4000 03-05-05 09:49:19
RCV: 3650 4000 03-05-05 09:49:19
---------------------------------------------------------------------------
LOC LINK
1101 A 80% 2000 5000* TX: 1851 2000 03-05-05 09:49:19
RCV: 1801 2000 03-05-05 09:49:19
1201 A 80% 2000 5000* TX: 1849 2000 03-05-05 09:49:19
RCV: 1799 2000 03-05-05 09:49:19
---------------------------------------------------------------------------
This example shows the output for a mixed linkset when IPSG M2PA links are included:
rept-stat-iptps:lsn=ipsgm2pa
rlghncxa03w 10-04-03 16:20:46 EST EAGLE 42.0.0
IP TPS USAGE REPORT
THRESH CONFIG/ CONFIG/ TPS PEAK PEAKTIMESTAMP
RSVD MAX
---------------------------------------------------------------------------
LSN
IPSGM2PA 100% 10000* 20000 TX: 4800 5000 03-05-05 09:49:09
RCV: 4850 5000 03-05-05 09:49:09
---------------------------------------------------------------------------
LOC LINK
1105 A 80% 2500* 5000 TX: 2399 2500 03-05-05 09:49:09
RCV: 2428 2500 03-05-05 09:49:09
1205 A 80% 2500* 5000 TX: 2401 2500 03-05-05 09:49:09
RCV: 2422 2500 03-05-05 09:49:09
1305 A 80% ---- ---- TX: ---- ---- -----------------
RCV: ---- ---- -----------------
2105 A 80% ---- ---- TX: ---- ---- -----------------
RCV: ---- ---- -----------------
---------------------------------------------------------------------------
This example shows the output for an E5-ENET-B IPSG card and displays TPS cost information for a specific location:
rept-stat-iptps:loc=1305:tpscost=yes eagle10212 11-07-20 09:07:34 EST EAGLE 44.0.0
IP TPS USAGE REPORT
Actual Derived Derived PEAK PEAKTIMESTAMP
TPS TPS TPS
--------------------------------------------------------------------------
LOC
1305 Tx: 8000 8240 8500 11-08-03 10:00:25
Rcv:8000 8240 8600 11-08-03 10:10:25
--------------------------------------------------------------------------
LSN LINK
lsm2pa1 A Tx: 4000 4120 4380 11-08-03 10:00:25
Rcv:4000 4120 4120 11-08-03 10:10:25
lsm2pa2 B Tx: 4000 4120 4120 11-08-03 10:00:25
Rcv:4000 4120 4480 11-08-03 10:10:25
--------------------------------------------------------------------------
Command Completed.This example shows the output for an E5-ENET-B IPSG card and displays TPS cost information for a linkset:
rept-stat-iptps:lsn=lsm2pa1:tpscost=yes eagle10212 11-07-20 09:07:34 EST EAGLE 44.0.0
IP TPS USAGE REPORT
Actual Derived Derived PEAK PEAKTIMESTAMP
TPS TPS TPS
--------------------------------------------------------------------------
LSN
lsm2pa1 Tx: 13400 14430 14675 11-08-03 10:00:25
Rcv:14200 15000 15320 11-08-03 10:10:25
--------------------------------------------------------------------------
LOC LINK
1305 A Tx: 6800 7150 7250 11-08-03 10:00:25
Rcv:7000 7340 7550 11-08-03 10:10:25
1306 B Tx: 6600 7280 7425 11-08-03 10:00:25
Rcv:7200 7660 7770 11-08-03 10:10:25
--------------------------------------------------------------------------
Command Completed.This example shows the output for an E5-ENET-B IPSG card and displays history information:
rept-stat-iptps:loc=1111:history=yes
eagle10212 12-01-18 09:07:34 EST EAGLE5 44.0.0
IP TPS USAGE HISTORY REPORT for Card LOC=1111
SAMPLE# SLK ACTUAL DERIVED AVG AVG TX AVG RX
TX RX TX RX RTT MSU SIZE MSU SIZE
--------------------------------------------------------------------------
1 A 1702 0 2331 --- 7 292 0
A1 3403 3403 4662 4662 14 292 292
--------------------------------------------------------------------------
.
.
.
SAMPLE# SLK ACTUAL DERIVED AVG AVG TX AVG RX
TX RX TX RX RTT MSU SIZE MSU SIZE
--------------------------------------------------------------------------
60 A 1702 0 2331 --- 7 292 0
A1 3403 3403 4662 4662 14 292 292
--------------------------------------------------------------------------
Command Completed.The following example reportsThis example shows the output for history information for link A of an E5-ENET-B IPSG card:
rept-stat-iptps:loc=1111:port=a:history=yes
eagle10212 12-01-18 09:07:34 EST EAGLE5 44.0.0
IP TPS USAGE HISTORY REPORT for Card LOC=1111 PORT=A
SAMPLE# SLK ACTUAL DERIVED AVG AVG TX AVG RX
TX RX TX RX RTT MSU SIZE MSU SIZE
--------------------------------------------------------------------------
1 A 3403 0 4662 --- 8 292 0
--------------------------------------------------------------------------
.
.
.
SAMPLE# SLK ACTUAL DERIVED AVG AVG TX AVG RX
TX RX TX RX RTT MSU SIZE MSU SIZE
--------------------------------------------------------------------------
60 A 3403 0 4662 --- 9 292 0
--------------------------------------------------------------------------
Command Completed.Legend
- LSN—Linkset name
- THRESH—Threshold at which an alarm will be generated to indicate that the actual linkset TPS is approaching the configured linkset iptps value (lsusealm value as shown in
rtrv-lsoutput). - CONFIG/RSVD—Reserved TPS for the linkset
- CONFIG/MAX—Maximum TPS for the linkset
- TPS—Current transmit (TX) and receive (RCV) TPS for 15 seconds
- PEAK—Peak transmit (TX) and receive (RCV) TPS usage for all 15 second periods since the last peak reset
- PEAKTIMESTAMP—Date and time that the displayed transmit and receive TPS peaks occurred
- LOC—Location of the card that contains a displayed link in the linkset
- PORT—A signaling link in the linkset
- THRESH—The slkusealm value as shown in
rtrv-lsoutput - CONFIG/RSVD—Reserved TPS for each link in the linkset. (-----). There is no configurable TPS for links.
- CONFIG/MAX—Maximum TPS for each link in the linkset. (-----). There is no configurable TPS for links.
- TPS—Current transmit (TX) and receive (RCV) TPS for 15 seconds
- PEAK—Peak transmit (TX) and receive (RCV) TPS usage for all 15 second periods since the last peak reset
- PEAKTIMESTAMP—Date and time that the displayed transmit and receive TPS peaks occurred
-
Derived TPS—Derived transmit (TX) and receive (RCV) TPS for 15 seconds
-
Derived Peak TPS—Derived peak transmit (TX) and receive (RCV) TPS usage for all 15 second periods since the last peak reset
-
Actual Tx/Rx—Actual transmit (TX) and receive (RCV) TPS for 60 seconds
-
Derived Tx/Rx—Actual transmit (TX) and receive (RCV) TPS for 60 seconds
-
Avg TX MSU Size—Average transmitted MSU size
-
Avg RTT—Average round trip time
-
Avg RX MSU Size—Average received MSU size
Related Topics