Once wireless is configured, the console of the Unified controller can get lots of messages about wlan events or portsec login failures. You can use the undo terminal monitor to get rid of all messages, or you can just disable specific category events.
This example disables the WMAC (associate/disassociate) and PORTSEC logging on the console (channel 0), all other events will still show:
info-center source WMAC channel 0 log state off trap state off
info-center source PORTSEC channel 0 log state off trap state off
If you still have some original H3C branded switches in your network, it is possible to re-brand them to HP, so they will be recognized as the HP counter-part of the H3C model.
To change the brand, use the brand command in the user-view of the system. Make sure some recent firmware is available, since the brand command was not included in the original H3C firmware. This is an example on the 5800 switch: Continue reading
Posted in Comware5
Multiple-Active Detection (MAD) is used to detect a split brain in an IRF system. When the MAD BFD method is used, a dedicated Layer3 VLAN interface needs to be configured for the MAD BFD operation.
This VLAN should be directly connected through an interface on each IRF member. Transit Layer2 device are supported, you just need to ensure they do not perform any kind of Layer2 blocking (STP or the like) on these ports.
This also means that the IRF member switches must offer a physical interface for the MAD BFD operation. Continue reading
There is a tricky “new” behavior in Comware7 Layer3 VLAN ACL processing: the applied ACL does not only filter the inter-vlan routed traffic (as would be expected), but it is applied to intra-vlan switched traffic as well by default. This behavior can now be controlled, so the admin can revert it to the “expected” behavior: Continue reading
When configuring a network device to be managed by an NMS such as HP IMC, you may want to send some test syslog or snmp traps to verify the correct operation of your settings.
You can generate traps/logs by triggering some events, but you also just use the test trap and log function on Comware5:
The HP 6125XLG is a Comware 7 based blade interconnect switch which has full support for FCoE.
I found this technical whitepaper with a sample FCoE NPV mode configuration, it is shown with uplinks to an existing Nexus 5500/6000 FCoE infrastructure.
Direct download link: Continue reading
The HP Unified Wireless manuals are quite extensive, but it can be challenging to get a complete picture of a certain feature.
HP has now published a series of whitepapers covering specific use cases and technologies, they can be found on the HP Support site under the manuals section of the controllers.
To get them: Continue reading
On the Unified wireless solution, guest users can be authenticated through the captive web-portal feature of the portal server.
The network admin could allow some guest traffic to pass without guest authentication to provide a “walled-garden” solution.
This was already possible using the portal free-rule configuration, but the free-rule only supported source/destination IP/TCP/UDP information. It was not possible to include a DNS domain name.
Release 3507P32 (830) and 2507P32 (850/870/20G) now includes a portal free rule for URLs containing a permitted string. In this post a quick overview of how the feature works. Continue reading
Comware has 2 types of link-aggregation:
- static link-aggregation: no control protocol is used, based on the configuration, the link-aggregation member interfaces will be actively participating (Selected) in the link-aggregation at the moment the interfaces come up.
- dynamic link-aggregation: LACP control protocol is used. Interfaces are added to the link-aggregation based on the config. The operational state (Selected/Unselected) depends on the result of the LACP negotiation with the peer
In some situations, a mix of both is required. This post shows how this can be configured. Continue reading
New to HP Networking products? Know Cisco IOS CLI and now work with HPN products? Or know Comware (from previous 3Com/H3C days) and now also work with HPN ProVision products? Or know HPN ProVision and now work with Comware? And more than anything, you just want a reference that shows you how to translate what you know in one of these CLI’s into the “new” CLI you’re trying to learn??? Well, the HP Networking and Cisco CLI Reference Guide is the book for you. Continue reading
In this post an overview of the integration of the IMC TAM module with an Active Directory LDAP Server.
The goal of this configuration is to ensure members of a specific Active Directory group (for example g_networkadmins) are granted a specific IMC TAM Policy level.
The HP IMC BYOD solution requires a network device to redirect guest or onboarding users to the BYOD web portal.
This functionality could be provided using almost any Comware 5/7 device (L3 Switches, routers, VSR, but not by the L3-lite such as the 5120 !).
However, when a network has mainly Provision devices, the network required the introduction of a Comware device to make the BYOD solution work.
With the current firmware (K.15.16.0004) of the 5400/3500/3800 series, the Portal redirect function has been introduced on the Provision platform as well. Details can be found in the K.15.16 Advanced Traffic Management Guide, the feature is referred to as BYOD-redirect.
When you use IRF to group multiple Comware switches into 1 logical device, it is generally recommended to enable some split brain detection (split brain happens when all the stacking links are down).
For the MAD LACP method, only Comware switch could be used so far, now the Provision switches firmware has been updated, so an LACP link between a Provision and Comware IRF can be used for the MAD LACP.
HP has released K.15.16.0004 firmware for the Provision asic switch series (3500/3800/5400/8200/etc). Next to some interesting new features (DHCP Server is now supported and it can be used for the IMC BYOD Portal Redirect), this firmware also enables the old premium license feature permanently on the switches.
Dear HPN Community,
Everyone wants to learn more around Software-Defined Networking. In order to make installation of controller really simple with only one command my colleague Shiraz Qureshi made awesome script.
Shiraz shared location of the script on our GitHub community:
So make it simple for yourself. Install Ubuntu in combination with this script and HP VAN SDN Controller is running.
Be innovative . . .