El conocimiento al alcance de todos.

Thanks to:  https://community.cisco.com/ You most likely have the following command enabled: key config-key password-encryption you can remove it by using the no version of the command but you will need the "master passphrase" password that was used to create the encryption to be able to decrypt it. ciscoasa(config)# more system:running-config | in key  key CISCO ciscoasa(config)# key config-key password-encryption New key: ******** Confirm key: ******** ciscoasa(config)# ciscoasa(config)# more system:running-config | in key  key 8 J3z3YkeRt3Ciw/ZIpRu93MGHEMM2 There is no easy way to remove it if you do not have the master key...If you MUST have the aaa key you will need to backup your configuration, issue a write erase, and reload.  Then load your configuration again. --

Thanks to:  https://zimmergren.net In SharePoint 2010, you’ve got some new capabilities for error reporting and logs. One of the most noted features for me as a developer is that whenever you bump into an error message – you’ll be presented with a correlation ID token. In this article I will try to explain how you can fetch that token from SharePoint, and also provide a small snippet of code to be able to build your own “Log Searcher Web Part” for your administrators. What is a Correlation ID in SharePoint? In SharePoint 2010, you get a Correlation ID (which is a GUID) attached to your logs/error messages when something happens. This ID can then be used to lookup that specific error from the logs. This Correlation ID is used per request-session in SharePoint 2010, and if you are in the process of requesting some information from SharePoint and bump into some problems along the way – your Correlation ID will be the best starting point for searching for what went wrong along t

Thanks to:  https://www.ciscozine.com/ Similarly to the old  Virtual Switching System (VSS) , the stackwise virtual allows the clustering of  two chassis  together  into a single ,  logical  entity, to allow high  availability ,  scalability ,  management  and  maintenance. This capability enables a  loop-free Layer 2 network  topology, since the StackWise Virtual switches are treated as one logical switch for both access and core switches. The StackWise Virtual switch also  simplifies  the  Layer 3  network topology by  presenting itself as one logical switch , thus reducing the number of routing peers in the network. Components  used in a StackWise virtual configuration: StackWise Virtual link  (red links): it carries data traffic and  in-band control traffic  between two switches. All the frames that are forwarded over the StackWise Virtual link are encapsulated with a special StackWise Virtual Header (SVH). The  data  is sent over a StackWise Virtual link  under  the