Sunday, 25 March 2012

ITIL: Study Notes for “ISEB BH0-012 – The Foundation ITIL” Exam

ITIL was built around Deming's plan-do-check-act cycle.

Definitions
+ Definitive media library (DML) = a secure library where definitive authorized versions of all media configuration items (CIs) are stored and protected
+ Governance = is concerned with policy and direction.
+ ITIL = Information Technology Infrastructure Library.
+ Implementation of ITIL service management requires the preparation and planning of the effective and efficient use of the four Ps = People, Process, Products, Partners
+ Service Management = a set of specialized organizational capabilities for providing value to customers in the form of services.
+ Service request = a request from a user for information, advice, or for a standard change.
+ SLA = Service Level Agreement: An agreement between the service provider and their customer

ITIL Service Lifecycle
1. Service Strategy
2. Service Design: Design the Processes
3. Service Transition: Plan and Prepare for Deployment
4. Service Operation: IT Operations Management
5. Continual Service Improvement
1. Service Strategy
1.1 Strategy Management for IT services
1.2 Service Portfolio Management
1.3 Financial Management of IT Services
… ensuring that the IT infrastructure is obtained at the most effective price (which does not necessarily mean cheapest) and calculating the cost of providing IT services so that an organisation can understand the costs of its IT services.
1.4 Demand Management
1.5 Business Relationship Management

2. Service Design
A service should always deliver value to customers.
Resources and capabilities create value for customers.
The Service Design Stage is MOST concerned with defining policies and objectives, and includes:
+ Producing quality, secure, and resilient designs for new or improved services
+ Taking service strategies and ensuring they are reflected in the service design processes and the service designs that are produced
+ Measuring the effectiveness and efficiency of service design and the supporting processes
A service design package (SDP) contains information that is passed to service transition to enable the implementation of a new service.
2.1 Design Coordination
2.2 Service Catalogue
The responsibility of service catalogue management:
+ Ensuring that information in the service catalogue is accurate
+ Ensuring that information in the service catalogue is consistent with information in the service portfolio
+ Ensuring that all operation services are recorded in the service catalogue
2.3 Service Level Management
The purpose of service level management = to ensure an agreed level of IT service is provided for all current IT services.
Service level management process is responsible for discussing reports with customers showing whether services have met their targets.
2.4 Availability Management
+ Reliability: Ability of an IT component to perform at an agreed level at described conditions.
+ Maintainability: The ability of an IT component to remain in, or be restored to an operational state.
+ Serviceability: The ability for an external supplier to maintain the availability of component or function under a third-party contract.
+ Resilience: A measure of freedom from operation failure and a method of keeping services reliable (e.g. redundancy)
+ Security: refers to the confidentiality, integrity, and availability of that data.
2.5 Capacity Management
The capacity management process includes business, service, and component sub-processes. The high-level activities include:
+ Application sizing
+ Workload management
+ Demand management
+ Modelling
+ Capacity planning
+ Resource management
+ Performance management
2.6 IT Service Continuity Management (ITSCM)
Involves the following basic steps:
+ prioritising the activities to be recovered by conducting a business impact analysis (BIA)
+ performing a risk assessment (risk analysis) for each of the IT services to identify the assets, threats, vulnerabilities and countermeasures for each service
+ evaluating the options for recovery
+ producing the contingency plan / business continuity strategy
+ testing, reviewing, and revising the plan on a regular basis
2.7 Information Security Management System
2.8 Supplier Management
Third-party contracts are the responsibility of supplier management to negotiate and agree.

3. Service Transition
Service transition stage responsibilities:
+ To ensure that a service can be managed and operated in accordance with constraints specified during design
+ To provide good-quality knowledge and information about services
+ To plan the resources required to manage a release
3.1 Transition planning and support
3.2 Change management
The RACI Matrix – Who's Responsible, Accountable, Consulted... and kept Informed
+ R(esponsible) – Who is responsible for actually doing it?
+ A(ccountable) – Who has authority to approve or disapprove it?
+ C(onsulted) – Who has needed input about the task?
+ I(nformed) – Who needs to be kept informed about the task?
The main aims of change management include:
+ Minimal disruption of services
+ Reduction in back-out activities
+ Economic use of resources involved in the change
Emergency change advisory board: group that should review changes that must be implemented faster than the normal change process
3.3 Service asset and configuration management
The configuration management system is part of the service knowledge management system.
The configuration management system (CMS) can help determine the level of impact of a problem.
The relationship in service asset and configuration management describes how the configuration items (CIs) work together to deliver services.
Includes the following key process areas:
+ Identification
+ Planning
+ Change Control
+ Change Management
+ Release Management
+ Maintenance
3.4 Release and deployment management
Objectives of release and deployment management: To define and agree release and deployment plans with customers and stakeholders. The goals of release management include:
+ Planning the roll-out of software
+ Designing and implementing procedures for the distribution and installation of changes to IT systems
+ Effectively communicating and managing expectations of the customer during the planning and roll-out of new releases
+ Controlling the distribution and installation of changes to IT systems
3.5 Service Validation and testing
3.6 Change evaluation
3.7 Knowledge management

4. Service Operation
Service operation stage of the service lifecycle, delivers and manages IT services at agreed levels to business users and customers. Service operations contribution to business is adding value, and the service value is visible to customers.
The following areas of service management can benefit from automation:
+ Design and modelling
+ Reporting
+ Pattern recognition and analysis
+ Detection and monitoring
List of processes:
4.1 Event management
The event management process is involved in monitoring an IT service and detecting when the performance drops below acceptable limits
4.2 Incident management
*Major incidents require separate procedures.
The objectives of incident management:
+ To restore normal service operation as quickly as possible
+ To minimize adverse impacts on business operations
4.3 Request fulfilment
4.4 Problem management
A problem = a condition often identified as a result of multiple incidents that exhibit common symptons.
Objectives of problem management:
+ Minimizing the impact of incidents that cannot be prevented
+ Preventing problems and resulting incidents from happening
+ Eliminating recurring incidents
4.5 Access management
Access management process is responsible for providing rights to use an IT service.

5. Continual Service Improvement (CSI)
Where to we want to be?
Define measurable targets (Service metrics measure: The end-to-end service.)
Improvement initiatives typically follow a seven-step process:
5.1 Identify the strategy for improvement
5.2 Define what you will measure
5.3 Gather the data
5.4 Process the data
5.5 Analyse the information and data
5.6 Present and use the information
5.7 Implement improvement

Appendix A: ITIL Function – Service Desk (function of Service Operation)
Service desk features include:
+ single point of contact (SPOC)
+ single point of entry
+ single point of exit
+ make life easier for customers
+ data integrity
+ incident control: life-cycle management of all service requests
+ communication: keeping a customer informed of progress and advising on workarounds
Types of service desk structure:
+ Local service desk: to meet local business needs
+ Central service desk: for organisations having multiple locations
+ Virtual service desk: for organisations having multi-country locations
+ Follow the Sun

Appendix B: ITIL Function - Software Asset Management (function of Service Operation)
Software asset management (SAM) practices include:
+ maintaining software license compliance
+ tracking inventory and software asset use
+ maintaining standard policies and procedures surrounding definition, deployment, configuration, use, and retirement of software assets and the DML

Saturday, 24 March 2012

HP P2000 G3: Installing Plug-in for VMware VAAI for vSphere 4.1

The following post continues from the previous post HP P2000 G3: Upgrading Firmware to TS230P008 and runs through a step by step walkthrough to install the HP P2000 Software Plug-in for VMware VAAI vSphere 4.1, into an ESXi 4.1 host using the VMware vSphere CLI.

Preliminaries:
1) Download softwares
Either Google "HP P2000 Software Plug-in for VMware VAAI vSphere 4.1" or try this link
2) Arrange downtime for host reboots if required

Install:
1) Place the host to be patched into maintenance mode
2) From the downloaded .zip file, extract contents including the hp_vaaip_p2000_XXX.zip file and place into the C:\Program Files (x86)\VMware\VMware vSphere CLI\bin folder
3) Install the VAAI Plug-in using the vCLI Command Prompt from C:\Program Files (x86)\VMware\VMware vSphere CLI\bin and the command
> vihostupdate.pl --server Host_IP_Address --username User_Name --password Account_Password --bundle hp_vaaip_p2000-xxx.zip --install
4) Restart the host
5) Exit maintenance mode

Appendix A: Verifying VAAI using the following vCLI commands:
a) Check for new HP P2000 claim rules:
> esxcli --server Host_IP_Address --username User_Name --password Account_Password corestorage claimrule list –c VAAI
b) Check for claimed storage devices:
> esxcli --server Host_IP_Address --username User_Name --password Account_Password vaai device list
Or visually check under the Hardware Acceleration column in the vSphere Client to see that Hardware Acceleration is now Supported (previously it would have been unknown.)
Appendix B: Enhancements of VAAI (source HP.com)
       Included in the VMware vSphere 4.1 management station, the vStorage API for Array Integration (VAAI) can be used to off-load certain functions from the target VMware host to the storage array. With the tasks being performed more efficiently by the array instead of the target VMware host, performance can be greatly enhanced.
       The HP P2000 Software Plug-in for VMware VAAI (VAAI Plug-in) allows offloading the following functions (primitives) to the MSA array: o Full copy—enables the array to make full copies of data within the array, without the ESX server having to read and write the data. o Block zeroing—enables the array to zero out a large number of blocks to speed up provisioning of virtual machines. o Hardware assisted locking—provides an alternative means to protect the metadata for VMFS cluster-file systems, thereby improving the scalability of large ESX server farms sharing a datastore.

HP P2000 G3: Upgrading Firmware to TS230P008

The following post runs through a step by step walkthrough to upgrade the storage controller firmware on a HP P2000 G3, using the Online ROM Flash Component for Windows and the GUI Option.
If the P2000 is hosting a VMware vSphere 4.1+ environment, it is highly recommended to upgrade the controller firmware to take advantage of the VMware VAAI features if the current firmware is not yet at a sufficient level (that is TS230R044 or better.)

Preliminaries:
1) Check current firmware revisions
2) (Optional but recommended) Check support agreements are in place with 4th line – HP Manufacturer – support just in case!
3) Download softwares
Either Google "Online ROM Flash Component for Windows – HP P2000 G3 MSA Arrays" or try this link
4) Arrange downtime
5) (Essential) Ensure backups from P2000 SAN are sufficient

Pre-Install Steps:
1) Disable any backup/replica jobs that access the P2000
2) Put into maintenance mode any VDI desktop groups that access LUNs on the P2000
3) Disable any monitoring and/or notify relevant personnel that works are in progress
4) Where possible to do so - shutdown VMware guests and hosts in order to facilitate the upgrade running smoothly

Upgrade:
1) Using the Storage Management Utility, check that no changes are in progress on the P2000 (if so then wait for progress to complete)
2) Double-click the downloaded firmware package, and select Run if the Security Warning box pops up
3) Click Install and wait for the package to extract
4) On the HP Package Setup window, enter IP Address, User Name, and Password for the system and click Continue
5) Click Install and wait! Allow approx. 30 minutes for firmware to load and automatic restart to complete on the first controller, and a further hour if there is a second controller in the system (total 90 minutes.)
Note: If the firmware is far out of date (like TS100R025 – see below), the installer will automatically upgrade to TS201R015 then to TS230P008. In this case it can take 3 hours for the firmware to apply across the two controllers!
The GUI will post updates from the Installation Log (saved to systemdrive\CPQSYSTEM\Log\MSA2000.log) showing the progress of the upgrade.
6) The End!

Friday, 23 March 2012

VBR6: Exchange AIR Single Item Email Recovery Setup and Configure Part 2/2

4: Exchange AIR Lab Request
i) Run the Exchange Application Item Recovery application from the Programs Menu
ii) Choose the duration you want the lab to run for and click Next >
Note: The lab duration can be extended later. Be careful not to leave the lab running too long as it locks the backup files it requires to run the lab, which will cause scheduled backups to fail if they try to run whilst the lab is up.

iii) Enter the name of a Global catalog, choose credentials for connection to Active Directory, click Connect to check connection to DC, then click Next >
iv) Complete the details for the Mailbox you want to restore items from, then click Next >
v) Choose the desired restore point, then click Next >
vi) Click Finish

5: Approving the Lab Request
i) Open Veeam Backup Enterprise Manager
ii) Go to the “Requests” tab and select the new request and click “Approve”
iii) On the Edit Lab Request screen, click Next > Next > Next > Next > Finish
Note: The Exchange AIR recovery needs the SureBackup job to be configured correctly in order to work

6: Performing the restore
i) Wait for the Virtual Lab to reach the Ready state, and when the lab status is Ready, then from within the Microsoft Exchange AIR Wizard, click Next >
Note: If the Wizard has been closed by mistake, from the Virtual Lab Manager GUI, select the Active and Ready Virtual Lab and select Open
ii) Verify the Mailbox Account selection, then click Next >
And follow through the wizard to complete the restore....


This post followed on from:

VBR6: Exchange AIR Single Item Email Recovery Setup and Configure Part 1/2

The following post takes you through a step by step walkthrough for setup and configuring Veeam Backup & Replication 6 for the recovery of emails from Microsoft Exchange using the Veeam Microsoft Exchange AIR utility. The steps involve:

Part 1/2 Setting Up The Lab, Application Group, and SureBackup job
1: Create the Virtual Lab
2: Create the Application Group
3: Create Corresponding SureBackup job for Exchange Server

Part 2/2 Lab Request and Performing the Restore
4: Exchange AIR Lab Request
5: Approving the Lab Request
6: Performing the Restore

Prerequisites:
+ Veeam Backup server with Enterprise Manager and Exchange AIR installed
+ Veeam Backup Enterprise License
+ A Veeam backup of the Exchange Server
+ A Veeam backup of a Domain Controller (which is also a DNS server and Global Catalog.)
+ A VMware host server to host the Virtual Lab
+ A datastore presented to the VMware host for running the Virtual Lab

Note: The following walkthrough has the Veeam backups configured as a separate job for the Exchange Server, and a separate job for the Domain Controller.

Step by step walkthrough:
Note: The steps below involve the UIs – Veeam Backup & Replication, Veeam Backup Enterprise Manager, Virtual Lab Manager, Exchange Application Item Recovery

1: Create the Virtual Lab
i) Expand the SureBackup node and right-click 'Virtual Labs', and select 'Create virtual lab...'
ii) Give the 'New Virtual Lab' a Name (e.g. vLab) and click Next >
iii) Choose the VMware Host server on which to run the lab, then click Next >
iv) Choose Datastore to host the lab, then click Next >
v) The proxy appliance needs to be configured for Exchange AIR recovery: configure Name, choose Production network connection, and configure IP settings (if not using DHCP,) then click Next >
vi) Configure Virtual Lab Networking as required and click Next >
Note: For the Exchange AIR recovery to work, it is important that the proxy is configured correctly. Later when the full lab is up and running, test ping from the Veeam server to the proxy appliance, and pings to the servers in the lab via the masquerade network address (see in Advanced configuration.) HINT: The “Proxy Appliance IP address in the isolated network is typically the same as the gateway IP address in the corresponding production network.”

vii) Finally, review the settings and if okay then click Next >
viii) Wait for the Virtual Lab configuration to complete, then click Finish >

2: Create the Application Group
i) Expand the SureBackup node and right-click 'Application Groups', and select 'Create application group...'
ii) Give the 'New Application Group' a Name (e.g. Application Group Active Directory) and click Next >
iii) Add the Domain Controller to the 'Application group VMs' using either by 'From VI...' or 'From Backup...', and use the Edit... button to specify the roles – DNS Server, Domain Controller, Global Catalog – which are on the Domain Controller, then click Next >
Note: You may want to skip some of the VM tests as displayed via the Edit... button
iv) Click Finish

3: Create corresponding SureBackup job for Exchange Server
i) Expand the SureBackup node and right-click 'Jobs', and select 'Create SureBackup job...'
ii) Give the 'New SureBackup Job' a Name (e.g. SureBackup Exchange) and click Next >
iii) Specify the 'Virtual lab' created earlier and click Next >
iv) Specify the 'Application group' created earlier and click Next >
v) Tick 'Link backup jobs', and add in the backup job containing the Exchange Server, use the Edit... button to specify the Mail Server role is running on the Exchange Server, then click Next >
Note: You may want to skip some of the VM tests as displayed via the Edit... button
vi) Specify DR verification job settings and click Next >
vii) Specify schedule as desired (i.e. after the Exchange job has run), and click Next >
viii) Review the settings, and if okay check the 'Run the job once I click Finish' box and click Finish
Note: Before running the Exchange AIR Recovery we need at least one successful Exchange SureBackup job to complete before a recovery can be performed.


Continues at:
VBR6: Exchange AIR Single Item Email Recovery Setup and Configure Part 2/2

Saturday, 17 March 2012

NetApp & Cisco: Lab. 6/6 - Cisco FC to FCoE Setup for NetApp using CLI

Lab setup:
Host: Windows Server 2008 R2 with Emulex OCe10102-F FCoE CNA
Switch: Nexus 5010 Switch with SFP-10G-SR SFPs
Target: FAS3070 with X1139A UTA running DOT 8.0.1 7-Mode
Cables: OM3 optical cables (OM4 recommended for optimum performance)

Introducing a:
Host: Windows Server 2008 R2 with Emulex FC HBA
DS-SFP-FC4G-SW SFP into the N5K-M1008 FC module on the Nexus 5010

To view current interface configuration:
switch(config)# show interface brief
To configure interface fc 2/2:
switch(config)# interface fc 2/2
switch(config-if)# no shutdown
switch(config-if)# exit
To verify that fc 2/2 is now enabled:
switch(config)# show interface brief
To verify the flogi database:
switch(config)# show flogi database
To configure the VSAN database:
switch(config)# vsan database
switch(config-vsan-db)# vsan 10 interface fc2/2
switch(config-vsan-db)# exit
To verify the flogi database:
switch(config)# show flogi database
To verify the nameserve database for VSAN 10:
switch(config)# show fcns database vsan 10
To create the third zone in VSAN 10:
switch(config)# zone name fchost2 vsan 10
Add the WWPN for storage system 3a:
switch(config-zone)# member pwwn 50:0a:09:81:87:09:3d:96
Add the WWPN for the Emulex FC HBA port 0:
switch(config-zone)# member pwwn 10:00:00:00:c9:43:f2:9e
switch(config-zone)# exit
Open the fcoe zoneset in VSAN 10:
switch(config)# zoneset name fcoe vsan 10
Add fchost2 to the zoneset:
switch(config-zoneset)# zone name fchost2
Reactive the zoneset to get the changes to show up
switch(config-zoneset)# zoneset activate name fcoe vsan 10
switch(config-zoneset)# exit

On the storage system:
To view the discovered initiators:
system> fcp show initiators

SEO: Walkthrough / Step by Step

NetApp & Cisco: Lab. 5/6 - Configuring FCoE with Cisco Nexus 5010 Switch for NetApp using CLI

*DOT 8.0.1 first allowed both FCoE and traditional Ethernet protocols using the same UTA
*FCoE Topologies: Fabric or network topology is the only supported attachment configuration (direct connection not supported)
*FCoE connects over the interconnect
*Within FCoE, a session is automatically created upon discovery

Lab Setup:
Host: Windows Server 2008 R2 with Emulex OCe10102-F FCoE CNA
Switch: Nexus 5010 Switch with SFP-10G-SR SFPs
Target: FAS3070 with X1139A UTA running DOT 8.0.1 7-Mode
Cables: OM3 optical cables (OM4 recommended for optimum performance)

1: Verify host OS releases, patches, volume manager, file system, MPIO, NetApp host utilities in the IMT
Install Multipath I/O feature in Windows 2008 R2
Install the DOT DSM for Windows MPIO
2: Install compatible CNA
OneCommand Manager used to manage Emulex CNA.
3: Install and configure required CNA drivers and utilities
4: Install compatible NetApp host utilities kit

DOT command to verify current hardware:
system> sysconfig
DOT command to add the FC service license:
system> license add FCCODEHERE

Cisco Nexus 5010:
After initial setup on boot.
To view currently installed licenses:
switch# show license usage
To view the current configuration of the interfaces on the switch:
switch# show interface brief
To enter configuration mode:
switch# configure terminal
To enable the FCoE feature:
switch(config)# feature fcoe
To create vsan 10 with name myvsan:
switch(config)# vsan database
switch(config-vsan-db)# vsan 10
switch(config-vsan-db)# vsan 10 name myvsan
switch(config-vsan-db)# exit
To create vlan 10:
switch(config)# vlan 10
To associate VLAN 10 with VSAN 10:
switch(config-vlan)# fcoe vsan 10
To verify the VLAN-VSAN configuration:
switch(config-vlan)# show vlan fcoe
To exit the VLAN configuration:
switch(config-vlan)# exit
To configure ethernet port 1/1 for FCoE:
switch(config)# interface ethernet 1/1
switch(config-if)# spanning-tree port type edge trunk
switch(config-if)# switchport mode trunk
To create a new Virtual Fibre Channel (VFC) identified as 1:
switch(config)# interface vfc1
switch(config-if)# bind interface ethernet 1/1
switch(config-if)# no shutdown
switch(config-if)# exit
*and repeat to create vfc2 for eth1/2, vfc3 for eth1/3, vfc4 for eth1/4 (only 1 FC is allowed per 10Gb ethernet connection)

To associate VFC 2 to VSAN 10:
switch(config)# vsan database
switch(config-vsan-db)# vsan 10 interface vfc 2
switch(config-vsan-db)# exit
To view the Fabric Login database:
switch(config)# show flogi database
To view the nameserver database:
switch(config)# show fcns database vsan 10

To check adapter 3b from storage CLI:
system> fcp show adapter 3b

To associate VFC 3 to VSAN 10:
switch(config)# vsan database
switch(config-vsan-db)# vsan 10 interface vfc 3
switch(config-vsan-db)# exit
switch(config)# show flogi database
switch(config)# show fcns database vsan 10

To associate VFC 4 to VSAN 10:
switch(config)# vsan database
switch(config-vsan-db)# vsan 10 interface vfc 4
switch(config-vsan-db)# exit
switch(config)# show flogi database
switch(config)# show fcns database vsan 10

To view the discovered initiators from storage CLI:
system> fcp show initiators

To create the first zone in VSAN 10:
switch(config)# zone name fcoehost1 vsan 10
Add the WWPN for storage system 3a:
switch(config-zone)# member pwwn 50:0a:09:81:87:09:3d:96
Add the WWPN for host port 0:
switch(config-zone)# member pwwn 10:00:00:00:c9:9c:6c:85
switch(config-zone)# exit
To create an fcoe zoneset called fcoe in VSAN 10:
switch(config)# zoneset name fcoe vsan 10
Add zone fcoehost1 to the zoneset:
switch(config-zoneset)# zone name fcoehost1
Activate the zoneset:
switch(config-zoneset)# zoneset activate name fcoe vsan 10
switch(config-zoneset)# exit

On storage system, to view the discovered initiators:
system> fcp show initiators

To create the second zone in VSAN 10:
switch(config)# zone name fcoehost2 vsan 10
Add the WWPN for storage system 3b:
switch(config-zone)# member pwwn 50:0a:09:82:87:09:3d:96
Add the WWPN for host port 1:
switch(config-zone)# member pwwn 10:00:00:00:c9:9c:6c:87
switch(config-zone)# exit
To open the fcoe zoneset called in VSAN 10:
switch(config)# zoneset name fcoe vsan 10
Add zone fcoehost2 to the zoneset:
switch(config-zoneset)# zone name fcoehost2
Re-activate the zoneset to get the changes to show up:
switch(config-zoneset)# zoneset activate name fcoe vsan 10
switch(config-zoneset)# exit

On storage system, to view the discovered initiators:
system> fcp show initiators

To verify connectivity to the host's Emulex port 1 through 3a on the storage system:
system> fcp ping 3a 0x3b0002
To view the topology visible through 3a:
system> fcp topology show 3a
Enter the following command to view the zones visible:
system> fcp zone show
Enter the following commands to view the UTA details:
system> priv set diag
system*> cna show

Quality of Service Configuration
To show the current policy maps:
switch# show policy-map
*default is 50% for FCoE traffic and 50% for other traffic.
switch# configure terminal
To create a new policy map called fcoe-80:
switch(config)# policy-map type queuing fcoe-80
To configure the FCoE class within the policy:
switch(config-pmap-que)# class type queuing class-fcoe
Set the FcoE bandwidth to 80%:
switch(config-pmap-c-que)# bandwidth percent 80
To configure the default class within the policy:
switch(config-pmap-c-que)# class type queuing class-default
Set the default bandwidth to 20%
switch(config-pmap-c-que)# bandwidth percent 20
switch(config-pmap-c-que)# exit
switch(config-pmap-que)# exit

Quality of Service Configuration:
switch(config)# system qos
To set the input policy to the fcoe-80 map:
switch(config-sys-qos)# service-policy type queuing input fcoe-80
To set the output policy to the fcoe-80 map:
switch(config-sys-qos)# service-policy type queuing output fcoe-80
switch(config-sys-qos)# end
To show the new policy maps:
switch# show policy-map system
switch# copy running-config startup-config

LUN connectivity steps with DOT
1: Create an igroup
2: Create a logical unit
3: Map the logical unit to the igroup

Best Practice: Do not put LUNs in the root volume

To create an igroup:
system> igroup create -f -t windows my_fcoegroup 10:00:00:00:C9:9C:6C:85 10:00:00:00:C9:9C:6C:87
To show the existing igroups:
system> igroup show

To create an aggregate:
system> aggr create aggr_SAN 7
To create the volume for the LUN:
system> vol create vol_SAN1 aggr_SAN 2g
To turn off the default Snapshot policy for the volume:
system> snap reserve vol_SAN1 0
system> vol options vol_SAN1 nosnap on
To create a LUN named LUN1:
system> lun create -s 500m -t windows /vol/vol_SAN1/lun1

To map the LUN to the igroup:
system> lun map /vol/vol_SAN1/lun1 my_fcoegroup
*DOT will automatically assign a LUN number in the absence of a given number
To verify the LUN and mapping:
system> lun show -m

IP-Based Protocols

Configuring the storage system's UTA.
To verify the current configuration of the network adapters:
system> ifconfig -a
To configure e3a and e3b for a private network:
system> ifconfig e3a 172.1.1.52 up netmask 255.255.255.0
system> ifconfig e3b 172.1.1.53 up netmask 255.255.255.0
Verify the configurations:
system> ifconfig -a

License and setup the CIFS service:
system> license add CIFSCODE
system> cifs setup
*Option 3 for Windows Workgroup authentication
*Accept default workgroup name
*Default share for root volume is automatically created during setup

Configure CNA in Windows for TCP/IPv4 on both adapters.
In Windows map drive to the UTA.
Results in successful demonstration of Ethernet convergence (CIFS and FCoE over same adapters)!

SEO: Walkthrough / Step by Step

Cisco: Lab. 4/6 - Configuring a Cisco FC Switch using CLI

1: Perform initial configuration steps
*Default access login=admin and password=password
2: Upgrade firmware, if needed
3: Create the VSAN and assign ports
4: Assign the domain ID
5: Assign port speeds
6: Verify configuration
7: Verify host and storage connectivity
8: Create FC zones
9: Save and back up the configuration

*Best practice to have same version of FabricWare across all switches.
CiscoFCSW# show version
To verify the image and system impact:
CiscoFCSW# show install all impact system
To install the upgrade:
CiscoFCSW# install all systems
To verify the installation:
CiscoFCSW# show install all status

Example to create a VSAN :
*Avoid using vsan 1 for production traffic
CiscoFCSW# config t
CiscoFCSW(config)# vsan database
CiscoFCSW(config-vsan-db)# vsan 2
CiscoFCSW(config-vsan-db)# vsan 2 interface fc1/8
CiscoFCSW(config-vsan-db)# vsan 2 interface fc1/9
*and repeat for each FC interface to be added to the VSAN

Example to assign the Domain ID:
*Each VSAN has a unique domain ID which can either be Static (join with given ID or not at all) or Preferred (try to join with the given ID, but join with another ID if necessary)
CiscoFCSW# conf t
CiscoFCSW(config)# fcdomain domain 10 static vsan 2
CiscoFCSW(config)# end

Assign port speeds to avoid negotiation errors and avoid prolonged fabric rebuilds:
CiscoFCSW# conf t
CiscoFCSW(config)# interface fc 1/1
CiscoFCSW(config-if)# switchport speed 8000
*speed can be either 1000, 2000, 4000, or 8000 Mbps
CiscoFCSW(config-if)# ^Z

To verify VSAN port assignments:
CiscoFCSW# show vsan membership
To verify one or more domain IDs:
CiscoFCSW# show fcdomain
To verify port speed configuration:
CiscoFCSW# show interface brief

To verify the host and storage ports are online:
CiscoFCSW# show flogi database
*Verify WWPNs are correct (compare with information from DOT CLI command> fcp show adapter, and host OS or HBA software)

Example to create FC zones:
CiscoFCSW# config t
CiscoFCSW(config)# device-alias database
CiscoFCSW(config-device-alias-db)# device-alias name x pwwn 21:01:00:e0:8b:2e:80:93
CiscoFCSW(config-device-alias-db)# end
CiscoFCSW# config t
CiscoFCSW(config)# device-alias commit
CiscoFCSW(config)# zone name myzone vsan 2
CiscoFCSW(config-zone)# member device-alias x
CiscoFCSW(config-zone)# exit

Example to create and activate zonesets:
CiscoFCSW# config t
CiscoFCSW(config)# zoneset name Zoneset1 vsan 2
CiscoFCSW(config-zoneset)# member myzone
CiscoFCSW(config-zoneset)# end
CiscoFCSW# config t
CiscoFCSW(config)# zoneset activate name Zoneset1 vsan 2

To save the configuration to nonvolatile RAM (NVRAM):
CiscoFCSW# copy running-config startup-config

To gather support data:
CiscoFCSW# show tech-support details

SEO: Walkthrough / Step by Step

Brocade: Lab. 3/6 - Configuring a Brocade FC Switch using CLI

1: Perform initial configuration steps
*Default access login=admin and password=password
2: Upgrade firmware, if needed
3: Assign the domain ID
*Each FC switch must have a unique domain ID.
*Recommend start numbering from 10 to avoid reserved IDs.
4: Assign port speeds
5: Verify configuration
6: Verify host and storage connectivity
7: Create FC zones
8: Save and back up the configuration

*Best practice to have same version of Fabric OS across all switches.
BrocadeFCSW> version
BrocadeFCSW> firmwareDownload

Domain ID defaults to 1, use the following steps to change the domain ID:
BrocadeFCSW> switchDisable
BrocadeFCSW> configure
BrocadeFCSW> switchEnable

Assign port speeds to avoid negotiation errors and avoid prolonged fabric rebuilds:
BrocadeFCSW> portCfgSpeed [slot/]port, speed

To verify switch configuration:
BrocadeFCSW> switchShow
*Verify the domain ID
*Verify active port speeds
*Verify the host and storage ports are online
*Verify WWPNs are correct (compare with information from DOT CLI command> fcp show adapter, and host OS or HBA software)

Finally, create FC Zones, create a configuration, storage the confguration, activate the configuration e.g.:
BrocadeFCSW> aliCreate WinA, 21:00:00:1b:32:1a:8b:1c
BrocadeFCSW> zoneCreate WinPriA, “WinA;Fas01A”
BrocadeFCSW> cfgCreate WinCfg, “WinPriA;WinPriB;WinSecA;WinSecB”
BrocadeFCSW> cfgSave
BrocadeFCSW> cfgEnable Wincfg

To back up the configuration:
BrocadeFCSW> configUpload
To restore the configuration:
BrocadeFCSW> configDownload
To retrieve support data:
BrocadeFCSW> supportSave

SEO: Walkthrough / Step by Step