Config snippets : Timezones for Cisco devices
One thing which came handy for me was list of timezones I can use on Cisco devices. That came very useful during NTP deployment. So, here is is… timezones available for use on Cisco platform.
One thing which came handy for me was list of timezones I can use on Cisco devices. That came very useful during NTP deployment. So, here is is… timezones available for use on Cisco platform.
In order to enable SSH access to Cisco Nexus 1000v (if it’s not enabled yet) followign commands have to be issues from Console or Telnet connection:
Nexus 1000v Switch login: admin Password: Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php nexus1000v# conf t Enter configuration commands, one per line. End with CNTL/Z. nexus1000v(config)# ssh key rsa 2048 force deleting old rsa key..... generating rsa key(2048 bits)..... . generated rsa key nexus1000v(config)# ssh server enable nexus1000v(config)#
Now you can use SecureCRT or PuTTY to connect to Cisco Nexus vis SSH of course if IP address is configured on the device and it is connected to network 🙂
Little issue with OpenSSL for Windows came out recently when I tried to create certificate request. Just after installation when tried to generate cert request got error message:
WARNING: can't open config file: /usr/local/ssl/openssl.cnf Unable to load config info from /usr/local/ssl/openssl.cnf
Reason was that by default OpenSSL couldn’t find configuration file (even if it was located in same folder as excutable file).
So, to fix it just set environmental variable with information where openssl.cfg file is located:
set OPENSSL_CONF=c:\OpenSSL-Win32\bin\openssl.cfg
You can consider adding this to system environmental variables.
After installation PostgreSQL is listening on localhost only. To change that adjustment has to be done in postgresql.conf.
After I instaled PostgreSQL on Amazon Linux AMI, first thing after database server was up and running I start thinking how to create user with administrative privileges, so I can access it using some management applications.
So, here is how to create superuser and set password, which will allow to access PostgreSQL using admin tools.