Recent content by gigaspeed

Personally, I'd ignore it. If it's filling your EpiCenter disable the alarm in EpiCenter. Out of 600 switches in our inventory we have around 5-10 that have had the overheating "false alarm" along with "Failed Fans." First, Extreme thought perhaps a code upgrade would work. It didn't. Then...

The sh config does list it in our working setup, so I don't think that's the problem then. I'm not sure about the ssh2 either, sorry. That seems normal to me from the little ssh experience to be honest though. We use Cisco ACS too, but we don't use ssh. (I know we should, but.......)

I don't think you need the "encrypted" option. It's odd, but I ran into the same thing getting an error when I originally tried that. Instead, just use the shared secret name: conf tacacs primary shared-secret "xxxxxx" See if that makes any differene.

I'm not sure if you're running wireless on the 300-24 or not, but if you are using Extreme's Altitude APs beware of going past code 7.2 or 7.3 (can't remember which). Instead of using the code for the Altitude's "brains" they went with a required separate tftp server on levels above 7.2 or 7.3...

The first step is to have the SSH code installed for the 300. I don't have the exact documentation in front of me, but I think if you are using the SSH code you just need to enable SSH. It will then ask to type in random letters prior to initializing SSH, which takes 10-15 minutes on the Extremes.

You need the .wxtr file to upgrade. This is a "wrapper" file that (I believe this is correct) reformats your flash to allow the larger 7.x code.

I believe you'll have to define a shared secret key too: conf tacacs primary shared-secret xxxxxx And then enable tacacs.

The only way I know to do that is to create a log filter that would display the log entry/word match "Port" to the console whenever "Port down" for example was logged. It's fairly simple. But, with the Extremes the idle timeout for telnet sessions is a maximum of 4 hours, so I'm not sure if...

I'm not 100 percent sure what you're asking, but if you want to see port status you can enter show port config. This will show the port status (linked, speed, negotiation, etc.) You can also show specific ports, such as show ports 1-3,5,9 config and this will only display those ports. As the...

From my experience with the "wxtr" file it worked across the network when I had to upgrade from 7.1 to 7.4 and use the "wrapper xtr" file, but I never tried going from 7.1 to 7.8. (My understanding, perhaps wrong, is it's only needed going from 7.1 to 7.3. After that it's just the .fxtr file...

Odd. I am running 12.0.4.5 and have used the "enable web http" command on all my switches. I was never at level 12.0.2.25 though. (I assume you typo'ed the "enable http web" command out of order?)

You could go into the bootrom menu as stated above and select force a factory default boot (d) then enter f to boot. Once you're in (admin no password) you could then give it an ip address and upload the configuration you're trying to save to a tftp server. (Just don't save the config or...

First, create a policy. Enter command: vi no67udp.pol (you can name it anything you want...just use a pol extension) If you're not familiar with vi then use Windows wordpad, save it as .pol and tftp it to the switch. (ls command will list the files/configs on the XOS switch...linux) The...

I believe there's quite a bit of configuring to enable DHCP to work on the Mgmt port, so if you didn't do any of that I highly doubt it's giving out addresses. If you enter show dhcp-server "Mgmt" does it say "not configured"?

I see it quite a bit too with our gear. It makes no sense in some areas. You may want to try turning auto-polarity off on those ports...I had that work in a few cases. We also replaced cable in others that worked and some new cables didn't make a difference. To top it off we even had some...