If you have a lot of OTHER Ethernet stuff going into/out of your DM1E's local Ethernet port, you may want to "isolate" your Ethernet-based I/O (EBC100) by putting it on a physically different network via an ERM module.
For instance, if you connect an HMI or Designer software via the DM1E's Ethernet port, which polls the PLC "as fast as possible", that could affect the Ethernet I/O that is being done at the same time (you may need to adjust your Ethernet I/O poll rates and/or timeout values). Sadly, there is no "hard rule" that says how much traffic your DM1E can handle - you will want to use the Ethernet I/O Monitor utility available under Designer's Debug menu to help determine that empirically. (You could use an ECOM100 module for HMI/Designer purposes in lieu of getting an ERM, or possibly use USB or Serial on the CPU for your Designer programming port).
Also, if you have a bunch of older EBC modules (not EBC100), those only work with ERM, not Ethernet I/O.
Note that Ethernet I/O has many advantages over ERM including configurable poll rates, built-in native support of GS-EDRV100s, and ability to configure the fatal error/warning response by Ethernet I/O whenever a slave goes "offline" or has mismatched I/O (ERM has no direct influence over PLC's RUN mode).