toasters August 2006

toasters@lists.teaparty.net

45 participants
54 discussions

RE: Exceeded the maximum allowed ssh sessions
by Jef Vandenbergen 21 Aug '06

21 Aug '06

I have currently a case running with NetApp concerning the same issue. You should try to find out which server has the hanging connections. Log in to the console (on the back of the filer) and do a netstat -an. Grep on denstination port 22. In my case it was the support console from netapp itself which caused the problem. Netapp support will run a script on the support console to kill the sessions. (is a known bug in the support console's software) The other only available option was rebooting the filer. Stopping and starting the secureadmin will not solve the problem. Regrads, Jef -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Willeke, Jochen Sent: maandag 21 augustus 2006 11:03 To: NetApp Toasters List Subject: Exceeded the maximum allowed ssh sessions Hi, after running a script several times i am no longer able to log on to a filer using ssh. Nevertheless telnet still works. In the eventlog of the filer i see some messages saying: Exceeded the maximum allowed ssh sessions: 12 I do not know why i reached this limit (do i have to close the ssh sessions in the script?) and how can i reset this sessions? Is there a possibility to restart the sshd? I am a little bit affraid of restarting the sshd out of the blue. Best Regards Jochen

2 1

Exceeded the maximum allowed ssh sessions
by Willeke, Jochen 21 Aug '06

21 Aug '06

Hi, after running a script several times i am no longer able to log on to a filer using ssh. Nevertheless telnet still works. In the eventlog of the filer i see some messages saying: Exceeded the maximum allowed ssh sessions: 12 I do not know why i reached this limit (do i have to close the ssh sessions in the script?) and how can i reset this sessions? Is there a possibility to restart the sshd? I am a little bit affraid of restarting the sshd out of the blue. Best Regards Jochen

1 0

RE: Disable CIFS for selected interface
by George, Andrew 21 Aug '06

21 Aug '06

What we usually do is add -wins to it's ifconfig (so the interface doesn't advertise to wins) and assign it a different IP that has a separate DNS record (like "hostname"-management). For a public network...not sure if that would work -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Borzenkov, Andrey (FSC) Sent: Friday, 18 August 2006 8:33 PM To: toasters(a)mathworks.com Subject: Disable CIFS for selected interface We got an interesting question - how to disable CIFS for a single interface? More generally - customer has internal network with clients that access filer using NFS or CIFS. This network is isolated and does not permit sending any autosupport (via any protocol). Customer would like to connect another interface to public network and use it for administration and sending autosupport. The question is - how to disable "normal" client access from public network? regards Andrey Borzenkov Senior system engineer Fujitsu Siemens Computers IT Product Services Tel: +7(495)737-2723 Email: Andrey.Borzenkov(a)fujitsu-siemens.com "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."

1 0

RE: Disable CIFS for selected interface
by Julio Calderon 18 Aug '06

18 Aug '06

If you have control of the swith the filer is plugged into you might be able to set up ACL for a specific VLAN conrrolling what type of traffic is allowed. Julio C -----Original Message----- From: Glenn Walker [mailto:ggwalker@mindspring.com] Sent: Fri Aug 18 05:40:07 2006 To: Borzenkov, Andrey (FSC); toasters(a)mathworks.com Subject: RE: Disable CIFS for selected interface The only way I've seen to do this in the past is with vfiler (multistore). Furthermore if the network is truly public (ie, security risk\internet), I wouldn't connect any interface to it - there are more potential problems that could happen other than access to data. -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Borzenkov, Andrey (FSC) Sent: Friday, August 18, 2006 6:33 AM To: toasters(a)mathworks.com Subject: Disable CIFS for selected interface We got an interesting question - how to disable CIFS for a single interface? More generally - customer has internal network with clients that access filer using NFS or CIFS. This network is isolated and does not permit sending any autosupport (via any protocol). Customer would like to connect another interface to public network and use it for administration and sending autosupport. The question is - how to disable "normal" client access from public network? regards Andrey Borzenkov Senior system engineer Fujitsu Siemens Computers IT Product Services Tel: +7(495)737-2723 Email: Andrey.Borzenkov(a)fujitsu-siemens.com

1 0

RE: Disable CIFS for selected interface
by Glenn Walker 18 Aug '06

18 Aug '06

The only way I've seen to do this in the past is with vfiler (multistore). Furthermore if the network is truly public (ie, security risk\internet), I wouldn't connect any interface to it - there are more potential problems that could happen other than access to data. -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Borzenkov, Andrey (FSC) Sent: Friday, August 18, 2006 6:33 AM To: toasters(a)mathworks.com Subject: Disable CIFS for selected interface We got an interesting question - how to disable CIFS for a single interface? More generally - customer has internal network with clients that access filer using NFS or CIFS. This network is isolated and does not permit sending any autosupport (via any protocol). Customer would like to connect another interface to public network and use it for administration and sending autosupport. The question is - how to disable "normal" client access from public network? regards Andrey Borzenkov Senior system engineer Fujitsu Siemens Computers IT Product Services Tel: +7(495)737-2723 Email: Andrey.Borzenkov(a)fujitsu-siemens.com

2 1

RE: Disable CIFS for selected interface
by Holland, William L 18 Aug '06

18 Aug '06

The only way to do this is to create a vFiler -- requires an additional license. -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Borzenkov, Andrey (FSC) Sent: Friday, August 18, 2006 6:33 AM To: toasters(a)mathworks.com Subject: Disable CIFS for selected interface We got an interesting question - how to disable CIFS for a single interface? More generally - customer has internal network with clients that access filer using NFS or CIFS. This network is isolated and does not permit sending any autosupport (via any protocol). Customer would like to connect another interface to public network and use it for administration and sending autosupport. The question is - how to disable "normal" client access from public network? regards Andrey Borzenkov Senior system engineer Fujitsu Siemens Computers IT Product Services Tel: +7(495)737-2723 Email: Andrey.Borzenkov(a)fujitsu-siemens.com

1 0

Disable CIFS for selected interface
by Borzenkov, Andrey (FSC) 18 Aug '06

18 Aug '06

We got an interesting question - how to disable CIFS for a single interface? More generally - customer has internal network with clients that access filer using NFS or CIFS. This network is isolated and does not permit sending any autosupport (via any protocol). Customer would like to connect another interface to public network and use it for administration and sending autosupport. The question is - how to disable "normal" client access from public network? regards Andrey Borzenkov Senior system engineer Fujitsu Siemens Computers IT Product Services Tel: +7(495)737-2723 Email: Andrey.Borzenkov(a)fujitsu-siemens.com

1 0

RE: Data Ontap 7.2
by BBonner＠msiinet.com 17 Aug '06

17 Aug '06

2 1

RE: SMSQL Config Question
by Hadrian Baron 17 Aug '06

17 Aug '06

Yes... the new version of SME will get rid of the need for a seperate lun. I agree with setting a fractional reserve instead of the full 100%. I'm going to start doing that. Thanks for your help - Hadrian Hadrian Baron Network Engineer VEGAS.com Office: 702-992-4853 Cell: 702-553-5699 _____ From: Eyal Traitel [mailto:etraitel@gmail.com] Sent: Thursday, August 17, 2006 12:35 PM To: Hadrian Baron Cc: toasters(a)mathworks.com Subject: Re: SMSQL Config Question Baron, You have to separate SME and SMSQL for this discussion. Latest versions of SME have added an optional disk space savings when combining the logs and SnapInfo directories together on the same lun, using NTFS Hard Links. This can be a great savings feature that answer youe requirement. SMSQL - As far as my experience goes, you have to back it up by design when using SMSQL - the SnapInfo is an integral part of the backup - so in a way - you can compare with backing up the backup catalog of a backup application - it's an additional information that you need to keep track of the backups, so that you can easily browse and perform the recovey. This is the reason you purchased it isn't it? So - if you care about disk space savings, you can still reduce the reservation amount unrelated to my discussion above - you will just have to monitor it more closely. Snapshots will continue to run, and SME and SMSQL will happily leave with that. By the way - most people tend to believe that an "aweful thing" happens if you reduce the space reservation and then a disk write cannot be accepted - but in fact what happens is that the lun is taken offline. It's downtime, but in a way it's a very simple one - you clean up some space, most likely by removing old backups (snapshots) and then take the lun online again, and you're up. Eyal. On 8/17/06, Hadrian Baron <Hadrian.Baron(a)vegas.com> wrote: So I had many replies about creating a separate LUN to store smsql (or sme) log files / installation directory. I had one question though: For this extra smsql LUN, do I need space reservation / snapshotting enabled? Why have a backup of a backup of a backup right? Hadrian Baron Network Engineer VEGAS.com Office: 702-992-4853 Cell: 702-553-5699 -- Yours, Eyal.

2 1

SMSQL Config Question
by Hadrian Baron 17 Aug '06

17 Aug '06

So I had many replies about creating a separate LUN to store smsql (or sme) log files / installation directory. I had one question though: For this extra smsql LUN, do I need space reservation / snapshotting enabled? Why have a backup of a backup of a backup right? Hadrian Baron Network Engineer VEGAS.com Office: 702-992-4853 Cell: 702-553-5699

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters August 2006