*
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 ... 21
16) Flex System Manager (FSM) / Re: /opt filling on FSM appliances
« on: November 12, 2015, 02:24:21 PM »
Hi Jason,

Before you performed the upgrade did you run...

smcli cleanupd -mva

That command is not included in the documentation but is definetely a very important step that should be included. This cleans out the entire update repository. Now, I'm not sure if the updates live under /opt but I also upgraded from 1.3.3 to 1.3.4 recently at a customer and did not see this issue so I have to believe they do.

If you have never ran this command then note that it could take an extraordinary amount of time to complete so please be patient.

After you clean out the updates, reboot the FSM, and try the update again.

However, if the FSM software cannot even start then I'm not sure this command would be available thus forcing you to rebuild the FSM.  :-\ If that is the case I am not sure what level of code your Recovery Partition is running but I would advise requesting IBM send you the Recovery media for 1.3.4  so you won't need to do a series of upgrades to your FSM post rebuild. The caveat to that is if you have a recent backup of the FSM on 1.3.3 code, if this is the case then I would request the Recovery Media for 1.3.3 just to be sure your restore will work.

Does that make sense?

Thanks!

17) Flex System Manager (FSM) / Re: FSM 1.3.4 and p260 firmware - VIO version
« on: October 27, 2015, 04:17:11 PM »
We have our p460 at FW783.00 (021)

Also FYI, update to 1.3.4 was successful using the same method as I needed for 1.3.3.

18) Flex System Manager (FSM) / Re: FSM 1.3.4 and p260 firmware - VIO version
« on: October 27, 2015, 03:09:20 PM »
karlochacon,

happy to help. Update to 1.3.3 was successful! I'm going to use the same method to go to 1.3.4 as I do not feel like playing games with the FSM today  :P

19) Flex System Manager (FSM) / Re: FSM 1.3.4 and p260 firmware - VIO version
« on: October 27, 2015, 02:14:35 PM »
My update from 1.3.2 to 1.3.3 failed on compliance check. I had to open a ticket with IBM to get my root/PESH password and then used the following article to resolve.

Take note of the last post and steps to resolve issues with compliance check during upgrade procedure...
http://mypuresupport.org/PureSystemsForum/index.php?topic=87.0

20) Flex System Manager (FSM) / Re: FSM 1.3.4 and p260 firmware - VIO version
« on: October 26, 2015, 12:59:17 PM »
Thanks, Karlochacon.

For everyones reference, here is a link to the various FSM upgrade guides.

https://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5091991&brandind=5431802

I will be attempting this upgrade to 1.3.4 as well from FSM version 1.3.2 this week. I will start a new thread if any issues are encountered.

Thanks!

21) Flex System Manager (FSM) / Re: FSM 1.3.4 and p260 firmware - VIO version
« on: October 26, 2015, 10:29:42 AM »
Karlochacon,

Good morning. In order to make sure your p260 has the correct firmware you must consult the Flex Upgrade guide for FSM 1.3.4. This document will show you how to upgrade to make sure all components within the Flex chassis are interoperable.

Thanks!

22) VMware Support / Re: moving guests from one chassis to another
« on: September 22, 2015, 03:47:59 PM »
Let me be clear VMcontrol is NOT a VMware utility  IBM confused everyone with the name. ;)

With that said the only requirements for vMotion between chassis's are the following.

1) Hosts from both chassis are in the same vSphere cluster withing vCenter (unless you are on ESXi6)
2) Backend SAN storage needs to be shared across all hosts in the cluster.
3) vMotion networks configured and on host vSwitches or vSphere Distributed Switch.

Please provide a screenshot if you have one to help troubleshoot further.

http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-D19EA1CB-5222-49F9-A002-4F8692B92D63.html

23) Chassis Management Module (CMM) / Re: SOL for a p260 Node
« on: September 22, 2015, 03:40:59 PM »
Have you tried to run inventory from the FSM?

Right-click on the node -> Collect Inventory

You should still have backward compatibility but your assumption may be correct.

24) VMware Support / Packet Drops on DOWN VMNIC
« on: September 16, 2015, 08:46:10 AM »
All,

As of yet I have no solution but am documenting this issue on MPS portfolio.

The issue is simple (or so we thought). We are seeing packet drops on vmnics that are administratively down in VMware.

The Infrastructure
Two HS23 (both exhibiting same issues)
Running ESXi 5.5 Update 2
Emulex 4-port One Connect Ethernet Adapter (driver version - 10.2.298.5)


The Issue
As you can see below. When I pull statistics from vmnic0 it is showing a large amount packets received and a large amount of packet drops. However, as mentioned above, this vmnic is administratively down as you will see below.

esxcli network nic stats get -n vmnic0
NIC statistics for vmnic0
   Packets received: 31547633303
   Packets sent: 0
   Bytes received: 16187874324373
   Bytes sent: 0
   Receive packets dropped: 1482863150
   Transmit packets dropped: 0
   Total receive errors: 0
   Receive length errors: 0
   Receive over errors: 0
   Receive CRC errors: 0
   Receive frame errors: 0
   Receive FIFO errors: 0
   Receive missed errors: 0
   Total transmit errors: 0
   Transmit aborted errors: 0
   Transmit carrier errors: 0
   Transmit FIFO errors: 0
   Transmit heartbeat errors: 0
   Transmit window errors: 0


As you can see, I have no vmnic0/1 in any vSwitch.

/usr/sbin/esxcfg-vswitch -l
Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0         5632        9           128               1500    vmnic2,vmnic3

  PortGroup Name        VLAN ID  Used Ports  Uplinks
  Production            0        2           vmnic2,vmnic3
  VMotion               0        1           vmnic2,vmnic3
  Management Network    0        1           vmnic2,vmnic3

Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitchUSB0      5632        4           128               1500    vusb0

  PortGroup Name        VLAN ID  Used Ports  Uplinks
  IMM_Network0          0        1           vusb0


If I list the statistics of vmnic2 right after I see that packets received on this vmnic IS ALMOST THE SAME AS vmnic0!
esxcli network nic stats get -n vmnic2
NIC statistics for vmnic2
   Packets received: 31547645008
   Packets sent: 23805666719
   Bytes received: 16187878339822
   Bytes sent: 39966911268856
   Receive packets dropped: 0
   Transmit packets dropped: 0
   Total receive errors: 0
   Receive length errors: 0
   Receive over errors: 0
   Receive CRC errors: 0
   Receive frame errors: 0
   Receive FIFO errors: 0
   Receive missed errors: 0
   Total transmit errors: 0
   Transmit aborted errors: 0
   Transmit carrier errors: 0
   Transmit FIFO errors: 0
   Transmit heartbeat errors: 0
   Transmit window errors: 0


When I run the below command and use WireShark to review the .pcap file I see (as confirmed by VMware technical support) that the file shows packets that mirror what vmnic2 is receiving. Almost as if the vmnic ports are replicating their traffic across ports??

pktcap-uw --uplink vmnic0 ?o /vmfs/volumes/ESXFshare-01/vmnic0_pktcap.pcap


Currently this is unresolved. VMware has asked that I open a hardware ticket for my Emulex card to see if there is a hardware defect causing this "packet replication" issue. I will update when/if a resolution is reached.

Thanks!

hi Eric,

Apologies for the late reply. The system-management processor is the power nodes FSP aka Flexible Service Processor or the ASM. You can issue a reboot from the CMM chassis view "Restart system management processor". Our power nodes show up the same way and eventually they come back!

26) Chassis Management Module (CMM) / Re: activate the license (upgrade1)
« on: August 07, 2015, 08:04:27 AM »
Hi Balagajan,

Welcome to MPS!

For the address it would be the address or hostname of your tftp server where the key file is located.

You can also try this link to a document from Lenovo explaining different methods to install an FOD key on these switchs.

http://www.redbooks.ibm.com/redpapers/pdfs/redp4895.pdf

Please let us know your status! Thanks!!

This is new to me.  :-\ I would recommend calling IBM to see what they can provide.

If they can give you a solution would you mind replying with the resolution?

Thanks!!

28) Chassis Networking / Re: EN2092 with x240
« on: July 09, 2015, 08:47:30 AM »
Hi Gatta,

Good morning and thank you for the question. Could you please provide your switches running config? Also, what is the x240's operating system and what BAY does the x240 reside?

Thanks!

29) General Discussion / Re: add feature on demande to switch EN2092
« on: July 06, 2015, 03:29:00 PM »
Do you see anything in the log window of the TFTP server when you try to connect? It should say establishing session with <your switch IP> and following messages about pulling down a file.

One thing to note. Make sure your key file is in the root of the TFTP directory and when you enter the filename into the switch GUI, make sure the filename includes the file extension and as long as the file is in your TFTP servers root directory you should only need to use the filename.

30) General Discussion / Re: add feature on demande to switch EN2092
« on: July 06, 2015, 11:16:33 AM »
Right-click on the TFTP server and try to run in compatibility mode for Windows XP.

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