Dell 8 manual

Page 48

#subnet 10.254.239.32 netmask 255.255.255.224 { #range dynamic-bootp 10.254.239.40 10.254.239.60; #option broadcast-address 10.254.239.31; #option routers rtr-239-32-1.example.org;

#}

#A slightly different configuration for an internal subnet. #subnet 10.5.5.0 netmask 255.255.255.224 {

#range 10.5.5.26 10.5.5.30;

#option domain-name-servers ns1.internal.example.org; #option domain-name "internal.example.org"; #option routers 10.5.5.1;

#option broadcast-address 10.5.5.31; #default-lease-time 600; #max-lease-time 7200;

#}

#Hosts which require special configuration options can be listed in

#host statements. If no address is specified, the address will be

#allocated dynamically (if possible), but the host-specific information

#will still come from the host declaration.

#host passacaglia {

#hardware ethernet 0:0:c0:5d:bd:95;

#filename "vmunix.passacaglia";

#server-name "toccata.fugue.com";

#}

#Fixed IP addresses can also be specified for hosts. These addresses

#should not also be listed as being available for dynamic assignment.

#Hosts for which fixed IP addresses have been specified can boot using

#BOOTP or DHCP. Hosts for which no fixed address is specified can only

#be booted with DHCP, unless there is an address range on the subnet

#to which a BOOTP client is connected which has the dynamic-bootp flag

#set.

#host fantasia {

#hardware ethernet 08:00:07:26:c0:a5;

#fixed-address fantasia.fugue.com

#}

#You can declare a class of clients and then do address allocation

#based on that. The example below shows a case where all clients

#in a certain class get addresses on the 10.17.224/24 subnet, and all

#other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {

#match if substring (option vendor-class-identifier, 0, 4) = "SUNW";

#}

#shared-network 224-29 {

#subnet 10.17.224.0 netmask 255.255.255.0 { #option routers rtr-224.example.org;

#}

#subnet 10.0.29.0 netmask 255.255.255.0 {

#option routers rtr-29.example.org;

#}

48

Image 48
Contents Active System Manager Version 8.0 Quick Installation Guide Page Contents Configuring Dhcp or PXE on External Servers What is New in this Release Accessing Online HelpAbout this Document Other Documents You May Need LicensingImportant Note ASM Port and Protocol Information Installing Active System Manger Information PrerequisitesDeployment Prerequisites Page Page Prerequisites for M1000e with MXL, S5000, and Compellent MXLInterface range fi 0/0 7 no shut Prerequisites for Rack Server, S5000, and Compellent Dcbx port-role auto-downstream Prerequisites for Rack Server, S5000, Brocade and Compellent Interface vlan Vlan ID Create Vlan for FCoE Exit Feature fcoe feature npiv feature lacp Prerequisites for Rack Server, Cisco Nexus, and Compellent Interface vfc101 Conf feature npv Resource Create VSAN-instantiate it in the Vsan database FC feature needs to be enabled on the MXL System Center Virtual Machine Manager Scvmm Prerequisites Deploying ASM from VMware vSphere ClientDeploying ASM using Scvmm Deploying ASM on Hyper-V host Changing Dell Administrator Password Configuring Static IP Address in the Virtual ApplianceConfiguring ASM Virtual Appliance as PXE Boot Responder Customizing Virtual Machine Templates for VMware and Hyper-V Main Server=dellasm Master Agent Customizing Linux Template Rm /lib/udev/rules.d/75-persistent-net-generator.rulesCustomizing Windows Template Crontab -lPage Adding NetApp Ruby SDK Enable Http or HTTPs for NFS share Configuring NetApp Storage ComponentPage Completing Initial Configuration Page Deploying WinPE on the Virtual Appliance Adding OS Image Repositories Page Page Configure Dhcp on Windows 2012 Dhcp Server Create the Dhcp User ClassCreate the Boot File Scope Option Configure Dhcp on Windows 2008 Dhcp ServerCreate the Dhcp Policy Create the Dhcp User Class Configuring Dhcp for Linux Sample Dhcp Configuration
Related manuals
Manual 36 pages 54.81 Kb