Forum Discussion
Management traffic sourced from the VIPRION primary blade may use the incorrect source IP address
Hi, in refers to sol11716: Management traffic sourced from the VIPRION primary blade may use the incorrect source IP address in my environment i've this configuration (it was fixed in BIG-IP 11.2.0)
Management ip address: 10.x.x.48 Cluster Member IP address Slot 1: 10.x.x.78 Cluster Member IP address Slot 1: 10.x.x.79
I've problem with Radius Authentication. On Radius Server Log i see that my source ip is 10.x.x.78
What tmsh command is necessary for to force source ip radius with 10.x.x.48? My version : BIG-IP 11.2.1 Build 807.10 Engineering Hotfix HF1
1 Reply
- Chris_Grant
Employee
This isn't something you can force with tmsh. If your system is using the incorrect IP for unsolicited management traffic (like radius authentication), you should really open a case with support so we can investigate and resolve.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com