Classification: NATO UNCLASSIFIED - RELEASABLE TO INTERNET Fritz,
This sounds a lot like a monitoring problem we are trying to solve here. Do you know how we would know if a DFE in an E7 chassis fails in the "stack"? We had this happen in one switch with two DFEs. One died, but we had no alarm or warning until the users complained about the loss of connectivity. Regards, Jesse Ohlsson Engineer, Information Systems Administration NCSA Sector Mons, Customer Services Squadron B7010 SHAPE Belgium NCN 254-8518, DSN 314-423-8518 Commercial Tel: 0032-65-448518 -----Original Message----- From: Fritz Buetikofer [mailto:[EMAIL PROTECTED] Sent: 06 November 2008 15:42 To: Enterasys Customer Mailing List Cc: [email protected] Mailing List Subject: Re:[enterasys] fan status on secure stacks Hi Joni (again), The problem with "Unassigned" or "Not Present" stack elements in an Enterasys network is not new for us. We have had several power outages in the past and have had then the situation that random stack elements failed to restart when the power came back. For chassis based systems I've added a special port_count attribute in Spectrum which is periodically checked again the actual port_counter; which then alarms us when the actual port_counter is less than what we expect. In the case of Secure Stacks this construct does not work, because the port_count remains the same, even when you un-power one stack element. So we do have the same problem as you have. So this is a severe behaviour distinction between chassis based vs. stacked systems from Enterasys. Best regard, --Fritz. On 03.11.2008, at 18:42, Joni Keller wrote: > In addition to fan and power supply status, the other thing I wish I > could look for with SNMP instead of a brutally ugly telnet-to- > everything script is when we lose a switch in a stack. > > cliConfig -l $LIST -telnetUser $USER -telnetPwd $PASSWD -c $CMDFILE | > grep -e Unassigned -e ^172 | grep -B 1 Unassigned > > $CMDFILE contains > > show switch > exit > > I flipped a coin to look for "Unassigned" or "Not Present" -- I don't > think there's a difference in the results (not to date). > > The other one I like to know about is whenever there are errors on the > stack connection because that stacking cable SHOULDN'T have errors. > > cliConfig -l $LIST -telnetUser $USER -telnetPwd $PASSWD -c $CMDFILE | > grep -e "Up" -e "Down" -e host | awk -F" " '{ if ($1~"host") print $2; > else {if ($2=="Up" || $2=="Down") {if ($4+$5+$7+$8>0) print $0} else > {if > ($3+$4+$6+$7>0) print $0}} }' | grep -B 1 -e "Up" -e "Down" > > And this $CMDFILE contains > > show ip address > show switch stack-ports > exit > > The first command is so I have an IP address I can find with grep; the > second command shows stack errors. > > Those are my SecureStack telnet scripts (so far). > > - Joni --- To unsubscribe from enterasys, send email to [EMAIL PROTECTED] with the body: unsubscribe enterasys [EMAIL PROTECTED] --- To unsubscribe from enterasys, send email to [EMAIL PROTECTED] with the body: unsubscribe enterasys [EMAIL PROTECTED]
