I’d just installed a new vCenter and Platform Services Controller for a client this week. When I tried to access the web consoles I saw this.
Content was blocked because it was not signed by a valid security certificate
For information see “About Certificate Errors” in Internet Explorer Help.
No amount of allowing certificates without revocation, and tinkering with the registry would let me in?
Solution
I cant believe how annoyingly simple it was to solve in the end! Go the the end of the URL and remove ‘/?csp’, problem solved
Related Articles, References, Credits, or External Links
I noticed I had a VM that was ‘Orphaned’ in my vCenter web console. It was not a production server or anything, I just wanted to delete it. However the option to Delete or Remove from Inventory was not available.
Solution
It turns out, you just need to ‘dig a little deeper’. All Virtual Infrastructure Action > More Uncategorized Actions > Remove from inventory.
Related Articles, References, Credits, or External Links
This is a pretty generic error. It basically means “I cant connect to what you are asking me to connect to, on TCP Port 443 (https)”.
Solution
Internet searching for this error is very frustrating, everyone who was posting this error was seeing it because, instead of putting the IP address or name in the box (that actually tells you to put in the IP address or name (see image above)). If you put in https://{Name or IP Address}, you will see this error. However this was NOT MY PROBLEM.
This is happening because there is no communication between you and the ESX/vCenter you are trying to connect to. The first thing you need to do is see if HTTPS is open. On the affected machine open a web browser and point it to the same target and make sure you see the web console of the ESX/vCenter server. If you can’t see this, check firewalls (and proxies) and make sure HTTPS is not getting blocked.
In my case I could see this but it still did not work! Then I was reminded we have had strange comms problems on this site before, which I have documented here. Sure enough, when I dropped the MTU on the server I was trying to connect from (which was over a site to site VPN tunnel). It started to work fine.
Related Articles, References, Credits, or External Links
You have a Draytek router (In my case a 2800 ADSL 2/2+), and you want to update the firmware to the latest version.
Solution
1. Make sure you have EXACTLY the correct model number, this one’s a Draytek Vigor2800.
2. Go here and download the latest firmware for your model.
3. The firmware will be in a ZIP file download and extract it to your machine.
4. Log into the web console of your Draytek > Navigate to > System Maintenance > Firmware Upgrade. (Note: Newer models will let you upload the firmware from here, ours sadly does not).
5. Download the run the Draytek Firmware Update Utility > Locate the IP address of your router (If you have multiple NICS select the one you will use) > Navigate to the firmware you extracted above > Enter the routers password > Send > Have a Coffee > OK.
Note: Select the firmware that has an .all extension, WARNING selecting the firmware that has an .rst extension will upgrade the router BUT it also removes all the settings.
6. If you now check your firmware version, it should be correct.
Related Articles, References, Credits, or External Links
The MSM 765zl and 775zl, unlike the rest of the HP MSM controller series, do not have any physical Ethernet ports on them.
So before you can get to its web management interface, you need to be able to give it an IP address, and then the controller needs to be able to find a route back to where you are, assuming you are not on a flat unrouted/single VLAN. Obviously if you are directly connected to the same network segment then you can set the devices ‘default route’ from the web management console.
Solution
1. Connect to the chassis that the controller is in, either via telnet or console cable. As I outlined in an earlier article you need to find the controllers slot letter and index number with a services command. (If you are sat in front of the switch the slot letter should already be known!)
2. Now, connect to the MSM directly and give the controller its LAN and WANIP addresses.
Note: HP call them LAN and WAN interfaces, (I know it’s confusing), the WAN interface does not have to connect to the WAN it only points in that direction. I’m assuming it’s a throw back from when these devices were developed by Colubris.
[box] CORE-SW# services F 2
CORE-SW(msm765-aplication-F)> enable
CORE-SW(msm765-aplication-F)# config
CORE-SW(msm765-aplication-F)(config)# interface ip wan
CORE-SW(msm765-aplication-F)(config-if-ip)# ip address 192.168.1.1/24
CORE-SW(msm765-aplication-F)(config-if-ip)# ip address mode static
CORE-SW(msm765-aplication-F)(config-if-ip)# end
CORE-SW(msm765-aplication-F)(config)# interface ip lan
CORE-SW(msm765-aplication-F)(config-if-ip)# ip address 10.254.0.100/16
CORE-SW(msm765-aplication-F)(config-if-ip)# ip address mode static
CORE-SW(msm765-aplication-F)(config-if-ip)# end
[/box]
3. Now if you are on the same network (or VLAN) as the controller, you should be able to connect to the web management console. If not you will need to do two further steps
a) Connect the TWO virtual ports of the MSM to the correct VLANs on the switch.
b) Add a route back to the network you are on, either by setting a default route (if there is only one) or a static route.
Connect The Two MSM Virtual Ports
At this point the MSM blade can be treated like any other blade with Ethernet ports on it. Above we found out the blade was in slot F, so the ports with show up on the chassis switch as F1 and F2.
Port number 1: Is the WAN/Internet port Port number 2: Is the LAN port
At the very least the WAN port should be in a different VLAN like so;
If all your LAN traffic is on VLAN 1 (which is the default), then the MSM LAN port will already be untagged in VLAN 1. If not you will also need to present the MSM LAN port to the LAN VLAN.
Adding Default and Static Routes to the MSM controller.
The controller needs a default route, or it will not be able to send traffic out of the local LAN. In a simple flat network that should be all that you need. But if you have multiple network segments (or VLANs), then it will also need a static route adding for each of these. This is important for both access to the web management console, and because your wireless access points need to be able to speak to the controller! If your wireless access points are on a different network you may need to follow the article below to let them know where the controller is.
CORE-SW# services F 2
CORE-SW(msm765-aplication-F)> enable
CORE-SW(msm765-aplication-F)# config
CORE-SW(msm765-aplication-F)(config)# ip route gateway 0.0.0.0/0 192.168.1.254 1
If you need to add additional routes the syntax is the same as above.
CORE-SW(msm765-aplication-F)(config)# ip route gateway 10.100.0.0/16 10.254.0.254 1
CORE-SW(msm765-aplication-F)(config)# ip route gateway 10.200.0.0/16 10.254.0.254 1
[/box]
Now you should be able to connect to the web management console and configure your wireless networks, this process is identical to configuring the physical controllers, like the MSM 720 see the link below.
I installed one of these a couple of weeks ago, and there’s some good documentation with the module itself so installing it into the UPS and giving it an IP address was easy, getting the right client software to talk to it was a pain.
Solution
Configure the Network Module
1. Physically install the module in the UPS, it’s fixed with two screws and you can install it with the UPS powered on.
2. It takes a while for the card to boot, pop in the console cable that came with it (into the Settings/AUX socket – see above). Fire up PuTTy and connect via serial.
Note: Standard Serial Settings,
Bits per second—9600
Data bits—8
Parity—None
Stop bits—1
Flow control—None
3. The default password is ‘admin’
4. Use the menus presented to change the IP details, you MUST restart the module when you are finished or the IP address WONT change.
5. Once its rebooted (again this takes a while) you can login with a web browser, (username admin password admin).
Configure the Client Machines.
1. Download HP Power Protector, (Note: there is no client and administrator software any more, this software will do BOTH. The network module has the administration software built in).
2. Install the software on your machine, and login (again username admin password admin).
3. Select client > Save.
4. Select the Device Discovery tab. The software usually detects the network module on its own quite quickly, if it does not you can use the options on right to do a scan.
Ports Required for HP UPS Network Module
If you are connecting through a firewall (or you machine has a software firewall), make sure the following six ports are open.
5. When it’s fully detected, select the network module and select ‘Configure power source’, supply the login credentials for the network module, and the load segment the machine is plugged into (see below) > Save.
6. Back in the web console of the network module > Open ‘Notified Applications’ and in about 5-10 minutes your server should appear.
Related Articles, References, Credits, or External Links
For such a ‘baby’ switch this has a LOT of features, I had to lock down the speed and duplex settings on one of the switch ports today. The main details you will be looking for are,
Default IP address = 192.168.2.10
Default Password = blank
Solution
1. Put yourself on the same network: Windows Key+R > ncpa.cpl {enter} > Right click your network connection > Properties > Internet Protocol Version 4 (TCP/IP) > properties > Set yout IP to 192.168.2.11 and set the subnet mask to 255.255.255.0 > OK > OK.
2. Open a web browser and navigate to http://192.186.2.10 log in with a blank password.
3. To Change the Switches IP: Setup Network
4. To change Speed/Duplex Settings: Switching > Port Configuration
5. To change the password: Maintenance > Password Manager.
Related Articles, References, Credits, or External Links
Essentially you can unbox this switch, plug it in and it will do what you want (unless you have VLANS, or trunks (port-channels)). Which is what my client had done, but I needed to get on the web console and have a look at what was going on, and there is NO CONSOLE socket on this unit at all.
Solution
1. Don’t bother looking in DHCP, it’s NOT set to DHCP by default. From the factory the switch will have the following IP address; 192.168.2.10 (255.255.255.0). So put yourself on the same network segment and connect to the switch via a normal network cable.
Note: Start > Run > ncpa.cpl will get you there.
2. Now open a browser window and connect to https://192.168.2.10 by default the password will be blank.
3. To change the IP address, navigate to System > IP Address > Set accordingly > Apply.
Note: Obviously this will kick you off, and you will need to change your IP address again to reconnect.
4. To change the password navigate to System > Password > change accordingly > Apply.
Related Articles, References, Credits, or External Links