e0M is a NIC that¹s ³owned² by ONTAP, that¹s not much different from e0a or e0b. Once you give it an IP address, you can ssh into it and get an ONTAP CLI, just like you could to e0a.

The RLM is a completely separate subsystem that has it¹s own network interface. If you ssh into the RLM¹s IP address or hostname, you¹ll have access to the RLM itself and it¹s CLI. From the RLM¹s CLI, you can issue the Œsystem console¹ command to tunnel into the main controller¹s CLI (ONTAP). Once you¹ve tunneled in, you¹re at the real ONTAP CLI. To exit and get back to the RLM¹s CLI, issue a Ctrl-D.

On a FAS3100 series, an optimization was made to put both ONTAP¹s e0M NIC and the RLM¹s NIC behind an internal Ethernet 10/100 switch and then we present a single RJ45 jack so you only need one cable from there to your management network (they could both go on a data network if you don¹t have a separate management network). This does assume you wanted e0M and the RLM on the same network.

So the trick to know is that you need an IP address for each device and there are two devices behind that RJ45. The other trick you need to know is how to get from the RLM to the ONTAP console and back. You can find more info in the SysAdmin guide, e.g.

http://now.netapp.com/NOW/knowledge/docs/ontap/rel732_vs/html/ontap/sysadmin /index.html Look for ³How to access the storage system² and ³How to use the RLM...²

While I have the floor, I want to put in a plug to check out the Remote Support Agent functionality:

http://now.netapp.com/NOW/knowledge/docs/remote_support_agent/pdfs/rsa_userg uide.pdf

We think it can vastly improve the support experience and reduce the case resolution time. Check it out.

Brad.

From: Kevin Sheen sheenk@zbzoom.net Date: Mon, 14 Jun 2010 10:02:51 -0400 To: Simon Vallet svallet@genoscope.cns.fr Cc: toasters@mathworks.com Subject: Re: Several questions about ONTAP 8.0 and DS4243 shelves

We may be experiencing your item 3 below. I have a case open with Netapp but have yet to really work on it.

Our experience with e0M on a new 3140 is that when you ssh to that interface, we are place directly into what I would consider the system console and we don't currently know how to get back to the actual rlm interface. We've tried to reboot that rlm. If I hear anything on our case I can post our solution. I'm curious, are you experiencing the same issue with your e0m interface? Our serial port to the rlm seems to be fine, meaning we can utilize the rlm interface cli as well as access the system console and then get back to the rlm interface. This new 3140 replaced a 3020.

Thanks, Kevin

At 09:05 AM 6/14/2010, you wrote:

Hi,

we recently acquired two filers (3140) with DS4243 shelves, and upgraded them to ONTAP 8.0. I know that this is a GA release, but I did notice some glitches (which are perfectly understandable), and have some questions for the people here who understand this better than me :

• installing the 8.0 doc yields a "Documentation for Data ONTAPTM 8.0 is installed, but is out-of-date." message ;

• I couldn't find any firmware updates for the DS4243 shelves on NOW -- is this normal? ;

• we configured the e0M interface (and I think that it is a great idea), but I couldn't find a way to configure the filer to exclusively be administrated through e0M (i.e. the embedded SSH server now answers on both interfaces) ;

• since we migrated from a 7.x release, our root volumes are on 32-bit aggregates -- is there a way to have the root volume on a 64-bit aggregate (and if not, what is the technical reason for it) ?

Do some of you have encountered the same questions ?

Regards, Simon --

Simon Vallet Ingénieur systèmes, réseaux, sécurité CEA DSV/IG/GEN - Genoscope Tél.: +33 1 60 87 36 06

Mél.: sjv@genoscope.cns.fr

On 06/14/2010 01:32 PM, Holland, William L wrote:

I have not run ONTAP 8 on anything other than a simulator, so I don't know this to be fact. I suspect, that if you wanted your root volume to be 64 bit, you could take steps similar to how they were moved from traditional volumes to flexible volumes: 1. Create a new flexible volume on a 64 bit aggregate with sufficient capacity to accommodate vol0 (for the sake of this argument, we'll call it newvol0) 2. QTree snapmirror or ndmpcopy vol0 to newvol0 3. vol options newvol0 root (this makes it the root volume instead of the original vol0) 4. Reboot 5. Rename vol0 to oldvol0 and rename newvol0 to vol0 - if you wish to retain vol0 as your root 6. If you are licensed for CIFS, you will have to change your CIFS shares that were on the original vol0 to point to the new vol0 as the renaming of the volumes caused the shares to follow the name changes.

Could be worth a try on a system that you don’t mind rebuilding.

You can not. In 8.0 the root aggr has to be on a 32-bit aggr. We just installed two clusters with 8.0 and ran into this limitation. I believe it's being addressed in a future version.

--rdp

Rich Payne Manager, Data Services AMD

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Simon Vallet Sent: Monday, June 14, 2010 9:06 AM To: toasters@mathworks.com Subject: Several questions about ONTAP 8.0 and DS4243 shelves

Hi,

we recently acquired two filers (3140) with DS4243 shelves, and upgraded them to ONTAP 8.0. I know that this is a GA release, but I did notice some glitches (which are perfectly understandable), and have some questions for the people here who understand this better than me :

• installing the 8.0 doc yields a "Documentation for Data ONTAPTM

8.0 is installed, but is out-of-date." message ;

• I couldn't find any firmware updates for the DS4243 shelves on NOW

-- is this normal? ;

• we configured the e0M interface (and I think that it is a great

idea), but I couldn't find a way to configure the filer to exclusively be administrated through e0M (i.e. the embedded SSH server now answers on both interfaces) ;

• since we migrated from a 7.x release, our root volumes are on

32-bit aggregates -- is there a way to have the root volume on a 64-bit aggregate (and if not, what is the technical reason for it) ?

Do some of you have encountered the same questions ?

Regards, Simon