ProCurve 5300xl Specifications Page 13

  • Download
  • Add to my manuals
  • Print
  • Page
    / 36
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 12
13
associated with the DHCP server. With DHCP relay agent information option (option 82), the
DHCP servers compliant with RFC 3046 Option 82 operations can use switch identity and
client source port information as criteria for selecting the IP addresses.
LLDP (Link Layer Discovery Protocol) – Provides a standard based method for the switches to
advertise themselves to adjacent devices and to learn about adjacent LLDP devices. This
feature also supports access by SNMP-based network discovery tools.
Proxy ARP
Up to 10,000 network address routes – enough for a large local environment
Up to 65,536 Layer 3 host address routes
Bootp Relay Service
Encapsulation type: Ethernet II
8 Subnets per VLAN: one primary subnet and up to 7 secondary subnets. Maximum 512
secondary subnets per chassis. (Max 256 primary subnets (VLANs) + 512 secondary subnets
= 768 max total subnets per chassis)
IPv4 routing, IPv6 switching: full routing of IPv4-based packets, IPv6-based packets are
switched at Layer 2
Rapid Spanning Tree Protocol, 802.1w
Spanning Tree Protocol (STP), part of the IEEE 802.1D standard, is a Layer 2 protocol that
allows switches to be interconnected with redundant multiple links for high availability that form
network loops. In a non-spanning tree environment these loops would immediately bring the
network down. Using link cost algorithms, Spanning Tree determines which redundant links
should be logically shut down thus preventing any active network path loops.
There are two concerns with the original Spanning Tree standard, 802.1D. The first is that all
redundant links except one are not used for actual network traffic. This wastes potential
bandwidth. This problem is usually addressed by routing at the switch instead of just switching.
Many network managers don’t want to do this, however, due to the higher level of management
needed in a routed environment over a Layer 2 environment. While the ProCurve 5300xl Switch
Series can perform Layer 3 routing, there is an easier solution in Switch Meshing, which is
described in the next section.
The second concern is on link failure or loss of the STP root switch, Spanning Tree can take up
to 45 seconds to re-establish network connections. In many networks a potential outage of 45
seconds is unacceptable. While many switch vendors in the past have implemented a
proprietary protocol to deal with this, the IEEE has now established the 802.1w standard, Rapid
Spanning Tree Protocol (RSTP) to update the STP so that it responds more rapidly to link failure
or loss of the root switch. Actual recovery time is dependent (as STP is) on network complexity
but can approach 1 second under optimal conditions. RSTP is better than the proprietary
protocols because it is standards based, leading to interoperability between different switch
vendors, and it provides backward compatibility with the original STP. Sections of the network
that are running under STP will recover with times associated with STP, while those running
under RSTP recover in RSTP timeframes.
IEEE 802.1D Spanning Tree Protocol
The ProCurve 5300xl Switch Series also support single instance spanning tree, per the 802.1D
specification. Running STP and RSTP in the same box is mutually exclusive; only one form can
be run at any given time. RSTP is the recommended configuration and can be run in the same
spanning tree domain with other switches that are running STP. STP is available, however, for
users that for some reason don’t want to run RSTP.
Switch Meshing (LAN Aggregation)
The ProCurve 5300xl Switch Series family supports ProCurve’s Switch Meshing, a way to
interconnect these switches in a meshed topology at Layer 2. Meshed switch-to-switch links can
all be used simultaneously to their full advantage, with traffic being load-balanced through
redundant links based on dynamically determined latency on the different possible paths
between switches. Highly available, fault tolerant networks can be easily built with very low
network administration required.
Page view 12
1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 35 36

Comments to this Manuals

No comments