McDATA ULTRANET EDGE 3000, User Manual

Page: 57 / 428

3
Network Design Criteria
3-3
Network Design
Required Network
Design Information for
an Ethernet Network
The following is a list of information for you need to know for the
network components when designing an Ethernet
network.
UltraNet Edge 3000
• The Ethernet maintenance interface is statically configured for
auto negotiate.
• Each IP interface on the UltraNet Edge 3000 needs to be on a
separate subnet. This includes the WAN interfaces, the Ethernet
maintenance interface, and the serial interface for PPP.
• The default PPP IP host address for the UltraNet Edge 3000’s
serial interface is 192.168.1.1/28. This can be changed using
UltraNet ConfigManager.
• The UltraNet Edge 3000 does not listen to routing broadcasts.
One default gateway can be configured along with multiple host
and network specific static routes. Generally the default gateway
is defined for the Ethernet maintenance interface and the other
static routes are used for the WAN.
• The end-to-end network must have less than 1% packet loss.
• The UltraNet Edge 3000 has SNMP support. SNMP access can be
configured to limit Get or Set requests on a host specific basis. Up
to six Trap destinations can be defined (see
Appendix F, Configure
SNMP for more information).
• The end-to-end network latency must be less than or equal to
200ms round-trip latency with less than 10% jitter.
• E_port and F_port Disk Streaming require dedicated ISLs. If
multiple ISLs have been deployed, zoning and ISL routing
(uroute, preferred pathing) should be incorporated.
IP Router
• The routers need to be configured for Ethernet Version II or IEEE
802.3.
• The routers need to be configured to pass interfaces 20/21 (ftp),
23 (telnet), and 161/162 (SNMP).
• The routers that are in the data path need to be configured to pass
protocol ID’s 01 (ICMP), 61 (McDATA’s Transport Protocol), 255
(McDATA’s test utilities), 800 (IP), and 806 (ARP).
• The routers need to support at least 50K packets per second.