cancel
Showing results for 
Search instead for 
Did you mean: 

FE80 connectivity issue ( Link-local IPv6 Address . . . . . : fe80::b0a3:c0ad:6bc4:8648%19)

former_member209962
Participant
0 Kudos

Hi Frineds,

We are facing an issue with IP 169.254. series this issue came when we did a kernel upgrade from 701 to 720 and restarted the server, upgrade was fine and sap came up without any issue but users where not able to connect to sap, we have configured load balancing in users gui

if we remove load balancing from SAP GUI users can login and everything is fine.

When i was hiting T code SMGW i was getting message as SAPGATEWAY DEACTIVED  but after maintaining parameter gw/monitor=1 this issue solved

but Its again showing ip 169.254.2.60 i dont no why?

when i hit ipconfig this what it is showing

C:\Users\fnpadm>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection* 8:

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::b0a3:c0ad:6bc4:8648%19

   IPv4 Address. . . . . . . . . . . : 169.254.1.12

   Subnet Mask . . . . . . . . . . . : 255.255.0.0

   Default Gateway . . . . . . . . . :

Ethernet adapter Public:

   Connection-specific DNS Suffix  . :

   IPv4 Address. . . . . . . . . . . : 192.168.30.21

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   IPv4 Address. . . . . . . . . . . : 192.168.30.70

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   IPv4 Address. . . . . . . . . . . : 192.168.30.71

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   IPv4 Address. . . . . . . . . . . : 192.168.30.72

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.30.1

Ethernet adapter Private:

   Connection-specific DNS Suffix  . :

   IPv4 Address. . . . . . . . . . . : 10.0.0.1

   Subnet Mask . . . . . . . . . . . : 255.0.0.0

   Default Gateway . . . . . . . . . :

Is this issue because of new kernel??

We have also followed note 1365796 but no success, please  help to solve this issue.

Thanks

Tabrayz

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello

Try adding server IP (IPv4) to hosts file and then run ipconfig /flushdns from command prompt. Also delete server caches from smicm transaction.

Best regards

former_member209962
Participant
0 Kudos

Hi Kaan

Tried that no luck

Thanks

Tabrayz

Former Member
0 Kudos

Hy Tabrayz,

have you solved your problem?

we are facing a similar problem in Microsoft environment

kind regards

Thomas

former_member209962
Participant
0 Kudos

yes problem is solved after assigning ip address in  t code smlg