This article explains the reason for the log message sfid[]: task_connect: task xxx.128.0.0.y addr 128.0.0.y: Can't assign requested address , which might occur on EX Series switches when the unit is rebooted. This is expected behavior.

On the EX series, the following log might appear when the unit is rebooted:

Apr 29 13:24:40 GUT-LAN-SW vccpd[1054]: task_connect: task ESP CLIENT:33010.8.1.80.f2.80.0.0.1 addr 8.1.80.f2.80.0.0.1: Can't assign requested address
Apr 29 13:24:40 GUT-LAN-SW sfid[1053]: task_connect: task NetBIOS.8.1.80.fe.80.0.0.1 addr 8.1.80.fe.80.0.0.1: Can't assign requested address
Apr 29 13:24:40 GUT-LAN-SW sfid[1053]: task_addr_local: task PFEPEER.8.1.18.5a.80.0.0.1 address 8.1.0.0.80.0.0.10: Can't assign requested address
Apr 29 13:24:40 GUT-LAN-SW sfid[1053]: task_connect: task SFLOW.8.1.18.c7.80.0.0.1 addr 8.1.18.c7.80.0.0.1: Can't assign requested address
Apr 29 13:24:40 GUT-LAN-SW sfid[1053]: task_addr_local: task PPM.8.1.17.7b.80.0.0.1 address 8.1.0.0.80.0.0.10: Can't assign requested address
Apr 29 13:24:40 GUT-LAN-SW sfid[1053]: TASK_TASK_BEGIN: Commencing virtual chassis control daemon, version , built by
Apr 29 13:24:40 GUT-LAN-SW sfid[1053]: task_connect: task PFEMAN.128.0.0.32 addr 128.0.0.32: Can't assign requested address
Apr 29 13:24:40 GUT-LAN-SW sfid[1053]: task_connect: task ASD.128.0.0.1 addr 128.0.0.1: Can't assign requested address
Apr 29 13:24:40 GUT-LAN-SW sfid[1053]: task_addr_local: task PFEPEER.128.0.0.1 address 128.0.0.17: Can't assign requested address

The reason for this error message is that following the reboot of the chassis, the SFI daemon comes up before other daemons (such as NetBIOS, ESP Client, SFLOW, ESWD, PFEM, etc.). SFI tries to connect to those daemons (which have not initiated) and hence the connection fails. This connectivity is re-initiated at regular intervals, and once those daemons come up, the connection succeeds.

This is an expected behavior. This is a display message and has no operational impact.

2020-08-04: Minor, non-technical edit.