Multicast Protocol, Security/VPN | 3Com 5000, 6000 specs

3Com Router 5000 and Router 6000 Family

Release Notes v2.41 • Page 13

•The BGP route is not advertised if the IGP route is present in the forwarding table. Import the route into BGP from the protocol which owns the route in the forwarding table.

•RIP Poison Reverse is not supported.

•IPX is not supported on HDLC and X25. IPX is only supported on Frame Relay, Ethernet, and PPP.

•The BGP received and advertised routes for a particular peer (display bgp routing-table peer <x.x.x.x> receivedadvertised) are not displayed in numerical order.

•With OAM and PVC states both down, the interface is still considered up and the directly connected route is not withdrawn from the routing table; Along the same line, with OAM active, a PVC’s going down does not have its learned routes deleted from the routing table. The router will need to rely on the individual routing protocol’s timeout feature to initiate route removal.

•Load Sharing statistics are not accurate when more than one next-hop router is reachable via the same physical interface.

•BGP Auto-summary does not work with the BGP Network command; Auto-Summary works in all other cases.

•Redistribution of IGP routes into IBGP will not have the IGP next-hop. Instead, the next hop will always be the router doing the redistribution.

3.8Multicast Protocol

•The default value for the IGMP query interval (60 seconds) does not match the recommended value in RFC 2236 (125 seconds). Set the query interval to match the query interval of other routers in the network.

•PIM is not supported with IP unnumbered FR interfaces. An IP address must be assigned to the FR interface.

•The router will continuously reboot if the MSDP configuration references an interface that is not available; this would most likely occur when a module is removed or replaced and the saved configuration still has a reference to the old interface.

3.9Security/VPN

•IPSec card-proposal does not have an option for ESP encapsulation. Those options do not show up until the “use” command is issued to specify which encryption module to use.

•The encryption card does not perform as well when passing large byte data(e.g. anything over 1464 bytes for 3DES/SHA1).

•“Display firewall ethernet-frame-filter all” does not work. Specify the exact interface to get the desired information.

•NAT traversal does not work in IKE Main Mode. IKE Aggressive Mode is required for NAT traversal to function properly.

•Packets with internal addresses appear outside the NAT boundary. NAT does not translate ESP or IGMP packets. NAT does not translate any IP protocols other than ICMP, TCP, UDP, and GRE (with respect to PPTP)

•The firewall drops FTP connections when ASPF is configured to filter TCP. ASPF must be configured with TCP and FTP together.

5000, 6000 specifications

The 3Com 6000 series, launched in the late 1990s, was a significant advancement in networking technology, designed to meet the growing demands of enterprise-level networking. This series provided powerful solutions for businesses seeking reliable, efficient, and scalable networking capabilities.

At its core, the 3Com 6000 series featured a modular design, allowing companies to customize their networks according to specific needs. This flexibility meant that organizations could add or replace components as their networking requirements evolved, ensuring investment protection and a tailored approach to connectivity. The ability to scale was particularly important for businesses that anticipated growth or change in operational demands.

One of the standout features of the 3Com 6000 was its advanced switching capabilities. The series employed high-performance switching technologies that supported various protocols, including Fast Ethernet and Gigabit Ethernet. This versatility made it suitable for diverse environments, from small offices to large corporate settings. The 3Com 6000 switches were engineered to deliver high throughput and low latency, crucial for applications requiring real-time data transfer.

The series also supported a range of network management tools, enhancing operational efficiency. With SNMP (Simple Network Management Protocol) support, network administrators could easily monitor and manage network performance, troubleshoot issues, and configure devices from a centralized location. This capability significantly streamlined network operations, reducing downtime and optimizing resource allocation.

Security was another significant concern addressed by the 3Com 6000. The series incorporated robust security features, including access control lists (ACLs) and VLAN (Virtual Local Area Network) support. These features allowed network administrators to segment traffic and enforce security policies, protecting sensitive data and ensuring compliance with organizational standards.

Moreover, the 3Com 6000 series was designed with energy efficiency in mind, reflecting a growing awareness of the environmental impact of IT infrastructure. By implementing power-saving features, the series helped organizations reduce their overall energy consumption while maintaining optimal network performance.

In summary, the 3Com 6000 series stood out for its modularity, advanced switching capabilities, extensive management tools, strong security features, and energy efficiency. It represented a forward-thinking solution for enterprises aiming to build robust network infrastructures capable of supporting a wide range of applications and services. As organizations increasingly relied on networked systems, the 3Com 6000 played a crucial role in shaping the landscape of enterprise networking.