Search results for query: *

btw, you are not able to place each port of a 4550 as trusted. In the documentation of that switch you can find the reason and a filter that needs to be configured.

I know nothing about solaris, but doesn't it has its own proprietary aggregation solution? Configure a static MLT on the 8600 and a static aggregation on the solaris box.

If you have placed a loopback plug, and if stp is disabled. Your port probably is blocked. Try a disable and enable. All the other stuff seems fine. But, is you portable 1 Gig ?

They are both stack products and a lot of the commands are the same for both product lines. The only difference is when you upgrade from a 470-24 towards a 5510-24. With the former you have 26 usable ports, with the latter only 24 fixed. So there you need some tuning. And it depends what kind...

are you sure that your laptop supports 1gig?

The numbers given by Nortel are save practise guidelines. It won't say that the number has to be followed. Since those numbers take all other protocol and features in account. If you need to be sure, you must take contact with the TRC but not the level 1 guys.

If you have another baystack, you could try to stack it. Since the password for stack's and standalone units are different.

Mixed feelings. One end ok since they also support 100M on fiber. But they will also switch people from the 5530 towards the 4500 series. I am not afraid for problems, ofcourse with first revisions it sometimes can be tricky. See to cisco 3750's, the problems they had/have with power supplies...

If CTRL-C does not work anymore, I suggest changing it. They have a LLT waranty, so contact you reseller or nortel.

I think the OPS has something to do with it. We had an issue, that the ops server changed the filter settings, so we stopped using it. So i guess, take a backup of your config before somebody performs a save function. You can restart the box or use source /flash/config.cfg to apply the old config.

Don't forget to perform "apply" to make your configuration changes active. In fact it is a cut down application switch. Only the switching part remains. So if you need documentation, check out http://www.alteon-help.info/ But just concentrate on the layer 2 part.

Check your server connections. Have the "server" guys implemented teaming? without any notice? If that is the case, this can cause problems. Track the mac-address of the servers and cross-check the forwarding table. If that flips, and no MLT's for that purpose has been configured, you know who...

Check the MTU size of the cisco devices. This could cause the ospf problems. the status stays stuck in exchange state when you encountered this issue.

You are confusing two concepts. First NSTP. This is proprietary, just as PVST+ of cisco is prprietary. If you want to talk with other vendors, you need to deploy MSTP. Yes nortel tags its bpdu vlan's (except for group 1), but this technology has nothing to do with SMLT. Second: SMLT, is a...

I never had issues with etherchannel/mlt combinations, as long as you define everything staticly. The only problems, we encountered were tagging issues with the native vlan. Cisco do not tagged them by default. Nortel does.

I guess it is the cpu or one of the line modules. Best is to open a case, trc will ask you do perform some hidden commands to pinpoint to problem

software upgrade. We moved it that time to the 3.7.10. Now you need to make a decision. 3.5 and 3.7 entered the MD cycle. So you need to go to the 4.0 or 4.1 stream. I prefer the latter since the former is based on 3.5 and the latter on 3.7 Never do an upgrade from 3.7 towards 4.0

We also had that problem, and we needed to upgrade

I guess you have 8600's in the core since you mention SMLT? If yes, try the slpp feature in versionn 4.1.1. If you are using SMLT with 8300, I don't know when it will be integrated in that platform...

Stacked vlan's is complex. The mac-address are still populating the fdb's. Spanning tree. Then you have to look into RSTP/MSTP. But with nortel you have a better alternative with SMLT. Be sure that you connect you servers away from the backbone.(unless you install them with teaming on 2 8600)...