Duplex mismatch discovered 9ESW and 6941 phones on Cat 3
I recently migrated a couple of 6941 phones from ports on a NME-16ES-1G-P that died to a 9ESW with POE. These two phones connect via Cat 3 and were set to 10 Mbps full duplex because of the cabling limitation.
Now, no matter how I configure the 9ESW (auto auto, 10 auto, 10 full, or even 10 half) I get continuous "duplex mismatch discovered" errors on the 2821 router. I've tried leaving the phone on auto and setting it to 10 full and 10 half. No combination works, even auto on the switch and auto on the phone. You would expect 10 full set at both ends would avoid any negotiation.
The router is running 15.1 something. The phone loads are DSP69xx.12-4-122-99.131025 and SCCP69xx.9-4-1-3SR1. The phones worked fine for years on the 16ES service module. I appreciate the 9ESW is a different beast from the 'ES and I had little difficulty migrating the other Cat5 connected phones to it. The 16ES was removed from the router to enable the 9ESW to operate.
The problem phones work fine connected over Cat 5 but replacing the premise wiring is not an option in this case. So to restore service I put the 6941 phones on an external third-party POE switch hooked to the same port on the 9ESW. Everything is fine (except the phones are in the wrong VLAN (native rather than voice but they still work OK).
In scaled EVPN deployments it can be wise to name ESI that way to represent the site/physical port/etc it is attached to. Thus on some remote location you can easily verify where particular route/MAC is coming from. Similar to phone numbers, where...
Want to enable Feature EPFT with “routing-protocols-enable”. However ,it is throwing an error and ask to configure the following command: “non-subscriber-interfaces mac” which once enabled drops the traffic without any penalty.
XR-vm - CLI's
look for any process crash, review time stamp[if it is too old, then no immediate action needed]
verify if standby state is Ready and NSR-Ready
show proc cpu | exclude " 0%"
It's been a long standing ask for XR to support conditional route advertisements in BGP.
The expected option of using the
option in RPL currently can only be used at the default-inf...
On IOS-XR, Quality of Service has an extension to WRED (Weighted Random Early Detection) called Explicit Congestion Notification (ECN). ECN will mark packets instead of dropping them when the average queue length exceeds a specific threshold value. When c...