toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

Java Thread & TimeDaemon
by Jay Orr 02 Nov '99

02 Nov '99

Huh.... I've been running 5.3.2R1 since Aug 12th, and I had set up the timed to : timed.enable on timed.log off timed.max_skew 2s timed.proto ntp timed.sched hourly timed.servers 205.246.15.5 Today, I started seeing in my syslogs : ..... Tue Nov 2 10:10:42 CST [Java Thread]: TimeDaemon: NTP server '205.246.15.5' reports that the time is Tue Nov 02 10:14:45 CST 1999, for both of the toasters. Anyone know what this is about? these toasters have been up for around 40 days or so... ----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO

1 0

Re: General VIF questions
by Sam Cramer 01 Nov '99

01 Nov '99

Menachem> Hi, We don't "yet" have clustered systems, so maybe my question Menachem> is a bit off, but how do you read a partners /et/rc file in the Menachem> event of a crash - are they mirrored to each other? If so how Menachem> does this mechanism work? The disks are dual-ported, so each node has access to the partner's disks. Check out http://www.netapp.com/products/filer/clusters.html and http://www.netapp.com/tech_library/1004.html for more details on Netapp's clustering technology. Sam

1 0

"quota report" for users
by Brian Tao 01 Nov '99

01 Nov '99

Is there any plans to have "quota report" only look up and display a single user? I know you can do it for quota trees, but not for user or group quotas (according to the 5.2 and 5.3 man pages). I have this in my /etc/quotas file: /www1 tree 20g 1m /www2 tree 20g 1m * user@www1 1g * user@www2 1g I know about using the "quota" command from a UNIX NFS client, but that has some drawbacks (only seeing filesystems it has mounted, output formatting problems on Solaris, not being able to specify a particular mount point, etc.). I'd rather ask the filer how much disk space and inodes are owned by a giving uid, without having to go through the entire "quota report" listing (currently at 5500 lines and growing). -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

1 0

Re: General VIF questions
by Sam Cramer 01 Nov '99

01 Nov '99

I wrote: > When a node takes over for its partner, it reads the partner's /etc/rc > file. The ifconfig commands are processed specially: they are examined > for a "partner" clause. If a partner clause is found, the interface > named in the partner clause takes over for the interface specified in the > ifconfig command. If no partner clause is found, the ifconfig command is > ignored. Whoops --- not enough caffeine! As tkaczma points out, this is exactly backwards: the partner clause is processed by the node destined to take over. Partner mappings (records which define which partner interface the local interface will take over for) --- are recorded at that time. When the node takes over its partner, the partner /etc/rc is run; partner ifconfig statements are matched with the partner mappings in order to determine which local interface will takeover for the partner interface or address in question. Sam

3 2

FW: crossover gigabit
by Francett, Robert D (SAIC) 29 Oct '99

29 Oct '99

fyi... > ---------- > From: Francett, Robert D (SAIC) > Sent: Friday, October 29, 1999 10:55 AM > To: 'Graham C. Knight' > Subject: RE: crossover gigabit > > Graham, > > We had to turn-on auto negotiate on our filer for the Gb connect to work. > This in the rc file too to ensure @ reboot. > #Turn-on auto negotiate > rc_toggle_basic > alttune 0 LinkNegotiation 1 > rc_toggle_basic > # > Regards, > Bob Francett > BP Exploration (Alaska) > > ---------- > From: Graham C. Knight[SMTP:grahamk@ast.lmco.com] > Sent: Friday, October 29, 1999 6:54 AM > To: toasters(a)mathworks.com > Subject: crossover gigabit > > > Does anyone know of any cheat sheets for setting up > a dedicated crossover gigabit ethernet between a filer > and an HP-UX system? > > I've gotten as far as a good link light, but cannot get > a ping to work. > > Thx, > Graham > >

1 0

crossover gigabit
by Graham C. Knight 29 Oct '99

29 Oct '99

Does anyone know of any cheat sheets for setting up a dedicated crossover gigabit ethernet between a filer and an HP-UX system? I've gotten as far as a good link light, but cannot get a ping to work. Thx, Graham

1 0

Is there a way to backup a specific snapshot...?
by Eyal Traitel 28 Oct '99

28 Oct '99

Hi! Does anybody know of a way to backup a specific snapshot using NDMP ? We're using 5.3.2 and up, Veritas NetBackup 3.11 and 3.2 Does anybody have experience with backuping Atria ClearCase ? I know there's a NOW article on that... Eyal.

2 1

Re: General VIF questions
by Sam Cramer 26 Oct '99

26 Oct '99

tkaczma> This is because I think that you cannot use IP addreses with trunk tkaczma> interfaces. At least you couldn't do it last time I set up tkaczma> "multi" trunking on a new rev of DOT. Right --- for vifs, partners must be specified by interface name, not IP address. Sam

1 0

Re: General VIF questions
by Sam Cramer 26 Oct '99

26 Oct '99

cramer> Which interface takes over is specified using the "ifconfig" cramer> "partner" clause. Please note that vif partners MUST be specified cramer> using the interface name (e.g. vif0), not the interface address cramer> (e.g. 172.27.5.50). This was not clearly spelled out in the cramer> documentation, and it has tripped up a number of people. Brian> Hrm, I'm not sure what you mean by using the interface address Brian> instead of the IP address. If I just give the partner the VIF name, Brian> how does it know what IP to use? Is that stored on the mailbox Brian> disk? When a node takes over for its partner, it reads the partner's /etc/rc file. The ifconfig commands are processed specially: they are examined for a "partner" clause. If a partner clause is found, the interface named in the partner clause takes over for the interface specified in the ifconfig command. If no partner clause is found, the ifconfig command is ignored. Sam

3 2

General VIF questions
by Brian Tao 26 Oct '99

26 Oct '99

I have two clustered pairs of F740's arriving soon, so I will likely be able to discover answers to most of my questions, but I figured I'd do a bit of legwork and check my assumptions while I'm still in the planning stages. I'll consider just one of the clustered pairs: nfs1 and nfs2. Both will be equipped with two QFE NIC's. They will connect to a pair of switches with an uplink between them (i.e., passing traffic between two hosts on the same subnet, but on different switches). Logically, consider it a single switch. Each Netapp will be visible on two subnets: 10.35.8.0/25 and 10.35.8.128/25. NFS clients in one subnet will not be able to see filer interfaces in the other. I want to create two single-mode VIF's on each filer, using four interfaces on each filer: ====Active VIF_Subnet1====[e1a] [e2a]----Standby VIF_Subnet1--- ----Standby VIF_Subnet2---[e1b] [e2b]====Active VIF_Subnet2==== ..........Unused..........[e1c] [e2c]..........Unused.......... ..........Unused..........[e1d] [e2d]..........Unused.......... Trunks are created across NIC's. Ports on e1 are cabled to switch 1, and ports on e2 are cabled to switch 2. Since this is a single- mode trunk, the switches shouldn't care, right? During normal operation, switch 1 only sees an active port from e1a, and switch 2 only sees an active port from e2b (since e2a and e1b are effectively "downed" interfaces). While it would be a bit less confusing to say "all interfaces on e1 are active, and all interfaces on e2 are on standby", I prefer to have an active interface on each NIC at all times. This should lessen the chance of Murphy's Law kicking in on an early Sunday morning when e1 does fail, only to reveal that e2 had also died quietly sometime before then. I also want those same physical interfaces to assume their partner's VIF configuration in a failover situation (i.e., what the manual calls "shared interface takover"). So this is what I have, based on the 5.3.2 documentation: nfs1> vif create single VIF_Subnet1 e1a e2a nfs1> vif create single VIF_Subnet2 e2b e1b nfs1> vif favor e1a nfs1> vif favor e2b nfs1> ifconfig VIF_Subnet1 10.35.8.1 netmask 255.255.255.128 partner 10.35.8.2 nfs1> ifconfig VIF_Subnet2 10.35.8.129 netmask 255.255.255.128 partner 10.35.8.130 nfs2> vif create single VIF_Subnet1 e1a e2a nfs2> vif create single VIF_Subnet2 e2b e1b nfs2> vif favor e1a nfs2> vif favor e2b nfs2> ifconfig VIF_Subnet1 10.35.8.2 netmask 255.255.255.128 partner 10.35.8.1 nfs2> ifconfig VIF_Subnet2 10.35.8.130 netmask 255.255.255.128 partner 10.35.8.129 This configuration should be able to withstand failure of a filer NIC port, a filer NIC, an Ethernet cable, a switch port, an entire switch and an entire filer. Certain combinations of double failures are also non-lethal. Since this is all theoretical (to me, anyway), I have some questions. :) What characters are allowed in a VIF name? Is anyone using single-mode VIF's across two different switches like this? How does the Netapp know which VIF to use with the "vif favor" command? I assume this means a physical interface can only participate in one VIF at a time. Is it possible to prioritize interfaces in a VIF with more than two ports trunked together? Can VIF's be shared in a cluster? Can they share ports as above? Special mention is only made about super VIF's and clustering in the 5.3.2 SAG. Can super VIF's be created from single-mode VIF's, or only multi-mode VIF's? Again, the manual only mentions the latter, but does not prohibit the former. Can super VIF's themselves be multi-mode, or single-mode only? I'll post the results of my configuration testing once I have the hardware to play with. -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

2 3

Jump to page:

2025

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