Search results for query: *

Generally if passes a POST they will be ok. Look in the logs while it's booting for any errors. On chassis based switches makes sure the diagnostic mode is set to complete then reboot .

You would make them standalone switches with addresses.They can only be part of the stack if they are tied together with the backplane stack cables.

What do you have for a boot statement ?

I wouls suspect something like faulty ram . You would have to look at the crash files and run it thru the cisco analyzer if you have access to cisco's support page.

The 6500's aren't going anywhere, cisco has stated they will be around well into the years 2020's .

See if this helps http://www.cisco.com/en/US/products/hw/switches/ps663/products_tech_note09186a00800949c3.shtml

Whycap is correct , that is far from a default config and port security features have to be configured. Under your ports none of this is default. switchport access vlan 20 switchport mode access switchport port-security switchport port-security aging time 2 switchport port-security...

To me it sounds like your music on hold device is lacking a defined default gateway . Once you get off the same vlan you can't talk it . I have seen some real old devices that do not have a gateway and you had to either define a static arp entry or use proxy arp on the subnet. Check the...

None that I know of, specially for old catos.

Do you have the correct cards for the Nexus to do Layer 3 ? If so then it is no different than othter cisco L3 switches just create a L3 SVI and put the address on it . Assign ports into that vlan.

Logging event link status will put an entry into the log when an interface goes up or down, whereas snmp trap link status will send an actual interface trap up/down to a management station station.

Legally you can't download them without a license from cisco. You would have to talk to a reseller.

Set modem and router port to 9600 and retry operation and see what happens.

If he has a lot of routed traffic that needs to go between vlans then it could be an issue because all routed traffic must go up to the router then back down the same pipe. You would have to look at the interface utilization during slow periods. Also routers cannot push large amounts of traffic...

A little fuzzy on what you are trying to do here. Maybe clarify. The core l3 switch should be the root for all vlans. Anything that has to travel between different vlans must go to the core anyway. Anything that is in the same vlan will not go to the core.

The router will run the code "IF" the router has enough nvram to accept the 12.4 image which will be considerably bigger .

Do you have a router on that end, if so just enable netflow and you should be able to determine who is cranking the data out by just looking at the netflow data.

How is the ap setup ? Do you have subinterfaces setup on the ethernet interface on the ap ?

Sounds like the management vlan for the 4510 is not allowed across the trunks but without the configs its hard to say. Is the 4500 management address in the same space as the pc you are using ? Crypto commands would have nothing to do with your issue.

A "show vlan" will indicate if you have created the L2 vlan or not. You just show you created a layer 3 SVI for each vlan.