Static IP - MAC address binding in Comware 7

[lorn10]

Hello to all

I am in the process to migrate from a MSR Comware 5 to a MSR Comware 7 router. Most part of the config-porting has worked so far, the only roadblock seems to be the static binding of an IP to a MAC address.

My Comware 5 config looks like:

dhcp server ip-pool 192.168.1.10
 static-bind ip-address 192.168.1.10 mask 255.255.255.0
 static-bind mac-address xxxx-xxxx-xxxx
 gateway-list 192.168.1.1
 dns-list 8.8.8.8 8.8.4.4

When I now enter the above command under Comware 7 I will get various error-messages::

[HP MSR1002]dhcp server ip-pool 192.168.1.10
[HP MSR1002-dhcp-pool-192.168.1.10]static-bind ip-address 192.168.1.10 mask 255.255.255.0
                                                                                          ^
 % Incomplete command found at '^' position.
[HP MSR1002-dhcp-pool-192.168.1.10]static-bind ip-address 192.168.1.10 mask 255.255.255.0 mac-address xxxx-xxxx-xxxx
                                                                                          ^
 % Unrecognized command found at '^' position.

Unfortunately all config examples which I found were Comware 5 related. Can someone please give here a Comware 7 example? THANKS!

regards
lorn10

[Ivan_B · Accepted solution]

Hi @lorn10 !

Try this:

static-bind ip-address 192.168.1.10 24 hardware-address xxxx-xxxx-xxxx

[lorn10]

Hi Ivan_B

Many thanks for the super fast replay! This was the solution!

Unbelievable they now really call it hardware-address instead of mac-address. *lol* (Well yes, this is or may be more logical but out of mine view it is absolutely uncommon.)

And by the way, the following would also help to find the solution, just put a question mark ?:

[HP MSR1002-dhcp-pool-192.168.1.10]static-bind ip-address 192.168.1.10 mask 255.255.255.0 ?
  client-identifier  Specify a client-identifier
  hardware-address   Specify a hardware address

Again many thanks @Ivan_B for the help. So far you find the time, please also check an other question of me here:

https://community.hpe.com/t5/Comware-Based/Inter-vlan-routing-and-or-static-routing/td-p/7115683

[Ivan_B]

Hi @lorn10 !

Yes, I know how you feel with this migration (-: A lot of commands have been revised and definitely it takes some time to accomodate to changes. 

As for the terminology, to be honest I find 'hardware address' more precise term as it fully complies with DHCP terminology, if you check RFCs you will see that 'chaddr' field contains "Client hardware address" and RFC always uses 'hardware address' and never 'MAC address'. It has a very obvious explanation - DHCP is universal protocol that can work over many types of Layer 2 networks, not only over Ethernet. And if link-layer addresses there can be very different from MAC addresses, they can have different format, different name etc. but they still can be used by DHCP as 'chaddr' parameter. In general that's the logic to use more general term 'hardware address' instead of Ethernet-specific term 'MAC address'.