*
News: SMF - Just Installed!


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

Login with username, password and session length

Recent Posts

Pages: 1 ... 8 9 [10]
91
VMware Support / Windows 2012 VM Loses WAN Access - ESXi 5.5
« Last post by PureSystemsTech on May 08, 2015, 07:57:04 AM »
All,

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!  ;)
92
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.

Thanks!
93
hi guys

users from a LPAR started reporting timeout to connect to servers after some troubleshooting we found these in the Networks IOs

May  4 13:17:42 10.4.25.31 NOTICE  server: link down on port INTA2
May  4 13:17:42 10.4.25.31 NOTICE  server: link up on port INTA2
May  4 13:24:43 10.4.25.31 NOTICE  server: link down on port INTA2
May  4 13:24:43 10.4.25.31 NOTICE  server: link up on port INTA2

First of all I would to understand why there are for every server like two internal ports? I mean INTA1 and INTB1? should add both when creating VLANS or only A1 is active?

second question how can I know if the problem is the NIC card for the VIO or the IO Nortel connector

BTW I see this in my VIO Server

7116720D   0830195814 P H ent5           ETHERCHANNEL CANNOT FAIL OVER
7116720D   0827034414 P H ent5           ETHERCHANNEL CANNOT FAIL OVER
42F2355C   0827034414 T H ent1           PROBLEM RESOLVED
F1814D51   0827034414 T H ent1           ETHERNET DOWN
91E229D7   0827034414 T H ent1           TRANSMIT FAILURE
7116720D   0825222114 P H ent5           ETHERCHANNEL CANNOT FAIL OVER


thanks a lot
94
Flex System Manager (FSM) / Re: FSM update 1.3.0 > 1.3.2 not working?
« Last post by PureSystemsTech 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

Quote
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
95
Flex System Manager (FSM) / FSM update 1.3.0 > 1.3.2 not working?
« Last post by paalb on April 27, 2015, 04:00:26 AM »
Hi guys, I am rather new to managing Flex systems and this is my first attempt to perform upgrades on the System. I've updated CMM without issues and when I hit the "Check and Update Flex System Manager" is says current version 1.3.0 / available version 1.3.2. I run the "Download and Install", and based on progress in GUI and logfiles to me the upgrade appears to complete. However, after restarting the console (using the Shut down or Restart IBM Flex System Manager in GUI) the FSM version remains on 1.3.0.

I'm including the logfile below, all help appreciated. In advance, thank you

April 24, 2015 5:22:13 PM CEST-Level:1-MEID:0--MSG: Job "Install Needed Updates - April 24, 2015 5:22:00 PM CEST" activated.
April 24, 2015 5:22:13 PM CEST-Level:200-MEID:0--MSG: Subtask "Install Needed Updates" activated.
April 24, 2015 5:22:13 PM CEST-Level:200-MEID:0--MSG: Starting clients
April 24, 2015 5:22:13 PM CEST-Level:100-MEID:0--MSG: Clients started for task "Install Needed Updates"
April 24, 2015 5:22:13 PM CEST-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:22:13 PM CEST-Level:1-MEID:0--MSG: Job activation status changed to "Active".
April 24, 2015 5:22:13 PM CEST-Level:200-MEID:0--MSG: Subtask activation status changed to "Starting".
April 24, 2015 5:22:13 PM CEST-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:22:13 PM CEST-Level:150-MEID:0--MSG: ATKUPD489I Collecting inventory for one or more systems.
April 24, 2015 5:25:32 PM CEST-Level:1-MEID:0--MSG: Job "Check for Updates" activated.
April 24, 2015 5:25:32 PM CEST-Level:200-MEID:0--MSG: Subtask "Check for Updates" activated.
April 24, 2015 5:25:32 PM CEST-Level:200-MEID:0--MSG: Starting clients
April 24, 2015 5:25:32 PM CEST-Level:100-MEID:0--MSG: Clients started for task "Check for Updates"
April 24, 2015 5:25:32 PM CEST-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:25:32 PM CEST-Level:1-MEID:0--MSG: Job activation status changed to "Active".
April 24, 2015 5:25:32 PM CEST-Level:150-MEID:0--MSG: ATKUPD470I The check for updates task has started.
April 24, 2015 5:25:32 PM CEST-Level:200-MEID:0--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:25:32 PM CEST-Level:150-MEID:0--MSG: ATKUPD421I A new update acquisition request is active.
April 24, 2015 5:25:32 PM CEST-Level:150-MEID:0--MSG: ATKUPD434I "Appliance Acquisition Provider" is querying for updates.
April 24, 2015 5:25:50 PM CEST-Level:150-MEID:0--MSG: ATKUPD435I "Appliance Acquisition Provider" is acquiring update information or files.
April 24, 2015 5:26:08 PM CEST-Level:150-MEID:0--MSG: ATKUPD450I Reacquired information for update "FSMApplianceFixPackage-1-3-2-1".
April 24, 2015 5:26:29 PM CEST-Level:100-MEID:0--MSG: Job "Check for Updates" activated.
April 24, 2015 5:26:29 PM CEST-Level:20000-MEID:0--MSG: Subtask "Check for Updates" activated.
April 24, 2015 5:26:29 PM CEST-Level:20000-MEID:0--MSG: Starting clients
April 24, 2015 5:26:29 PM CEST-Level:10000-MEID:0--MSG: Clients started for task "Check for Updates"
April 24, 2015 5:26:29 PM CEST-Level:20000-MEID:0--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:26:29 PM CEST-Level:100-MEID:0--MSG: Job activation status changed to "Active".
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD470I The check for updates task has started.
April 24, 2015 5:26:29 PM CEST-Level:20000-MEID:0--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD421I A new update acquisition request is active.
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD434I "Appliance Acquisition Provider" is querying for updates.
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD435I "Appliance Acquisition Provider" is acquiring update information or files.
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD450I Reacquired information for update "FSMApplianceFixPackage-1-3-2-1".
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD436I "Appliance Acquisition Provider" completed successfully.
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD461I Processing the update information.
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD462I Completed processing the update information.
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD426I The update acquisition request has ended successfully.
April 24, 2015 5:26:29 PM CEST-Level:10000-MEID:0--MSG: IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981 client job status changed to "Complete".
April 24, 2015 5:26:29 PM CEST-Level:15000-MEID:0--MSG: ATKUPD472I The check for updates task has completed. No new updates were found.
April 24, 2015 5:26:29 PM CEST-Level:20000-MEID:0--MSG: Subtask activation status changed to "Complete".
April 24, 2015 5:26:29 PM CEST-Level:100-MEID:0--MSG: Job activation status changed to "Complete".
April 24, 2015 5:26:32 PM CEST-Level:150-MEID:0--MSG: ATKUPD436I "Appliance Acquisition Provider" completed successfully.
April 24, 2015 5:26:32 PM CEST-Level:150-MEID:0--MSG: ATKUPD461I Processing the update information.
April 24, 2015 5:26:32 PM CEST-Level:150-MEID:0--MSG: ATKUPD462I Completed processing the update information.
April 24, 2015 5:26:32 PM CEST-Level:150-MEID:0--MSG: ATKUPD426I The update acquisition request has ended successfully.
April 24, 2015 5:26:32 PM CEST-Level:100-MEID:0--MSG: IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981 client job status changed to "Complete".
April 24, 2015 5:26:32 PM CEST-Level:150-MEID:0--MSG: ATKUPD472I The check for updates task has completed. No new updates were found.
April 24, 2015 5:26:32 PM CEST-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete".
April 24, 2015 5:26:32 PM CEST-Level:1-MEID:0--MSG: Job activation status changed to "Complete".
April 24, 2015 5:26:47 PM CEST-Level:100-MEID:4144--MSG: FSM-6CAE8B7C4D7A.npaid.org client job status changed to "Active".
April 24, 2015 5:26:54 PM CEST-Level:1-MEID:4197--MSG: Job "Install Updates" activated.
April 24, 2015 5:26:54 PM CEST-Level:200-MEID:4197--MSG: Subtask "Install Updates" activated.
April 24, 2015 5:26:54 PM CEST-Level:200-MEID:4197--MSG: Starting clients
April 24, 2015 5:26:54 PM CEST-Level:100-MEID:4197--MSG: Clients started for task "Install Updates"
April 24, 2015 5:26:54 PM CEST-Level:200-MEID:4197--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:26:54 PM CEST-Level:200-MEID:4197--MSG: Subtask activation status changed to "Starting".
April 24, 2015 5:26:54 PM CEST-Level:1-MEID:4197--MSG: Job activation status changed to "Active".
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD725I The update install task has started.
April 24, 2015 5:26:54 PM CEST-Level:200-MEID:4197--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD487I The download task has finished successfully.
April 24, 2015 5:26:54 PM CEST-Level:100-MEID:4197--MSG: IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981 client job status changed to "Active".
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD629I Installation staging will be performed to 1 systems.
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD632I The Installation Staging task is starting to process system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: DNZDVM093I The appliance update is for the management server and does not need to be distributed. No further action is required.
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD633I The Installation Staging task has finished processing system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD630I The update installation staging has completed.
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD760I Start processing update "fsm_appliance_update_preparation_1.3.0" and system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD764I Update "fsm_appliance_update_preparation_1.3.0" was installed on system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981" successfully.
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
Once system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981" is active, collect inventory.
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: DNZDVM133I Updates to the IBM Flex System Manager? might require additional updates to other components, including the CMM. When you have finished updating the IBM Flex System Manager?, check for updates to other components using the update chassis components link found on the initial setup tab.
April 24, 2015 5:26:54 PM CEST-Level:100-MEID:4197--MSG: IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981 client job status changed to "Complete".
April 24, 2015 5:26:54 PM CEST-Level:150-MEID:4197--MSG: ATKUPD739I Collecting inventory on system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:27:42 PM CEST-Level:150-MEID:4197--MSG: ATKUPD572I Running compliance on system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:29:21 PM CEST-Level:100-MEID:0--MSG: Job "Install Updates" activated.
April 24, 2015 5:29:21 PM CEST-Level:20000-MEID:0--MSG: Subtask "Install Updates" activated.
April 24, 2015 5:29:21 PM CEST-Level:20000-MEID:0--MSG: Starting clients
April 24, 2015 5:29:21 PM CEST-Level:10000-MEID:0--MSG: Clients started for task "Install Updates"
April 24, 2015 5:29:21 PM CEST-Level:20000-MEID:0--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:29:21 PM CEST-Level:20000-MEID:0--MSG: Subtask activation status changed to "Starting".
April 24, 2015 5:29:21 PM CEST-Level:100-MEID:0--MSG: Job activation status changed to "Active".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD725I The update install task has started.
April 24, 2015 5:29:21 PM CEST-Level:20000-MEID:0--MSG: Subtask activation status changed to "Active".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD487I The download task has finished successfully.
April 24, 2015 5:29:21 PM CEST-Level:10000-MEID:0--MSG: IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981 client job status changed to "Active".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD629I Installation staging will be performed to 1 systems.
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD632I The Installation Staging task is starting to process system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: DNZDVM093I The appliance update is for the management server and does not need to be distributed. No further action is required.
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD633I The Installation Staging task has finished processing system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD630I The update installation staging has completed.
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD760I Start processing update "fsm_appliance_update_preparation_1.3.0" and system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD764I Update "fsm_appliance_update_preparation_1.3.0" was installed on system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981" successfully.
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--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
Once system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981" is active, collect inventory.
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: DNZDVM133I Updates to the IBM Flex System Manager? might require additional updates to other components, including the CMM. When you have finished updating the IBM Flex System Manager?, check for updates to other components using the update chassis components link found on the initial setup tab.
April 24, 2015 5:29:21 PM CEST-Level:10000-MEID:0--MSG: IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981 client job status changed to "Complete".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD739I Collecting inventory on system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD572I Running compliance on system "IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981".
April 24, 2015 5:29:21 PM CEST-Level:10000-MEID:0--MSG: IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981 client job status changed to "Complete".
April 24, 2015 5:29:21 PM CEST-Level:20000-MEID:0--MSG: Subtask activation status changed to "Complete".
April 24, 2015 5:29:21 PM CEST-Level:100-MEID:0--MSG: Job activation status changed to "Complete".
April 24, 2015 5:29:21 PM CEST-Level:15000-MEID:0--MSG: ATKUPD727I The update install task has finished successfully.
April 24, 2015 5:29:24 PM CEST-Level:100-MEID:4197--MSG: IBM 795501M 10A505B CBFC194C-5EA7-4279-A695-6F7E624EC981 client job status changed to "Complete".
April 24, 2015 5:29:24 PM CEST-Level:200-MEID:4197--MSG: Subtask activation status changed to "Complete".
April 24, 2015 5:29:24 PM CEST-Level:1-MEID:4197--MSG: Job activation status changed to "Complete".
April 24, 2015 5:29:24 PM CEST-Level:150-MEID:4197--MSG: ATKUPD727I The update install task has finished successfully.
April 24, 2015 5:29:30 PM CEST-Level:100-MEID:4144--MSG: FSM-6CAE8B7C4D7A.npaid.org client job status changed to "Complete".
April 24, 2015 5:29:30 PM CEST-Level:150-MEID:4197--MSG: ATKUPD288I The install needed updates task has completed successfully.
April 24, 2015 5:29:30 PM CEST-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete".
April 24, 2015 5:29:30 PM CEST-Level:1-MEID:0--MSG: Job activation status changed to "Complete".
96
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.
97
Did you ever find a workaround?  I've been battling this for a while.  Using a Windows AD server, I can LDAP authenticate successfully to both the FSM and the CMM, but the Flex V7000 is complaining that it can't communicate with the LDAP server.  I can tell it's using the same Windows AD servers as the CMM.
98
Flex System Manager (FSM) / Re: FSM Initial Setup
« Last post by PureSystemsTech 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.

99
Flex System Manager (FSM) / Re: FSM Initial Setup
« Last post by orhan on April 14, 2015, 03:41:22 PM »
Thank you for response.

I think i missed that part really. "the FSM is ONLY using ETH0 then it will be routing through the CMM in that chassis and NOT the network switches." I may need to double check this one. This never occured to me. Currently switch port is configured as access port as far as i can tell. so i will look into that.

Here is the latest status
we decided to  use eth1 one as well as currently i am not getting anything back from IBM. I am in the process of uploading support files.

Here is the current setup:
CMM IP: 10.10.10.10
FSM: eth0 = 10.10.10.250
FSM: Subnet Mask: 255.255.255.0
FSM Default Gateway: 10.10.10.1
FSM eth1: 10.120.97.40 Subnet Mask: 255.255.255.128  No default gateway.

on the chassis where FSM resides chassis switches are pass though so there is no configuration and they are directly connected core swithes.  the ports configuration for both eth0 and eth1 configured as access port on the core switches.

Both Ips assigned to FSM on eth0 and eth1 is routable IPs with the correct gateway.

Question is:
Where the default gateway needs to be defined, on eth0 or eth1. Currently it is defined on eth0?
Does it matter whether the FSM is on slot 1 or 7 etc? Currently it is on Slot 7. I am wondering of that has anything to do with it.

I am going to chance the default gateway  that and define on eth1 see if that chances anything.

thanks,
Orhan

I am definetely missing something but not sure where.



100
Flex System Manager (FSM) / Re: FSM Initial Setup
« Last post by PureSystemsTech 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.

Thoughts?

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

Thanks!
Pages: 1 ... 8 9 [10]