HP NC326m HP ProLiant Essentials Intelligent Networking Pack - Windows Edition - Page 39
Configuring Discovery Protocol
View all HP NC326m manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 39 highlights
Problem Possible cause Unable to select VLAN ID for This may be expected Active Path, Fast Path, and behavior based on the Router Path. configured settings. Possible solution Go to Advanced Redundancy Tab and enable the failover mechanism such as Active Path Failover or Fast Path Failover or Router Path Failover for which you are unable to set VLAN ID. Open the NCU and go to the Information tab for the team. Check the Current Mode. If the current team mode is 802.3ad Dynamic with Fault Tolerance or SLB (Switch-assisted Load Balancing), this is normal behavior. These team modes do not support Fast Path Failover, Active Path Failover and Router Path Failover. If you are unable to set the VLAN ID for fast path even though Fast Path has been selected in the Advanced Redundancy tab, then consider changing the Spanning Tree Protocol as Cisco PVST+. Configuring Discovery Protocol Problem Possible cause Possible solution When using CDPv1 the information tab does not display the VTP management domain name for my devices. This is expected behavior when using CDPv1. This feature is only available with CDPv2. If this information is important to you, consider using CDPv2 instead. The Discovery Protocol Settings group is disabled and I can't set the CDP or LLDP. This is expected behavior for Install a ProLiant Essentials Intelligent licensable features. Networking Pack license key CDP or LLDP is enabled and CDP or LLDP frames are being transmitted by the network device but they are not being received by the team. When CDP or LLDP is first Disable CDP or LLDP then re-enable it and enabled, it may take 30 verify that the team registers the address. seconds to receive the first CDP or LLDP frame. It is possible that this delay occurred as the teaming driver attempted to register the CDP or LLDP multicast address with the miniport. This delay may have caused the team to fail to register the multicast address. Troubleshooting 39