%AMDP2_FE-5-LATECOLL: FastEthernet0/0 transmit error

Hi, one of our customers using c2610xm is having %AMDP2_FE-5-LATECOLL: FastEthernet0/0 transmit error' frequently and after sometime router gets hung and user unable to ping fastethernet 0/0. Once router is power cycled user can again use the network. Here below is the sh int output. Just would like to know if this is due c2610xm fasteithernet hardware problem or otherwise as customer has thorougly checked their lan and confirmed all ok. Concered about number of interface resets as well
Thanks Bandula
router#sh int fastEthernet 0/0
FastEthernet0/0 is up, line protocol is up
Hardware is AmdFE, address is 000f.9008.a260 (bia 000f.9008.a260)
Description: --- Customer LAN
Internet address is 192.168.16.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 01:31:18
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 2000 bits/sec, 5 packets/sec
5 minute output rate 57000 bits/sec, 9 packets/sec
47150 packets input, 11187528 bytes
Received 4424 broadcasts, 0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 1 ignored
0 watchdog
0 input packets with dribble condition detected
49567 packets output, 30650716 bytes, 0 underruns
0 output errors, 8 collisions, 15 interface resets
0 babbles, 15 late collision, 11 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
router#

Hi Ankur
Seems to be ok after config change. Shall continue to monitor. Many thank for your excellant advise
Regards Bandula
pcmb127#sh int fastEthernet 0/0
FastEthernet0/0 is up, line protocol is up
Hardware is AmdFE, address is 000f.9008.a260 (bia 000f.9008.a260)
Description: --- Customer LAN
Internet address is 192.168.16.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:09, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:35:06
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 11000 bits/sec, 10 packets/sec
5 minute output rate 128000 bits/sec, 15 packets/sec
16590 packets input, 1931773 bytes
Received 1666 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
20386 packets output, 20086403 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
pcmb127#

Similar Messages

Transmit error in 2621 router

Dear All,
I got the following errors from my cisco 2621 router - the network connection between our ISP and our router suddenly unstable and have packet lost. But after router reload, the problem will be resolved.
This error message does not show up from time to time but today it happen again. Last time this problem happened, i had checked with ISP engineer to make sure "Duplex & Speed" are the same between our router and their network switch.
From Cisco website, the problem explanation is "Possible causes are usually incorrect cabling or a non-compliant number of hubs in the network. Bad network interface cards (NICs) can also cause late collisions". I personally don't think this is the problem, so any other reason ? E.g. IOS version not stable ?
router>sh ver
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-I-M), Version 12.0(3)T3, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 15-Apr-99 15:41 by kpma
Image text-base: 0x80008088, data-base: 0x80693A88
ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
hkcyberu uptime is 6 hours, 9 minutes
System restarted by reload at 10:23:34 HKT Fri Apr 29 2005
System image file is "flash:c2600-i-mz.120-3.T3"
cisco 2621 (MPC860) processor (revision 0x102) with 24576K/8192K bytes of memory.
Processor board ID JAD04420INF (3795023180)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
2 FastEthernet/IEEE 802.3 interface(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read/Write)
Configuration register is 0x2102
Error message:
"%AMDP2_FE-5-LATECOLL: FastEthernet0/1 transmit error" & "%AMDP2_FE-3-UNDERFLO: FastEthernet0/1 transmit error
Alex Leung

Hello Alex,
just to make sure: when you say that you have checked speed and duplex settings on both sides, does that mean that both sides are set to fixed full duplex and speed settings (no autonegotiate) ?
As for the UNDERFLO error message, this is what CCO says:
Error Message
%AMDP2_FE-3-UNDERFLO: AMDP2/FE([dec]/[dec]), Transmit underflow
Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Regards,
GP

Java.io,IOException: Failed to transmit error in whatsapp.....HELP!!

I get java.io,IOException: Failed to transmit when I input my phone number into Whatsapp. I need help to get past it because I have made sure my data has stayed on while trying to connect and it still has not worked and I keep getting this message.
Could someone please help me!!

could you provide details stack trace...
Leslie Love

Fax Transmit Error

Hi Expert,
I have a problem when sending a fax to PSTN. This is a logical connection.
Fax-PSTN-NECPABX-VG-SatelitLink-CallManager-ATA-Analog Fax Machine
but if i try using this one
Fax-NECPABX-VG-Callmanager-ATA-Analog Fax Machine
it's working
We using g729 codec
Can somebody give me a advice to resolve this.
Best Regards
Andri

The first connection has both a satellite link and a PSTN connection - either of which could be the source of the problem.
Try to rule out each of these in turn, then concentrate on whichever seems to have the problem.
Regards
Aaron
Please rate helpful posts...

Monitoring Transmit and Receive Error

We have an monitoring system to monitor all the access points transmit and receive errors.
There are four column name "Receive Error", "Receive Discard", "Transmit Error" and "Transmit Discards".
I have notice that there are a lot of transmit discards packets than the rest of the columns for one of the AP.
Is it normal for the packets of the AP to have transmit discards high?

I notice that this AP the Dot11 driver runtime (1331728) is very high than normal Access point (78157)
The rest of the process runtime looks equal.
Is this indicate that the Dot11 driver is going to be faulty?
Transmit Discards AP
CPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
22 127 10867611 0 0.00% 0.00% 0.00% 0 Per-Second Jobs
23 218 2173540 0 0.00% 0.00% 0.00% 0 Compute load avg
24 1134632 181178 6262 0.00% 0.00% 0.00% 0 Per-minute Jobs
25 1331728 317947128 4 0.08% 0.02% 0.00% 0 Dot11 driver
Normal AP
CPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
21 238 10867159 0 0.00% 0.00% 0.00% 0 TTY Background
22 101 10867206 0 0.00% 0.00% 0.00% 0 Per-Second Jobs
23 170 2173453 0 0.00% 0.00% 0.00% 0 Compute load avg
24 1125336 181172 6211 0.00% 0.00% 0.00% 0 Per-minute Jobs
25 78157 318443069 0 0.00% 0.00% 0.00% 0 Dot11 driver

Read the transmit/receive error counter from CAN

I would like to read every packet that runs accross the CAN bus. I am in a situation where my Can Receive.vi is set to read any CAN bus errors, but I would like to see the entire can packet(including CRC values, DLC values, etc etc). Is there a way to do this? Any sample vi's out there?
Also, I'de like to read the status of the receive/transmit error counter on either side I assume. I am trying to see what my arbitration values hover around (less than 128, over 128, etc etc).
Thanks for any help.
Andre

Hi Andre
The NI CAN hardware does not have the ability to access the full raw CAN frame. This is because of the used CAN controller (Philips SJA 1000 on Series 2 CAN hardware) does which does not provide all of this information. However, the following data is provided:
Arbitration ID (11 or 29 bit)
Data Length (DLC)
Remote Frame Flag (RTR)
Data (0-8 byte)
As you are interested in the raw/unconverted CAN data, you should focus on the NI-CAN Frame API, as the NI-CAN Channel API tries to abstract these information.
With Series 2 CAN hardware, you have read access to the receive/transmit error counter. Take a look at the ncGetAttr function (Frame API) or the GetProperty function (Channel API) and query the ‘Series 2 Error/Arb Capture’ attribute or the ‘Interface Series 2 Error / Arb Capture’ property for that. You can find more details on how to read the returned data in the help for the two functions.
-B2k

Sent a picture to someone yesterday. status is stll "sending". Can I delete this. It seems to be locked up. I can't even get a failed message error. It is just out there in space.

how do I delete a sent message that won't complete the transmission. It has been "sending message" for 24 hrs. I can't even get a failed to transmit error. I can't delete it like I would delete a sent message because it won't show up in my messages until it completes the transmission or I get a message of failed transmission.

Hey there,
If I understand correctly, at the moment your messages application seems to be unresponsive and you cannot send any messages, and this started after trying to send an image to someone else. I would start by quitting not just Messages but all the running apps on the phone:
iOS: Force an app to close
Double-click the Home button.
Swipe left or right until you have located the app you wish to close.
Swipe the app up to close it.
When you have done that restart the device and test the issue again by trying to send the image one more time:
iOS: Turning off and on (restarting) and resetting
Thank you for using Apple Support Communities.
All the best,
Sterling

VM Causes Output Errors

I'm looking for some out of the box thinking here.
Here's the setup:
vSphere 5.1 Cluster
4 x B200M2 in Chassis A
4 x B200M2 in Chassis B
Chassis A has 2104XP IOM and does not use port-channeled connectivity.
Chassis B has 2208XP IOM and DOES use port-channels.
Windows 2008R2 virtual machine, hardware version 8, VMXNET3 network interface.
Here's the problem:
If the VM is running on an ESXi host in Chassis A, the physical interface that server is pinned to will start clocking output errors slowly. If you move it to another host in the same chassis, the physical link for that host will start clocking errors. If you move it to a host in the other chassis, the port-channel starts clocking output errors.

Summary is accurate, I grabbed some stats off one of the hosts.
For reference:
vmnic0 and 1 are for Management only
vmnic2 and 3 are for VDS
vmnic5 and 6 are vMotion
~ # esxcli network nic stats get -n vmnic0
NIC statistics for vmnic0
Packets received: 183853406
Packets sent: 14248
Bytes received: 15109232248
Bytes sent: 10860364
Receive packets dropped: 0
Transmit packets dropped: 0
Total receive errors: 0
Receive length errors: 0
Receive over errors: 0
Receive CRC errors: 0
Receive frame errors: 0
Receive FIFO errors: 0
Receive missed errors: 0
Total transmit errors: 0
Transmit aborted errors: 0
Transmit carrier errors: 0
Transmit FIFO errors: 0
Transmit heartbeat errors: 0
Transmit window errors: 0
~ # esxcli network nic stats get -n vmnic1
NIC statistics for vmnic1
Packets received: 216684173
Packets sent: 78566218
Bytes received: 47589164213
Bytes sent: 83540882074
Receive packets dropped: 27
Transmit packets dropped: 0
Total receive errors: 17
Receive length errors: 0
Receive over errors: 0
Receive CRC errors: 17
Receive frame errors: 0
Receive FIFO errors: 0
Receive missed errors: 0
Total transmit errors: 0
Transmit aborted errors: 0
Transmit carrier errors: 0
Transmit FIFO errors: 0
Transmit heartbeat errors: 0
Transmit window errors: 0
~ # esxcli network nic stats get -n vmnic2
NIC statistics for vmnic2
Packets received: 2308445804
Packets sent: 1769198467
Bytes received: 760268005329
Bytes sent: 1007781294817
Receive packets dropped: 5801
Transmit packets dropped: 0
Total receive errors: 4
Receive length errors: 0
Receive over errors: 0
Receive CRC errors: 4
Receive frame errors: 0
Receive FIFO errors: 0
Receive missed errors: 0
Total transmit errors: 0
Transmit aborted errors: 0
Transmit carrier errors: 0
Transmit FIFO errors: 0
Transmit heartbeat errors: 0
Transmit window errors: 0
~ # esxcli network nic stats get -n vmnic3
NIC statistics for vmnic3
Packets received: 3515742297
Packets sent: 1260747637
Bytes received: 795264860939
Bytes sent: 382208295578
Receive packets dropped: 0
Transmit packets dropped: 0
Total receive errors: 179
Receive length errors: 0
Receive over errors: 179
Receive CRC errors: 0
Receive frame errors: 0
Receive FIFO errors: 0
Receive missed errors: 0
Total transmit errors: 0
Transmit aborted errors: 0
Transmit carrier errors: 0
Transmit FIFO errors: 0
Transmit heartbeat errors: 0
Transmit window errors: 0
~ # esxcli network nic stats get -n vmnic4
NIC statistics for vmnic4
Packets received: 4822791
Packets sent: 13
Bytes received: 660278761
Bytes sent: 832
Receive packets dropped: 0
Transmit packets dropped: 0
Total receive errors: 0
Receive length errors: 0
Receive over errors: 0
Receive CRC errors: 0
Receive frame errors: 0
Receive FIFO errors: 0
Receive missed errors: 0
Total transmit errors: 0
Transmit aborted errors: 0
Transmit carrier errors: 0
Transmit FIFO errors: 0
Transmit heartbeat errors: 0
Transmit window errors: 0
~ # esxcli network nic stats get -n vmnic5
NIC statistics for vmnic5
Packets received: 129866853
Packets sent: 43742076
Bytes received: 186885321654
Bytes sent: 51537911982
Receive packets dropped: 53669
Transmit packets dropped: 0
Total receive errors: 8
Receive length errors: 0
Receive over errors: 0
Receive CRC errors: 8
Receive frame errors: 0
Receive FIFO errors: 0
Receive missed errors: 0
Total transmit errors: 0
Transmit aborted errors: 0
Transmit carrier errors: 0
Transmit FIFO errors: 0
Transmit heartbeat errors: 0
Transmit window errors: 0

I need a recommended way of recovering from Bus Off errors

I have write problems when a UUT is instructed to reset. When the UUT in the reset state I get Error Passive warnings and Bus Off errors after attempting to write extended CAN messages using the Frame API.
In brief the test goes like this,
1. I send extended message 0x500 with 8 data bytes containing information to tell the UUT to go into reset.
2. I wait 400ms hopeing that the UUT get's at least 1 of the 3 possible messages. It always does and does a reset.
3. I then MUST send message 0x500 with updated data telling the UUT to come out of reset.
Problem is the write fails with a Bus Off error (can't remember the error code as I am typing this at home). I can get this to work in a brute force kind of way by repeating these steps below several times in a loop,
1. reopen the network object
2. reopen all perodic tx objects,
3. do a ncAction NC_OP_RESET on the network object,
4. do a ncAction NC_OP_RESET on all periodic tx objects,
5. do a ncAction NC_OP_START on the network object,
6. do a ncAction NC_OP_START on all the periodic tx objects,
(no warnings or errors so far from these calls allthough occasionally ends up with an exception and NI-CAN internal driver errors. I'm probably abusing the CAN standard and API with all the rapid opening and closing of all these handles and blindly ignoring errors.)
7. then do a ncWrite for all periodic tx objects (we usually get Error Passive warnings here, if the write is repeated it frequently gets a Bus Off error).
When the UUT (by chance in all honesty) gets the 0x500 message and comes out of reset, CAN operations are fine, but the problem lies when the UUT is in reset, I can't send the updated 0x500 message to tell it to come out of reset. I get randomly Error Passive errors and Bus Off errors.
Found out today this is what the UUT is doing when in reset (written in PDL),
while not received 0x500 with data indicating to come out of reset
   possibly repower most of the UUT circuitry (I can't remember)
   reset Bosch CANBUS controller circuitry on ASIC (takes 2us I'm told)
   do some unit reset processing, takes up to 100ms
wend
(yes, it resets the CANBUS controller roughly every 100ms!)
I need a sensible way of recovering from a Bus Off error and retry sending that 0x500 message again.
Any thoughts, comments, solutions?
Regards.

Hi Flump,
The idea here is that many CAN devices will "sleep" after some predetermined period of inactivity (not receiving a frame). In such cases, the device usually wakes up after seeing activity on the bus, where the amount of time it takes to go from the "sleep" state to an "active" state will inevitably vary from device to device. Well, suppose the controller on a CAN network sends a frame to a device which is "sleeping," and the device takes, for arguments sake, 10 seconds to "wake up" and become active again. By definition in the CAN standard, frames which are not acknowledged will be retransmitted. Also in the CAN standard is the requirement that a device or controller implement transmit and receive "error counters" in order that an "errant" device or controller can be "silenced" if it continues to generate errors. There are 3 basic error states, the last (worst) of which is the Bus Off Error State, which occurs when the error counter exceeds 255. Herein lies the problem; if a device takes a long time to wake up, then a controller will send, and subsequently resend, the frame while it attempts to communicate with the "sleeping" device. Since the controller's transmit error counter will increase by 8 for each frame which is sent and NOT acknowledged, and it will continue sending frames until acknowledged, the controller can actually reach a Bus Off Error state before the device fully "wakes up." This is usually undesirable, and can be prevented.
For more information about the CAN standard, see Appendix B of the NI-CAN Hardware and Software Manual linked in the Related Links section below.
The solution may be to send a single wake-up frame (just one time), then delay to allow the device to "wake-up," and then continue normal communication. It is important to realize that when a device "sleeps," it actually relies on the fact that a CAN controller will send frames multiple times. That is, the first frame received when a device is "sleeping" is NOT processed. The sudden voltage change on the bus caused by a frame transmission is sensed by a CAN device and will cause it to resume active operating conditions, but the frame which initiates the wakeup cannot be processed because the hardware was previously asleep (some of it literally not powered). Thus, if we have a mechanism for sending a single "wake-up" frame, and then delay until all devices (or at least the one we intend to communicate with) wake up, we can resume normal communications while knowing deterministically that subsequent commands should/will be processed by the device to which we wish to communicate.
In the NI-CAN API, the way to transmit a single frame - one time only - is by setting the Single Shot Transmit attribute to 1 (using the set attribute function: in LabVIEW use the ncSetAttr.vi for the Frame API and CAN Set Property.vi for the Channel API). For Frame API users, the Network Configuration object (programmed explicitly) can be used, where of course we must stop and start the task (using ncAction.vi) around the attribute setting. The sequence of events would generally be: Network Config (should have happened anyway at some point), Network Open, Stop, Set Attribute, Start, Write "wakeup frame," proceed with the program after sufficient delay. Please note that the required delay may be very small; the "10 second" wake-up time suggested for a device above is much much longer than a normal device's "wake-up period". Of course, the baud rate used on a given network will factor into how many frames can be sent by a controller in a given period, and therefore how fast a corresponding error counter will increment as a result of unacknowledged frames.
Attached is an example, which will write a single "wake-up" frame using the technique described above, where the write will take place when a "Wake-Up" button is clicked.
Is this what you are looking for?
AdamB
Message Edited by AdamB on 12-12-2006 04:47 AM
Applications Engineering Team Leader | National Instruments | UK & Ireland
Attachments:
SendSingleWakeUpFrame.vi ‏73 KB

Task Sequence has failed with error code: 0x80070570

I've created task sequence for Windows XP OS Deployment. WinPE boot image loads successfully, Partitions are formatted successfully too. But during "Applying image 1 from volume C:\" I receive following error:
Task Sequence: My_task_sequence_name has failed with error code: 0x80070570.
What I need to do? Any ideas? (My computer has following details: ASUS P5KSE motherboard, Core 2 Duo, SATA HDD, Atheros L1 adapter)

No, a build and capture task sequence automates the build of the image removing any and all human intervention so that rebuilding or refreshing an image becomes a simple matter. Building images by actually manually installing Windows is anti-IT.
File corruption can be caused by many, many things; e.g., anti-virus, physical disk errors, network transmit errors, etc.
Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

CSS FLOWMGR ERROR

Good day!
Often in log of my CSS 11503 is appeared next error messages:
APR 3 23:18:05 1/1 113661 FLOWMGR-6:
FM_ReTransTimeout: Re-Transmit timeout ERROR
APR 3 23:18:05 1/1 113662 FLOWMGR-6:
FM_Tcp: Handling generic FMTCP flowRe-Transmit ERROR
APR 3 23:18:05 1/1 113663 FLOWMGR-6:
FM_ReTransTimeout: Re-Transmit timeout ERROR
APR 3 23:18:05 1/1 113664 FLOWMGR-6:
FM_Tcp: Handling generic FMTCP flowRe-Transmit ERROR
APR 3 23:41:15 2/1 239613 FLOWMGR-6:
FM_ReTransTimeout: Re-Transmit timeout ERROR
APR 3 23:41:15 2/1 239614 FLOWMGR-6:
FM_Tcp: Handling generic FMTCP flowRe-Transmit ERROR
APR 3 23:41:15 2/1 239615 FLOWMGR-6:
FM_ReTransTimeout: Re-Transmit timeout ERROR
APR 3 23:41:15 2/1 239616 FLOWMGR-6:
FM_Tcp: Handling generic FMTCP flowRe-Transmit ERROR
What does it mean? How I can see about what kind of flows there are these messages? Is it serious error or I can ignore it?
Thanks!

this is a level 6 message [info], so you can ignore it.
If this was serious you would get a level 1 or 2 or 3.
You should set your logging level back to 4.
Too much logging is useless.
It can only create confusion.
Gilles.

Satellite L500 - Lost wireless connection

My Satellite L500 recently lost wireless connection. I looked up the Realtek wireless device in Device Manager, and it says the device is working properly. I have tried using "ping 192.168.1.1" to reach the router, and I get "Transmit error - general failure".
Any ideas?

Hi buddy,
And now does Windows recognize some WLAN networks in range? Your posting lost wireless connection is not very useful
You should try a WLAN driver update that you can download on official Toshiba page:
http://aps2.toshiba-tro.de/wlan/
If you still cannot find or connect to WLAN networks disable the WLAN power saving mode in Windows power profiles. You have to set it to maximum performance.

IDSM CPU 1 High Probleme

Hi everyone.
My name is wan tae kim in korea.
I have the question to idsm problem.
Is using idsm by ips mode in our customer.
Cpu1 will be continued in 100% state but does not know cause.
Is used by Inline mode but need Configuration verification.
I want to receive steers of many persons.
I ask counsel whether take Configuration.
IDSM Configuration:
service interface
exit
service authentication
exit
service event-action-rules rules0
overrides deny-packet-inline
override-item-status Enabled
risk-rating-range 90-100
exit
general
global-overrides-status Enabled
exit
exit
service host
network-settings
host-ip x.x.x.x/25,x.x.x.x.
host-name R_Core2_IDSM
telnet-option enabled
access-list x.x.x.0/24
access-list x.x.x.0/24
access-list x.x.x.0/24
access-list x.x.x.x/32
exit
time-zone-settings
offset 540
standard-time-zone-name GMT+09:00
exit
exit
service logger
exit
service network-access
exit
service notification
exit
service signature-definition sig0
signatures 2152 0
engine flood-host
rate 100
exit
exit
signatures 5684 2
alert-severity medium
exit
signatures 13003 0
engine traffic-anomaly
event-action produce-alert
exit
exit
signatures 13003 1
engine traffic-anomaly
event-action produce-alert
exit
exit
exit
service ssh-known-hosts
exit
service trusted-certificates
exit
service web-server
exit
service anomaly-detection ad0
exit
service external-product-interface
exit
service analysis-engine
virtual-sensor vs0
description default virtual sensor
physical-interface GigabitEthernet0/7
physical-interface GigabitEthernet0/8
exit
switch Configuration:
monitor session 3 source vlan 305
monitor session 3 destination intrusion-detection-module 9 data-port 1
Thank you.

Hi Wan Tae Kim,
The 100% CPU utilization is actually expected behavior and should not be cause for concern. To confirm the actual load on the sensor you can use the command:
show stat virt
and check the line "Processing Load Percentage ="
Additionally, you can check the output of:
show int
and verify that the number of "Receive FIFO Overruns" is low/zero, indicating that the sensor is able to keep up with the rate of traffic being sent to it via your SPAN session.
Here are examples of both outputs with the important lines in bold
sensor# show stat virt
Virtual Sensor Statistics
   Statistics for Virtual Sensor vs0
      Name of current Signature-Defintion instance = sig0
      Name of current Event-Action-Rules instance = rules0
      List of interfaces monitored by this virtual sensor = InterfacePair0 subinterface 0,GigabitEthernet0/3 subinterface 0
      General Statistics for this Virtual Sensor
         Number of seconds since a reset of the statistics = 1627117
         MemoryAlloPercent = 31
         MemoryUsedPercent = 31
         MemoryMaxCapacity = 1800000
         MemoryMaxHighUsed = 634880
         MemoryCurrentAllo = 566529
         MemoryCurrentUsed = 561597
         Processing Load Percentage = 1
         Total packets processed since reset = 7875642
         Total IP packets processed since reset = 3782287
         Total IPv4 packets processed since reset = 3755319
         Total IPv6 packets processed since reset = 26968
         Total IPv6 AH packets processed since reset = 0
         Total IPv6 ESP packets processed since reset = 0
         Total IPv6 Fragment packets processed since reset = 0
         Total IPv6 Routing Header packets processed since reset = 0
         Total IPv6 ICMP packets processed since reset = 94
         Total packets that were not IP processed since reset = 4093355
         Total TCP packets processed since reset = 204508
         Total UDP packets processed since reset = 2252490
         Total ICMP packets processed since reset = 14688
         Total packets that were not TCP, UDP, or ICMP processed since reset = 1310601
         Total ARP packets processed since reset = 2923053
         Total ISL encapsulated packets processed since reset = 0
         Total 802.1q encapsulated packets processed since reset = 0
         Total packets with bad IP checksums processed since reset = 0
         Total packets with bad layer 4 checksums processed since reset = 268
         Total number of bytes processed since reset = 1029553988
         The rate of packets per second since reset = 4
         The rate of bytes per second since reset = 632
         The average bytes per packet since reset = 130
      Denied Address Information
         Number of Active Denied Attackers = 0
         Number of Denied Attackers Inserted = 0
         Number of Denied Attacker Victim Pairs Inserted = 0
         Number of Denied Attacker Service Pairs Inserted = 0
         Number of Denied Attackers Total Hits = 0
         Number of times max-denied-attackers limited creation of new entry = 0
         Number of exec Clear commands during uptime = 0
      Denied Attackers and hit count for each.
      Denied Attackers with percent denied and hit count for each.
sensor# show int
Interface Statistics
   Total Packets Received = 29934896
   Total Bytes Received = 4010927826
   Missed Packet Percentage = 0
   Current Bypass Mode = Auto_off
MAC statistics from interface GigabitEthernet0/0
   Interface function = Sensing interface
   Description = Connected to Attacker Switch
   Media Type = TX
   Default Vlan = 0
   Inline Mode = Paired with interface GigabitEthernet0/1
   Pair Status = Up
   Hardware Bypass Capable = No
   Hardware Bypass Paired = N/A
   Link Status = Up
   Admin Enabled Status = Enabled
   Link Speed = Auto_100
   Link Duplex = Auto_Full
   Missed Packet Percentage = 0
   Total Packets Received = 4095925
   Total Bytes Received = 298897396
   Total Multicast Packets Received = 3431616
   Total Broadcast Packets Received = 0
   Total Jumbo Packets Received = 0
   Total Undersize Packets Received = 0
   Total Receive Errors = 0
   Total Receive FIFO Overruns = 0
   Total Packets Transmitted = 664379
   Total Bytes Transmitted = 42520256
   Total Multicast Packets Transmitted = 0
   Total Broadcast Packets Transmitted = 0
   Total Jumbo Packets Transmitted = 0
   Total Undersize Packets Transmitted = 0
   Total Transmit Errors = 0
Best Regards,
Justin

IDSM-2(5.0)inline mode- Pair Status=down??

I have trouble with configuring idsm-2 inline mode(5.0).
it seems that traffic doesn't go through idsm.
I chechked it on command: sh interfac gi0/7(idsm mode)
the 'pair Status=down'(below) shows that, i think.
moreover, total packet received doesn't increase.
how do i solve it?
Please help!
xxsystems# sh int gigabitEthernet0/7
MAC statistics from interface GigabitEthernet0/7
Media Type = backplane
Missed Packet Percentage = 0
Inline Mode = Paired with interface GigabitEthernet0/8
Pair Status = Down
Link Status = Up
Link Speed = Auto_1000
Link Duplex = Auto_Full
Total Packets Received = 38
Total Bytes Received = 2584
Total Multicast Packets Received = 38
Total Broadcast Packets Received = 0
Total Jumbo Packets Received = 0
Total Undersize Packets Received = 0
Total Receive Errors = 0
Total Receive FIFO Overruns = 0
Total Packets Transmitted = 12
Total Bytes Transmitted = 1152
Total Multicast Packets Transmitted = 0
Total Broadcast Packets Transmitted = 12
Total Jumbo Packets Transmitted = 0
Total Undersize Packets Transmitted = 0
Total Transmit Errors = 0
Total Transmit FIFO Overruns = 0

You can only pair interfaces on your sensor if your sensor is capable of inline monitoring.
http://www.cisco.com/en/US/products/sw/secursw/ps2113/products_installation_and_configuration_guide_chapter09186a00803eb069.html

Functional Location measuring point UOM not displayed on mobile device

Dear Experts,
I am running SAP Work Manager 6.0 with Agentry Server v6.1.4.179 and SAP ECC 6.0 with SMFND 610_700 SP01 and SMERP 610_700 SP01 and Agentry Client v6.1.3.10200 on an iPhone.
When I display from the iPhone the "Valve Water Flow in m3/h" counter, the UOM is represented as "***"
The "Pump Bearing Oil Level in mm" counter UOM is displayed properly.
The Measuring Points are associated to a FLOC. A work Order with this FLOC has been transmitted to mobile device.
Thanks for your help.
Didier.
Reading Points definition in SAP:
Reading Points on iPhone:
Tags edited by: Michael Appleby

Hi Bill,
Thanks for your reply. In fact , I have the same problem with the WPF client and if I enter a reading value, I will get the following error message during the transmit. "Unit *** is not created in language EN"
WPF client display:
Transmit error:
Agentry log:
readDataObjectMeasuringPoint::begin
BAPI::begin
User::getString::begin
User::getString::Property: transaction.point = 26
User::getString::begin
User::getString::Property: transaction.shortText =
User::getString::begin
User::getString::Property: transaction.reading = 0
User::getString::begin
User::getString::Property: transaction.UOM = ***
User::getString::begin
User::getString::Property: transaction.referenceObjectNumber = OR000004000293
User::getString::begin
User::getString::Property: transaction.prevCodeGroup =
User::getString::begin
User::getString::Property: transaction.prevCatalogType =
User::getString::begin
User::getString::Property: transaction.ValuationCode =
User::getString::begin
User::getString::Property: transaction.isCounter = False
User::getString::begin
User::getString::Property: transaction.codeTextOnly not found, returning empty s
tring
User::getString::Property: transaction.codeTextOnly =
User::getString::begin
User::getString::Property: transaction.description = Pump Bearing Temperature
User::getString::begin
User::getString::Property: transaction.skipReading = False
User::getString::begin
User::getString::Property: transaction.status not found, returning empty string
User::getString::Property: transaction.status =
User::getString::begin
User::getString::Property: transaction.IsNotRead = False
User::getString::begin
User::getString::Property: transaction.tmpReading not found, returning empty str
ing
User::getString::Property: transaction.tmpReading =
User::getString::begin
User::getString::Property: transaction.CodeGroup not found, returning empty stri
ng
User::getString::Property: transaction.CodeGroup =
User::getString::begin
User::getString::Property: transaction.code not found, returning empty string
User::getString::Property: transaction.code =
readDataObjectMeasuringPoint::SkipReading=False
User::getString::begin
User::getString::Property: transaction.point = 26
User::getString::begin
User::getString::Property: transaction.shortText =
User::getString::begin
User::getString::Property: transaction.reading = 0
User::getString::begin
User::getString::Property: transaction.UOM = ***
User::getString::begin
User::getString::Property: transaction.referenceObjectNumber = OR000004000293
User::getString::begin
User::getString::Property: transaction.prevCodeGroup =
User::getString::begin
User::getString::Property: transaction.prevCatalogType =
User::getString::begin
User::getString::Property: transaction.ValuationCode =
User::getString::begin
User::getString::Property: transaction.isCounter = False
User::getString::begin
User::getString::Property: transaction.codeTextOnly not found, returning empty s
tring
User::getString::Property: transaction.codeTextOnly =
User::getString::begin
User::getString::Property: transaction.description = Pump Bearing Temperature
User::getString::begin
User::getString::Property: transaction.skipReading = False
User::getString::begin
User::getString::Property: transaction.status not found, returning empty string
User::getString::Property: transaction.status =
User::getString::begin
User::getString::Property: transaction.IsNotRead = False
User::getString::begin
User::getString::Property: transaction.tmpReading not found, returning empty str
ing
User::getString::Property: transaction.tmpReading =
User::getString::begin
User::getString::Property: transaction.CodeGroup not found, returning empty stri
ng
User::getString::Property: transaction.CodeGroup =
User::getString::begin
User::getString::Property: transaction.code not found, returning empty string
User::getString::Property: transaction.code =
create::/SMERP/PM_DOMEASUREMENTDOC_CRT Connection ID: com.sap.mw.jco.JCO$Client@
42499d6d
create::Function /SMERP/PM_DOMEASUREMENTDOC_CRT created
setImportParameters::TIMESTAMP_FROM_MOBILE=20140701214858
setImportParameters::COMMIT_WAIT=X
setImportParameters::MOBILE_USER=MJONES
setImportParameters::USER_GUID=005056913EE61EE3B5A27E3E2BC46F0D
setImportParameters::MIDDLEWARE_CALL=X
setParameters::begin
setParameters::POINT=26
setParameters::IDATE=20140701
setParameters::ITIME=172024
setParameters::MDTXT=
setParameters::READR=MJONES
setParameters::RECDV=0
setParameters::RECDU=***
setParameters::RECDVI=X
setParameters::CODGR=
setParameters::VLCOD=
setParameters::CODCT=
setParameters::IV_WORK_ORDER_OBJECTNR=OR000004000293
execute::::MJONES::before BAPI execute: /SMERP/PM_DOMEASUREMENTDOC_CRT
User::rethrowException::begin
User::rethrowException::Exception caught: Unit *** is not created in language EN

%AMDP2_FE-5-LATECOLL: FastEthernet0/0 transmit error

Similar Messages

Maybe you are looking for