Forum Discussion

ClaudioDG_15244's avatar
ClaudioDG_15244
Icon for Nimbostratus rankNimbostratus
Feb 17, 2016

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

 

BIG-IP
devops

1 Reply

Sort By
  • Chris_Grant's avatar
    Chris_Grant
    Icon for Employee rankEmployee
    Feb 17, 2016

    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.