Re: RME 3.5: WS-6506-E cannot be removed from Out of Sync Report
If this is LMS 2.2, I find there's been a behavior change in how RME 3.5 timestamps configs after IDU 8.0. Startup configs now always get a new timestamp in Out-of Sync report, whenever CiscoWorks polls the device successfully for Startup config, *regardless* of whether there's an actual change in the device's Startup config. Running configs' timestamps in CiscoWorks stay true to the "show run" timestamps on the devices, so the Running Config timestamps will get updated in the Config Out-of-Sync Report *only if* CiscoWorks detects an actual change in the device's Running config. So you end up seeing Startup config timestamps siginificantly newer than Running configs' in Out of Sync reports, which startles most people.
To fix the Out of Sync report, first do "copy run start" on the device, of course. Then force an immediate retrieval of Startup config: RME -> Configuration Management -> (select any menulet that brings up device Startup and Running configs) -> click on the 'Startup' hyperlink.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...