First look at ONTAP 9

NTAP_logoToday, NetApp announced the new version on Data ONTAP, now called ONTAP 9. Not clustered data ONTAP nor data ONTAP 7-mode. From now on, it will just be ONTAP, since 7-mode is no longer being developed. RC1 is scheduled to be out by late June, 2016.

The last few years, NetApp has focused on bringing feature parity to cdot, so new features and usability were a little behind in my opinion. However, the company is now at a point of greater innovation and most importantly, it appears that they are finally listening to the partners, and customers.

ONTAP 9 brings enhancements to the already well known features such as DataMotion, Compression, and dedup among others. It also includes features such as data compaction, HeadRoom, and RAID-TEC among others. More on new features on a separate post.

The main noticeable change on ONTAP 9 is a major face lift. Yes, the GUI is different; way different, while keeping some of the old look. In my opinion, it makes a lot more sense to control everything at a higher level, rather than having to hunt drop-down menus at different locations, just like the 8.2 days.  The new UI brings simplicity and usability at the same time, with an intuitive, non-cluttered set of tabs.

Here is a sneak peek of ONTAP 9 UI. The main menu is composed of 7 tabs that will give you access to manage and configure your NetApp cluster. Categories include Dashboards, LUNs, SVMs, Network, Hardware and Diagnostics, Protection, and Configurations.

Rather than describing what each tab does, I will just be posting the screenshots since they are self explanatory in my opinion. Enjoy…

DASHBOARD

ONTAP_9_Dashboard2

ONTAP_9_Dashboard

 

LUNs

ONTAP_9_LUNs

 

SVMs

ONTAP_9_SVM

ONTAP_9_SVM2

 

NETWORK

ONTAP_9_Network

 

HARDWARE and DIAGNOSTICS

ONTAP_9_HW

 

PROTECTION

ONTAP_9_Protection

 

CONFIGURATIONS

ONTAP_9_Config

 

You can find a step-by-step guide by Neil Anderson at http://www.flackbox.com/netapp-simulator/

HTML 5 – vSphere and ESXi Host Web Clients

H5The wait is over (almost). Since the introduction of vSphere Web Client, many admins have slowed down the adoption of the Web Client as well as updates to vSphere due to the performance of said client.

VMware has released a couple of flings in relation to this problem. One of them was the host web client, where you can manage your hosts directly without the need to install the vSphere client. This fling is now part of the latest update to vSphere 6.0 U2. A few days ago, VMware released a similar option for vCenter. Both of these options are based on HTML 5 and javascript.

Host Web Client

Like I mentioned before, starting with vSphere 6.0 U2, the host web client is already embedded into vSphere. If you do not have this update you can still download the OVA and access the host web client that way. Currently it only works if you have vSphere 6.0+ but once version 5.5 U3 is released, it will also work with that version. Here is a link to download the fling.

To access the web client, you will need to add “/ui” at the end of the name/ip address of your host. For example https://<host-name-or-IP>/ui

The client is very responsive and has a nice UI. Not all the features are currently supported, but more will be coming at some point in the near future.

host_ui

 

vCenter Web Client

This HTML web client is only available as a fling at the moment. You will need to deploy an OVA and register the appliance with the vCenter that you would like to manage. Being a fling, not all features are included. It basically focuses on VM management, but I am sure they are working to port all the features over at some point (I hope).

To deploy this ova, you will need to enable SSH and Bash Shell on your VCSA. You can do both from the VCSA web UI. If you are running Windows based vCenter refer to the Fling documentation here.

vcsa_uI-shell

Prior to going through the configuration you will need to

  1. Create an IP Pool (If deploying via C# Client)
    • Note: I deployed using Web Client and didn’t create the IP Pool for me automatically as it is supposed to, so double check you have an IP Pool before powering on the appliance
  2. Deploy the OVA

IP_Pool

After deploying the OVA, creating an IP Pool, and enabling both SSH and Bash Shell on VCSA, it is time to configure the appliance.

  • SSH to the IP address you gave to the appliance using root as the user and demova as the password
  • Type shell to access Bash Shell
  • run the following command in Bash Shell
    • /etc/init.d/vsphere-client configure –start yes –user root –vc <FQDN or IP of vCenter> –ntp <FQDN or IP of NTP server>
  • If you need to change the default password for your root account, you can run the following command from bash shell
    • /usr/bin/chsh -s “/bin/bash” root
  • answer the question by answering YES
  • and enter the credentials for your vCenter


H5_deploy1

H5_deploy2

 

The HTML Web Client is pretty awesome, I gotta say, even if not all the features are there yet. It is super clean, and responsive. I can’t wait for it to be embedded with a full feature set.

 

H5_1

H5_2

The path of the “Swiss Army” admin – Career Advice

Many-hatsDefinition: The “Swiss Army” admin/engineer is also referred to as a technical staff member wearing many hats. Such individual is often overlooked and under-appreciated in the business.

In many environments, usually in small and medium businesses, the IT staff is comprised of one of two people that take care of the entire infrastructure. This means that there are usually a handful of people that take care of storage, virtualization, network, application, email, databases, and administration of other critical applications for the entire business. This person is a jack of all trades, but master of none.

I come across this type of individuals on a daily basis and most of them are not thrilled about their situation. They are asked to take care of the entire IT infrastructure, do it fast and efficiently with no additional tools and low compensation. Oh yes, and be available 24/7, of course.

Although this sounds horrible, and many of us have been there or are still going through this, there is an upside of being a “Multi-mode” admin/engineer.

I started my career backwards. I began working at huge, multi-billion dollar enterprises consisting of hundreds of thousands of users. I was doing two or three things as part of my responsibilities, but that was the responsibility ceiling for me. I was not allowed to learn anything else outside my expertise, so I decided to move on to smaller companies. Turns out that the smaller the company, the more I got to do and learn. Yes, I was busier and there were no processes in place. It was more like shooting from the hip, which did not amuse me, but at least I was learning a lot.

The point is, wearing many hats allows you to learn many different areas of IT, but it shouldn’t stop there. If you want to grow in your career and/or move to bigger companies, you need to master multiple areas of IT. Obviously this does not happen overnight and takes quite a bit of involvement, effort, and more importantly your personal time and sacrifice.

Why do I need expertise in multiple areas?

Well, if you wear many hats, you are more than capable of administering an environment. But that is pretty much it. When you study and use labs for other technologies or even deep dives with existing solutions, you learn how things work and interact. The more you learn about separate solutions, the more you see how this is a big circle and it makes sense from an interaction point of view. Learning, understanding and being able to speak intelligently about the interactions between different technologies makes you an invaluable asset to the business.

One may argue that to be an expert, you need to specialize in one and only one particular area. I agree with that, but nothing stops you from mastering areas as time goes by. I’m not saying you need to be an expert on everything right now, but pick an area where you think you are good at and dive into. Once you feel you have mastered that domain or close to, you can move on to another area.

What it comes down to is depth of knowledge. Swiss army admins have a breadth of knowledge but little depth. Having both breadth and depth of knowledge will allow you to greatly expand your career, as these individuals are few within job markets. So, work on deepen the knowledge you currently have. Such depth of knowledge will increase as long as you consistently work on them, allowing you to become not just a Swiss Army admin but a well rounded technology expert.

Cisco UCS Generation 3 First Look.

Worth a read…

Colin Lynch's avatarUCSguru.com

I noticed last week that Cisco have just released the eagerly awaited Cisco UCS 3.1 code “Granada” on CCO.

Whenever a major or a minor code drop appears the first thing I always do is read the  Release Notes , to see what new features the code supports or which bugs it addresses. Well in reading the 3.1 release notes it was like reading a Christmas list. There are far too many new features and enhancements to delve into in this post, so I will just be calling out the ones that most caught my eye

Cisco UCS Gen 3 Hardware

At the top of the release notes is the announcement that 3.1 code supports the soon to be released Cisco UCS Generation 3 Hardware.

With the new Gen 3 products the UCS infrastructure now supports full end to end native 40GbE.

The Generation 3 Fabric Interconnects come in 2 models the…

View original post 677 more words

Bug Catcher: SRA/SRM testFailoverStart

scared-bugI’ve decided to write this post since I spent quite a bit of time troubleshooting this problem just to find out that it was a bug, grrrr. So, hopefully this will save someone some hair tearing and time as well.

I was recently implementing SRM 6.1 on a NetApp cluster running clustered mode (8.3.1). Configuration was flawless and was happy that I may complete a project early on a Friday. We decided to run a failover test to DR site, and this is where the issue came about.

After double checking all the settings, I had no luck finding any resources with this issue/resolution. The job would fail almost immediately after starting, with the error “Storage ports not found”. I checked the SRA ontap_config file to make sure the IPv4 option (isipv4) was set to match the IP format of the NFS configuration within SRM. Checked to make sure the firewall on the NetApp was set properly to allow communication, but everything looked correct.

I learned later on, that SRA 2.1 cannot detect NetApp interfaces that are set to mgmt. So, with NetApp LIFs, you have the option to “bundle” your data and mgmt interfaces within the same LIF (NFS, CIFS). If this is the case, those interfaces will be set to have the mgmt firewall-policy rather than the data firewall-policy, which is ok unless you are trying to use SRM/SRA in that setup.

Resolution:

  • Create a separate/dedicated mgmt LIF for your NFS SVM (per SVM)
    • Otherwise you are removing all mgmt interfaces for that SVM without a replacement
  • Remove the mgmt option for the NFS data LIFs
  • Change the firewall-policy for the NFS data LIFs from mgmt to data
    • You can use this command to do so:

network interface modify -vserver [vserver_name] -lif [data_lif_name] -firewall-policy data

Also make sure to check the ontap_config file for SRA. This is located under C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\CMODE_ONTAP.  If the ip addresses for the data LIFs are IPv4, this option needs to be set to YES.

ontap_config_SRA

 

 

 

Bug should be fixed with SRA 3…. coming soon to a datacenter near you.