trunk port to other switch just dies

I have a cisco 3750G switch that for some strange reason, all of a sudden my trunk port, that is the link to the other switch just stopped working.
I have restarted the switch, works fine for a few hours and then shut off again.  I don't get any errors in the logs, just dies, any idea how to troubleshoot?
DanNetwork EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wayne88Commented:
How old is the switch?  I had a Cisco 2950 - 48 port switch that would slow down traffic then eventually freeze (all lights blinks).   The only way to get out of it was to power reset.  Went back in and no error code.  Gave up and replaced the almost decade old switch.  Maybe it's time for a new switch as well in your case.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DanNetwork EngineerAuthor Commented:
We bought all our switches used, it’s from 2011.  I have another one, exactly the same, I will replace it tomorrow, just wasn’t sure I’d its a hardware issue or some other network issue, it’s just I haven’t made any network changes for months.
0
aleghartCommented:
sh post

Open in new window


Look for things that failed, like:
POST: Inline Power Controller Tests : Begin
POST: Inline Power Controller Tests : End, Status Failed

Open in new window

0
Prepare for an Exciting Career in Cybersecurity

Help prevent cyber-threats and provide solutions to safeguard our global digital economy. Earn your MS in Cybersecurity. WGU’s MSCSIA degree program curriculum features two internationally recognized certifications from the EC-Council at no additional time or cost.

Craig BeckCommented:
What shows in the log when the trunk goes down?
0
DanNetwork EngineerAuthor Commented:
I did a show post and everything is passed, no failed.
0
DanNetwork EngineerAuthor Commented:
oh wait, this is on the replacement switch, I have to start up the old one and check it
0
DanNetwork EngineerAuthor Commented:
just did the show post on the old switch, and it's all passed as well.
0
DanNetwork EngineerAuthor Commented:
I've added the switch in my test bench, so I'll wait to see when it goes down again, to look at the logs
0
DanNetwork EngineerAuthor Commented:
So I looked through the log and the clock was wrong, so I fixed that, but I don't see anything in there that shows anything about the port going down.
0
Wayne88Commented:
You may not be able to see it if the electronic components are deteriorating as in my case.  You will just know when it's not functioning correctly.  Btw, have you tried upgrading the firmware?
0
DanNetwork EngineerAuthor Commented:
I bought  most of my switches last year, used, and I upgraded the firmware to a newer v 15 firmware.  All of the 3750G switches are on the same firmware.
0
Wayne88Commented:
Do you have any special configuration on the switch (VLANs)?  If not, try resetting the switch to factory default then test again.  If you do then you may have to export the settings first then reset then import the configuration file back.
0
DanNetwork EngineerAuthor Commented:
I can try that, for now, I have the switch up and running on my test work bench, connected to the network and I'm using my PRTG to ping the port continuously so I can see when it goes down.  So far, it's been 2 days and it has not went down yet.  I replaced the switch last Thursday, so the other switch so far has been good, it hasn't went down yet.
0
Wayne88Commented:
The Cisco switch that I had initially wouldn't show any symptoms of problems when on a test bench then slowly deteriorate when under load.  It got worse over time to the point that it would freeze even on a test bench with no load.
0
DanNetwork EngineerAuthor Commented:
Interesting, thanks for the info, as it's been running for 3 days now with no issues.  Maybe it's time to toss it.
1
DanNetwork EngineerAuthor Commented:
here's what the logs show, which doesn't seem to show anything really helpful to me, besides the last date, the dates are wrong.

*Mar  1 00:02:38.829: %STACKMGR-4-SWITCH_ADDED: Switch 1 has been ADDED to the stack
*Mar  1 00:02:40.390: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
*Mar  1 00:02:42.697: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
*Mar  1 00:02:44.299: %DC-4-FILE_OPEN_WARNING: Not able to open flash:/dc_profile_dir/dc_default_profiles.txt
*Mar  1 00:02:44.299: %DC-6-DEFAULT_INIT_INFO: Default Profiles DB not loaded.
*Feb 28 17:02:46.656 pst: %SYS-6-CLOCKUPDATE: System clock has been updated from 00:02:46 UTC Mon Mar 1 1993 to 17:02:46 pst Sun Feb 28 1993, configured from console by console.
*Feb 28 17:02:46.882 pst: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 192.168.100.135 port 0 CLI Request Triggered
*Feb 28 17:02:46.950 pst: %SYS-5-CONFIG_I: Configured from memory by console
*Feb 28 17:02:47.084 pst: %STACKMGR-5-SWITCH_READY: Switch 1 is READY
*Feb 28 17:02:47.084 pst: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 1 Switch 1 has changed to state DOWN
*Feb 28 17:02:47.084 pst: %STACKMGR-4-STACK_LINK_CHANGE: Stack Port 2 Switch 1 has changed to state DOWN
*Feb 28 17:02:47.554 pst: %STACKMGR-5-MASTER_READY: Master Switch 1 is READY
*Feb 28 17:02:48.476 pst: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C3750 Software (C3750-IPBASEK9-M), Version 15.0(2)SE10a, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Thu 03-Nov-16 14:17 by prod_rel_team
*Feb 28 17:02:48.501 pst: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Feb 28 17:02:48.535 pst: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 192.168.100.135 port 514 started - CLI initiated
*Feb 28 17:02:52.922 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28, changed state to up
*Feb 28 17:02:53.954 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/28, changed state to up
*Feb 28 17:03:20.949 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
*Feb 28 17:03:22.568 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
*Feb 28 17:03:23.557 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/28, changed state to down
*Feb 28 17:03:26.577 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/28, changed state to up
*Feb 28 17:03:55.635 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
May 23 10:40:39.921 pst: %SYS-5-CONFIG_I: Configured from console by admin on vty0 (192.168.102.10)
0
Wayne88Commented:
Hi Dan, yes it doesn't show much other than configuration changes.  Unfortunately with deteriorating electronic parts the log isn't helpful.
0
Craig BeckCommented:
I doubt it's deteriorating electronics causing a trunk to go down. Just keep monitoring and grab the logs when it fails and we'll see what's what.

Can you get logs from the other end of the trunk link too?
0
Wayne88Commented:
You can keep checking the log but if it's an electronic failure it's very highly unlikely you will see it in the log.

Also, if he already tried resetting the switch to factory default and reconfigure it with the same symptoms reappearing then it sounded like the hardware itself is bad.  Unless if the appliance at the other end of the connection is faulty.
0
Craig BeckCommented:
There can be a number of reasons why a trunk goes down but if it was electrical I would not expect a logical entity to fail while everything else appears to work ok.
0
Wayne88Commented:
Disagree, if it's an electronic component failure then it's most likely to affect the whole appliance.  As he stated (48 port switch that would slow down traffic then eventually freeze (all lights blinks).

It's highly unlikely to have just one port (the trunk port) go bad than say a leaking capacitor (for example) affecting the performance of the whole appliance.
0
DanNetwork EngineerAuthor Commented:
Here's the log from the other switch, but I don't know why it only has the last 2 days, shouldn't it keep at least a week or more?
This log is useless as well.  It doesn't state why a port goes down, only that it went down.


No Inactive Message Discriminator.


    Console logging: level debugging, 5395 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging:  level debugging, 5395 messages logged, xml disabled,
                     filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    File logging: disabled
    Persistent logging: disabled

No active filter modules.

    Trap logging: level informational, 5621 message lines logged
        Logging to 192.168.100.135  (udp port 514,  audit disabled,
              authentication disabled, encryption disabled, link up),
              5621 message lines logged,
              0 message lines rate-limited,
              0 message lines dropped-by-MD,
              xml disabled, sequence number disabled
              filtering disabled

Log Buffer (4096 bytes):
EPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
May 22 18:21:07.008 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
May 22 18:21:08.006 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to down
May 22 18:21:10.154 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to up
May 22 18:21:11.169 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
May 23 01:34:40.714 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
May 23 01:34:41.712 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to down
May 23 01:34:44.053 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to up
May 23 01:34:45.059 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
May 23 01:37:05.998 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
May 23 01:37:07.995 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
May 23 03:59:26.531 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
May 23 03:59:27.529 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to down
May 23 03:59:29.911 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to up
May 23 03:59:30.918 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
May 23 04:01:52.896 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
May 23 04:01:54.901 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
May 23 07:27:52.689 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/5, changed state to down
May 23 07:27:53.687 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to down
May 23 07:58:53.072 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to up
May 23 07:58:54.078 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/5, changed state to up
May 23 07:59:12.181 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/5, changed state to down
May 23 07:59:13.179 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to down
May 23 07:59:24.286 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to up
May 23 07:59:25.293 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/5, changed state to up
May 23 09:45:59.250 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
May 23 09:46:00.248 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to down
May 23 09:46:03.142 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to up
May 23 09:46:04.149 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
May 23 10:01:55.037 pst: %SYS-3-CPUHOG: Task is running for (2098)msecs, more than (2000)msecs (3/3),process = SNMP ENGINE.
-Traceback= 1731390 1731384 18B4058 2912A74 28E66B0 28D7018 2901DE0 1B9774C 1B8E1D8
May 23 10:01:55.238 pst: %SNMP-3-CPUHOG: Processing GetNext of lldpRemEntry.6
May 23 11:46:56.472 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to down
May 23 11:46:57.470 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to down
May 23 11:46:59.601 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/26, changed state to up
May 23 11:47:00.608 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/26, changed state to up
May 23 11:50:41.615 pst: %SYS-3-CPUHOG: Task is running for (2097)msecs, more than (2000)msecs (4/3),process = SNMP ENGINE.
-Traceback= 1731350 1731348 18B5D68 18B4058 2912A74 28E66B0 28D7018 2901DE0 1B9774C 1B8E1D8
May 23 11:50:41.800 pst: %SNMP-3-CPUHOG: Processing GetNext of lldpRemEntry.6
w_whub_.39#
w_whub_.39#
w_whub_.39#
0
Craig BeckCommented:
Wayne, I can't ever see Dan say that.

Re-read what I said then re-read what you said.

I'm saying that an electrical issue would affect the whole switch, not just a logical interface. You're agreed on that? So there's no evidence to suggest that the whole switch has a problem - just the trunk.

@Dan - you need to put it all back as it was, monitor until it happens again, then grab logs from both ends. Also share your configs. This will either be a config issue, a cable issue or a code bug. I've seen a SNMP traceback in your log so I'd say bug as CPUHOG messages should not be seen during normal operation of the switch.
0
Wayne88Commented:
"Wayne, I can't ever see Dan say that."

My mistake, that was mine.

"I'm saying that an electrical issue would affect the whole switch, not just a logical interface. You're agreed on that?"

Most likely but not always.

" So there's no evidence to suggest that the whole switch has a problem - just the trunk. "

Again, I have asked Dan to try factory resetting the switch meaning that any configuration will be set to default.  But if after doing so it's still a problem and hence how I narrowed down to either a bad switch or the problem is at the other end of the trunk link as I said earlier.

However, I am open for you to prove me wrong.  Let's see how you troubleshoot.
0
Craig BeckCommented:
I've said already there looks like a code bug which hogs the CPU. I'd look at a code upgrade to fix it and see what happens.
0
Wayne88Commented:
I am open to suggestions but now we're going down an interesting path and am not being argumentative just asking questions.

Wouldn't a code bug hogging the cpu affect the whole system not just the trunk port?  Also, if the router was reset already how would a code bug would be relevant?  Otherwise the symptom would have been there from day 1.  I am just not seeing it.

But sure, a firmware upgrade is definitely worth a shot if one is available.
0
Craig BeckCommented:
CPU being hogged may happen periodically and it could just be that the process maintaining the trunk is unable to run. It could be a number of things but, with respect, electrical faults are extremely unlikely to only cause a trunk to fail.

I too am open to suggestions but I'm basing my estimation based on likelihood and past experience. It's usually bad config or cabling that causes these issues but code can contribute. I thi k we all agree that code bugs can cause spurious issues and aren't always predictable enough to make sense.
0
Wayne88Commented:
I am also basing my reasoning from past experience.  I am not so sure it's only the trunk that's failing and Dan will have to confirm.  How was this tested?  I think there's slowness across the switch but the trunk was suspected because one would automatically assume that's where the problem is when all the device connected to the ports are slow.

Thinking from programming perspective a bug causing CPU hog in a switch is highly unlikely.  Especially after a hard reset.  A question that kept getting left unanswered.  Again, if this was a bug causing CPU hog then the situation should have been there from day 1 Dan got the switch.  It doesn't just appear out of the blue.  The problem should be consistent otherwise it's not valid.
0
aleghartCommented:
Blown capacitor can start with degradation or only noticing when device is under load.  I just lost a 3750g PoE with a blown cap on the main board, not the PSU.  Sometimes, lights would die.  Sometimes blink.  Everything died at once, so I didn't have switchports, trunks, or console working.  Much easier to make the decision to crack it open.

I have also have issues on a 6509 blade that would take out one ASIC, killing some (but not all) ports on a blade.  Upon reboot, all ports might be OK.  Or, some other group of ports would be dead and the others OK.  Current workaround:  don't reboot, and put blue tape over the current "dead" ports, until we can source a new card.

If this is sitting on a test bench, there is likely not enough load or heat to generate a voltage problem with a degrading capacitor.

If the only thing monitored/used is a single trunk, then one might not notice a couple of other ports going south.

Also, did we ever determine how this trunk is connected?  SFP?  OM1?  Cat5?  I've had just as many SFPs go bad as full switches.

I know it can be frustrating.  That's why many people just toss the equipment and get a replacement.  Sometimes, it will save days or weeks of troubleshooting.  It's not the most technical method...but we toss phones and wireless access points for the same reason.  The cost of a replacement is cheaper than troubleshooting for X hours at $Y/hr + ill-will + downtime.
1
Craig BeckCommented:
Wayne your assumptions aren't correct. It may be some element of the config causing the CPUHOG to trigger, or an event that occurs. It's completely inaccurate to say that it would be visible even with a blank config.

Also, you're making assumptions. I don't see any evidence to suggest that anything other than the trunk failure is the problem here. I've not heard any mention of slowness or other issues and we still don't know what the config is at each end. It could be as simple as that.

Alan, so electrical faults have considerable and obvious consequences. One single logical trunk would not fail due to a capacitor failing.

There's a number of things to check before condemning the switch. As Alan says, it could be a cable, SFP, etc, or even noise on a copper cable. Dumping the switch should be a last resort.
0
Wayne88Commented:
Agreed that dumping the switch is the last resort but nope, I don't agree with your analysis.  

" It may be some element of the config causing the CPUHOG to trigger, or an event that occurs."

So you think a CPU hog, a spike in CPU activity will not affect the operation of the entire appliance?  Nope, doesn't make sense.  

Let's agree to disagree as you're making a lot of assumptions as well and IMHO are illogical assumptions.  In fact, you still haven't been able to logically explain why the problem is only appearing now when Dan have owned the switch for over a year?

"There's a number of things to check before condemning the switch. As Alan says, it could be a cable, SFP, etc, or even noise on a copper cable. Dumping the switch should be a last resort."

Did Dan not swapped the switch and the problem went away?  What do you deduce from this action?  I am thinking we can eliminate the cabling and the appliance at the other end of the trunk port.

In any case, I will let you take over and monitor this thread but I will chime in if your deductive reasoning don't make sense.  Good luck!
0
aleghartCommented:
I didn't see how the trunk is connected, if an SFP was swapped or not.

Also, we have inheirited Cat5/5e cables that make 1000-full connections on one switch, but not another.

Or, gigabut trunk on one port, but fail to come up on another port on the same switch.

One could argue it's on the edge of some electrical tolerance...but swapping to a newer cable was easy.

So, I cut the questionable cable in half, and tossed it in the recycle bin.

Swapping is time-consuming, but a decent way to eliminate questions.
0
Craig BeckCommented:
Wayne, you're not doing well here.

"So you think a CPU hog, a spike in CPU activity will not affect the operation of the entire appliance?  Nope, doesn't make sense."

In some cases it doesn't. For example, some traffic is switched in hardware so CPU utilization has less bearing on it, whereas the switch responding to a ping, at the same time as high CPU utilization is apparent (for example), would show as latency or failure to respond.

Swapping the switch and testing for this short time proves little unless the problem was apparent immediately on the old switch. We already know it didn't happen straight away so it's simply not fair to say the original switch is definitely bust.

"Did Dan not swapped the switch and the problem went away?  What do you deduce from this action?  I am thinking we can eliminate the cabling and the appliance at the other end of the trunk port."

No, that's completely naive to assume. Swapping the switch involves what? Moving cables and maybe SFPs too. Are you saying it's not at all possible that a badly-seated cable or SFP could be the cause, or that wires can't suffer from poor terminations or loose wires? And again, it could be something at the other end. I'm guessing you haven't heard of errdisable recovery?

@Alan, I've asked for configs and logs when the issue occurs again, assuming the original switch is in-place.
0
Wayne88Commented:
Nope, you're grasping for straws.

You're making a lot of assumptions.  I did not say that the cause is an electronic failure only that I have been consistent in saying that if it was then the log is useless.  Anything is possible from bad cables to connection except for electronic failure right?

Let's just stop here Craig and you keep troubleshooting.  Let's help Dan get to the bottom of the problem.  I am very sure it will not be a bug causing CPU hog. Until then, please keep your statements and method of troubleshooting consistent and logical.
0
Craig BeckCommented:
Oh, Wayne. Look over at the points...

Anyway, my troubleshooting is completely logical.

You've based your whole argument on faulty hardware. In your first post you didn't suggest anything valuable in order to troubleshoot. You just said swap the switch.

The CPUHOG is a known bug so youre wrong on that point too.

Any assumptions I'm making are based on evidence provided and sound technical knowledge and experience. It's HIGHLY unlikely that bad hardware in the switch itself is causing the fault with a purely LOGICAL entity. What's your excuse? :-)

I agree though, let's help Dan. Lets give him some valuable troubleshooting assistance after the original switch is back in-situ and the configs have been provided.
0
Craig BeckCommented:
0
Wayne88Commented:
I didn't want to get long winded but thanks for the link which supported my points.  Actually you're wrong again.  My point to Dan was that if the hardware is going then the log will be of little help.

Now let's try to logically explain one of my questions of why do you think it could only affect the trunk AFTER a year using the info on the link you provided?  Please calm down, I meant no offense.  Just be logical and consistent with your train of thoughts.
0
Craig BeckCommented:
Wayne you're not making sense. How exactly did my link support your point that a CPUHOG isn't caused by a bug? It seems you're chopping and changing all the time.

I am calm. I'm just bewildered at your arguments.  You said a CPUHOG won't be caused by a bug and now you've seen clear evidence to prove you wrong you're saying I'm wrong again. I'm lost for words on that one.

If hardware is going the Cisco diagnostics often do highlight it. The POST will show detailed info. Yes, if a capacitor, for example, is on the way out it may not catch that exact failure, but again I'll ask...

Why would a component failure ONLY break a single logical entity? It makes no sense whatsoever.  As far as we know NOTHING else is breaking.

What does make sense is one of the following being the cause:

Bad config
Bad or poorly-connected cable
Bad SFP
Bad code
Network event

I know this because I do it day in, day out. I regularly work with Cisco TAC to resolve switching issues on all platforms.

As I've said time and time again, getting the configs for each end as well as logs when the issue occurs will reveal the problem if one of the above typical causes is apparent. I'm not trying to be obstructive or argumentative but it's not likely to be hardware based on the info given so far.
0
Wayne88Commented:
No you misunderstood.  I didn't agree that a bug causing a cpu hog is the problem.  You can scroll up and quote me if I said different.  I am willing to learn from you and I hope you're right with your analysis
0
Craig BeckCommented:
I didn't misunderstand. You said...

"I am very sure it will not be a bug causing CPU hog."

The link I gave categorically states that during normal operation of the device the CPUHOG is caused by a code bug most of the time. It is rare that it isn't.

We know that it is happening but can't see a reason why. That screams bug to me. In any event though we don't know if it is the cause of the issue or not but it is worth investigating. My advice would be to upgrade the code to the 15.0.2-SE11(MD) release regardless of other issues or not.

There is a known caveat with the version of code Dan curreny has on the switch...

"CSCuu33092
The switch experiences continuous traceback and CPU hog when you configure the scheduler max-task-time 500 command.

The workaround is to disable the scheduler configuration."

This is also worth looking at.
0
Wayne88Commented:
Ok , I am taking your points and after reading your links I am not seeing how it can affect just the trunk.  If you are going to assume that a bug is hogging the CPU it should also affect the operation of the whole switch.  The only time I can see that this is not true is if the CPU is a multicore and the bug is contained only to operate in one core and allowing all the other processes to use the rest of unaffected cores.  A highly unlikely scenario.

I am not arguing a bug causing a CPUHOG is not possible.  I am arguing the assumption that a CPUHOG can affect just one port.  Your link indicated that it will hog the entire CPU not limited to just one port

We have a few Cisco switch models in house and one did have bugs where the CPU was overloaded at one point but it affected the whole switch not just a port.
0
Craig BeckCommented:
It is entirely possible that the CPU being maxxed can cause one function to fail, especially if there's not much else configured.

Please don't confuse a port with a trunk. A port is a physical entity. A trunk is logical.

With respect, it doesn't sound like you know how a switch operates.
0
Wayne88Commented:
My question is still unanswered.  With respect it starting to look like you intentionally avoid my specific logical question and tip toeing with general answers.

You said "a trunk is logical".  So trunk will need to use shared system resources like the CPU and the memory to function.  Do you agree?
0
aleghartCommented:
Trunks bouncing is a common symptom of overloaded CPU.  The switchports controlled by ASICs will continue to switch in hardware without CPU use.

VLAN management, DHCP flooding, STP, broadcast storm...all things that can happen during a trunk up/down are also CPU-intensive.

Waiting for the OP to post more info seems the most logical, to me.

If more strange behavior shows up, this should show spikes up to 72 hours ago:

show processes cpu history
0
Wayne88Commented:
I was never against OP to post more info and do further investigation.  I simply had logical questions I was trying to get answers from Craig and I finally have a technical an he never went into details.  Now that I have a technical answer it makes logical sense. I am looking forward to see how this issues is troubleshot.
0
DanNetwork EngineerAuthor Commented:
Update.  So even with the new, replaced switch, as it's not new switch, it happened again. The port went down for 15 minutes and it came back up again by itself.   This is crazy.
So it happened in the middle of the night, around 5 am, and there's no body there at work.  I will post both of my configs from both switches, and do show logs from both switches and post those as well.  Not sure what else to do to troubleshoot, I guess I can replace the trans receivers on both sides, but I don't see how those can go bad?

Since I don't have Smartnet, I'm not sure how I can get another copy of the iOS?
0
DanNetwork EngineerAuthor Commented:
I just took some snapshots from my phone of the memory and processor utilization, same with the bandwidth, so it doesn't look like the problem was heavy load.  I'll upload the pictures as soon as I get into work Tuesday morning. I am using PRTG to monitor my network.
0
Craig BeckCommented:
Dan, will your logs go back far enough? Do you have syslog configured? If not, get a syslog server set up and point the switches at it.
0
DanNetwork EngineerAuthor Commented:
yes, I am using kiwi syslog, I went back since Thursday, which should be enough, since it happened over the weekend.
Here's all the files, let me know if you guys need anything else.
So the problem is happening on c_rack.38 switch, port 28, which is connected to the whub.39 switch on port 50.

Let me know if there's any other info I need to gather?

The memory seems to be high, but maybe that's normal.  The processor has been around 10%, and never higher.

whub cdpcrack cdpmemory 30 dayprocessor 30 dayping 2 dayAll-Kiwi-Syslog-Server-Events.csv
c_rack-config.txt
whub-config.txt
0
Craig BeckCommented:
Cheers, Dan.

A few things...

The CPUHOG is definitely a bug.
5/28/2018,10:01:55,Local7,Error,192.168.100.39,5777: May 28 10:01:54.893 pst: %SNMP-3-CPUHOG: Processing GetNext of lldpRemEntry.6
5/28/2018,10:01:55,Local7,Error,192.168.100.39,5776: -Traceback= 1A7B834 15D9F48 15D66F8 185479C 17A17B0 17A1758 17A7334 17A781C 17A1860 1731334 1731348 1731384 18B5D68 18B4058 2912A74 28E66B0
5/28/2018,10:01:55,Local7,Error,192.168.100.39,"5775: May 28 10:01:54.691 pst: %SYS-3-CPUHOG: Task is running for (2097)msecs, more than (2000)msecs (1/1),process = SNMP ENGINE."
There's a traceback in the log, so this is a problem, likely related to LLDP.  You should upgrade your code but appreciate you don't have a service contract.  You may be able to purchase a contract for a single switch to download the software, then you "could" install the same on all of your 3750s.


I can see a VLAN1 flapping issue in the log.
%SW_MATM-4-MACFLAP_NOTIF: Host 8489.ad99.4e2f in vlan 1 is flapping between port Gi1/0/51 and port Gi1/0/52
Without a network diagram and configs for other switches I can't say 100% why, but it's usually a loop somewhere.  Check for misconfigured etherchannels too.  This will be causing STP issues.

You have PVST+ configured at the c_rack switch but Rapid-PVST+ configured at the whub switch.  This is "ok" but you should run the same version of STP on all switches to help with convergence, etc.

Do:

spanning-tree mode rapid-pvst

...at all switches.


The trunk port at c_rack is configured for dynamic trunking.  Change this to match whub's port config.  This is misconfiguration which can cause trunks to drop.

Do:

interface GigabitEthernet0/28
 switchport trunk encapsulation dot1q
 switchport mode trunk


...at c_rack switch.


Give all that a whirl and see how it goes :-)
0
DanNetwork EngineerAuthor Commented:
I don't have any etherchannels anywhere. I'll check and fix the STP on these two swithces, and I'll check all of the rest as well.
0
DanNetwork EngineerAuthor Commented:
I have a script that I follow when I configure new switches so I don't forget, here's what I use, is this not good?

            a. in config mode:
            b. spanning-tree mode rapid-pvst
            c. Perform this on all the switches
                  1. Configure each port that connects to core with the following:
                        a. Int gi1/0/1  (use the correct interface)
                        b. Switch trunk encap dot1q   (if not recognized, ignore it, switch does not support ISL, only supports 802.1q)
                        c. Switch mode trunk
                        d. Switch nonegotiate
                                e. spanning-tree portfast default
0
aleghartCommented:
why not 'spanning portfast trunk'?

This means you have to be sure there are no possible connections that would cause loops.

I don't use portfast on trunks between switches specifically because there may be another path for resiliency.

I'll use it for trunks to a server, virtualization host, or small NAS/SAN.
0
DanNetwork EngineerAuthor Commented:
Not sure why I did that, are you saying the trunk option is better than the default?

Does that mean I need to touch each switch I have and configure each trunk port right?
0
aleghartCommented:
'spanning-tree portfast default' is a global command that turns on portfast on all non-trunking ports as the default setting.  Normally, portfast is off by default.

It's not used on the switchport individually.

And it doesn't affect trunk ports.
1
Craig BeckCommented:
How are you getting on, Dan?
0
DanNetwork EngineerAuthor Commented:
So it just happened again. it's been like 2 weeks where it ran fine, and today, the port just died, the trunk port.
The switch was still on, and all the other ports that were on had the lights on, so they were on.  
I unplugged the cable from the trunk port, waited 20 seconds and plugged it back in, and it never came back up.
I unplugged the cable from the trunk port again, and plugged it into another port, and the link came up.  Then I plugged the cable back into the original port, port 28, the trunk port, and the port came back up and it's been running since then.
I also first did a reload on the switch, and that did NOT cause the port to come back up, it was still down after the reload.
I did save the log from the switch, but the problem is, my laptop just crashed about an hour ago, and it's not booting., the system restore failed as well, so it's a bummer as i had a lot programs I have to reload, more time spent.

That almost makes me believe it's some kind of configuration issue, or something???
Here's the logs from all my swithces, it covers about 3 or 4 hours before the trunk port died, it's port 28 on switch 192.168.100.38
This switch is connected to switch 192.168.100.39 on port 50

I got to run for the day, but I'll post the config of both switches on Monday.


6/14/2018      12:09:55      Local7      Warning      192.168.100.39      10865: Jun 14 12:09:54.378 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:08:55      Local7      Warning      192.168.100.39      10864: Jun 14 12:08:54.374 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:07:55      Local7      Warning      192.168.100.39      10863: Jun 14 12:07:54.361 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:06:55      Local7      Warning      192.168.100.39      10862: Jun 14 12:06:54.349 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:05:55      Local7      Warning      192.168.100.39      10861: Jun 14 12:05:54.328 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:04:55      Local7      Warning      192.168.100.39      10860: Jun 14 12:04:54.315 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:03:55      Local7      Warning      192.168.100.39      10859: Jun 14 12:03:54.311 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:02:59      Local7      Error      192.168.100.128      Jun 14 12:02:59 netmon PRTG: [PRTG Network Monitor (NETMON)] c_rack_.38 PING 1 9 (Ping) Down ESCALATION  (Request timed out (ICMP error # 11010))
6/14/2018      12:02:55      Local7      Warning      192.168.100.39      10858: Jun 14 12:02:54.299 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:01:55      Local7      Warning      192.168.100.39      10857: Jun 14 12:01:54.278 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      12:00:55      Local7      Warning      192.168.100.39      10856: Jun 14 12:00:54.257 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:59:55      Local7      Warning      192.168.100.39      10855: Jun 14 11:59:54.261 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:59:12      Local7      Error      192.168.100.39      10854: Jun 14 11:59:11.345 pst: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/50, changed state to down
6/14/2018      11:59:11      Local7      Notice      192.168.100.39      10853: Jun 14 11:59:10.330 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/50, changed state to down
6/14/2018      11:58:55      Local7      Warning      192.168.100.39      10852: Jun 14 11:58:54.249 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:57:55      Local7      Warning      192.168.100.39      10851: Jun 14 11:57:54.228 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:57:48      Local7      Notice      192.168.100.45      8923: Jun 14 11:57:48.278 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/6, changed state to up
6/14/2018      11:57:48      Local7      Error      192.168.100.45      8922: Jun 14 11:57:47.277 pst: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/6, changed state to up
6/14/2018      11:57:45      Local7      Error      192.168.100.45      8921: Jun 14 11:57:44.844 pst: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/6, changed state to down
6/14/2018      11:57:44      Local7      Notice      192.168.100.45      8920: Jun 14 11:57:43.837 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/6, changed state to down
6/14/2018      11:56:55      Local7      Warning      192.168.100.39      10850: Jun 14 11:56:54.207 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:55:55      Local7      Warning      192.168.100.39      10849: Jun 14 11:55:54.211 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:54:55      Local7      Warning      192.168.100.39      10848: Jun 14 11:54:54.199 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:53:55      Local7      Warning      192.168.100.39      10847: Jun 14 11:53:54.170 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:52:55      Local7      Warning      192.168.100.39      10846: Jun 14 11:52:54.157 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:51:55      Local7      Warning      192.168.100.39      10845: Jun 14 11:51:54.136 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:50:55      Local7      Warning      192.168.100.39      10844: Jun 14 11:50:54.132 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:49:55      Local7      Warning      192.168.100.39      10843: Jun 14 11:49:54.120 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:48:55      Local7      Warning      192.168.100.39      10842: Jun 14 11:48:54.107 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:47:55      Local7      Warning      192.168.100.39      10841: Jun 14 11:47:54.086 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:46:55      Local7      Warning      192.168.100.39      10840: Jun 14 11:46:54.074 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:45:55      Local7      Warning      192.168.100.39      10839: Jun 14 11:45:54.070 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:44:55      Local7      Warning      192.168.100.39      10838: Jun 14 11:44:54.057 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:43:55      Local7      Warning      192.168.100.39      10837: Jun 14 11:43:54.028 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:42:55      Local7      Warning      192.168.100.39      10836: Jun 14 11:42:54.016 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:41:55      Local7      Warning      192.168.100.39      10835: Jun 14 11:41:54.020 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:40:55      Local7      Warning      192.168.100.39      10834: Jun 14 11:40:53.999 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:39:55      Local7      Warning      192.168.100.39      10833: Jun 14 11:39:53.978 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:38:55      Local7      Warning      192.168.100.39      10832: Jun 14 11:38:53.974 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:37:54      Local7      Warning      192.168.100.39      10831: Jun 14 11:37:53.970 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:36:54      Local7      Warning      192.168.100.39      10830: Jun 14 11:36:53.949 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:35:54      Local7      Warning      192.168.100.39      10829: Jun 14 11:35:53.945 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:34:54      Local7      Warning      192.168.100.39      10828: Jun 14 11:34:53.916 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:33:54      Local7      Warning      192.168.100.39      10827: Jun 14 11:33:53.912 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:32:54      Local7      Warning      192.168.100.39      10826: Jun 14 11:32:53.899 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:31:54      Local7      Warning      192.168.100.39      10825: Jun 14 11:31:53.887 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:30:54      Local7      Warning      192.168.100.39      10824: Jun 14 11:30:53.866 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:29:54      Local7      Warning      192.168.100.39      10823: Jun 14 11:29:53.862 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:28:54      Local7      Warning      192.168.100.39      10822: Jun 14 11:28:53.849 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:27:54      Local7      Warning      192.168.100.39      10821: Jun 14 11:27:53.828 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:26:54      Local7      Warning      192.168.100.39      10820: Jun 14 11:26:53.824 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:25:54      Local7      Warning      192.168.100.39      10819: Jun 14 11:25:53.812 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:24:54      Local7      Warning      192.168.100.39      10818: Jun 14 11:24:53.791 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:23:54      Local7      Warning      192.168.100.39      10817: Jun 14 11:23:53.770 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:22:54      Local7      Warning      192.168.100.39      10816: Jun 14 11:22:53.757 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:21:54      Local7      Warning      192.168.100.39      10815: Jun 14 11:21:53.745 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:20:54      Local7      Warning      192.168.100.39      10814: Jun 14 11:20:53.724 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:20:38      Local7      Notice      192.168.100.32      3261: Jun 14 11:20:38.253 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/42, changed state to up
6/14/2018      11:20:38      Local7      Error      192.168.100.32      3260: Jun 14 11:20:37.246 pst: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/42, changed state to up
6/14/2018      11:20:23      Local7      Error      192.168.100.32      3259: Jun 14 11:20:23.902 pst: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/42, changed state to down
6/14/2018      11:20:23      Local7      Notice      192.168.100.32      3258: Jun 14 11:20:22.901 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/42, changed state to down
6/14/2018      11:19:54      Local7      Warning      192.168.100.39      10813: Jun 14 11:19:53.720 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:18:54      Local7      Warning      192.168.100.39      10812: Jun 14 11:18:53.707 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:17:54      Local7      Warning      192.168.100.39      10811: Jun 14 11:17:53.687 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:16:54      Local7      Warning      192.168.100.39      10810: Jun 14 11:16:53.666 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:15:54      Local7      Warning      192.168.100.39      10809: Jun 14 11:15:53.653 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:14:54      Local7      Warning      192.168.100.39      10808: Jun 14 11:14:53.649 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:13:54      Local7      Warning      192.168.100.39      10807: Jun 14 11:13:53.637 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:12:54      Local7      Warning      192.168.100.39      10806: Jun 14 11:12:53.616 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:11:54      Local7      Warning      192.168.100.39      10805: Jun 14 11:11:53.603 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:10:54      Local7      Warning      192.168.100.39      10804: Jun 14 11:10:53.599 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:09:54      Local7      Warning      192.168.100.39      10803: Jun 14 11:09:53.586 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:08:54      Local7      Warning      192.168.100.39      10802: Jun 14 11:08:53.566 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:07:54      Local7      Warning      192.168.100.39      10801: Jun 14 11:07:53.545 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:06:54      Local7      Warning      192.168.100.39      10800: Jun 14 11:06:53.541 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:05:54      Local7      Warning      192.168.100.39      10799: Jun 14 11:05:53.528 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:04:54      Local7      Warning      192.168.100.39      10798: Jun 14 11:04:53.516 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:03:54      Local7      Warning      192.168.100.39      10797: Jun 14 11:03:53.495 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:02:54      Local7      Warning      192.168.100.39      10796: Jun 14 11:02:53.491 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:01:54      Local7      Warning      192.168.100.39      10795: Jun 14 11:01:53.478 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      11:00:54      Local7      Warning      192.168.100.39      10794: Jun 14 11:00:53.466 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:59:54      Local7      Warning      192.168.100.39      10793: Jun 14 10:59:53.445 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:58:54      Local7      Warning      192.168.100.39      10792: Jun 14 10:58:53.441 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:57:54      Local7      Warning      192.168.100.39      10791: Jun 14 10:57:53.428 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:56:54      Local7      Warning      192.168.100.39      10790: Jun 14 10:56:53.416 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:55:55      Local7      Warning      192.168.100.39      10789: Jun 14 10:55:54.385 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:54:55      Local7      Warning      192.168.100.39      10788: Jun 14 10:54:54.355 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:53:55      Local7      Warning      192.168.100.39      10787: Jun 14 10:53:54.342 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:52:55      Local7      Warning      192.168.100.39      10786: Jun 14 10:52:54.322 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:51:55      Local7      Warning      192.168.100.39      10785: Jun 14 10:51:54.309 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:50:55      Local7      Warning      192.168.100.39      10784: Jun 14 10:50:54.288 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:49:55      Local7      Warning      192.168.100.39      10783: Jun 14 10:49:54.275 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:48:55      Local7      Warning      192.168.100.39      10782: Jun 14 10:48:54.263 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:47:55      Local7      Warning      192.168.100.39      10781: Jun 14 10:47:54.242 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:46:55      Local7      Warning      192.168.100.39      10780: Jun 14 10:46:54.237 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:45:55      Local7      Warning      192.168.100.39      10779: Jun 14 10:45:54.233 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:44:55      Local7      Warning      192.168.100.39      10778: Jun 14 10:44:54.204 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:43:55      Local7      Warning      192.168.100.39      10777: Jun 14 10:43:54.183 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:42:55      Local7      Warning      192.168.100.39      10776: Jun 14 10:42:54.170 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:41:55      Local7      Warning      192.168.100.39      10775: Jun 14 10:41:54.158 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:40:55      Local7      Warning      192.168.100.39      10774: Jun 14 10:40:54.145 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:39:55      Local7      Warning      192.168.100.39      10773: Jun 14 10:39:54.124 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:38:55      Local7      Warning      192.168.100.39      10772: Jun 14 10:38:54.102 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:37:55      Local7      Warning      192.168.100.39      10771: Jun 14 10:37:54.090 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:36:55      Local7      Warning      192.168.100.39      10770: Jun 14 10:36:54.077 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:35:55      Local7      Warning      192.168.100.39      10769: Jun 14 10:35:54.065 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:34:55      Local7      Warning      192.168.100.39      10768: Jun 14 10:34:54.052 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:33:55      Local7      Warning      192.168.100.39      10767: Jun 14 10:33:54.048 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:32:55      Local7      Warning      192.168.100.39      10766: Jun 14 10:32:54.010 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:31:55      Local7      Warning      192.168.100.39      10765: Jun 14 10:31:53.989 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:30:54      Local7      Warning      192.168.100.39      10764: Jun 14 10:30:53.968 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:29:54      Local7      Warning      192.168.100.39      10763: Jun 14 10:29:53.964 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:28:54      Local7      Warning      192.168.100.39      10762: Jun 14 10:28:53.943 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:27:54      Local7      Warning      192.168.100.39      10761: Jun 14 10:27:53.939 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:26:54      Local7      Warning      192.168.100.39      10760: Jun 14 10:26:53.909 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:25:54      Local7      Warning      192.168.100.39      10759: Jun 14 10:25:53.905 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:24:54      Local7      Warning      192.168.100.39      10758: Jun 14 10:24:53.893 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:23:54      Local7      Warning      192.168.100.39      10757: Jun 14 10:23:53.880 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:22:54      Local7      Warning      192.168.100.39      10756: Jun 14 10:22:53.859 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:21:54      Local7      Warning      192.168.100.39      10755: Jun 14 10:21:53.863 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:20:54      Local7      Warning      192.168.100.39      10754: Jun 14 10:20:53.842 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:19:54      Local7      Warning      192.168.100.39      10753: Jun 14 10:19:53.821 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:18:54      Local7      Warning      192.168.100.39      10752: Jun 14 10:18:53.809 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:17:54      Local7      Warning      192.168.100.39      10751: Jun 14 10:17:53.788 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:16:54      Local7      Warning      192.168.100.39      10750: Jun 14 10:16:53.776 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:15:54      Local7      Warning      192.168.100.39      10749: Jun 14 10:15:53.763 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:15:07      Local7      Notice      192.168.100.42      84192: Jun 14 10:15:07.888 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      10:15:07      Local7      Error      192.168.100.42      84191: Jun 14 10:15:06.882 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      10:14:57      Local7      Error      192.168.100.42      84190: Jun 14 10:14:56.690 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      10:14:56      Local7      Notice      192.168.100.42      84189: Jun 14 10:14:55.692 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      10:14:54      Local7      Warning      192.168.100.39      10748: Jun 14 10:14:53.751 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:13:54      Local7      Warning      192.168.100.39      10747: Jun 14 10:13:53.738 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:12:54      Local7      Warning      192.168.100.39      10746: Jun 14 10:12:53.734 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:11:54      Local7      Warning      192.168.100.39      10745: Jun 14 10:11:53.722 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:10:54      Local7      Warning      192.168.100.39      10744: Jun 14 10:10:53.701 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:09:54      Local7      Warning      192.168.100.39      10743: Jun 14 10:09:53.689 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:08:54      Local7      Warning      192.168.100.39      10742: Jun 14 10:08:53.676 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:07:54      Local7      Warning      192.168.100.39      10741: Jun 14 10:07:53.672 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:06:54      Local7      Warning      192.168.100.39      10740: Jun 14 10:06:53.652 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:05:54      Local7      Warning      192.168.100.39      10739: Jun 14 10:05:53.639 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:04:54      Local7      Warning      192.168.100.39      10738: Jun 14 10:04:53.618 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:03:54      Local7      Warning      192.168.100.39      10737: Jun 14 10:03:53.614 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:02:54      Local7      Warning      192.168.100.39      10736: Jun 14 10:02:53.594 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:01:57      Local7      Warning      192.168.100.39      10735: Jun 14 10:01:56.199 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      10:01:56      Local7      Error      192.168.100.39      10734: Jun 14 10:01:55.418 pst: %SNMP-3-CPUHOG: Processing GetNext of lldpRemEntry.6
6/14/2018      10:01:56      Local7      Error      192.168.100.39      10733: -Traceback= 173132C 18B5D68 18B4058 2912A74 28E66B0 28D7018 2901DE0 1B9774C 1B8E1D8
6/14/2018      10:01:56      Local7      Error      192.168.100.39      10732: Jun 14 10:01:55.217 pst: %SYS-3-CPUHOG: Task is running for (2097)msecs, more than (2000)msecs (1/0),process = SNMP ENGINE.
6/14/2018      10:00:54      Local7      Warning      192.168.100.39      10731: Jun 14 10:00:53.544 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:59:54      Local7      Warning      192.168.100.39      10730: Jun 14 09:59:53.531 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:58:54      Local7      Warning      192.168.100.39      10729: Jun 14 09:58:53.511 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:57:54      Local7      Warning      192.168.100.39      10728: Jun 14 09:57:53.507 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:56:54      Local7      Warning      192.168.100.39      10727: Jun 14 09:56:53.469 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:55:54      Local7      Warning      192.168.100.39      10726: Jun 14 09:55:53.465 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:54:54      Local7      Warning      192.168.100.39      10725: Jun 14 09:54:53.453 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:53:54      Local7      Warning      192.168.100.39      10724: Jun 14 09:53:53.432 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:52:55      Local7      Warning      192.168.100.44      1 2015-04-03T00:59:19-08:00 192.168.100.44 STP - PORTSTATUS - %STP-W-PORTSTATUS: gi5: STP status Forwarding  
6/14/2018      9:52:55      Local7      Info      192.168.100.44      1 2015-04-03T00:59:19-08:00 192.168.100.44 LINK - Up - %LINK-I-Up:  gi5, aggregated (1)  
6/14/2018      9:52:54      Local7      Warning      192.168.100.39      10723: Jun 14 09:52:53.428 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:52:47      Local7      Warning      192.168.100.44      1 2015-04-03T00:59:11-08:00 192.168.100.44 LINK - Down - %LINK-W-Down:  gi5  
6/14/2018      9:52:46      Local7      Info      192.168.100.44      1 2015-04-03T00:59:10-08:00 192.168.100.44 LINK - Up - %LINK-I-Up:  gi5  
6/14/2018      9:51:54      Local7      Warning      192.168.100.39      10722: Jun 14 09:51:53.416 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:50:55      Local7      Warning      192.168.100.39      10721: Jun 14 09:50:54.402 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:49:55      Local7      Warning      192.168.100.39      10720: Jun 14 09:49:54.381 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:49:24      Local7      Notice      192.168.100.42      84188: Jun 14 09:49:24.269 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      9:49:24      Local7      Error      192.168.100.42      84187: Jun 14 09:49:23.262 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      9:49:13      Local7      Error      192.168.100.42      84186: Jun 14 09:49:12.593 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      9:49:12      Local7      Notice      192.168.100.42      84185: Jun 14 09:49:11.594 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      9:48:55      Local7      Warning      192.168.100.39      10719: Jun 14 09:48:54.377 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:47:55      Local7      Warning      192.168.100.39      10718: Jun 14 09:47:54.364 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:46:55      Local7      Warning      192.168.100.39      10717: Jun 14 09:46:54.360 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:45:55      Local7      Warning      192.168.100.39      10716: Jun 14 09:45:54.340 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:44:55      Local7      Warning      192.168.100.39      10715: Jun 14 09:44:54.327 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:43:55      Local7      Warning      192.168.100.39      10714: Jun 14 09:43:54.315 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:42:55      Local7      Warning      192.168.100.39      10713: Jun 14 09:42:54.294 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:41:55      Local7      Warning      192.168.100.39      10712: Jun 14 09:41:54.282 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:40:55      Local7      Warning      192.168.100.39      10711: Jun 14 09:40:54.269 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:39:55      Local7      Warning      192.168.100.39      10710: Jun 14 09:39:54.257 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:38:55      Local7      Warning      192.168.100.39      10709: Jun 14 09:38:54.253 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:37:55      Local7      Warning      192.168.100.39      10708: Jun 14 09:37:54.241 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:36:55      Local7      Warning      192.168.100.39      10707: Jun 14 09:36:54.228 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:35:55      Local7      Warning      192.168.100.39      10706: Jun 14 09:35:54.207 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:34:55      Local7      Warning      192.168.100.39      10705: Jun 14 09:34:54.195 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:33:55      Local7      Warning      192.168.100.39      10704: Jun 14 09:33:54.183 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:32:55      Local7      Warning      192.168.100.39      10703: Jun 14 09:32:54.179 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:31:55      Local7      Warning      192.168.100.39      10702: Jun 14 09:31:54.158 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:30:55      Local7      Warning      192.168.100.39      10701: Jun 14 09:30:54.146 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:29:55      Local7      Warning      192.168.100.39      10700: Jun 14 09:29:54.133 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:28:55      Local7      Warning      192.168.100.39      10699: Jun 14 09:28:54.129 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:27:55      Local7      Warning      192.168.100.39      10698: Jun 14 09:27:54.117 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:26:55      Local7      Warning      192.168.100.39      10697: Jun 14 09:26:54.088 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:25:55      Local7      Warning      192.168.100.39      10696: Jun 14 09:25:54.084 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:24:55      Local7      Warning      192.168.100.39      10695: Jun 14 09:24:54.055 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:23:55      Local7      Warning      192.168.100.39      10694: Jun 14 09:23:54.051 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:22:55      Local7      Warning      192.168.100.39      10693: Jun 14 09:22:54.038 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:21:55      Local7      Warning      192.168.100.39      10692: Jun 14 09:21:54.026 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:20:55      Local7      Warning      192.168.100.39      10691: Jun 14 09:20:54.005 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:19:55      Local7      Warning      192.168.100.39      10690: Jun 14 09:19:53.993 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:18:55      Local7      Warning      192.168.100.39      10689: Jun 14 09:18:53.980 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:17:54      Local7      Warning      192.168.100.39      10688: Jun 14 09:17:53.951 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:16:54      Local7      Warning      192.168.100.39      10687: Jun 14 09:16:53.939 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:15:54      Local7      Warning      192.168.100.39      10686: Jun 14 09:15:53.918 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:15:28      Local7      Notice      192.168.100.42      84184: Jun 14 09:15:28.151 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      9:15:28      Local7      Error      192.168.100.42      84183: Jun 14 09:15:27.144 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      9:15:17      Local7      Error      192.168.100.42      84182: Jun 14 09:15:16.382 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      9:15:16      Local7      Notice      192.168.100.42      84181: Jun 14 09:15:15.384 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      9:14:54      Local7      Warning      192.168.100.39      10685: Jun 14 09:14:53.906 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:13:54      Local7      Warning      192.168.100.39      10684: Jun 14 09:13:53.893 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:12:54      Local7      Warning      192.168.100.39      10683: Jun 14 09:12:53.881 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:11:54      Local7      Warning      192.168.100.39      10682: Jun 14 09:11:53.869 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:10:54      Local7      Warning      192.168.100.39      10681: Jun 14 09:10:53.856 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:09:54      Local7      Warning      192.168.100.39      10680: Jun 14 09:09:53.852 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:08:54      Local7      Warning      192.168.100.39      10679: Jun 14 09:08:53.832 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:07:54      Local7      Warning      192.168.100.39      10678: Jun 14 09:07:53.811 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:06:54      Local7      Warning      192.168.100.39      10677: Jun 14 09:06:53.798 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:05:54      Local7      Warning      192.168.100.39      10676: Jun 14 09:05:53.794 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:04:54      Local7      Warning      192.168.100.39      10675: Jun 14 09:04:53.782 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:03:54      Local7      Warning      192.168.100.39      10674: Jun 14 09:03:53.761 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:02:54      Local7      Warning      192.168.100.39      10673: Jun 14 09:02:53.749 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:01:54      Local7      Warning      192.168.100.39      10672: Jun 14 09:01:53.737 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      9:00:54      Local7      Warning      192.168.100.39      10671: Jun 14 09:00:53.733 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:59:54      Local7      Warning      192.168.100.39      10670: Jun 14 08:59:53.712 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:58:54      Local7      Warning      192.168.100.39      10669: Jun 14 08:58:53.691 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:57:54      Local7      Warning      192.168.100.39      10668: Jun 14 08:57:53.679 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:56:54      Local7      Warning      192.168.100.39      10667: Jun 14 08:56:53.666 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:56:42      Local7      Notice      192.168.100.42      84180: Jun 14 08:56:42.510 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      8:56:42      Local7      Error      192.168.100.42      84179: Jun 14 08:56:41.503 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      8:56:39      Local7      Error      192.168.100.42      84178: Jun 14 08:56:38.526 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      8:56:38      Local7      Notice      192.168.100.42      84177: Jun 14 08:56:37.527 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      8:56:36      Local7      Notice      192.168.100.42      84176: Jun 14 08:56:36.252 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      8:56:36      Local7      Error      192.168.100.42      84175: Jun 14 08:56:35.246 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      8:56:31      Local7      Error      192.168.100.42      84174: Jun 14 08:56:30.808 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      8:56:30      Local7      Notice      192.168.100.42      84173: Jun 14 08:56:29.810 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      8:55:54      Local7      Warning      192.168.100.39      10666: Jun 14 08:55:53.646 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:54:54      Local7      Warning      192.168.100.39      10665: Jun 14 08:54:53.633 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:53:54      Local7      Warning      192.168.100.39      10664: Jun 14 08:53:53.629 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:52:54      Local7      Warning      192.168.100.39      10663: Jun 14 08:52:53.609 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:51:54      Local7      Warning      192.168.100.39      10662: Jun 14 08:51:53.605 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:50:54      Local7      Warning      192.168.100.39      10661: Jun 14 08:50:53.584 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:49:54      Local7      Warning      192.168.100.39      10660: Jun 14 08:49:53.580 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:48:54      Local7      Warning      192.168.100.39      10659: Jun 14 08:48:53.559 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:47:54      Local7      Warning      192.168.100.39      10658: Jun 14 08:47:53.547 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:46:54      Local7      Warning      192.168.100.39      10657: Jun 14 08:46:53.543 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:45:54      Local7      Warning      192.168.100.39      10656: Jun 14 08:45:53.522 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:44:54      Local7      Warning      192.168.100.39      10655: Jun 14 08:44:53.510 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:43:54      Local7      Warning      192.168.100.39      10654: Jun 14 08:43:53.497 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:42:54      Local7      Warning      192.168.100.39      10653: Jun 14 08:42:53.485 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:41:54      Local7      Warning      192.168.100.39      10652: Jun 14 08:41:53.473 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:40:54      Local7      Warning      192.168.100.39      10651: Jun 14 08:40:53.460 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:39:54      Local7      Warning      192.168.100.39      10650: Jun 14 08:39:53.456 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:38:54      Local7      Warning      192.168.100.39      10649: Jun 14 08:38:53.444 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:37:54      Local7      Warning      192.168.100.39      10648: Jun 14 08:37:53.432 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:36:55      Local7      Warning      192.168.100.39      10647: Jun 14 08:36:54.392 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:35:55      Local7      Warning      192.168.100.39      10646: Jun 14 08:35:54.380 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:34:55      Local7      Warning      192.168.100.39      10645: Jun 14 08:34:54.376 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:34:41      Local7      Notice      192.168.100.42      84172: Jun 14 08:34:41.686 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      8:34:41      Local7      Error      192.168.100.42      84171: Jun 14 08:34:40.680 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to up
6/14/2018      8:34:31      Local7      Error      192.168.100.42      84170: Jun 14 08:34:30.496 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      8:34:30      Local7      Notice      192.168.100.42      84169: Jun 14 08:34:29.498 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/21, changed state to down
6/14/2018      8:33:55      Local7      Warning      192.168.100.39      10644: Jun 14 08:33:54.355 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:32:55      Local7      Warning      192.168.100.39      10643: Jun 14 08:32:54.334 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:31:55      Local7      Warning      192.168.100.39      10642: Jun 14 08:31:54.314 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:30:55      Local7      Warning      192.168.100.39      10641: Jun 14 08:30:54.310 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:29:55      Local7      Warning      192.168.100.39      10640: Jun 14 08:29:54.289 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:28:55      Local7      Warning      192.168.100.39      10639: Jun 14 08:28:54.285 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:27:55      Local7      Warning      192.168.100.39      10638: Jun 14 08:27:54.264 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:26:55      Local7      Warning      192.168.100.39      10637: Jun 14 08:26:54.260 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:25:55      Local7      Warning      192.168.100.39      10636: Jun 14 08:25:54.248 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:24:55      Local7      Warning      192.168.100.39      10635: Jun 14 08:24:54.236 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:23:55      Local7      Warning      192.168.100.39      10634: Jun 14 08:23:54.215 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:22:55      Local7      Warning      192.168.100.39      10633: Jun 14 08:22:54.211 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:21:55      Local7      Warning      192.168.100.39      10632: Jun 14 08:21:54.190 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:20:55      Local7      Warning      192.168.100.39      10631: Jun 14 08:20:54.186 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:19:55      Local7      Warning      192.168.100.39      10630: Jun 14 08:19:54.174 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:18:55      Local7      Warning      192.168.100.39      10629: Jun 14 08:18:54.153 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:17:55      Local7      Warning      192.168.100.39      10628: Jun 14 08:17:54.141 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:16:55      Local7      Warning      192.168.100.39      10627: Jun 14 08:16:54.120 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:15:55      Local7      Warning      192.168.100.39      10626: Jun 14 08:15:54.116 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:14:55      Local7      Warning      192.168.100.39      10625: Jun 14 08:14:54.104 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:13:55      Local7      Warning      192.168.100.39      10624: Jun 14 08:13:54.083 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:12:55      Local7      Warning      192.168.100.39      10623: Jun 14 08:12:54.070 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:11:55      Local7      Warning      192.168.100.39      10622: Jun 14 08:11:54.066 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:10:55      Local7      Warning      192.168.100.39      10621: Jun 14 08:10:54.046 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:09:55      Local7      Warning      192.168.100.39      10620: Jun 14 08:09:54.033 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:08:55      Local7      Warning      192.168.100.39      10619: Jun 14 08:08:54.021 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:07:55      Local7      Warning      192.168.100.39      10618: Jun 14 08:07:54.017 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:06:55      Local7      Warning      192.168.100.39      10617: Jun 14 08:06:54.005 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:05:54      Local7      Warning      192.168.100.39      10616: Jun 14 08:05:53.984 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:04:54      Local7      Warning      192.168.100.39      10615: Jun 14 08:04:53.972 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:03:54      Local7      Warning      192.168.100.39      10614: Jun 14 08:03:53.968 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:02:54      Local7      Warning      192.168.100.39      10613: Jun 14 08:02:53.955 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:01:54      Local7      Warning      192.168.100.39      10612: Jun 14 08:01:53.935 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      8:00:54      Local7      Warning      192.168.100.39      10611: Jun 14 08:00:53.922 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:59:54      Local7      Warning      192.168.100.39      10610: Jun 14 07:59:53.918 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:58:54      Local7      Warning      192.168.100.39      10609: Jun 14 07:58:53.898 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:57:54      Local7      Warning      192.168.100.39      10608: Jun 14 07:57:53.885 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:56:54      Local7      Warning      192.168.100.39      10607: Jun 14 07:56:53.881 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:55:54      Local7      Warning      192.168.100.39      10606: Jun 14 07:55:53.869 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:54:54      Local7      Warning      192.168.100.39      10605: Jun 14 07:54:53.848 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:53:54      Local7      Warning      192.168.100.39      10604: Jun 14 07:53:53.844 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:52:54      Local7      Warning      192.168.100.39      10603: Jun 14 07:52:53.832 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:51:54      Local7      Warning      192.168.100.39      10602: Jun 14 07:51:53.819 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:50:54      Local7      Warning      192.168.100.39      10601: Jun 14 07:50:53.807 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:50:33      Local7      Notice      192.168.100.42      84168: Jun 14 07:50:33.682 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/43, changed state to up
6/14/2018      7:50:33      Local7      Error      192.168.100.42      84167: Jun 14 07:50:32.676 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/43, changed state to up
6/14/2018      7:50:00      Local7      Error      192.168.100.42      84166: Jun 14 07:49:59.585 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/43, changed state to down
6/14/2018      7:49:59      Local7      Notice      192.168.100.42      84165: Jun 14 07:49:58.586 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/43, changed state to down
6/14/2018      7:49:54      Local7      Warning      192.168.100.39      10600: Jun 14 07:49:53.795 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:49:04      Local7      Notice      192.168.100.42      84164: Jun 14 07:49:04.265 pst: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/43, changed state to up
6/14/2018      7:49:04      Local7      Error      192.168.100.42      84163: Jun 14 07:49:03.259 pst: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/43, changed state to up
6/14/2018      7:48:54      Local7      Warning      192.168.100.39      10599: Jun 14 07:48:53.774 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:47:54      Local7      Warning      192.168.100.39      10598: Jun 14 07:47:53.770 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:46:54      Local7      Warning      192.168.100.39      10597: Jun 14 07:46:53.758 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:45:54      Local7      Warning      192.168.100.39      10596: Jun 14 07:45:53.737 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:44:54      Local7      Warning      192.168.100.39      10595: Jun 14 07:44:53.725 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
6/14/2018      7:43:54      Local7      Warning      192.168.100.39      10594: Jun 14 07:43:53.721 pst: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet1/0/11 (not half duplex), with T460015655DED40 WAN PORT (half duplex).
0
DanNetwork EngineerAuthor Commented:
aleghart - how would you configure the trunk ports, to ensure that there are no loops?  I don't care if it takes 1 minute for them to come up if the switch is rebooted?
0
DanNetwork EngineerAuthor Commented:
Thanks guys, I really thank you for all your input, so far,  I replaced the switch, and since then, the port dropped again twice.  Since then I made a few changes, and so far, it's been 2 weeks and no issues, so I'll see what happens.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.