在部署了ITA业务策略的组网环境中,我们将标记了计费级别的用户流量称为ITA业务流量,其它的用户流量称做非ITA业务流量。这样,根据每个用户是否有ITA业务流量可以将该用户的总计费流量分成两种情况:一,总计费流量仅由非ITA业务流量组成;二,总计费流量是ITA业务流量和非ITA业务流量的和。用户的总计费流量是否包含ITA业务流量可以通过配置进行控制。各个级别的ITA业务流量可以独立于用户的总流量进行计费,可以与总计费流量采用不同的计费方案。总体策略汇总如下:
1. 统一计费和非统一计费(accounting-merge enable命令用来开启统一计费功能,缺省处于关闭状态)
统一计费是指平台aaa发送的计费报文,子会话的计费报文只发送一个level,最小level,其他子会话的数据全部封装在该报文中发送。
非统一计费是指平台aaa发送的计费报文,每个子会话都是单独发送计费报文。
统一计费的应用场景就是各个子会话的费率是一样的场景,这样可以达到减少aaa交互报文数量的目的,如果费率是不一样的就只能非统一计费。
2. 计费分离和计费合并(traffic-separate enable命令,缺省未指定需要计费的流量计费级别)
计费分离是指主会话发送计费报文里面不包含子会话的流量,计费合并则是主会话发送的计费报文里面已经加了子会话的数据,同时子会话还会再发送计费报文。主会话指默认不命中子会话的流量,全部走的主会话
3. 实际上统一计费和计费分离功能是相互独立的两个功能,可以组合使用,不冲突。
配置举例如下,可进一步理解上述计费策略,现网其他的配置大家可以结合理解:
如果是如下配置:
ita policy ita
accounting-method radius-scheme test
accounting-level 2 ipv4
accounting-level 3 ipv4
accounting-merge enable
traffic-separate enable level 2 3
此时的效果就是:我们会发两个计费包到radius(主会话和子会话)。
1)
2)子会话与主会话计费分离,也就是指主会话发送计费报文里面不包含子会话level2的流量。
<SR8804X-1>dis ip subscriber session verbose
Flow statistic:
Uplink packets/bytes : 8746/8990888///此流量是主会话的,不包括子会话。
Downlink packets/bytes : 0/0
IPv6 uplink packets/bytes : 0/0
IPv6 downlink packets/bytes : 0/0
ITA:
Acct merge : Enabled
Acct quota-out action : Offline
Denied level : None
Level-2 Inbound CAR : N/A
Outbound CAR : N/A
Traffic separate : Enabled
Session duration : N/A, remaining: N/A
Traffic quota : N/A
Traffic remained : N/A
Uplink packets/bytes : 4615/4827290////// Level-2的
Downlink packets/bytes : 0/0
IPv6 uplink packets/bytes : 0/0
IPv6 downlink packets/bytes : 0/0
Level-3 Inbound CAR : N/A
Outbound CAR : N/A
Traffic separate : Enabled
Session duration : N/A, remaining: N/A
Traffic quota : N/A
Traffic remained : N/A
Uplink packets/bytes : 4458/4663068//////level3的。但是此时向radius发包是只发一个level2的包,里面包括(level2+level3)
Downlink packets/bytes : 0/0
IPv6 uplink packets/bytes : 0/0
IPv6 downlink packets/bytes : 0/0
发给Radius的报文有两个:
1)主会话
<SR8804X-1>*Mar 9 07:48:39:836 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
Sent a RADIUS packet
Server IP : 192.168.214.13
NAS-IP : 172.31.1.155
VPN instance : M
Server port : 1813
Type : Accounting request
Length : 396
Packet ID : 146
*Mar 9 07:48:39:837 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
User-Name="59.66.4.58@l3default"
H3c-Acct-Update-Address=0
H3C-Auth-Detail-Result=2
NAS-Identifier="SR8804X-1"
NAS-Port-
NAS-Port=34607104
NAS-Port-Type=Ethernet
Acct-Output-Packets=0
Acct-Session-Time=1263
Acct-Input-Packets=8673 ///此流量是主会话的,不包括子会话
Acct-Output-Octets=0
Acct-Output-Gigawords=0
Acct-Input-Octets=8915844
Acct-Input-Gigawords=0
H3c-Tariff-Switch-Interval=0
Acct-Session-
H3c-Ip-Host-Addr="59.66.4.58 78:2c:29:c1:7b:94"
Calling-Station-
Framed-IP-Address=59.66.4.58
H3c-Domain-Name="l3default"
Framed-Protocol=PPP
Service-Type=Framed-User
H3c-Auth-Type=IPoE
Acct-Authentic=0
*Mar 9 07:48:39:837 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
H3c-AVPair="car:car-unit=kbps"
NAS-IP-Address=172.31.1.155
Acct-Status-Type=Interim-Update
Acct-Delay-Time=0
Event-Timestamp="Mar 9 2022 07:48:39 UTC"
H3c-Product-
H3c-Nas-Startup-Timestamp=1293840086
*Mar 9 07:48:39:837 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
04 92 01 8c f6 70 68 ec 57 aa 4f 00 93 7a 4d 23
02 f1 16 f6 01 16 35 39 2e 36 36 2e 34 2e 35 38
40 6c 33 64 65 66 61 75 6c 74 1a 0c 00 00 63 a2
9f 06 00 00 00 00 1a 0c 00 00 63 a2 f6 06 00 00
00 02 20 0b 53 52 38 38 30 34 58 2d 31 57 23 73
6c 6f 74 3d 32 3b 73 75 62 73 6c 6f 74 3d 31 3b
70 6f 72 74 3d 31 3b 76 6c 61 6e 69 64 3d 30 3b
05 06 02 10 10 00 3d 06 00 00 00 0f 30 06 00 00
00 00 2e 06 00 00 04 ef 2f 06 00 00 21 e1 2b 06
00 00 00 00 35 06 00 00 00 00 2a 06 00 88 0b 84
34 06 00 00 00 00 1a 0c 00 00 63 a2 10 06 00 00
00 00 2c 26 30 30 30 30 30 30 30 38 32 30 32 32
30 33 30 39 30 37 32 37 33 36 30 30 30 30 30 31
38 32 30 30 31 30 31 30 1a 24 00 00 63 a2 3c 1e
35 39 2e 36 36 2e 34 2e 35 38 20 37 38 3a 32 63
*Mar 9 07:48:39:838 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
3a 32 39 3a 63 31 3a 37 62 3a 39 34 1f 13 37 38
2d 32 43 2d 32 39 2d 43 31 2d 37 42 2d 39 34 08
06 3b 42 04 3a 1a 11 00 00 63 a2 11 0b 6c 33 64
65 66 61 75 6c 74 07 06 00 00 00 01 06 06 00 00
00 02 1a 0c 00 00 63 a2 b4 06 00 00 00 02 2d 06
00 00 00 00 1a 19 00 00 63 a2 d2 13 63 61 72 3a
63 61 72 2d 75 6e 69 74 3d 6b 62 70 73 04 06 ac
1f 01 9b 28 06 00 00 00 03 29 06 00 00 00 00 37
06 62 28 5b d7 1a 0b 00 00 63 a2 ff 05 48 33 43
1a 0c 00 00 63 a2 3b 06 4d 1e 6e d6
*Mar 9 07:48:39:851 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
Received a RADIUS packet
Server IP : 192.168.214.13
NAS-IP : 172.31.1.155
VPN instance : M
Server port : 1813
Type : Accounting response
Length : 20
Packet ID : 146
*Mar 9 07:48:39:851 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
05 92 00 14 aa ae f5 a2 26 99 2a 02 f5 94 7a cc
8d 1b f6 0f
2)子会话,只发送了level2。
*Mar 9 07:48:41:236 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
Sent a RADIUS packet
Server IP : 192.168.214.13
NAS-IP : 172.31.1.155
VPN instance : M
Server port : 1813
Type : Accounting request
Length : 390
Packet ID : 147
*Mar 9 07:48:41:236 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
User-Name="59.66.4.58@l3default"
H3c-Acct-Update-Address=0
NAS-Identifier="SR8804X-1"
NAS-Port=34607104
NAS-Port-Type=Ethernet
NAS-Port-
Acct-Output-Packets=0
Acct-Session-Time=1264
H3C-Ita-Policy="ita"
Acct-Input-Packets=9011///////可以看到,此处计费总数是lever2+level3的。
Acct-Multi-Session-
Acct-Output-Octets=0
Acct-Output-Gigawords=0
H3C-Accounting-Level=2
Acct-Input-Octets=9425506
Acct-Input-Gigawords=0
Acct-Session-
H3c-Ip-Host-Addr="59.66.4.58 78:2c:29:c1:7b:94"
Calling-Station-
Framed-IP-Address=59.66.4.58
H3c-Domain-Name="l3default"
Framed-Protocol=PPP
*Mar 9 07:48:41:237 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
Service-Type=Framed-User
NAS-IP-Address=172.31.1.155
Acct-Status-Type=Interim-Update
Acct-Delay-Time=0
Event-Timestamp="Mar 9 2022 07:48:41 UTC"
H3c-Product-
H3c-Nas-Startup-Timestamp=1293840086
*Mar 9 07:48:41:237 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
04 93 01 86 7f dc 92 31 bc f7 ff 13 32 00 42 ed
60 57 8e 2f 01 16 35 39 2e 36 36 2e 34 2e 35 38
40 6c 33 64 65 66 61 75 6c 74 1a 0c 00 00 63 a2
9f 06 00 00 00 00 20 0b 53 52 38 38 30 34 58 2d
31 05 06 02 10 10 00 3d 06 00 00 00 0f 57 23 73
6c 6f 74 3d 32 3b 73 75 62 73 6c 6f 74 3d 31 3b
70 6f 72 74 3d 31 3b 76 6c 61 6e 69 64 3d 30 3b
30 06 00 00 00 00 2e 06 00 00 04 f0 1a 0b 00 00
63 a2 d8 05 69 74 61 2f 06 00 00 23 33 32 26 30
30 30 30 30 30 30 38 32 30 32 32 30 33 30 39 30
37 32 37 33 36 30 30 30 30 30 31 38 32 30 30 31
30 31 30 2b 06 00 00 00 00 35 06 00 00 00 00 1a
0c 00 00 63 a2 d7 06 00 00 00 02 2a 06 00 8f d2
62 34 06 00 00 00 00 2c 26 30 30 30 30 30 30 30
38 32 30 32 32 30 33 30 39 30 37 32 37 33 36 30
*Mar 9 07:48:41:237 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
30 30 30 30 31 38 33 30 30 31 30 31 30 1a 24 00
00 63 a2 3c 1e 35 39 2e 36 36 2e 34 2e 35 38 20
37 38 3a 32 63 3a 32 39 3a 63 31 3a 37 62 3a 39
34 1f 13 37 38 2d 32 43 2d 32 39 2d 43 31 2d 37
42 2d 39 34 08 06 3b 42 04 3a 1a 11 00 00 63 a2
11 0b 6c 33 64 65 66 61 75 6c 74 07 06 00 00 00
01 06 06 00 00 00 02 04 06 ac 1f 01 9b 28 06 00
00 00 03 29 06 00 00 00 00 37 06 62 28 5b d9 1a
0b 00 00 63 a2 ff 05 48 33 43 1a 0c 00 00 63 a2
3b 06 4d 1e 6e d6
*Mar 9 07:48:41:247 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
Received a RADIUS packet
Server IP : 192.168.214.13
NAS-IP : 172.31.1.155
VPN instance : M
Server port : 1813
Type : Accounting response
Length : 20
Packet ID : 147
*Mar 9 07:48:41:247 2022 SR8804X-1 RADIUS/7/PACKET: -MDC=1-Slot=2;
05 93 00 14 77 79 a8 a6 f8 13 30 42 93 7d 09 ee
bd 65 fc a8
PS:此部分功能我司和华为的实现差异:
1、华为命令accounting-together enable开启统一计费,和我司accounting-merge enable命令功能一致,差异是我司统一发送的计费报文发送的level是最小的,华为的发送level是最大的level。
2、华为命令traffic-separate enable开启业务分离功能,同时开启了流量分离和计费分离,对应我司的命令为traffic-separate enable开启计费分离功能。
3、华为命令user accounting-together enable(华为这条命令必须有计费分离前置命令才会生效)把分离的流量合并到主会话计费,对应我司不开启traffic-separate enable命令的情况,也就是计费合并的功能。
4、配置命令accounting-service-policy { inbound | outbound } auto,可以根据DAA用户当前的业务带宽配置智能地决策是否使用上行/下行流量进行DAA业务匹配功能。如果用户的全部上行/下行业务都没有配置带宽,则禁止上行/下行流量进行DAA业务匹配功能,并且不申请上行/下行DAA Qos资源。我司没有对应的功能,默认都会直接分配qos资源。
该案例暂时没有网友评论
✖
案例意见反馈
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作