Search results for query: *

Not possible. You can implement "load balancing" to a certain extent depending on the routing protocols, but you can not bond interfaces on different routers to do MLPPP for instance.

Dumb question but are you certain that the power cable is making a secure connection in the back of the switch? If so and it is not even finishing boot before reloading again, it could be a corrupt image or config as mentioned.

You CAN do that but it is kind of a pain. When you enable MAC security it is by port, so if you enter MAC addresses manually you have to specify the port that it will be on. So what you COULD do is manually enter each MAC on every port...so that would be X MAC address entries on each of the 48...

InErrors are the total amount of packets that "had errors" that prevented them from being delivered, such as if you have a speed/duplex mismatch and get alignment errors, FCS, frame too shorts, etc (as mentioned). If you literally add them up, they will be identical to the InErrors field. If...

You have to assign an IP address on the VLAN on the switch if that is not yet done. Then from the command line: config t ip dhcp-relay fwd-path <agent(switch VLAN IP)IP> <DHCP servr IP> mode dhcp ip dhcp-relay fwd-path <agent(switch VLAN IP)IP> <DHCP servr IP> enable

Put your IST L3 communication in it's own VLAN, so that the L3 route exchange is in it's own broadcast domain. So just the IST ports on both would be in that VLAN, and that is what you would use for attaching the IP addresses and route info. In regards to SMLT, ensure that the SMLT ID's are...

You can not mirror 2 ports to 1 unless the 2 ports that you are mirroring have a combined speed less than the monitor port. Well, it will let you configure it, but you won't get most of the packets you need. The only way that 2-1 will work is the following: Mirrored ports are 10meg and the...

From the master just type "peer telnet (without the quotes). You will have to log in again as you did on the master.

Not certain if RWA works. I know that RW (case sensitive) does. So for the username use RW and for the password use your telnet password.

It makes the decision based on the source/destination MAC address.

Any VLANs that are spanned across the switches, such as with SMLT's, you need all of those VLANs on the IST as well, yes, added through the MLT area.

Not certain about any new versions of IPSEC, however we use GRE tunnels to do full dynamic routing (OSPF) within the IPSEC tunnels. I could be wrong but I do not believe that you can do dynamic routing any other way over the IPSEC tunnels.

After moving them to the proper VLAN in DM, did you ensure that the PVID of the ports were changed to match properly?

Do you have port 135 explicitly denied on either router? Likely would have been done to stop/contain the Nachi and/or MSBlast worms.

The 7200 likely has a T1 controller module, so on the controller T1 slot in question it is simply: clock source internal

Did it give you any sort of failure? What was the error?

What version of code?

Here is what you need for a successful SMLT. 8600 configs: 1.) The SMLT must be configured in the MLT area...not under the port. The port config is for single port SMLT which will not work in this case. 2.) Spanning tree must be disabled on the SMLT ports. 3.) The port type must be set to...

Not certain what the root cause of this is...as I have witnessed similar symptoms on other product lines. However, I would HIGHLY recommend upgrading the switches to 4.x...preferably the latest that is available. By the way...a reboot of the switch/stack will resolve the issue that you are...

What do your spanning tree configs look like? Also...in regards to 450's and SMLT...any switch...by any manufacturer that I am aware of can work with an SMLT because according to the 450 it is just an MLT...it's the 8600's that are configured for the SMLT with the IST...