As you saw in the previous post, missing ntp configuration on one the vSphere hosts burnt me. I did not want to go through 30 some hosts manually, so decided to bulk update the ntp configuration on all my hosts. After a quick google search i found SnowVM blog post on this.

Here is the commands for my own quick reference.

Connect-VIServer vCenterServerFQDNorIP
Get-VMHost | Add-VMHostNtpServer NTPServerFQDNorIP
Get-VMHost | Get-VMHostFirewallException | where {$_.Name -eq "NTP client"} | Set-VMHostFirewallException -Enabled:$true
Get-VMHost | Get-VmHostService | Where-Object {$_.key -eq "ntpd"} | Start-VMHostService
Get-VMhost | Get-VmHostService | Where-Object {$_.key -eq "ntpd"} | Set-VMHostService -policy "automatic"

So I installed VMware vSphere Big Data Extensions using the OVF file and logged in management-server and installed the extension, enabled SSO and updated the certificate and tried connecting from vSphere webclient using BDE plugin to connect to the server, it fails with error

Please check the server has enabled SSO.

I found VMware KB 2060544, but not much help, I saw the same error in the log (/opt/serengeti/logs/serengeti.log) file, but re-enabling SSO or re-updating the certificate or rebooting the management-server did not help.

Then i noticed the timezone and then a light-bulb went “on” in my head, checked the VM time and it was off by a couple of hours, as the ESX host did not have ntp configured!!! rookie mistake :(.

Fixing ntp on host and rebooting the management server vm to allow it to sync up host time fixed the issue!

Just to clarify, this is not a post on how to configure apache/nginx to proxy requests to iPython notebook server or a backend proxy.

This is when you have a iPython notebook server running on your laptop/desktop behind a corporate/school proxy/firewall and any web requests needs to go through such proxy. On bash shell you just export the env variable like this and its taken care off. However for a iPython server the env variables are not inherited from user bash profile.

You have to modify the iPython notebook server env. Create a file named 00-something.py under your .ipython notebook server profile and add the following:

For example:
vi /.ipython/profile_myserver/startup/00-startup.py

and add

import sys,os,os.path
os.environ['HTTP_PROXY']="http://proxy.example.com:port:80"
os.environ['HTTPS_PROXY']="http://proxy.example.com:port:443"

you confirm the env variables by running

%env in a cell and the output

{'CLICOLOR': '1',
'GIT_PAGER': 'cat',
'HOME': '/home/jay',
'HTTP_PROXY': 'http://proxy.example.com:80',
..

Next try
import requests
requests.get("http://google.com")

If you get a response [200] then you are all set.

I had a few of folks ask me about snmp configuration on 1000v last so am reusing the content I sent them for this post. This is basically a 5 minute configuration of Nexus 1000v SNMP monitoring with SolarWinds NPM.

Software Versions used:

Nexus 1000v version 4.0(4)SV1(3b)

Nexus 1000v version 4.0(4)SV1(4)

SolarWinds Orion NPM 10.2

Network Topology:
SolarWinds NPM was running in a VM on the same cluster as the VSM. Basically they were connected to the same physical Nexus 5020 and on the same vlan. So a very flat backend network topology and no firewall in between. before you begin make sure you can ping from Nexus 1000v to the NMS.

Configuration Steps:

Step 1.
Configure Nexus 1000v SNMP to send traps to the NMS.

Here we are using user xxxxxx to send traps to the NMS using management interface.
Continue reading

Note 1: Even though Cisco fully supports VUM based upgrades we generally recommend the CLI for VEM upgrades as it provides moreĀ granularĀ control on what gets upgraded when.

Note 2: If you plan on manually upgrading the VEM modules make sure you have disabled VMware Update Manager (VUM) service so that it does not automatically roll back changes we make. Once the vem upgrade is complete we can start it back up.

Step 0 Run a “show mod” to check the status of the modules

switch#  show mod
Mod  Ports  Module-Type                       Model               Status
---  -----  --------------------------------  ------------------  ------------
1    0      Virtual Supervisor Module         Nexus1000V          active *
3    248    Virtual Ethernet Module           NA                  ok
4    248    Virtual Ethernet Module           NA                  ok
5    248    Virtual Ethernet Module           NA                  ok
6    248    Virtual Ethernet Module           NA                  ok

Mod  Sw               Hw
---  ---------------  ------
1    4.0(4)SV1(3b)     0.0
3    4.0(4)SV1(3b)     1.11
4    4.0(4)SV1(3b)     1.11
5    4.0(4)SV1(3b)     1.11
6    4.0(4)SV1(3b)     1.11 

Mod  MAC-Address(es)                         Serial-Num
---  --------------------------------------  ----------
1    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8  NA
3    02-00-0c-00-03-00 to 02-00-0c-00-03-80  NA
4    02-00-0c-00-04-00 to 02-00-0c-00-04-80  NA
5    02-00-0c-00-05-00 to 02-00-0c-00-05-80  NA
6    02-00-0c-00-06-00 to 02-00-0c-00-06-80  NA

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    172.16.165.55    NA                                    NA
3    172.16.165.91    dcedbaac-1dc0-11df-0000-00000000000e  172.16.165.91
4    172.16.165.92    dcedbaac-1dc0-11df-0000-00000000000d  172.16.165.92
5    172.16.165.93    dcedbaac-1dc0-11df-0000-00000000000c  172.16.165.93
6    172.16.165.94    dcedbaac-1dc0-11df-0000-00000000000b  172.16.165.94
* this terminal session

This is looking good, with one active VSM and multiple VEM modules and all running the same version.
Continue reading