SE 7.5 Limitations

Assuming your DMX-3 arrays are up to date with current 5773 code SE 7.5 should fully support them (according to eLabNavigator).

Are you getting an error running the symcfg discover? Or is it happening somewhere else?

I'm installing over 7.3.1.0 for Solaris.  Yes, the exact same thing happens each time, which I run symcfg disc, remove symapi_db.bin, and run symcfg disc again.  The file gets to 17456 bytes, then pauses.  Forever.  Nothing logged.

I figured it out thanks to both you guys, the Symms are on 5671.  I also have a couple at another site on 5773.176 - correct to assume we can't go to SE 7.5 on those either?  Or is 5773.176 later code than 5773.79?

Hmmm... off the top of my head, this is the point I would engage EMC Support. I suspect they will get you to set the debug dump options to gather more detailed info from SE while attempting the discover again. Then they can analyze the output for the root cause.

I guess first we should confirm though that this host does actually see it's gatekeeper devices and is therefore actually communicating with the array? Does this host have storage allocated from this array, or does it just have GKs allocated for control functions? If you run a sympd list can you confirm that there are no issues with communication to the array?

So this is a fresh install of SE. Am I assuming correctly from your note that each time this happens you are removing the existing symapi_db file and trying to create a new one from scratch?

symcfg discover begins discovery but pauses each time at 17456 bytes.  The symapi_db file doesn't get a bigger after this point no matter how long I wait.  Nothing in the logs.

I'm suspicious it's an Enginuity code issue and that I'll have to roll back.

A SR with support is probably a good idea. You could in the meantime set the environmental variable SYMCLI_DEBUG=-1 (yes not a typo--negative one) and re-run the discovery operation and see if there are any errors in the discovery. I would pipe it to a file though as it will generate A LOT of output.

In any case, I rolled this server back to SE 7.3.

Well, that would certainly do it since those wouldn't even be DMX-3s :-) When you get enough stuff deployed it's easy to get confused over what is where.

As for the DMX-3s at the other site, they should be fine at that code level.

5671 should be supported too though. That Enginuity has not end-of-life'ed yet so should be supported by current SE and from what I see in the support matrix it is.

Yeah .176 is later than .79. The code levels read like "one hundred, seventy-six", not "one-seven-six" so it is a later level and is supported.

Sorry sorry sorry they are DMX 3000s.  It is one old part of the environment from before my time that we never use.  Just tried the upgrade to keep all the mgmt servers consistent.  I am leaving it on 7.3 for now.

I stand corrected Cody. I could easily have misread the Support Matrix info as I was specifically looking for the 5773 code compatibility at the time.

Easy to miss, those documents are huge sometimes! Had to doublecheck myself.