Recent content by goodingsd

Multi-link trunks do not load share on a conversation basis. A server being backed up by another server will use the same trunk link for the entire transaction. I beleive that the trunk selection on an 8600 is based on source destination IP address. This would likely explain issues brought up...

1st stacks need to have all units at same code level i.e. BOSS 3.1 or 4.0. 2nd you can upgrade to newest firmware but need to upgrade the software to compatible version - check Nortel web site for switch type and its version fw & sw. 3rd you need to look at the ISVN number of code rev being...

If you want the entire config backed up you'll need the top level access to do so. If you access with anything else then the config you backup contains only config settings that that access level can access / see.

1 - Create a "Role Combination" that includes all the ports you want this L2 QoS Policy to apply to. 2 - Create "Layer 2 Classifier Element" with: - VLAN Tag = 2 - EtherType = IP - all others "Ignore" (Application > QoS > Rules > L2 Classifier Element) 3 - Create "Classifier" adding in above...

We are interested in a 8600 configuration option "IP Spoofing" but were wondering if anyone has enabled same on their core switches. If so: - what was the global auto-recovery you used ? - any adverse performance hist on the network ? - how long have you run this feature ? - how big is your...

You didn't state whether you were ICMPing from on or off segment nor what the latency from where you're ICMPing from and switch. If local and not remote then ... Assuming you've configured the management IP interface properly - IP address, subnet mask & gateway - I'd guess that your switch is...

I'm guessing you IST is over a single port MLT and you've got CP Limit enabled for broadcast & multicast. The error message says you are exceeding the threshold value and the CPU shows that port down - also killing your IST. Either this appliance is generating a broadcast storm or when its...

Thanks Jynxx, the specific issue is having an NFS client switch port connected at 100M FD pulling data from a server that is swicth port connected at GIG FD - extremely slow (20 min vs 5 sec). NFS client configured to use UDP. This happens 100% of time when server & client are on the same test...

If your DHCP server has a /16 scope and different VLAN's - /24 subnets - are forwarding to DHCP server it won't work. Why ? Because the forwarded DHCP broadcast includes the source VLAN information that ID's which scope to hand out addresses from. This source information is the forwarding VLAN's...

Not entirely sure about the 8300, but the 55xx can now only do static's. Nortel staff we met with as far back as 2 years ago indicated that these boxes will be fully L3 capable with RIP & OSPF. That was before the 5520 & 5530 were on sale and we are still waiting.

When you create an IST you start with an MLT. When you create an IST on an MLT you need to point each switch to the other switches VLAN IP address. After creating the IST you need to enable it. Our 8600's running 3.3.0.0 and sho conf statements on one that create the IST on the MLT are ...

The switch is telling you that default SNMP v3 settings are in effect. You need to change them unless defaults are OK on your network. For example, if I had JDM running on laptop connected to your network and went in with SNMP v3 using ID "initialmd5" with MD5 access and using password...

We've run up against a very odd problem where a 100Tx client, with an NFS automount / soft mount, to 1000Tx server gets extemely slow transfer times on test files that normally take less than ten seconds. Client & server both at 100Tx or 1000Tx - no prob Client & server both on 450-24T...

Please clarify if you are trying to connect a Nortel 8616GTE 1000Tx port to a Cisco 100Tx port because if you are it can't be done since the 8616GTE is ONLY 1000Tx. Previous Nortel to Cisco GIG connection experience was over 1000Sx which we eventually got to work by playing with various flow...

You need to setup each switch port for a collocated VoIP phone / PC to be an Untag PVID only with the default VLAN ID for the port set to the PC VLAN. The phone boots up in the default VLAN and gets a response back from the DHCP server telling it which VLAN to be in. For the i2004 phone DHCP...