News: SMF - Just Installed!

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - PureSystemsTech

Pages: 1 2 [3] 4 5 ... 21
31) General Discussion / Re: add feature on demande to switch EN2092
« on: July 06, 2015, 09:11:51 AM »
Hi Gatta,

Are you familiar with using TFTP or SFTP? You can download an easy to use client here from Solarwinds. http://download.cnet.com/SolarWinds-TFTP-Server/3000-18506_4-10974238.html

From the command line you have the same options as in the GUI so there's no other way to get the key to the switch. Make sure you have your license key file that you received from IBM placed in the root directory that you configure for your TFTP server. From there you just enter the information requested and then 'Install Key'.

32) VMware Support / VMware Performance Monitoring in the CLOUD
« on: July 03, 2015, 12:18:14 PM »
Identify issues with your VMware environments before they happen. Identify configuration issues, locate exhausted or underutilized resources, and isolate problems. Access configuration information?including operating system (OS) utilization levels, devices, processor/memory information, and virtual features. At-a-Glance Cluster level, Host level, and virtual machine (VM) level statistics allow you to customize your graphical user interface (GUI) dashboard for each level within your VMware infrastructure. Configuration and Capacity Data allow you to view configurations, objects, and capacity from your dashboard. You can drill down from the Cluster level, through the Host level, and into the VM level statistics.

Configuration and Charts
Full Usage Details for CPU, Memory, Disk and Network
Object types / Charts for:
vCenters (Data Center)
Configuration and Capacity Data for all object types
Real world problem solving assistance charts, for example:
Memory Ballooning
Memory Swap In and Out Rate
CPU Ready Time Percentage
I/O Latency
Network Packet Drops
Stacked charts showing VM metrics across the entire environment
Comparison of metrics between any two virtual machines in your environment


Hi Sashi,

Have you tried rebuilding the profile and ensuring everything is correct?

34) Chassis Networking / Re: switch FC3171 - error login webgui
« on: June 29, 2015, 04:53:16 PM »
Hi Sandro,

I have not seen this before but wondering if when the switch is put in transparent config mode it disables any configuration in the GUI?

35) Flex System Manager (FSM) / Re: CMM/IMM Separate VLANS?
« on: June 02, 2015, 11:14:47 AM »
Hi Dongdp,

Great question. It appears the CMM/IMM has VLAN options. It seems, however, there may be two pieces to this configuration. The CMM has options to define a CMM VLAN and multiple VLANs which you can add your static routes from each IMM to (this is what I THINK needs to happen). Then there is another piece called the Chassis Internal Network that on the 'Configuration' tab has an option to add a Chassis Internal Network aka CIN VLAN ID (I'm not sure exactly what this gives us).

I don't see much documentation on this. I also do not see on the IMMs a way to make the VLAN checkbox clickable, it seems to stay greyed out no matter what changes I make on the CMM.

In my humble opinion. I would play around with setting up VLANs and static routes through the CMM (Found under Chassis Configuration --> VLAN Configuration) and place an IMM on that new VLAN/static route/subnet to see if it pings an is accessible.

Also keep in mind that if you add another VLAN to the CMM you will need to make the top of rack switchport a trunk port to allow for multiple VLANs to pass through that switchport.

Please keep us updated with your progress!


36) General Discussion / Re: Keep up the Great Work!
« on: May 21, 2015, 01:16:02 PM »
Thank you! Our site is only as good as the members that contribute so a very warm/big thank you to you as well!!  :D

37) VMware Support / Windows 2012 VM Loses WAN Access - ESXi 5.5
« on: May 08, 2015, 07:57:04 AM »

I had a very strange problem after running Windows updates this morning on all 3 of our Domain Controllers running Windows 2012 Standard on ESXi 5.5 (build ID 2403361). After reading numerous articles telling me VMXNET3 adapters are the way to go I tried what was quite possibly the dumbest fix ever.

We already had VMXNET3 because this has happened before on e1000 adapters so we made the change a while back.

To fix the problem I did the following:

1. Open the vSphere Client and find the VM
2. Right-click and "Edit Settings"
3. Remove the network adapter then add the same adapter back using the add hardware wizard choosing VMXNET3
4. Click "OK" to apply the change
5. After a quit blip in your Remote Desktop Session you should see your internet connection back to normal.

And the Internet Returns!  ;)

To answer your first question. There are two internal ports because some servers come with a 4-port Ethernet card. So, ports A1 would be the first two ports on the card, the second ports would be B1 (you may have a 4-port card and just need the switch upgrade to light up the B1 ports).

For your second question this is tough. First, I would make sure everything is up to date on firmware or patches, switch/card/VIO. If that doesn't fix it then there is possibly a problem with you etherchannel settings on the VIO servers. I believe if the BNT switches are not stacked then you can not make a true port-channel aka etherchannel on the switch side.

If you wouldn't mind please send your switch configs as well as your etherchannel configs for your VIO servers.


39) Flex System Manager (FSM) / Re: FSM update 1.3.0 > 1.3.2 not working?
« on: April 27, 2015, 09:46:20 AM »
Hi paalb,

The reboot you performed just restarts the FSM web services. See the excerpt from the log file below. Notice the command smshutdown -t now -r. This command is the command line way to reboot the FSM hardware/software and is what the FSM wants you to do to complete the upgrade. Try this full reboot and then please reply with the output of the following command.

'lsconfig -V'
This command will show us the full version that the FSM thinks it is as well as any patches applied

April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: DNZDVM115I To complete the upgrade for system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981", verify that no critical tasks are active, log off the console, and then issue the following command: smshutdown -t now -r

Unfortunately no we did not. We tried to add the FSM to AD and that made the v7000 lose communication to the FSM LDAP server but when the FSM was set to central management mode aka as an LDAP server the v7000 could see it but then it wasn't attached to AD so it still didn't work.

41) Flex System Manager (FSM) / Re: FSM Initial Setup
« on: April 14, 2015, 03:54:07 PM »
Hi Orhan,

Appreciate the detailed information. Bay location shouldn't matter but all of the FSMs I have seen have been in Bay 1. You may want to put it there in case there is another internal network path to the CMM that Bay 1 gets that the other Bays do not. I would start there first.

Second, I'm not sure that you should just add ETH1 to an existing configuration. In my humble opinion I would try a total rebuild of the FSM and select "Use separate networks for data and management" when asked during the initial setup wizard.

Lastly, I am not a network guru but I believe you will need to have a default gateway for the FSM so that other subnets can be routed to it and also if multiple subnets need to be passed down to the FSM then the core switchports should not be static access but trunk ports so that multiple VLANs/subnets can be passed down to the FSM.

42) Flex System Manager (FSM) / Re: FSM Initial Setup
« on: April 14, 2015, 12:57:04 PM »
Hi Orhan,

Are the CMMs all plugged into the same chassis switches or your core switch? Your answer was not clear to me. Also, it definitely sounds like a routing issue. If the FSM is ONLY using ETH0 then it will be routing through the CMM in that chassis and NOT the network switches. Knowing this, the CMM may need to be plugged into a switchport that is set to trunking mode with the allowed VLANs/subnets that the FSM needs to access. Now this has never been tested by myself and I am not sure if the CMM will allow multiple subnets to be passed through on the way to the FSMs ETH0. The proper way to do this is to use ETH0 for chassis management aka CMM management and then ETH1 for NTP/DNS etc... since ETH1 is connected to the chassis switches you will be able to set the FSM chassis network switchport to access multiple VLANs by setting VLAN to '1' and then making the EXT (external) ports that uplink to the core as trunk ports to pass all of the VLANs/subnets you need the FSM to access.


Also, what is IBM saying. Can you provide some of their action plans so we can discuss them as well.


43) VMware Support / VMFS Datastore Not Persistently Mounting Snapshots
« on: April 08, 2015, 03:01:18 PM »

Recently we added a couple of hosts to our VMware environment and noticed that 10 out of 21 datastores would not mount upon reboot.

VMware gave us the following solution.

run esxcli storage vmfs snapshot mount -l <datastore_name>
The -l in this command stands for Persistent-mount which according to VMwares documentation means mount persistently across reboots

This was not the case for us as rebooting still resulted in these 10 datastores from being seen and VMware had no solution to the problem other than taking downtime to perform datastore resignatures which ended up to be the only viable option after almost 2 months waiting for VMware to fix their persistent-mount command.


The final solution was to resignature the VMFS volumes using the following command.

esxcli storage vmfs snapshot resignature -l=<datastore_name>

PLEASE NOTE - this command needs to be run on a datastore with NO RUNNING VMS!

   1. Shutdown VMs running on datastore
   2. On problem host run esxcli storage vmfs snapshot list ....to verify it is seen as a snapshot volume
   Volume Name: ESXSshare-06
   VMFS UUID: 49708f15-345694dc-877a-00215e521038
   Can mount: true
   Reason for un-mountability:
   Can resignature: true
   Reason for non-resignaturability:
   Unresolved Extent Count: 1

   3. Remove any VMs from inventory
   4. Unmount datastore from ALL hosts FIRST before performing maintainance
   5. Perform resignature

      1. Example -  esxcli storage vmfs snapshot resignature -l=ESXSshare-06

   6. In vSphere datastore view rename the datastore back to its original name
   7. Rescan for VMFS volumes on ALL hosts
   8. Validate datastore is seen from ALL hosts tab in the datastore view

Now this is where it gets a little tricky. The datastore will now automatically mount but every single VM that was removed from inventory now has pointers to the disks old signature in their .VMX file. To fix this you need to browse the datastore and download the .VMX file locally. Open it with Notepad or Notepad++ (preferred utility) and change the path to the vmdk files.


In the .VMX file find the following line(s)......
sched.swap.derivedName = "/vmfs/volumes/49708cc0-68198024-4582-00215e521038/ATSVMDC/ATSVMDC-16886a2c.vswp"
Change the above UUID in the filepath to the NEW UUID that was changed. This can be found a few ways but I like to SSH to the host and cd to the /volumes directory then ls -l to list the volumes and their mounts, the mounts are shown as DATASTORE_NAME->UUID.

lrwxr-xr-x    1 root     root            35 Apr  8 18:58ESXFshare-01 ->  551c95f2-989d58c6-d057-40f2e987aa40
lrwxr-xr-x    1 root     root            35 Apr  8 18:58 ESXFshare-02 -> 551c94a1-1ade708e-24ce-40f2e987aa40
lrwxr-xr-x    1 root     root            35 Apr  8 18:58 ESXFshare-03 -> 551c95b0-82cded88-fe13-40f2e987aa40

Once this step is carefully completed, move onto step #9.

    9. Add back VMs to inventory
   10. Bring up VMs that were originally shutdown
   11. Repeat

If none of the above steps work please respond to this post. If you are not a member join already, ITS FREE!  ;D

44) Flex System Manager (FSM) / Re: FSM Initial Setup
« on: March 24, 2015, 06:15:48 PM »
Hi Orhan,

Thanks for the question! The only limitation that I am aware of is that using only ETH0 does not allow for more advanced management features like OS deployment and inventory of OS objects. And overall I've been told in the past by IBMers/Lab Services at that time they recommended using separate networks for data and management traffic because it "works better".

The first things to get out of the way is make sure the FSM and CMM are at the latest firmware levels or at levels that are compatible with each other.

Are there multiple CMMs that cannot be accessed by the same FSM?
Are the CMMs plugged into the back of the chassis switches or your core switch?
Were there IPv6 addresses created on ETH0 when you did the initial setup?
If so, are the IPv6 addresses pingable?


Yes!! Love to hear that and glad that I could help!

Pages: 1 2 [3] 4 5 ... 21