简介
本文档介绍监控协议/用户在控制和用户平面分离(CUPS)用户平面(UP)上关于选项34呼叫搜索空间(CSS)数据的行为,其中行为从传统非CUPS系统更改。
问题
在传统非CUPS中,当为监控协议/用户启用选项34(CSS数据)时,将打印发往增强计费服务(ECS)模块或从该模块发送的数据包。
MONITOR GLOBAL PROTOCOLS:
11 - SNMP 21 - L2TP (Admin only)
12 - RADIUS Authentication (Admin only) 22 - L2TPMGR (Admin only)
13 - RADIUS Accounting (Admin only) 23 - L2TP Data (Admin only)
14 - A11 (R-P Interface) (Admin only) 24 - GTPC (Admin only)
15 - Mobile IPv4 (Admin only) 25 - TACACS (Admin only)
16 - A11MGR (Admin only) 26 - GTPU (Admin only)
17 - PPP (Admin only) 27 - GTPP (Admin only)
18 - A10 (Admin only) 28 - DHCP (Admin only)
19 - User L3 (Admin only) 29 - CDR (Admin only)
20 - USERTCP STACK (Admin only) 30 - DHCPV6 (Admin only)
31 - RADIUS COA (Admin only) 51 - SCTP (Admin only)
32 - MIP Tunnel (Admin only) 52 - M3UA (Admin only)
33 - L3 Tunnel (Admin only) 53 - SCCP (Admin only)
> 34 - CSS Data (Admin only) 54 - TCAP (Admin only)
35 - CSS Signaling (Admin only) 55 - MAP (Admin only)
传统非CUPS PGW的输出示例如下:
Sunday May 02 2021
<<<
CSS Uplink Output PDU to ACS- slot:2 cpu:17 inst:4369
192.168.0.177 > 192.168.3.1: icmp: echo request (DF) (ttl 64, id 45402, len 84)
Sunday May 02 2021
***CONTROL*** 11:22:22:165 Eventid:77202
Rule matched : DEFAULT for uplink packet of subscriber MSID : 593440538564309
Sunday May 02 2021
INBOUND>>>>> 11:22:22:165 Eventid:77001(9)
CSS Uplink Input PDU from ACS- slot:3 cpu:34 inst:8738
192.168.0.177 > 192.168.3.1: icmp: echo request (DF) (ttl 64, id 45402, len 84)
但是,使用CUPS UP时,选项34不再打印数据包,而只是匹配消息的规则。
Wednesday May 12 2021
***CONTROL*** 03:46:03:656 Eventid:77203
Rule matched : DEFAULT for uplink packet of subscriber CallID : 0x3e02061
解决方案
由于新架构(控制平面和用户平面分离,涉及矢量分组处理器(VPP)等),CUPS UP的监控功能被重写。 作为此更改的一部分,选项34不再打印数据包。相反,选项19(用户L3)将在ECS中修改任何数据包后打印该数据包,尽可能接近SGi。
总之,选项26(GTPU)和选项19(用户L3)可用于监控用户流量。
有关监控用户选项中上行链路/下行链路数据包显示方式的图片
在上行链路方向,要在修改数据包之前获得数据包的副本,我们需要GTPU的选项26。选项19应是SGi上看到的数据包,包括报头丰富、TCP MSS修改等。
在下行链路方向,选项19和NO GTPU生成了2个数据包副本。这是有意的,因为在出站方向,sessmgr看不到GTPU封装的数据包。会话管理器处理数据包后,VPP会添加GTPU报头。相反,实施被更改以由用户L3再次打印后ECS数据包,因此2个数据包副本由选项19打印。
此处显示了非CUPS和CUPS的输出示例,供比较。
CUPS:
Wednesday May 12 2021
INBOUND>>>>> 03:46:03:652 Eventid:142004(3)
GTPU Rx PDU, from fe80:192:168:1::3:2152 to fe80:10:200:1::100:2152 (92) TOS:0
TEID: 0x0000200E, Message type: GTP_TPDU_MSG (0xFF)
Sequence Number:: NA
GTP HEADER FOLLOWS:
Version number: 1
Protocol type: 1 (GTP C/U)
Message Type: 0xFF (GTP_TPDU_MSG)
Message Length: 0x0054 (84)
Tunnel ID: 0x0000200E
GTP HEADER ENDS.
Payload protocol: IPv4
PROTOCOL PAYLOAD FOLLOWS:
192.168.1.1 > 192.168.205.1: icmp: echo request (DF) (ttl 64, id 1521, len 84)
PROTOCOL PAYLOAD ENDS.
Wednesday May 12 2021
INBOUND>>>>> 03:46:03:652 Eventid:51000(0)
IPv4 Rx PDU
192.168.1.1 > 192.168.205.1: icmp: echo request (DF) (ttl 64, id 1521, len 84)
Wednesday May 12 2021
***CONTROL*** 03:46:03:656 Eventid:77203
Rule matched : DEFAULT for uplink packet of subscriber CallID : 0x3e02061
Wednesday May 12 2021
<<<
IPv4 Tx PDU
192.168.205.1 > 192.168.1.1: icmp: echo reply (DF) (ttl 64, id 11245, len 84)
Wednesday May 12 2021
***CONTROL*** 03:46:03:658 Eventid:77203
Rule matched : DEFAULT for downlink packet of subscriber CallID : 0x3e02061
Wednesday May 12 2021
<<<
IPv4 Tx PDU
192.168.205.1 > 192.168.1.1: icmp: echo reply (DF) (ttl 64, id 11245, len 84)
传统非CUPS:
Sunday May 02 2021
INBOUND>>>>> 11:22:22:165 Eventid:142004(3)
GTPU Rx PDU, from 192.168.1.4:2152 to 192.168.10.1:2152 (92) TOS:0
TEID: 0x800CA001, Message type: GTP_TPDU_MSG (0xFF)
Sequence Number:: NA
GTP HEADER FOLLOWS:
Version number: 1
Protocol type: 1 (GTP C/U)
Message Type: 0xFF (GTP_TPDU_MSG)
Message Length: 0x0054 (84)
Tunnel ID: 0x800CA001
GTP HEADER ENDS.
Payload protocol: IPv4
PROTOCOL PAYLOAD FOLLOWS:
192.168.0.177 > 192.168.3.1: icmp: echo request (DF) (ttl 64, id 45402, len 84)
PROTOCOL PAYLOAD ENDS.
Sunday May 02 2021
INBOUND>>>>> 11:22:22:165 Eventid:51000(0)
IPv4 Rx PDU
192.168.0.177 > 192.168.3.1: icmp: echo request (DF) (ttl 64, id 45402, len 84)
Sunday May 02 2021
<<<
CSS Uplink Output PDU to ACS- slot:2 cpu:17 inst:4369
192.168.0.177 > 192.168.3.1: icmp: echo request (DF) (ttl 64, id 45402, len 84)
Sunday May 02 2021
***CONTROL*** 11:22:22:165 Eventid:77202
Rule matched : DEFAULT for uplink packet of subscriber MSID : 593440538564309
Sunday May 02 2021
INBOUND>>>>> 11:22:22:165 Eventid:77001(9)
CSS Uplink Input PDU from ACS- slot:3 cpu:34 inst:8738
192.168.0.177 > 192.168.3.1: icmp: echo request (DF) (ttl 64, id 45402, len 84)
Sunday May 02 2021
<<<
IPv4 Tx PDU
192.168.3.1 > 192.168.0.177: icmp: echo reply (ttl 64, id 56260, len 84)
Sunday May 02 2021
<<<
CSS Downlink Output PDU to ACS- slot:2 cpu:17 inst:4369
192.168.3.1 > 192.168.0.177: icmp: echo reply (ttl 64, id 56260, len 84)
Sunday May 02 2021
***CONTROL*** 11:22:22:166 Eventid:77202
Rule matched : DEFAULT for downlink packet of subscriber MSID : 593440538564309
Sunday May 02 2021
INBOUND>>>>> 11:22:22:166 Eventid:77003(9)
CSS Downlink Input PDU from ACS- slot:3 cpu:34 inst:8738
192.168.3.1 > 192.168.0.177: icmp: echo reply (ttl 64, id 56260, len 84)
Sunday May 02 2021
<<<
GTPU Tx PDU, from 192.168.10.1:2152 to 192.168.1.4:2152 (92) TOS:0
TEID: 0x60010896, Message type: GTP_TPDU_MSG (0xFF)
Sequence Number:: NA
GTP HEADER FOLLOWS:
Version number: 1
Protocol type: 1 (GTP C/U)
Message Type: 0xFF (GTP_TPDU_MSG)
Message Length: 0x0054 (84)
Tunnel ID: 0x60010896
GTP HEADER ENDS.
Payload protocol: IPv4
PROTOCOL PAYLOAD FOLLOWS:
192.168.3.1 > 192.168.0.177: icmp: echo reply (ttl 63, id 56260, len 84)
PROTOCOL PAYLOAD ENDS.