Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

VRRP on 5400zl

SOLVED
Go to solution
knite
Occasional Advisor

VRRP on 5400zl

Hi guys, I had configured the two 5400zl for VRRP, and created 4 VLANS, after finishing the configuration, I disconnect the owner and the ping start to be unsuccessful, is that normal?
thx

note: attached files is the running configurations for both core switches.
3 REPLIES
Matt Hobbs
Honored Contributor
Solution

Re: VRRP on 5400zl

Yes that is normal.

http://www.hp.com/rnd/support/faqs/5400zl-3500yl.htm#question46



» Return to top
Q: How does one enable pre-standard PoE support?
The ProCurve Switch 5400zl and 3500yl Series Switches support some pre-802.3af devices. This feature is enabled by default. It can be disabled using the no power pre-std-detect command.

» Return to top
Q: Are Jumbo frames supported on the ProCurve Switch 5400zl and 3500yl series switches?
Yes. Ports operating at 1 Gbps or 10 Gbps speeds accept forward packets of up to 9220 bytes (including four bytes for a VLAN tag) when configured for jumbo traffic. Note that on ports operating at 10 Mbps or 100 Mbps, the Maximum Transmission Unit (MTU) is fixed at 1522 bytes. The switch drops any inbound packets larger than the MTU allowed on a port.

» Return to top
Q: Are Jumbo frames enabled per VLAN or per physical interface?
Inbound jumbo packets are enabled on a per-VLAN basis. That is, on a VLAN configured for jumbo traffic, all ports belonging to that VLAN and operating at 1 Gbs or 10 Gbps allow inbound jumbo packets of up to 9220 bytes.

» Return to top
Q: When support is enabled by the registration of a Premium Edge license, what would a sample VRRP topology look like?
Please see the configuration examples for this information.

» Return to top
Q: What type of spanning tree implementation do the ProCurve Switch 5400zl and 3500yl Switches support?
IEEE 802.1s Multiple Spanning Tree Protocol is supported.

» Return to top
Q: How would MSTP interact with switches that support only 802.1D STP or 802.1w RSTP?
MSTP is backward-compatible with the RSTP-enabled and STP-enabled switches in your network. Use the following command to optimize this interoperability.

ProCurveSwitch5406zl(config)# spanning-tree force-version < stp-compatible | rstp-operation | mstp-operation>

An excerpt from the parameter descriptions follows. For more detail, please see the Advanced Traffic Guide for the ProCurve Switch 5400zl, 3500yl, and 6200yl Series Products.

stp-compatible: The switch applies 802.1D STP operation on all ports.
rstp-operation: The switch applies 802.1w operation on all ports except those ports where it detects a system using 802.1D Spanning Tree.

» Return to top
Q: What advantage does implementation of IEEE 802.1s MSTP offer over legacy STP or RSTP?
The 802.1D and 802.1w spanning tree protocols operate without regard to a network's VLAN configuration, and maintain one common spanning tree throughout a bridged network. Thus, these protocols map one loop-free, logical topology on a given physical topology. This causes redundant links to be blocked; they are then available on a standby basis. With MSTP, each spanning tree instance can include one or more VLANs and applies a separate, per-instance forwarding topology. Thus, when a port belongs to multiple VLANs, it may be dynamically blocked in one spanning tree instance, but forwarding in another instance. This achieves load-balancing across the network while still providing fault tolerance through rapid, automatic reconfiguration if there is a failure in a network's physical topology.

» Return to top
Q: Is any special planning required for implementation of MSTP?
To optimally configure MSTP for load-balancing across a network of MSTP-enabled switches, there are planning tips which are detailed in the MSTP documentation.

» Return to top
Q: Will the ProCurve 5400zl or 3500yl support routing when Switch Meshing is enabled?
No. If meshing is configured on the switch, the routing features (IP routing, RIP, and OSPF) must be disabled. The switch's meshing and routing features cannot be enabled at the same time.

» Return to top
Q: When configured for meshing, are the ProCurve Switch 5400zl, 3500yl and 6200yl Series backwards-compatible with older model ProCurve switches that support meshing?
The ProCurve 5400zl, 3500yl, and 6200yl switches are compatible with the meshing feature on the 5300xl and 3400cl Series switches. There is no backward-compatibility mode for interoperation with a ProCurve Switch 4000M mesh.

» Return to top
Q: How does UDP Broadcast Forwarding work?
Some applications rely on client requests sent as limited IP broadcasts addressed to a UDP application port. If a server for the application receives such a broadcast, the server can reply to the client. Since typical router behavior, by default, does not allow broadcast forwarding, a client's UDP broadcast requests cannot reach a target server on a different subnet unless the router is configured to forward client UDP broadcasts to that server.

A switch with routing enabled includes optional per-VLAN UDP broadcast forwarding that allows up to 256 server and/or subnet entries on the switch (16 entries per-VLAN). If an entry for a particular UDP port number is configured on a VLAN and an inbound UDP broadcast packet with that port number is received on the VLAN, then the switch routes the packet to the appropriate subnet. Each entry can designate either a single device or a single subnet.

For configuration details, please see the Multicast and Routing Guide for these switches.

» Return to top
Q: Can 802.1x, Web-based authentication, and MAC-based authentication all be used concurrently on a switch port?
Yes. Details about configuring these features may be viewed in the ProCurve 6200yl/5400zl/3500yl Access Security Guide.

» Return to top
Q: Are there limits to the number of Access Control Entries (ACEs) supported within an Access Control List (ACL)?
The total number of supported ACEs in all the ACLs depends on the combined resource usage by ACL, QoS, IDM, Virus-Throttling, ICMP, and Management VLAN features. For more on this topic, refer to "Monitoring Shared Resources" in the Advanced Traffic Management Guide.

» Return to top
Q: Is there a limit to the number of ACLs supported by the 3500yl, 5400zl, or 6200yl?
You can configure up to 2048 ACL assignments to VLANs, as follows:

* Named (Extended or Standard) ACLs: Up to 2048 (minus any numeric ACL assignments)
* Numeric Standard ACLs: Up to 99; numeric range: 1 - 99
* Numeric Extended ACLs: Up to 100; numeric range: 100 - 199
* Total ACEs in all ACLs: Depends on the combined resource usage by ACL, QoS, IDM, Virus-Throttling, ICMP, and Management VLAN features

For more on this topic, refer to "Monitoring Shared Resources" in the Advanced Traffic Management Guide.

» Return to top
Q: How does Source port filtering work?
When you create a source-port filter, the switch automatically sets the filter to forward traffic from the designated source to all destinations for which you do not specifically configure a "drop" action. Thus, it is not necessary to configure a source-port filter for traffic you want the switch to forward unless the filter was previously configured to drop the desired traffic. Details about configuration of the filter command can be reviewed in the Access Security Guide for the 5400zl, 3500yl, and 6200yl products.

» Return to top
Q: What are the default DSCP codepoint values?
The DSCP Policy Table associates an 802.1p priority with a specific ToS byte codepoint in an IPv4 packet. This enables you to set a traffic management policy that operates independently of 802.1Q VLAN-tagging. In the default state, most of the 64 codepoints do not assign an 802.1p priority, as indicated by "No-override" value in the table below.

No-override values

You can use the [show] qos dscp-map command to list the current DSCP Policy table, change the codepoint priority assignments, and assign optional names to the codepoints.

» Return to top
Q: How do I enable sFlow support on the ProCurve Switch 5400zl, 3500yl and 6200yl Switches? Must I configure anything on the switch?
If you are using ProCurve Manager Plus (PCM+) for traffic monitoring on your switches, no further CLI configuration is necessary. sFlow monitoring requires the use of a management software application such as ProCurve Manager Plus 2.0 which receives, collects, and displays the traffic data. The process of configuring the management application for data collection involves sending snmp set commands that trigger the switch to send the sFlow data. Please see the configuration examples for further information on the snmp set commands used.

To allow the management station to configure the sFlow parameters, the software will need to be configured with valid read and write SNMP community names or valid SNMPv3 configuration information that matches what is configured on the switch.

The show sflow command set may be used to view various aspects of the sFlow configuration and status.

» Return to top
Q: How do I take advantage of multiple configuration files?
The switch allows up to three startup-config files with options for selecting which startup-config file to use for:

* A fixed reboot policy using a specific startup-config file for a specific boot path (primary or secondary flash)
* Overriding the current reboot policy on a per-instance basis

multiple configuration files

While you can still use remote storage for startup-config files, you can now maintain multiple startup-config files on the switch and choose which version to use for a reboot policy or an individual reboot.

This choice of which configuration file to use for the startup-config at reboot provides the following new options:

* The switch can reboot with different configuration options without having to exchange one configuration file for another from a remote storage location.
* Transitions from one software release to another can be performed while maintaining a separate configuration for the different software release versions.
* By setting a reboot policy using a known good configuration and then overriding the policy on a per-instance basis, you can test a new configuration with the provision that if an unattended reboot occurs, the switch will come up with the known, good configuration instead of repeating a reboot with a misconfiguration.

For more detail on the use of multiple configuration files, please see the Management and Configuration Guide.

» Return to top
Q: What is the benefit of maintaining current software on my ProCurve Switch?
One of the benefits of owning a ProCurve product is free software updates. Maintaining current software can proactively add to the reliability of your product. In addition to addressing occasional issues in new software versions, ProCurve Networking also adds features and enhancements to software which provide investment protection by extending the value and functional life of products. A proactive notification service is available on the MyProCurve portal. This service generates an e-mail alert when the product line you select has a new version of software posted to the ProCurve web site.


Q: Why doesn't the VRRP backup router respond to pings when it is in the master role?

This behavior is by design, and is required by section 6.4.3 of the VRRP RFC 3768. The backup router will forward traffic as appropriate for its gateway role, but will not respond to ping. The failed ping response is often an important mechanism for reporting the failover which has occurred on the network segment.
Matt Hobbs
Honored Contributor

Re: VRRP on 5400zl

Oops, accidentally pasted the whole thing.

Q: Why doesn't the VRRP backup router respond to pings when it is in the master role?

This behavior is by design, and is required by section 6.4.3 of the VRRP RFC 3768. The backup router will forward traffic as appropriate for its gateway role, but will not respond to ping. The failed ping response is often an important mechanism for reporting the failover which has occurred on the network segment.

knite
Occasional Advisor

Re: VRRP on 5400zl

This behavior is by design, and is required by section 6.4.3 of the VRRP RFC 3768. The backup router will forward traffic as appropriate for its gateway role, but will not respond to ping. The failed ping response is often an important mechanism for reporting the failover which has occurred on the network segment.