Hiya, Daniel!
No, there was no need. iSCSI was always started automatically.
However, since I've have no idea what stopped it, I've added an iscsi start line at the end of my simulator's /etc/rc script - here's what I got:
Mon Nov 9 08:51:00 CET [netif.linkUp:info]: Ethernet ns0: Link up.
add net default: gateway 192.168.0.1
iscsi: service not ready
Mon Nov 9 08:51:00 CET [iscsi.service.startup:info]: iSCSI service startup
Mon Nov 9 08:51:01 CET [rc:ALERT]: timed: time daemon started
Mon Nov 9 08:51:01 CET [perf.archive.start:info]: Performance archiver started. Sampling 22 objects and 192 counters.
Mon Nov 9 08:56:03 CET [mgr.boot.disk_done:info]: NetApp Release 7.3.1 boot complete. Last disk update written at Mon Nov 9 08:55:30 CET 2009
Mon Nov 9 08:56:03 CET [mgr.boot.reason_ok:notice]: System rebooted after a reboot command.
CIFS local server is running.
It would appear that adding iscsi start doesn't help, since the service is not yet ready to be administered. At least not on the simulator, but I think it's the same thing with real filers...
I need to execute that command after the system has fully rebooted. How do I do that?