Alcatel Unleashed

Hi Team,

Can any one help me to do the configuration for the below concepts.
I have 4Nos Omni OS6250 series switch and 1Nos Omni-OS6450 switch.
-> 4 Nos of OS6250 directly connected to OS6450(port no 1/1,1/2,1/3 &1/4).
-> And each port of OS6250 switch should be configure in separate vlan (i.e, vlan 101 to 124 for 1st switch)
vlan 201 to 224 for 2nd switch, vlan 301 to 324 for 3rd switch & vlan 401 to 424 for 4th switch)
-> Each vlan should falls under separate network and no need intervlan communication.
-> But All the system(96 nos) connected in switches(OS6250) should communicate to FTP server which is connected to one of the port at OS 6450 switch.

? is it possible to configure dhcp server in the switch itself to supply Different network IP for each port ?

Quick Steps to Configure Internal DHCP Server
DHCP server software is installed on the OmniSwitch to centrally manage IP addresses and other TCP/IP
configuration settings for clients present on a network.
Follow the steps in this section for a quick tutorial on how to configure an internal DHCP server on the
OmniSwitch.
Note. For detailed information on how to configure the DHCP server on OmniSwitch, see the Configuring
DHCP Server on OmniSwitch section.
1 Navigate to /flash/switch directory.
-> cd /flash/switch
2 Copy the dhcpd.conf.template file and save it as dhcpd.conf. The dhcpd.conf file can then be
customized as necessary.
-> cp dhcpd.conf.template dhcpd.conf
3 Copy the dhcpd.pcy.template file and save it as dhcpd.pcy. The dhcpd.pcy file can then be customized
as necessary.
4 Customize the dhcp.conf and dhcpd.pcy files according to your requirements. Use the vi command to
modify the existing configuration file.
-> vi dhcpd.conf
Declare dynamic DHCP options, global options, and server configuration parameters for client
interfaces in the dhcpd.conf file. Add DHCP related information for a particular subnet.
For example, for the subnet 200.0.0.0, define the dynamic DHCP range, router option, domain name and
other details using the following code:
server-identifier sample.example.com;

subnet 200.0.0.0 netmask 255.255.255.0
{
dynamic-dhcp range 200.0.0.10 200.0.0.11
{
option subnet-mask 255.255.255.0;
option routers 200.0.0.254;
option domain-name-servers 200.0.0.99;
option domain-name "example.com";
option dhcp-lease-time 30000;
}
}
Note. See “Configuration File Parameters and Syntax” on page -13 topic of the Configuring DHCP Server
section for details on what each of the optional keywords specify.
Quick Steps to Configure Internal DHCP Server Configuring DHCP Server
page 32-4 OmniSwitch 6250/6450 Network Configuration Guide June 2013
5 After entering the required information in the dhcpd.conf file. Type :wq to save the changes made to
the dhcpd.conf file.
Note.
• If the dhcpd.conf file is corrupted, the dhcpd.conf.lastgood file is used as a backup file.
• If the dhcpd.conf file is updated successfully, then the dhcpd.conf.lastgood file is over written with
the configurations present in the dhcpd.conf file.
• Properly configured dhcpd.conf and dhcpd.pcy files can be transferred to the switch remotely instead
of using the vi editor.
6 Restart the DHCP server using the dhcp-server restart command. The changes made in the
dhcpd.conf file are applied to the OmniSwitch.
-> dhcp-server restart
Note. The dhcp-server restart command automatically updates the dhcpd.conf, dhcpd.conf.lastgood
and dhcpd.pcy files.
7 Enable the DHCP server using the dhcp-server command.
-> dhcp-server enable
Configuring DHCP Server DHCP Server Overview
OmniSwitch 6250/6450 Network Configuration Guide June 2013 page 32-5
8 Check the IP address leases by entering the following command:
-> show dhcp-server leases
IP address MAC address Lease Granted Lease Expiry Type
-------------+----------------+---------------------+--------------------+---------
200.255.91.53 10:fe:a2:e4:32:08 2010-01-16 11:38:47 2010-01-17 11:38:47 Dynamic
200.255.91.5 20:fe:a2:e4:32:08 2010-01-16 10:30:00 2010-01-18 10:30:00 Static
200.255.91.56 20:fe:a2:e4:33:08 2010-01-16 10:30:00 2010-01-18 10:30:00 Dynamic
200.255.91.58 20:fe:a2:e4:34:08 2010-01-16 10:30:00 2010-01-18 10:30:00 Dynamic

Ref:
http://enterprise.alcatel-lucent.com/as ... _revD1.pdf

https://mdnurain.wordpress.com/

It should be possible to serve all clients with ip addresses.
For that the switch needs an IP in each VLAN (according to Docs 128 IP interfaces are supported). Otherwise it will not serve an IP.

I see more problems in the "no intervlan communication" as as soon as you have an IP interface the switch will start routing.
you may need to have some deeper looks into qos rules which can act as acls. depending pon your needs it may work.
e.g.
permit any -> ftp
permit ftp -> any
Once you start trying to do some more stuff (e.g. permit vlan 1 to vlan 12 but only with ports A/B/C and vlan 12 -> vlan 1 ping only) it will get nasty very fast.

i;ve following this solution but dhcp server still cannot offer IP to client

check:
show dhcp-server statistics

and push the output of
dhcp-server restart