We recently had an issue where our 'hw_assist' IPs were on a network that experienced some downtime, and (possibly) as a result caused our filers to panic and then reboot.
We're still investigating the coredump, but in the meantime we want to connect our filers to directly each other (filerA and filerB) on an unused onboard port (e0a, since e0M isn't in use) and used that for the 'cf.hw_assist.cf.hw_assist.partner.address' IP.
I've already configured e0a on filerA as: 172.16.3.111/24 and e0a on filerB as: 172.16.3.113/24. Here is how cf.hw_assist is configured on both systems:
filerA> ifconfig e0a
e0a: flags=0x6f48867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
Hw_assist requires connectivity between filer head on one side and partner RLM on another side. So direct connection between two onboard ports is not going to work for obvious reasons. You would need to use small switch to connect two RLM and two dedicated ports together.
I just thought I would add to this post to save people some time resolving hw_assist timeout issues with a Service Processor (SP):
Firstly check SP speed / duplex, type 'sp status' and check SP has negotiated 100Mb / Full, if not reconfigure SP network switch ports to auto / auto i.e. speed / duplex.
Once this has been completed type 'sp status' to confirm 100Mb / full duplex, if the output still shows 100Mb / half duplex, type sp reboot and use sp status to confirm reboot has completed and speed / duplex is set correctly.
Another reason for getting time out messages is if the SP has not been configured properly. This may be observed by a SP prompt without hostname i.e. 'SP>'. The SP prompt should be 'SP hostname>'
To fix this issue use the following commands:
sp status options sp.setup off sp setup (using info from sp status) cf hw_assist test cf hw_assist status