Hello again Vadim, nice to see you here!
No need to apologize about asking questions, that’s what we’re here for, to answer them as best we can!
The only way you can access the switch using SSH or Telnet is via an IP address that has been assigned to an SVI. An L2 switch does indeed have SVIs and you can actually configure more than one. If you want to have access to them you either need to connect a PC to a port on the same VLAN as the SVI, or put the PC on another subnet and configure the default gateway for the switch so it can reach other networks.
If you have a pure L2 switch, you cannot assign IP addresses the ports nor can you create loopbacks. Other than console/aux access, the only way to obtain a CLI on the switch is via an SVI. If you want the redundancy that management interfaces or loopbacks provide, you will just have to buy a higher end L3 switch.
This feature is actually quite innovative. It is an option that allows you to obtain a configuration file using the DHCP protocol. DHCP is a protocol that provides much more information than just an IP address, subnet mask, gateway, and DNS server. It has many options that can be added to provide additional information to the requesting host. The “autoconfiguration with DHCP” feature takes advantage of DHCP in this way.
If it is enabled, the IOS device asks for an IP address using DHCP. The DHCP server will respond with the IP address, subnet mask, gateway and DNS server, but will also provide a url from which the device can download it’s configuration file. This will replace the running config and will allow the device to be automatically configured. THis is similar to the way that IP phones will obtain configuration information from the DHCP option 150 which provides the address of a TFTP server from where configs can be downloaded.
Now for this to work, the DHCP server must be configured with the appropriate option and a server must also be configured that will contain the appropriate configs.
I hope this has been helpful!
Laz