Cisco error on switch

The following is an excerpt from cisco.com defining policy drops and their possible causes:

This drop is usually seen when a port is not configured correctly. This drop is incremented when a packet cannot be successfully forwarded within switch ports as a result of the default or user configured switch port settings. The following configurations are the likely reasons for this drop:

•The nameif command was not configured on the VLAN interface.

Note For interfaces in the same VLAN, even if the nameif command was not configured, switching within the VLAN is successful, and this counter does not increment.

•The VLAN is shut down.

•An access port received an 802.1Q-tagged packet.

•A trunk port received a tag that is not allowed or an untagged packet.

•The security appliance is connected to another Cisco device that has Ethernet keepalives. For example, Cisco IOS software uses Ethernet loopback packets to ensure interface health. This packet is not intended to be received by any other device; the health is ensured just by being able to send the packet. These types of packets are dropped at the switch port, and the counter increments.

•The VLAN only has one physical interface, but the DEST of the packet does not match the MAC address of the VLAN, and it is not the broadcast address

Throubleshoot these and see if any of them apply to you. Thank you for choosing fixya.com.

Going through the GUI would take too long, so use CLI to add the commands below. After that, check the GUI and see how those changes appear.

VLANs:
On all equipment use 802.1q tagging. The example below puts adsl ports 1 to 10 in vlan10 and ports 11-12 in vlan2. These vlans are 802.1q tagged on the ethernet ports.

switch vlan set 1 1~12:X enet1~enet2:FT DEFAULT
switch vlan set 2 1~10:X 11~12:FU enet1~enet2:FT VLAN2
switch vlan set 10 1~10:FU 11~12:X enet1~enet2:FT VLAN10
switch vlan set 17 1~12:X enet1~enet2:FT VLAN17
switch vlan pvid 1~10 10
switch vlan pvid 11~12 2
switch vlan pvid enet1~enet2 1
switch vlan priority * 0
switch vlan gvrp * disable
switch vlan frametype * all
switch vlan cpu set 1

ATM circuit:
Each port requires one or more VPI/VCI circuit. You could map different circuits to corresponding vlans. The config below creates a primary circuit 1/35 on each port. On ports 5 and 9 is another circuit 1/32 mapped to vlan10

adsl pvc set * 1 35 super DEFVAL
adsl pvc set 5,9 1 32 10 0 DEFVAL

Remember a dslam is just a switch, bridging packets from a VC onto a VLAN or straight onto ethernet.

Hi
I am a damm fool. Had moved the cable at the back. Sound and vision great now. Thanks for codes
J

Dec 04.2008.

NTELL
0=3F B8 36 62 72 E5 E2 76
1=35 5E D6 40 6E AA 99 41
TW
0=C0 F6 61 87 91 F9 67 57
1=F0 83 35 E5 28 40 49 B2

4.12.08.

ntell
0=3F B8 36 62 72 E5 E2 76
1=35 5E D6 40 6E AA 99 41
tw
0=C0 F6 61 87 91 F9 67 57
1=F0 83 35 E5 28 40 49 B2

4.12.08.

ntell
0=3F B8 36 62 72 E5 E2 76
1=35 5E D6 40 6E AA 99 41

tw
0=C0 F6 61 87 91 F9 67 57
1=F0 83 35 E5 28 40 49 B2

4.12.08.
ntell
0=3F B8 36 62 72 E5 E2 76
1=35 5E D6 40 6E AA 99 41
tw
0=C0 F6 61 87 91 F9 67 57
1=F0 83 35 E5 28 40 49 B2

4.12.08.
ntell.
0=3F B8 36 62 72 E5 E2 76
1=35 5E D6 40 6E AA 99 41
tw
0=C0 F6 61 87 91 F9 67 57
1=F0 83 35 E5 28 40 49 B2

0=3F B8 36 62 72 E5 E2 76
1=DB 7A A2 F2 4B 12 7E 59

Start troubleshooting the problem by checking the physical layer (Plugs, Jacks, Cables). Replace them with known working equipment.

Once you have traced the line from your Cisco to each other end (through to ISP, and to network switch), then reset your error counters, by restarting the cisco.

Check the ethernet interfaces on the network switch and the Cisco. Make sure they are both set to Autonegotiate or both set to the same settings like 100mbs Full-duplex. If they are not communicating the same way lots of errors will be generated.