Users Guide
Table Of Contents
- Active System Manager Release 8.3.1 User’s Guide
- Overview
- Getting started with ASM 8.3.1
- Initial Setup
- Dashboard
- Services
- Deploying service
- Add existing service
- Viewing service details
- Editing service information
- Deleting service
- Exporting service details
- Retrying service
- Viewing all settings
- Migrating servers (service mobility)
- Migrating servers
- Upgrading components
- Adding components to an existing service deployment
- Deleting resources from service
- Templates
- Managing templates
- Viewing template details
- Creating template
- Editing template information
- Building template overview
- Building and publishing template
- Importing template
- Exporting template
- Uploading external template
- Editing template
- Viewing template details
- Deleting template
- Cloning template
- Deploying service
- Deploying multiple instances of service
- Adding Attachments
- Decommissioning services provisioned by ASM
- Component types
- Component combinations in templates
- Additional template information
- Managing templates
- Resources
- Resource health status
- Resource operational state
- Port View
- Resource firmware compliance status
- Updating firmware
- Removing resources
- Viewing firmware and software compliance report
- Discovery overview
- Configuring resources or chassis
- Removing discovered resources
- Configuring default firmware repository
- Running firmware compliance
- Configuring global chassis settings
- Configuring unique chassis settings
- Configuring unique server settings
- Configuring unique I/O module settings
- I/O module configuration
- Completing the chassis configuration
- Adding or editing Chassis Management Controller (CMC) user
- Adding or editing Integrated Dell Remote Access Controller (iDRAC) user
- Updating resource inventory
- Viewing resource details
- Understanding server pools
- Settings
- Troubleshooting

NOTE: The virtual MAC identity that ASM assigns to the NIC depends on the network type selected when adding a
network.
• For a LAN network type, a virtual MAC address is assigned to the server.
• For an iSCSI network type, a virtual iSCSI MAC address is assigned to the server.
6. In the VLAN ID eld, type the VLAN ID between 1 and 4094.
NOTE: ASM uses the VLAN ID specically to congure I/O modules to enable network trac to ow from the
server to congured networks during deployment.
NOTE: The VLAN ID can be edited only if the network is not currently referenced by a template.
7. Select Congure static IP address ranges check box, and then do the following:
NOTE: After a network is created, you cannot select or clear the Congure static IP address ranges check box to
congure static IP address pools.
a. In the Gateway eld, type the default gateway IP address for routing network trac.
b. In the Subnet Mask eld, type the subnet mask.
c. Optionally, in the Primary DNS and Secondary DNS elds, type the IP addresses of primary DNS (required) and secondary
DNS (optional).
d. Optionally, in the DNS Sux eld, type the DNS sux to append for host name resolution.
e. Click Add IP Range, type a Starting IP Address and Ending IP Address, and then click Save IP Range. Repeat this step to
add multiple IP address ranges based on the requirement.
NOTE: The IP address ranges cannot overlap. For example, you cannot create an IP address range of 10.10.10.1–
10.10.10.100 and another range of 10.10.10.50–10.10.10.150.
NOTE: The network type can be edited only if the network is not currently referenced by a template.
8. To dene the network conguration, click Save.
Related links
Network types
Network types
Using ASM, you can manage the following network types:
• Private LAN—Used to access network resources for functions such as vMotion trac or heartbeat communication.
• Public LAN—Used to access network resources for basic Networking activities.
NOTE: Private and public LANs are functionally identical in ASM. The purpose of oering both labels is to help users
categorize LANs based on functional use.
• SAN (iSCSI)—Used to manage storage-related trac on an iSCSI network. If an IP address pool is associated with the network,
then ASM can use it to congure the iSCSI initiator IP address when doing a SAN (iSCSI) boot. Static or DHCP.
• Hypervisor Management—Used to identify the management network for a hypervisor or operating system deployed on a
server.
• Hypervisor Migration—Used to manage the network that you want to use for live migration. Live migration allows you to move
running virtual machines from one node of the failover cluster to dierent node in the same cluster.
• Hypervisor Cluster Private — Used for private cluster heartbeat network communication.
• OS Installation — Allows static or DHCP network for OS imaging on servers.
NOTE: When the OS Installation network is set to Static, OS Installation is supported only for installing Linux, ESXi,
and Windows on bare-metal systems with Intel NICs.
• Hardware Management—Used for out-of-band management of hardware infrastructure.
• The FIP VLAN Request is multicast to the destination MAC Address of ALL-FCF-MACs. The Source Address for the VLAN
Request is the ENode MAC, and it is important to note that the frame is transmitted without an 802.1Q (VLAN) tag.
VLAN ID
A VLAN ID is a unique identier that enables switching and routing of network trac.
97