Sure. Connection paths are a sequence of “hops” from the initial connection point, where each hop is a pair of “exit port”, then “address” via that port. Port number 1 is reserved for backplanes, and the accompanying address is the slot number to target. Higher port numbers are for other networks supported by the device. If the network is DeviceNet or ControlNet, the accompanying address is the node number to target. If the network is Ethernet/IP, the accompanying address is the IP address in string format.
Port 2 is the typical exit port for network modules. Modules with two independent network ports usually use Ports 2 & 3 (like a DHRIO module). This is not a requirement, and I’ve seen EDS files that specify odd port numbers. The EDS file must have the port numbers if the vendor wants configuration tools to be able to hop through them (tools like RSLinx).