Sun Storage 7110

[pete]

John,

 

if you need any help or assistance then please do not hesitate to contact me.

 

Regards,

 

Phil

 

So.....are you volunteering for help with heavy lifting Phil? *eyes vaguely Sun-related UPS he has to shift*

[Hebdenlad]

Lol. i'm sure you're plenty strong enough to lift a 7210.... they only weight about 80KG (full). don't forget to take out the drives before you lift it. If you have an SSD then that goes in slot 3

[john]

So.....are you volunteering for help with heavy lifting Phil? *eyes vaguely Sun-related UPS he has to shift*

Lifted and fitted it all by myself this evening :p hehe, its sitting there making a bit noise (god they are loud!) in the Server Room The noise in the Gents loo is loud (it backs onto the gents loo does the server room), its having a contest with my 2U HP Proliant it sits under I think for who can make the most noise

 

@Cookie, put the IP of the SAN into the Bypass proxy on the Guardian > Proxy stuff and then set the proxy for the SAN as your IP for smoothwall port 801 and don't enter any authentication info that makes it work fine Seems it doesn't like the Sun SAN via authenticated stuff for some reason

[cookie_monster]

@ Chris and john

 

Phil rang me earlier and assaulted the 7110 with a cunning series of special moves until it relented it turns out that the default route in the network config was missing.

 

Thanks again Phil.

[Hebdenlad]

@ Chris and john

 

Phil rang me earlier and assaulted the 7110 with a cunning series of special moves until it relented it turns out that the default route in the network config was missing.

 

Thanks again Phil.

Grant,

 

All part of the service. Hope you have many happy hours with your S7000.

 

Warmest regards,

 

Phil

[Duke]

hehe, its sitting there making a bit noise (god they are loud!) in the Server Room The noise in the Gents loo is loud (it backs onto the gents loo does the server room), its having a contest with my 2U HP Proliant it sits under I think for who can make the most noise

 

Funny you mention that, I've had a couple of people over here who have been testing either 7110's or 7210's and they've said they run fairly loud and warm - not worryingly so at all, but about what you'd expect from a SAN. However, the 7410 (and presumably the 7310) runs really cool and quiet comparatively, presumably due to the separate HDD chassis. My 7410 makes about half the noise of my NetApp FAS2020 and is one of the coolest running things in the server room. The front of the 7410 chassis is really cold to the touch and the air out the back of the J4400 is barely warm!

 

Phil rang me earlier and assaulted the 7110 with a cunning series of special moves until it relented it turns out that the default route in the network config was missing.

 

Cool, glad you got it sorted mate! We've had various initial troubles with the SAN, but no more so than any new bit of hardware. Once it's up and running and you stop fiddling with settings it appears to be rock solid and fast as anything!

 

EDIT: New minor firmware release is out - http://wikis.sun.com/display/FishWorks/ak-2009.04.10.5.0+Release+Notes

 

Cheers,

Chris

Edited August 12, 2009 by Duke

[Soulfish]

Has anyone had any trouble getting a S7000 to join AD? We're in the process of moving to a new AD domain and despite changing the DNS servers that the 7110 is using and restarting services/restarting the 7110 it keeps giving me the error:

 

The specified domain controller could not be contacted, or the domain is invalid for the controller.

 

Anyone have any ideas?

[Duke]

Has anyone had any trouble getting a S7000 to join AD? We're in the process of moving to a new AD domain and despite changing the DNS servers that the 7110 is using and restarting services/restarting the 7110 it keeps giving me the error:

 

The specified domain controller could not be contacted, or the domain is invalid for the controller.

 

Have you got NTP running, or at least manually synced the clocks with a machine that gets its time from the AD server? Any firewalls set up on the AD machine? If you're moving to a new domain is it on the same IP range (and is the 7110's IP valid for that range) and have you tried specifying the server by IP address to rule out DNS issues?

 

Anyone know if there's a ping or traceroute utility on the CLI to check connectivity and name resolution?

 

Chris

[kmount]

Yep, seen this yesterday.

 

Try lowering the Lan Manager compatibility level to 2 under CIFS and if necessary set a specific DC as a preferred DC (only used prior to joining).

[kmount]

Anyone know if there's a ping or traceroute utility on the CLI to check connectivity and name resolution?

 

Chris

 

Ping and nslookup are on there for certain, not checked for traceroute.

[kmount]

Yes, traceroute is on there too.

 

:> traceroute

error: usage "traceroute [host|addr]"

 

:> ping

error: usage "ping [host|addr]"

 

:> nslookup

error: usage "nslookup [host|addr]"

[Duke]

Yes, traceroute is on there too.

 

Awesome, cheers! Nice to know in case we ever run into connectivity issues...

[Soulfish]

Have you got NTP running, or at least manually synced the clocks with a machine that gets its time from the AD server? Any firewalls set up on the AD machine? If you're moving to a new domain is it on the same IP range (and is the 7110's IP valid for that range) and have you tried specifying the server by IP address to rule out DNS issues?

 

Anyone know if there's a ping or traceroute utility on the CLI to check connectivity and name resolution?

 

Chris

 

Same IP range, and I've specified the DC in the CIFS using both IP and it's hostname on different occasions. Pinging the DC's hostname + IP both work from the 7110 so DNS isn't the issue. Trying to join a invalid AD domain also results in it throwing a DNS based error instead.

 

The time on the DCs and the 7110 are all within 30 seconds of each other.

 

Annoyingly this worked perfectly on the old 2003 R2 domain but it doesn't seem to like the 2008 R2 DCs

 

Yep, seen this yesterday.

 

Try lowering the Lan Manager compatibility level to 2 under CIFS and if necessary set a specific DC as a preferred DC (only used prior to joining).

 

I've just seen a thread on the sun forums suggesting that (Storage General Discussion - Active Directory broken in 7000-series 2009Q2 release?). Just tried it (leaving the CIFS section blank and then tried again with it completed) and it's now throwing a different error:

 

The attempt to join the Active Directory domain failed for unknown reasons. Check that all properties are correct and try again. If the problem persists, contact your service provider.

 

Anyone encountered that error?

[kmount]

Soulfish,

 

Looks exactly like what I seen yesterday (when talking to a 2008 R2 DC!); have a look in the logs and see if there's anything about being unable to import resource.

[Soulfish]

Soulfish,

 

Looks exactly like what I seen yesterday (when talking to a 2008 R2 DC!); have a look in the logs and see if there's anything about being unable to import resource.

 

Sure is: An attempt to import the resource 'ak:/ad/' has failed

Lots of them

[kmount]

I've got a call logged with Sun for it, can you do the same please?

 

I'll make our channel away of this problem and see if we can get a prompt response.

[Duke]

Just as an FYI to people - Sun Support is 0870 6003222. Have the serial numbers of your hardware ready and be aware that if you've bought through a reseller you may need to get them to update your contact details as the hardware may be registered to the distributor.

 

Cheers,

Chris

[Soulfish]

I've got a call logged with Sun for it, can you do the same please?

 

I'll make our channel away of this problem and see if we can get a prompt response.

 

Logged a call with Sun support - hopefully we can get a fix for this soon

 

Just as an FYI to people - Sun Support is 0870 6003222. Have the serial numbers of your hardware ready and be aware that if you've bought through a reseller you may need to get them to update your contact details as the hardware may be registered to the distributor.

 

Cheers,

Chris

 

Thanks for that - was going to go lookup the number but you saved me the hassle

[john]

Same IP range, and I've specified the DC in the CIFS using both IP and it's hostname on different occasions. Pinging the DC's hostname + IP both work from the 7110 so DNS isn't the issue. Trying to join a invalid AD domain also results in it throwing a DNS based error instead.

 

The time on the DCs and the 7110 are all within 30 seconds of each other.

 

Annoyingly this worked perfectly on the old 2003 R2 domain but it doesn't seem to like the 2008 R2 DCs

 

 

 

I've just seen a thread on the sun forums suggesting that (Storage General Discussion - Active Directory broken in 7000-series 2009Q2 release?). Just tried it (leaving the CIFS section blank and then tried again with it completed) and it's now throwing a different error:

 

The attempt to join the Active Directory domain failed for unknown reasons. Check that all properties are correct and try again. If the problem persists, contact your service provider.

 

Anyone encountered that error?

It's MEEEEEEEEEEEEEEEEEEEEEEEEE

Okai enough of the LOL factor, its me that Kim has had this problem with trust me to be the one to break it.

[Duke]

Okai enough of the LOL factor, its me that Kim has had this problem with trust me to be the one to break it.

 

Don't worry, I've broken our 7410 enough times that Andy or Phil just phone me up and sigh now.

 

I think of it as doing Sun a favour by stress testing it...

[cookie_monster]

Don't worry, I've broken our 7410 enough times that Andy or Phil just phone me up and sigh now.

 

I think of it as doing Sun a favour by stress testing it...

 

Not to mention that we're generating a bit list of bugs and more important fixes

[john]

Yeh well its a bug for 2008 R2 we think, mine was fine when it was in love with my 2003 R2 DC but then it rebooted and decided to love my 2008 R2 DC instead and refuses to get divorced from it and do as I want it to which is join the 2003 R2 instead!!!!

[Soulfish]

Yeh well its a bug for 2008 R2 we think, mine was fine when it was in love with my 2003 R2 DC but then it rebooted and decided to love my 2008 R2 DC instead and refuses to get divorced from it and do as I want it to which is join the 2003 R2 instead!!!!

 

You see mine was happily in love with our 2003 R2 DC, but refuses to talk to our 2008 R2 DC

 

Haven't tried rejoining the 2003 R2 domain yet.

[john]

You see mine was happily in love with our 2003 R2 DC, but refuses to talk to our 2008 R2 DC

 

Haven't tried rejoining the 2003 R2 domain yet.

Yup snap We are both in the same boat then, just need to get sun to look a bit harder at it now (Cue Kim kicking them up the ass as it must be a bug in the 2008 R2 release)

[kmount]

I blame John personally...