9 Legend

 • 

20.4K Posts

October 30th, 2008 04:00

you do not want to present metas to Celerra and second thing you do not want to expand device already presented to Celerra (create metas). So let's say you need to create a 100G file system for a new project. Your hyper size on the array is around 50G so you will need to map two hypers to FAs used by Celerra. You will map starting at LUN address 11 and then 12. Once mapping is complete, rescan on the Celerra side. Run nas_disk -l and you should see your two hypers listed at the bottom of the list. Now try to create your file system.

90 Posts

October 24th, 2008 11:00

What commands are you running on the Celerra to "re-scan"?

9 Legend

 • 

20.4K Posts

October 24th, 2008 11:00

is your hyper set to CELERRA_FBA emulation ?

October 24th, 2008 15:00

Also make sure that you are using a TID greater then 10

Message was edited by:
tonydcdi

9 Legend

 • 

20.4K Posts

October 24th, 2008 18:00

Tony ..where did you see this requirement ? I have FAs from DMX2000 and DMX3 and my devices are only using LUN id ..TID is not used at all (set to 0). My LUN addresses start from 001, 000 is VCM.

16 Posts

October 26th, 2008 22:00

I am using the web GUI to run the re-scan.

How can i check is the hyper set to CELERRA_FBA emulation ?

The device i have map to the FA port only comes with LUN number, what is TID?

9 Legend

 • 

20.4K Posts

October 27th, 2008 03:00

run:

symdev show -sid hyper#

and look for device emulation field.

TID is target id, as far as i know it's only used with FA that have Volume set Addressing enabled for HPUX.

Here is a thread that explains how to provision space from DMX to Celerra gateway.

http://forums.emc.com/forums/thread.jspa?messageID=594750򑌾

October 27th, 2008 18:00

The Celerra reserves LUN ID from 000-00F for the DART code and others. When using the DMX you need to start with LUN ID 010 for data luns. Same holds true for CLARiiON arrays. When you present a data LUN, the HLU needs to start at 16 or higher as the Dart code reserves the lower luns.

9 Legend

 • 

20.4K Posts

October 27th, 2008 18:00

The Celerra reserves LUN ID from 000-00F for the
DART code and others. When using the DMX you need to
start with LUN ID 010 for data luns.


i see ..this applies for DMX you are booting off, if you have additional DMX ..its LUNs can be mapped to LUN address 0 and up. Thanks for clarification Tony.

674 Posts

October 28th, 2008 08:00

to be more on the save way,

do not use Lun 00 to 0F even on a second DMX. Then there would be no way, the datamover would try to boot from the wrong DMX. Even with cleared binding tables.

9 Legend

 • 

20.4K Posts

October 28th, 2008 10:00

Peter,

my second DMX has been in production for 2 years now ..so it will be hard to re-do it now. Can you point to any documentation that explains how to provision DMX storage to Celerra gateway ? I have always seen instructions for Clariion ..but never for DMX.

Thanks

9 Legend

 • 

20.4K Posts

October 28th, 2008 13:00

i knew it ...teasing us customers with all these fancy tools you got. :)

9 Legend

 • 

20.4K Posts

October 28th, 2008 13:00

there is a proc generator for Celerra ? Where do i find it ? I've looked here

Home > Support > Product and Diagnostic Tools > Celerra Tools

4 Operator

 • 

1.5K Posts

October 28th, 2008 13:00

Sorry my friend - the Celerra Procedure Generator is for EMC internal use only - mainly for Customer Support activities. Unlike CLARiiON procedure Generator, it does not help much on the configuration or implementation part. Also there is no Customer version for this unlike CLARiiON Procedure generator.
Sorry again not to help you this time :(
Sandip

October 28th, 2008 13:00

Hey Dynamox

Most of the docs that I use are internal EMC docs as I am an ASN partner, however, have you tried the Customer Celerra Procedure Generator?
No Events found!

Top