I was hoping to glean some information from the community on the undocumented differences between the ME3400 and ME3400E. It's quite clear to see from CCO documentation that the newer E variant now takes field replaceable power supplies and fan modules so from a hardware point of view they are a different chassis, having said that experience tells me that this is likely not to be the only hardware diffrerence once you get inside the chassis. On the software side, both switches have been aligned to run the same IOS software so it's reasonable to expect that the software only features i.e. the ones that does not rely on specific hardware to have been aligned too.
Whilst waiting for some ME3400Es to arrive I upgraded a pair of lab ME3400s to 12.2(58)SE2 Metro IP Access software, which runs on both platforms. I have noticed that these non Es do not support selective QinQ even though the software advisor claims they do. Is that the only difference? I expect not.
Any comments from either POC / Lab testing or operational experience on the differences between these 2 models would be useful. In particular I would be interested to hear about QOS shaping and policing, layer 2 features differences and other hardware related information.
Some of you may have watched the session at Cisco’s first all-digital Cisco Live and I hope you found it helpful. This is the first in a series of companion blogs that will later cover in more detail the topics discussed in the session today. ...
CCO documentation lists out the ability to do a password recovery for eXR with a ZTP/PXE boot.
One can also perform the operation manually, like a "turboboot" for classic XR in this facinity.
this procedure will wipe out the complete system and install a...
Below is a link to a video showing how to analyze traceroute output in L3VPN and look up CEF forwarding and MPLS/TE/SR/SR-TE forwarding for labels through a domain. Some basic examples of traffic engineering are used but the concepts lend the...
This document summarises various health checks that can be done on a Cisco VIM pod.
Cloud sanity checks the health status of network, storage and various openstack infrastructure components like mariadb, rabbitmq etc....
The following pre-requisites are necessary for the migration from RSP440 to RSP880-LT to be successful.
Make sure that you have console access to the router.
Verify that the system is running a minimum o...