J Datastore 7.03 serial key or number

J Datastore 7.03 serial key or number

J Datastore 7.03 serial key or number

J Datastore 7.03 serial key or number

YangModels / yang

module ietf-interfaces {namespace"urn:ietf:params:xml:ns:yang:ietf-interfaces";prefix if;import ietf-yang-types {prefix yang; }// import xmas {// prefix xmas;// }organization"IETF NETMOD (NETCONF Data Modeling Language) Working Group";contact"WG Web: <cromwellpsi.com> WG List: <mailto:netmod@cromwellpsi.com> WG Chair: David Kessens <mailto:cromwellpsi.coms@cromwellpsi.com> WG Chair: Juergen Schoenwaelder <mailto:cromwellpsi.comwaelder@cromwellpsi.com> Editor: Martin Bjorklund <mailto:mbj@cromwellpsi.com>";description"This module contains a collection of YANG definitions for managing network interfaces. Copyright (c) IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (cromwellpsi.com). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices.";// RFC Ed.: replace XXXX with actual RFC number and remove this// note.// RFC Ed.: update the date below with the date of RFC publication// and remove this note.revision {description"Proposed. Added xmas annotations to the original draft.";reference"RFC XXXX: A YANG Data Model for Interface Management"; }/* * Typedefs */// xmas:module-id 0x;typedef interface-ref {typeleafref {path"/if:interfaces/if:interface/if:name"; }description"This type is used by data models that need to reference configured interfaces."; }typedef interface-state-ref {typeleafref {path"/if:interfaces-state/if:interface/if:name"; }description"This type is used by data models that need to reference the operationally present interfaces."; }/* * Identities */identity interface-type {description"Base identity from which specific interface types are derived."; }/* * Features */feature arbitrary-names {description"This feature indicates that the device allows user-controlled interfaces to be named arbitrarily."; }feature pre-provisioning {description"This feature indicates that the device supports pre-provisioning of interface configuration, i.e., it is possible to configure an interface whose physical interface hardware is not present on the device."; }feature if-mib {description"This feature indicates that the device implements IF-MIB.";reference"RFC The Interfaces Group MIB"; }/* * Configuration data nodes */container interfaces {description"Interface configuration parameters.";list interface {key"name";description"The list of configured interfaces on the device. The operational state of an interface is available in the /interfaces-state/interface list. If the configuration of a system-controlled interface cannot be used by the system (e.g., the interface hardware present does not match the interface type), then the configuration is not applied to the system-controlled interface shown in the /interfaces-state/interface list. If the configuration of a user-controlled interface cannot be used by the system, the configured interface is not instantiated in the /interfaces-state/interface list.";leaf name {typestring;description"The name of the interface. A device MAY restrict the allowed values for this leaf, possibly depending on the type of the interface. For system-controlled interfaces, this leaf is the device-specific name of the interface. The 'config false' list /interfaces-state/interface contains the currently existing interfaces on the device. If a client tries to create configuration for a system-controlled interface that is not present in the /interfaces-state/interface list, the server MAY reject the request, if the implementation does not support pre-provisioning of interfaces, or if the name refers to an interface that can never exist in the system. A NETCONF server MUST reply with an rpc-error with the error-tag 'invalid-value' in this case. If the device supports pre-provisioning of interface configuration, the feature 'pre-provisioning' is advertised. If the device allows arbitrarily named user-controlled interfaces, the feature 'arbitrary-names' is advertised. When a configured user-controlled interface is created by the system, it is instantiated with the same name in the /interface-state/interface list."; }leafdescription {typestring;description"A textual description of the interface. A server implementation MAY map this leaf to the ifAlias MIB object. Such an implementation needs to use some
Источник: [cromwellpsi.com]
, J Datastore 7.03 serial key or number

VMware Horizon Composer

Help sought &#; Pools stuck “customising”, Composer Guest Agent service fails to start in clones (but is fine in Master VM)

Hi,

My apologies for posting this here, but I am completely stuck and not sure what else to try…

I have just rebuilt my working Horizon View setup from to version , clearing the SQLExpress databases on both the Composer and Connection servers (including Adam DB) before re-installing from media.

I can connect to the Master VM using a direct connect mode, but when I remove the direct agent software and configure to the Connection Server as a Dynamic Pool using Composer, the pool VM&#;s all stick at Customising and timeout.

If I connect to the console of the pool VM&#;s, I can see that the &#;VMware Horizon View Composer Guest Agent Server&#; Windows service fails to start &#; which I presume is the problem. The service starts fine on the Master VM, though.

The Windows event log error relating to this is:

Faulting application name: cromwellpsi.com, version: ,, time stamp: 0x5ddc6
Faulting module name: cromwellpsi.com, version: , time stamp: 0x6dbf7eae
Exception code: 0xc
Fault offset: 0xgcaa2
Faulting process ID: 0x
Faulting application start time: 0x01d5e
Faulting application path: C:\Program Files (x86)\Common Files\VMware\View Composer Guest Agent\cromwellpsi.com
Faulting module path: C:\Windows\System32\cromwellpsi.com
Report ID. fc4ff-ca5cfd-a49e-cd
Faulting package full name:
Faulting package-relative application ID:

I have tried removing all Anti-Virus and disabled Windows defender in the registry, am now a bit stuck and could really do with some help or suggestions how to debug?

Thanks in advance

Gary

Источник: [cromwellpsi.com]
J Datastore 7.03 serial key or number

FlexPod Datacenter with VMware vSphere U1, Cisco UCS 4th Generation Fabric, and NetApp AFF A-Series

Deployment Guide for FlexPod Datacenter with VMware vSphere U1, Cisco UCS Manager (2), and ONTAP

Published: November

NOTE: Works with document’s Advanced Properties “Last Updated” property. Click File | Properties | Advanced Properties | Custom.

In partnership with:                                                       

About the Cisco Validated Design Program

The Cisco Validated Design (CVD) program consists of systems and solutions designed, tested, and documented to facilitate faster, more reliable, and more predictable customer deployments. For more information, go to:

cromwellpsi.com

ALL DESIGNS, SPECIFICATIONS, STATEMENTS, INFORMATION, AND RECOMMENDATIONS (COLLECTIVELY, "DESIGNS") IN THIS MANUAL ARE PRESENTED "AS IS," WITH ALL FAULTS.  CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.  IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THE DESIGNS, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE.  USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS.  THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF CISCO, ITS SUPPLIERS OR PARTNERS.  USERS SHOULD CONSULT THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS.  RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY CISCO.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unified Computing System (Cisco UCS), Cisco UCS B-Series Blade Servers, Cisco UCS C-Series Rack Servers, Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS Management Software, Cisco Unified Fabric, Cisco Application Centric Infrastructure, Cisco Nexus Series, Cisco Nexus Series. Cisco Prime Data Center Network Manager, Cisco NX-OS Software, Cisco MDS Series, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study,  LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (R)

© Cisco Systems, Inc. All rights reserved.

 

Table of Contents

Executive Summary. 9

Solution Overview.. 10

Introduction. 10

Audience. 10

Purpose of this Document10

What’s New in this Release?. 10

Deployment Hardware and Software. 11

Architecture. 11

Topology. 12

Software Revisions. 12

Configuration Guidelines. 13

Physical Infrastructure. 14

Network Switch Configuration. 17

Physical Connectivity. 17

FlexPod Cisco Nexus Base. 17

Set Up Initial Configuration. 17

FlexPod Cisco Nexus Switch Configuration. 19

Enable Licenses. 19

Set Global Configurations. 19

Create VLANs. 19

Add NTP Distribution Interface. 20

Add Individual Port Descriptions for Troubleshooting and Enable UDLD for UCS Interfaces. 20

Create Port Channels. 21

Configure Port Channel Parameters. 22

Configure Virtual Port Channels. 23

Uplink into Existing Network Infrastructure. 23

Switch Testing Commands. 24

Storage Configuration. 25

NetApp All Flash FAS A Controllers. 25

NetApp Hardware Universe. 25

Controllers. 25

Disk Shelves. 25

NetApp ONTAP 25

Complete Configuration Worksheet25

Configure ONTAP Nodes. 26

Set Up Node. 29

Log into the Cluster35

Verify Storage Failover35

Set Auto-Revert on Cluster Management36

Zero All Spare Disks. 36

Set Up Service Processor Network Interface. 36

Create Aggregates. 37

Remove Ports from Default Broadcast Domain. 37

Disable Flow Control on 10GbE and GbE ports. 37

Disable Auto-negotiate on GbE Ports. 38

Disable Auto-negotiate on Fibre Channel Ports. 38

Enable Cisco Discovery Protocol39

Enable Link-layer Discovery Protocol on all Ethernet Ports. 39

Create Management Broadcast Domain. 39

Create NFS Broadcast Domain. 39

Create Interface Groups. 39

Change MTU on Interface Groups. 39

Create VLANs. 40

Configure Network Time Protocol40

Configure Simple Network Management Protocol40

Configure SNMPv1 Access. 41

Create SVM.. 41

Create Load-Sharing Mirrors of SVM Root Volume. 41

Create Block Protocol (FC) Service. 42

Configure HTTPS Access. 42

Configure NFSv3. 43

Create FlexVol Volumes. 44

Create Boot LUNs. 44

Schedule Deduplication. 44

Create FC LIFs. 44

Create NFS LIFs. 45

Add Infrastructure SVM Administrator45

Configure and Test AutoSupport45

Cisco UCS Configuration. 47

Cisco UCS Base Configuration. 47

Perform Initial Setup of Cisco UCS Fabric Interconnects for FlexPod Environments. 47

Cisco UCS Setup. 48

Log into Cisco UCS Manager48

Upgrade Cisco UCS Manager Software to Version (2d)48

Anonymous Reporting. 49

Configure Cisco UCS Call Home. 49

Configure Unified Ports (FCP)49

Add Block of IP Addresses for KVM Access. 52

Synchronize Cisco UCS to NTP. 52

Add Additional DNS Server(s)54

Add an Additional Administrative User55

Enable Port Auto-Discovery Policy. 56

Enable Info Policy for Neighbor Discovery. 57

Edit Chassis Discovery Policy. 58

Enable Server and Uplink Ports. 58

Acknowledge Cisco UCS Chassis and FEX. 59

Create Uplink Port Channels to Cisco Nexus Switches. 60

Add UDLD to Uplink Port Channels. 63

Create a WWNN Pool for FC Boot (FCP)66

Create WWPN Pools (FCP)67

Create VSANs (FCP)70

Enable FC Uplink VSAN Trunking (FCP)72

Create FC Uplink Port Channels (FCP)73

Disable Unused FC Uplink Ports (FCP)76

Create an Organization. 76

Create vHBA Templates (FCP)77

Create SAN Connectivity Policy (FCP)79

Create MAC Address Pools. 81

Create UUID Suffix Pool83

Create Server Pool84

Create VLANs. 84

Modify Default Host Firmware Package. 87

Set Jumbo Frames in Cisco UCS Fabric. 88

Create Local Disk Configuration Policy (Optional)89

Create Network Control Policy for Cisco Discovery Protocol (CDP) and Link Layer Discovery Protocol (LLDP)91

Create Power Control Policy. 92

Create Server BIOS Policy. 94

Update the Default Maintenance Policy. 99

Create vNIC Templates.

Create High Traffic VMware Adapter Policy.

Create LAN Connectivity Policy for FC Boot (FCP)

Create FC Boot Policy (FCP)

Create Service Profile Template (FCP)

Configure Storage Provisioning.

Configure Networking.

Configure SAN Connectivity.

Configure Zoning.

Configure vNIC/HBA Placement

Configure vMedia Policy.

Configure Server Boot Order

Configure Maintenance Policy.

Configure Server Assignment

Configure Operational Policies.

Create vMedia-Enabled Service Profile Template.

Create Service Profiles.

Add More Servers to FlexPod Unit

Gather Necessary Information.

SAN Switch Configuration.

Physical Connectivity.

FlexPod Cisco MDS Base.

Cisco MDS T A.

FlexPod Cisco MDS Switch Configuration.

Enable Licenses.

Add Second NTP Server

Configure Individual Ports.

Create VSANs.

Create Device Aliases.

Create Zones and Zoneset

Storage Configuration – Boot LUNs.

ONTAP Boot Storage Setup.

Create igroups.

Map Boot LUNs to igroups.

VMware vSphere U1 Setup.

VMware ESXi U1.

Download ESXi U1 from VMware.

Log into Cisco UCS Fabric Interconnect

Set Up VMware ESXi Installation.

Install ESXi

Set Up Management Networking for ESXi Hosts.

Reset VMware ESXi Host VMkernel Port vmk0 MAC Address (Optional)

Log into VMware ESXi Hosts by Using VMware Host Client

Set Up VMkernel Ports and Virtual Switch.

Install VMware Drivers for the Cisco Virtual Interface Card (VIC)

Mount Required Datastores.

Configure NTP on ESXi Hosts.

VMware vCenter U1.

Build the VMware vCenter Server Appliance.

Adjust vCenter CPU Settings.

Setup VMware vCenter Server

Add AD User Authentication to vCenter (Optional)

FlexPod VMware vSphere Distributed Switch (vDS)

Configure the VMware vDS in vCenter

VMware ESXi U1 TPM Attestation.

FlexPod Management Tools Setup.

Cisco UCS Manager Plug-in for VMware vSphere Web Client

Cisco UCS Manager Plug-in Installation.

FlexPod UCS Domain Registration.

Use the Cisco UCS vCenter Plugin.

NetApp Virtual Storage Console Deployment Procedure.

Virtual Storage Console Pre-installation Considerations.

Install Virtual Storage Console

Download the NetApp NFS VAAI Plug-In.

Discover and Add Storage Resources.

Optimal Storage Settings for ESXi Hosts.

Virtual Storage Console Provisioning Datastores.

NetApp SnapCenter

Deploy NetApp SnapCenter

SnapCenter Server Requirements.

SnapCenter License Requirements.

SnapCenter Server

SnapCenter Plug-In for VMware vSphere.

Support for Virtualized Databases and File Systems.

SnapCenter Installation.

SnapCenter Configuration.

Install SnapCenter Plug-In for VMware.

Host and Privilege Requirements for the Plug-In for VMware vSphere.

Run As Credentials.

Install the Plug-in for VMware vSphere from the SnapCenter GUI

Configure SnapCenter Plug-In for vCenter

View Virtual Machine Backups and Restore from vCenter by Using SnapCenter Plug-In.

View Backups.

Restore from vCenter by Using SnapCenter Plug-In.

Install OnCommand Unified Manager

Install the Extra Packages for Enterprise Linux (EPEL) and MySQL Repositories.

Install Open VM Tools on the CentOS Virtual Machine.

Configure CentOS Firewall

Install OnCommand Unified Manager

Add Storage Systems to OnCommand Unified Manager

Sample Tenant Provisioning.

Provision a Sample Application Tenant

Appendix.

FlexPod iSCSI Addition.

Cisco Nexus Switch Configuration.

NetApp Storage Configuration.

Create Block Protocol (iSCSI) Service.

Create iSCSI Broadcast Domains.

Create iSCSI VLANs.

Add VLANs to iSCSI Broadcast Domains.

Create iSCSI LIFs.

Create igroups.

Map Boot LUNs to igroups.

Cisco UCS iSCSI Configuration.

VMware vSphere Configuration.

Create a FlexPod ESXi Custom ISO using VMware vCenter

FlexPod Backups.

Cisco UCS Backup.

Cisco Nexus and MDS Backups.

VMware VCSA Backup.

About the Authors.

Acknowledgements.

 

 

Cisco Validated Designs include systems and solutions that are designed, tested, and documented to facilitate and improve customer deployments. These designs incorporate a wide range of technologies and products into a portfolio of solutions that have been developed to address the business needs of customers. Cisco and NetApp have partnered to deliver FlexPod, which serves as the foundation for a variety of workloads and enables efficient architectural designs that are based on customer requirements. A FlexPod solution is a validated approach for deploying Cisco and NetApp technologies as a shared cloud infrastructure.

This document describes the Cisco and NetApp® FlexPod Datacenter with Cisco UCS Manager unified software release (2) and VMware vSphere U1. Cisco UCS Manager (UCSM) (2) provides consolidated support of all current Cisco UCS Fabric Interconnect models (, , (Cisco UCS Mini)), ,/ series IOM, Cisco UCS B-Series, and Cisco UCS C-Series.  FlexPod Datacenter with Cisco UCS unified software release (2), and VMware vSphere U1 is a predesigned, best-practice data center architecture built on the Cisco Unified Computing System (UCS), the Cisco Nexus® family of switches, MDS multilayer fabric switches, and NetApp AFF A-Series storage arrays running ONTAP® 9 storage OS.

Introduction

The current industry trend in data center design is towards shared infrastructures. By using virtualization along with pre-validated IT platforms, enterprise customers have embarked on the journey to the cloud by moving away from application silos and toward shared infrastructure that can be quickly deployed, thereby increasing agility and reducing costs. Cisco and NetApp have partnered to deliver FlexPod, which uses best of breed storage, server and network components to serve as the foundation for a variety of workloads, enabling efficient architectural designs that can be quickly and confidently deployed.

Audience

The audience for this document includes, but is not limited to; sales engineers, field consultants, professional services, IT managers, partner engineers, and customers who want to take advantage of an infrastructure built to deliver IT efficiency and enable IT innovation.

Purpose of this Document

This document provides a step by step configuration and implementation guide for the FlexPod Datacenter with Cisco UCS Fabric Interconnects, NetApp AFF storage, Cisco MDS, and Cisco Nexus solution.

What’s New in this Release?

The following design elements distinguish this version of FlexPod from previous FlexPod models:

·       Support for the Cisco UCS (2) unified software release, Cisco UCS BM5 servers, and Cisco UCS CM5 servers, Cisco Series Virtual Interface Cards (VICs)

·       Support for the latest Cisco UCS Fabric Interconnect

·       Support for the NetApp AFF A storage controller

·       Support for the latest release of NetApp ONTAP®

·       Support for NetApp Virtual Storage Console (VSC)

·       Support for NetApp SnapCenter

·       Fibre channel, NFS, iSCSI (appendix) storage design

·       Validation of VMware vSphere U1

·       Unified Extensible Firmware Interface (UEFI) Secure Boot of VMware ESXi U1

·       Trusted Platform Module (TPM) Attestation of UEFI Secure Boot of VMware ESXi U1

·       Gigabit per second Ethernet Connectivity

·       32 Gigabit per second Fibre Channel Connectivity

Architecture

FlexPod is a defined set of hardware and software that serves as an integrated foundation for both virtualized and non-virtualized solutions. VMware vSphere® built on FlexPod includes NetApp All Flash FAS storage, Cisco Nexus® networking, Cisco MDS storage networking, the Cisco Unified Computing System (Cisco UCS®), and VMware vSphere software in a single package. The design is flexible enough that the networking, computing, and storage can fit in one data center rack or be deployed according to a customer's data center design. Port density enables the networking components to accommodate multiple configurations of this kind.

One benefit of the FlexPod architecture is the ability to customize or "flex" the environment to suit a customer's requirements. A FlexPod can easily be scaled as requirements and demand change. The unit can be scaled both up (adding resources to a FlexPod unit) and out (adding more FlexPod units). The reference architecture detailed in this document highlights the resiliency, cost benefit, and ease of deployment of a Fibre Channel and IP-based storage solution. A storage system capable of serving multiple protocols across a single interface allows for customer choice and investment protection because it truly is a wire-once architecture.

Figure 1 shows the VMware vSphere built on FlexPod components and the network connections for a configuration with the Cisco UCS Fabric Interconnects. This design has port-channeled 10 Gb Ethernet connections between the Cisco UCS Blade Chassis and the Cisco UCS Fabric Interconnects, port-channeled 25 Gb Ethernet connections between the C-Series rackmounts and the Cisco UCS Fabric Interconnects, and Gb Ethernet connections between the Cisco UCS Fabric Interconnect and Cisco Nexus , and between Cisco Nexus and NetApp AFF A storage array. This infrastructure option expanded with Cisco MDS switches sitting between the Cisco UCS Fabric Interconnect and the NetApp AFF A to provide FC-booted hosts with 32 Gb FC block-level access to shared storage.  The reference architecture reinforces the "wire-once" strategy, because as additional storage is added to the architecture, no re-cabling is required from the hosts to the Cisco UCS fabric interconnect.

Topology

The reference Gb based hardware configuration includes:

·       Two Cisco Nexus c-FX2 switches

·       Two Cisco UCS fabric interconnects

·       Two Cisco MDS T multilayer fabric switches

·       One NetApp AFF A (HA pair) running ONTAP with internal NVMe SSD disks

Software Revisions

Table 1   lists the software revisions for this solution.

Table 1    Software Revisions

Layer

Device

Image

Comments

Compute

Cisco UCS Fabric Interconnects , UCS B M5, UCS C M5

(2d)

Includes the Cisco UCS-IOM , Cisco UCS Manager, Cisco UCS VIC and Cisco UCS VIC

Network

Cisco Nexus C-FX2 NX-OS

(3)I7(6)

 

 

Cisco MDS T

(2)

 

Storage

NetApp AFF A

ONTAP

 

Software

Cisco UCS Manager

(2d)

 

 

Cisco UCS Manager Plugin for VMware vSphere Web Client

 

 

VMware vSphere

U1

 

 

VMware ESXi nfnic FC Driver

 

 

VMware ESXi nenic Ethernet Driver

 

 

NetApp Virtual Storage Console (VSC) / VASA Provider Appliance

P1

 

 

NetApp NFS Plug-in for VMware VAAI

 

 

NetApp SnapCenter Backup Management

Includes the vSphere plug-in for SnapCenter

Configuration Guidelines

This document explains how to configure a fully redundant, highly available configuration for a FlexPod unit with ONTAP storage. Therefore, reference is made to which component is being configured with each step, either 01 or 02 or A and B. For example, node01 and node02 are used to identify the two NetApp storage controllers that are provisioned with this document, and Cisco Nexus A or Cisco Nexus B identifies the pair of Cisco Nexus switches that are configured. The Cisco UCS fabric interconnects are similarly configured. Additionally, this document details the steps for provisioning multiple Cisco UCS hosts, and these examples are identified as: VM-Host-Infra, VM-Host-Infra to represent infrastructure hosts deployed to each of the fabric interconnects in this document. Finally, to indicate that you should include information pertinent to your environment in a given step, <text> appears as part of the command structure. See the following example for the network port vlan create command:

Usage:

network port vlan create ?

 [-node] <nodename>                  Node

 { [-vlan-name] {<netport>|<ifgrp>}  VLAN Name

 |  -port {<netport>|<ifgrp>}        Associated Network Port

 [-vlan-id] <integer> }              Network Switch VLAN Identifier

Example:

network port vlan create -node <node01> -vlan-name a0a-<vlan id>

This document is intended to enable you to fully configure the customer environment. In this process, various steps require you to insert customer-specific naming conventions, IP addresses, and VLAN schemes, as well as to record appropriate MAC addresses. Table 2  describes the VLANs necessary for deployment as outlined in this guide.

Table 2    Necessary VLANs

VLAN Name

VLAN Purpose

ID Used in Validating This Document

Out of Band Mgmt

VLAN for out-of-band management interfaces

13

In-Band Mgmt

VLAN for in-band management interfaces

Native

VLAN to which untagged frames are assigned

2

Infra-NFS

VLAN for Infrastructure NFS traffic

FCoE-A

VLAN for FCoE encapsulation of VSAN-A

FCoE-B

VLAN for FCoE encapsulation of VSAN-B

vMotion

VLAN for VMware vMotion

VM-Traffic

VLAN for Production VM Interfaces

Table 3   lists the VMs necessary for deployment as outlined in this document.

Table 3    Virtual Machines

Virtual Machine Description

Host Name

IP Address

vCenter Server

 

 

NetApp VSC

 

 

NetApp SnapCenter

 

 

Physical Infrastructure

FlexPod Cabling

The information in this section is provided as a reference for cabling the physical equipment in a FlexPod environment. To simplify cabling requirements, a cabling diagram was used.

The cabling diagram in this section contains details for the prescribed and supported configuration of the NetApp AFF A running NetApp ONTAP®

This document assumes that out-of-band management ports are plugged into an existing management infrastructure at the deployment site. These interfaces will be used in various configuration steps.

         Be sure to use the cabling directions in this section as a guide.

The NetApp storage controller and disk shelves should be connected according to best practices for the specific storage controller and disk shelves. For disk shelf cabling, refer to NetApp Support.

Figure 2 details the cable connections used in the validation lab for the FlexPod topology based on the Cisco UCS fabric interconnect.  Two 32Gb uplinks connect as port-channels to each Cisco UCS Fabric Interconnect from the MDS switches, and a total of four 32Gb links connect the MDS switches to the NetApp AFF controllers.  Also, Gb links connect the Cisco UCS Fabric Interconnects to the Cisco Nexus Switches and the NetApp AFF controllers to the Cisco Nexus Switches. Additional 1Gb management connections will be needed for an out-of-band network switch that sits apart from the FlexPod infrastructure.  Each Cisco UCS fabric interconnect and Cisco Nexus switch is connected to the out-of-band network switch, and each AFF controller has two connections to the out-of-band network switch. Layer 3 network connectivity is required between the Out-of-Band (OOB) and In-Band (IB) Management Subnets.

This section provides a detailed procedure for configuring the Cisco Nexus s for use in a FlexPod environment. Follow these steps precisely because failure to do so could result in an improper configuration.

Physical Connectivity

Follow the physical connectivity guidelines for FlexPod as explained in the section FlexPod Cabling.

FlexPod Cisco Nexus Base

The following procedures describe how to configure the Cisco Nexus switches for use in a base FlexPod environment.  This procedure assumes the use of Cisco Nexus (3)I7(6), the Cisco suggested Nexus switch release at the time of this validation.

        The following procedure includes the setup of NTP distribution on both the mgmt0 port and the in-band management VLAN. The interface-vlan feature and ntp commands are used to set this up. This procedure also assumes that the default VRF is used to route the in-band management VLAN.

 

        With Cisco Nexus release (3)I7(6), autonegotiation (40G/G) is not supported on ports and on the Cisco Nexus C-FX2 switch.  Since those ports are in use in this validation, port speed and duplex are hard set at both ends of the connection.

Set Up Initial Configuration

Cisco Nexus A

To set up the initial configuration for the Cisco Nexus A switch on <nexus-A-hostname>, follow these steps:

1.     Configure the switch.

        On initial boot and connection to the serial or console port of the switch, the NX-OS setup should automatically start and attempt to enter Power on Auto Provisioning.

Abort Power On Auto Provisioning [yes - continue with normal setup, skip - bypass password and basic configuration, no - continue with Power On Auto Provisioning] (yes/skip/no)[no]: yes

Disabling POAPDisabling POAP

poap: Rolling back, please wait (This may take minutes)

 

         System Admin Account Setup

 

Do you want to enforce secure password standard (yes/no) [y]: Enter

Enter the password for "admin": <password>

Confirm the password for "admin": <password>

Would you like to enter the basic configuration dialog (yes/no): yes

Create another login account (yes/no) [n]: Enter

Configure read-only SNMP community string (yes/no) [n]: Enter

Configure read-write SNMP community string (yes/no) [n]: Enter

Enter the switch name: <nexus-A-hostname>

Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: Enter

Mgmt0 IPv4 address: <nexus-A-mgmt0-ip>

Mgmt0 IPv4 netmask: <nexus-A-mgmt0-netmask>

Configure the default gateway? (yes/no) [y]: Enter

IPv4 address of the default gateway: <nexus-A-mgmt0-gw>

Configure advanced IP options? (yes/no) [n]: Enter

Enable the telnet service? (yes/no) [n]: Enter

Enable the ssh service? (yes/no) [y]: Enter

 

Type of ssh key you would like to generate (dsa/rsa) [rsa]: Enter

Number of rsa key bits <> []: Enter

Configure the ntp server? (yes/no) [n]: y

NTP server IPv4 address: <global-ntp-server-ip>

Configure default interface layer (L3/L2) [L2]: Enter

Configure default switchport interface state (shut/noshut) [noshut]: shut

Configure CoPP system profile (strict/moderate/lenient/dense/skip) [strict]: Enter

Would you like to edit the configuration? (yes/no) [n]: Enter

2.     Review the configuration summary before enabling the configuration.

Use this configuration and save it? (yes/no) [y]: Enter

Cisco Nexus B

To set up the initial configuration for the Cisco Nexus B switch on <nexus-B-hostname>, follow these steps:

1.     Configure the switch.

        On initial boot and connection to the serial or console port of the switch, the NX-OS setup should automatically start and attempt to enter Power on Auto Provisioning.

Abort Power On Auto Provisioning [yes - continue with normal setup, skip - bypass password and basic configuration, no - continue with Power On Auto Provisioning] (yes/skip/no)[no]: yes

Disabling POAPDisabling POAP

poap: Rolling back, please wait (This may take minutes)

 

         System Admin Account Setup

 

Do you want to enforce secure password standard (yes/no) [y]: Enter

Enter the password for "admin": <password>

Confirm the password for "admin": <password>

Would you like to enter the basic configuration dialog (yes/no): yes

Create another login account (yes/no) [n]: Enter

Configure read-only SNMP community string (yes/no) [n]: Enter

Configure read-write SNMP community string (yes/no) [n]: Enter

Enter the switch name: <nexus-B-hostname>

Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: Enter

Mgmt0 IPv4 address: <nexus-B-mgmt0-ip>

Mgmt0 IPv4 netmask: <nexus-B-mgmt0-netmask>

Configure the default gateway? (yes/no) [y]: Enter

IPv4 address of the default gateway: <nexus-B-mgmt0-gw>

Configure advanced IP options? (yes/no) [n]: Enter

Enable the telnet service? (yes/no) [n]: Enter

Enable the ssh service? (yes/no) [y]: Enter

 

Type of ssh key you would like to generate (dsa/rsa) [rsa]: Enter

Number of rsa key bits <> []: Enter

Configure the ntp server? (yes/no) [n]: y

NTP server IPv4 address: <global-ntp-server-ip>

Configure default interface layer (L3/L2) [L2]: Enter

Configure default switchport interface state (shut/noshut) [noshut]: shut

Configure CoPP system profile (strict/moderate/lenient/dense/skip) [strict]: Enter

Would you like to edit the configuration? (yes/no) [n]: Enter

2.     Review the configuration summary before enabling the configuration.

Use this configuration and save it? (yes/no) [y]: Enter

FlexPod Cisco Nexus Switch Configuration

Enable Licenses

Cisco Nexus A and Cisco Nexus B

To license the Cisco Nexus switches, follow these steps:

1.     Log in as admin.

2.     Run the following commands:

config t

feature udld

feature interface-vlan

feature lacp

feature vpc

feature lldp

Set Global Configurations

Cisco Nexus A and Cisco Nexus B

To set global configurations, complete the following step on both switches:

1.     Run the following commands to set global configurations:

spanning-tree port type network default

spanning-tree port type edge bpduguard default

spanning-tree port type edge bpdufilter default

port-channel load-balance src-dst l4port

ntp server <global-ntp-server-ip> use-vrf management

ntp master 3

ip route /0 <ib-mgmt-vlan-gateway>

copy run start

Create VLANs

Cisco Nexus A and Cisco Nexus B

To create the necessary virtual local area networks (VLANs), complete the following step on both switches:

1.     From the global configuration mode, run the following commands:

vlan <ib-mgmt-vlan-id>

name IB-MGMT-VLAN

vlan <native-vlan-id>

name Native-VLAN

vlan <vmotion-vlan-id>

name vMotion-VLAN

vlan <vm-traffic-vlan-id>

name VM-Traffic-VLAN

vlan <infra-nfs-vlan-id>

name Infra-NFS-VLAN

exit

Add NTP Distribution Interface

Cisco Nexus A

1.     From the global configuration mode, run the following commands:

interface Vlan<ib-mgmt-vlan-id>

ip address <switch-a-ntp-ip>/<ib-mgmt-vlan-netmask-length>

no shutdown

exit
ntp peer <switch-b-ntp-ip> use-vrf default

Cisco Nexus B
Источник: [cromwellpsi.com]
.

What’s New in the J Datastore 7.03 serial key or number?

Screen Shot

System Requirements for J Datastore 7.03 serial key or number

Add a Comment

Your email address will not be published. Required fields are marked *