Comware

 View Only
last person joined: yesterday 

Back to discussions
Expand all | Collapse all

Migrated from 4104GL to 5406ZL and DHCP on VLAN2 no longer works

This thread has been viewed 0 times

  • 1.  Migrated from 4104GL to 5406ZL and DHCP on VLAN2 no longer works

    Posted Aug 10, 2011 04:04 AM

    As in the subject,  we have transferred the settings from the old to the new switch (both show run outputs are in the attached files) but on VLAN2 the 10.0.0.0 range a machine does not pick up an IP address when connected to a port on this VLAN.  However,  if we connect a patch lead to the old switch (having the same IPS!) the machine gets an IP address.  Something must be missing on the 5406ZL settings but we cannot figure out what it is.  Any help gratefully received - Thanks.  Richard


    #migration

    Attachment(s)

    pdf
    5406ZL Settings.pdf   703 B 1 version
    pdf
    4104GL Settings.pdf   703 B 1 version


  • 2.  RE: Migrated from 4104GL to 5406ZL and DHCP on VLAN2 no longer works

    Posted Aug 14, 2011 12:43 PM

    Hi

     

    Your DHCP server is on 192.168.3 -range, but there's no interface on either switch to that range. So your router must route the DHCP packets to the server. It sounds like your 4200 doesn't have a route to the 192.168.3 -range at all, but your 5400 has. Check your topology and router configuration.



  • 3.  RE: Migrated from 4104GL to 5406ZL and DHCP on VLAN2 no longer works

    Posted Aug 15, 2011 03:37 AM

    Hi,

    Thanks for the reply.  Must admit to being confused by this.  I thought the Ip helper address of 192.168.3.2 did this - or am I misunderstanding what you mean by 'router'?  As both switches seem to have the same settings,  replacing one by the other and then not getting the DHCP on the 10. scope but it working on thr 192. scope I really cannot get my head around.

     

    Richard



  • 4.  RE: Migrated from 4104GL to 5406ZL and DHCP on VLAN2 no longer works

    Posted Sep 27, 2011 10:15 AM

    Just to update my post with a solution from an HP engineer, in case anyone else has a similar problem in the future.  The command which cured the issue was

     

    No management-vlan 1

     

    Apparently due to extra security on VLAN1 whcih was also the VLAN attached to the DHCP server.