hi all,
i have tried to confifure an internal dhcp server on omniswitch os6900 ,with the attached (scope)
dhcp.conf file , but it did not work, please advise.
Note:
10.0.0.254,10.101.0.254,10.102.0.254,10.103.0.254,10.104.0.254,10.105.0.254 and 10.106.0.254
are an ip interfaces for 11,101,102,103,104,105 and 106 Vlan.
sw:7.3.3.384R01
BR
internal dhcp server
internal dhcp server
You do not have the required permissions to view the files attached to this post.
Re: internal dhcp server
very old software is used....
And what is the error-message if you enable AND restart the dhcp-server? ls output (ls -l) of directory switch (where both the files has to be).
regards
Silvio
And what is the error-message if you enable AND restart the dhcp-server? ls output (ls -l) of directory switch (where both the files has to be).
regards
Silvio
Re: internal dhcp server
hi Silvio
you are absolutely right, but unfortunately and according to Alcatel doc. we can not have an internal DHCP and DHCP snooping in a switch at the same time, therefore I have installed a Separate win. Dhcp Server .
this Network has a OS6900 Core Sw. connected to the No. of five A6450 stack switches (Star Connection) configured as a layer 2 SW and the Core will handle all the routing process.the PBX (DHCP) and DHCP win Server are connected to the Core.
So may I ask you it is ok to config dhcp snooping in the core and just trust the PBX & DHCP Server with enable a dhcp snooping binding & ip-source-filter
on ports connected to the Stack switches to stop any sniff attack and prevent any ip duplicate.
what about "dhcp-snooping option-82-data-insertion admin-state" should be enable/disable in a core/stack ?
please advise
BR
you are absolutely right, but unfortunately and according to Alcatel doc. we can not have an internal DHCP and DHCP snooping in a switch at the same time, therefore I have installed a Separate win. Dhcp Server .
this Network has a OS6900 Core Sw. connected to the No. of five A6450 stack switches (Star Connection) configured as a layer 2 SW and the Core will handle all the routing process.the PBX (DHCP) and DHCP win Server are connected to the Core.
So may I ask you it is ok to config dhcp snooping in the core and just trust the PBX & DHCP Server with enable a dhcp snooping binding & ip-source-filter
on ports connected to the Stack switches to stop any sniff attack and prevent any ip duplicate.
what about "dhcp-snooping option-82-data-insertion admin-state" should be enable/disable in a core/stack ?
please advise
BR
Re: internal dhcp server
yes - you can't use internal dhcp-server and dhcp-snooping at the same switch. In this case I use an other switch (not the core) as dhcp server (or external server).
If you have a separate core (without any clients direct connected) than you don't need there ISF (IP-Source-Filter). I prefere to use this feature only at the access switches (with connected dhcp-clients). Than you have to trust the uplink to all the real dhcp servers.
If you need to forward the option 82 to your dhcp-server than you need to keep this info (at the core) in the orign dhcp-packet (from the access switch). At core "ip helper agent-information policy keep"
regards
Silvio
If you have a separate core (without any clients direct connected) than you don't need there ISF (IP-Source-Filter). I prefere to use this feature only at the access switches (with connected dhcp-clients). Than you have to trust the uplink to all the real dhcp servers.
If you need to forward the option 82 to your dhcp-server than you need to keep this info (at the core) in the orign dhcp-packet (from the access switch). At core "ip helper agent-information policy keep"
regards
Silvio
Re: internal dhcp server
hi Silvio,
thank you for your reply, things are clear now.
thanks again
BR
thank you for your reply, things are clear now.
thanks again
BR
