How to remove a specific RADIUS attribute which the ISG sends in the Accounting-Request packet?
The ISG is running IOS-XE Version 16.6.4.
We have a select number of radius-server attributes configured. However, the ISG is sending the radius attribute 151 in its Accounting-Request packet. In the packet and under the RADIUS Protocol > Attribute Value Pairs, their list AVP: t=PMIP6-Home-HN-Prefix(151) l=10 val=[invalid reserved byte for IPv6 prefix]. Below you can see a Radius Accounting-Request Packet with some attributes removed.
Code: Accounting-Request (4)
Packet identifier: 0xcd (205)
[The response to this request is in frame 153]
Attribute Value Pairs
... other attributes removed ...
AVP: t=PMIP6-Home-HN-Prefix(151) l=10 val=[invalid reserved byte for IPv6 prefix]
Attribute 151 is the attribute I would like to remove or exclude from sending.
The IOS does not list the radius attribute 151 so that we can exclude, below are the ios command output
isg(config)#radius-server attribute ?
11 Filter-Id attribute configuration
188 Num-In-Multilink attribute configuration
218 Address-Pool attribute
25 Class attribute
30 DNIS attribute
31 Calling Station ID
32 NAS-Identifier attribute
4 NAS IP address attribute
44 Acct-Session-Id attribute
55 Event-Timestamp attribute
6 Service-Type attribute
60 CHAP-Challenge attribute
61 NAS-Port-Type attribute configuration
66 Tunnel-Client-Endpoint attribute
67 Tunnel-Server-Endpoint attribute
69 Tunnel-Password attribute
77 Connect-Info attribute
8 Framed IP address attribute
95 NAS IPv6 address attribute
list List of Attribute Types
nas-port NAS-Port attribute configuration
nas-port-id Nas-Port-Id attribute configuration
wireless Radius wireless attributes
Does anyone have any idea about how to exclude radius attribute 151?
This guide will explain how to check where a particular directory resides within the filesystem in terms of physical disk, logical volume, volume group, etc by taking a look at where the install repository actually resides on an NCS5500.
According to the RFC 7432:
Extended Community enables split-horizon procedures for multihomed sites. The ESI Label field represents an ES by the advertising PE, and it is used in split-horizon filtering by other PEs that are connected to th...
In scaled EVPN deployments it can be wise to name ESI that way to represent the site/physical port/etc it is attached to. Thus on some remote location you can easily verify where particular route/MAC is coming from. Similar to phone numbers, where...
Want to enable Feature EPFT with “routing-protocols-enable”. However ,it is throwing an error and ask to configure the following command: “non-subscriber-interfaces mac” which once enabled drops the traffic without any penalty.
XR-vm - CLI's
look for any process crash, review time stamp[if it is too old, then no immediate action needed]
verify if standby state is Ready and NSR-Ready
show proc cpu | exclude " 0%"