Can I use SFP-10G-LR to connect Chassis placed at long distance from Fabric Interconnect ? Do I will face any latency issue ?   -Amit ... View more

Thanks Walter for your reply If possible please help me with the scripts location from where I can see those scripts and try to implement in my environment Also is there any way we can automate Service Profile creation via Service Profile template and get that template attached to required server ? Please do reply if you have any idea on this   -Amit ... View more

Thanks Walter for your reply Correct me if my understanding is wrong So, if I have 2 Chassis, IOM + Blades running on 2.1(1f) I can upgrade the UCSM + Fabric Interconnect to 2.1(3a) and use new chassis with it + my 2 chassis will keep running on 2.1(1f) as per below support matrix captured from release notes -Amit ... View more

I have raised the SR and TAC engineer is working on it Mean while I wanted to know / understand following two things How Fail over happens in Fabric Interconnect? i.e. how Primary Subordinate role gets transfer from one to another What is the ideal time to create sub-interface on peer fabric interconnect for VIP when Primary FI reboot or powered down   ... View more

No, haven't delete key ring but have rebooted FI's multiple times ... View more

I am not hitting this bug, because these devices are shipped with 2.2.(1b) Not sure what will be the issue ?   ... View more

I am also assume the same that it might be a bug Yes, Admin status is enabled and Monitoring Mechanism is MII Status But above setting also didn't help, when I restarted the primary FI, I lost the ping VIP and FI-A and VIP response came after FI-A came up   ... View more

I can only ping FI-B and unable to ping VIP until FI-A come up ... View more

Below is the output before power off FI-A ================================================ lavender-A(local-mgmt)# show cluster extended-state Cluster Id: 0x7bce8766ecdc11e3-0xa1b4002a6ac23b41 Start time: Sat Jun 14 21:05:55 2014 Last election time: Sat Jun 14 21:17:57 2014 A: UP, PRIMARY B: UP, SUBORDINATE A: memb state UP, lead state PRIMARY, mgmt services state: UP B: memb state UP, lead state SUBORDINATE, mgmt services state: UP    heartbeat state PRIMARY_OK INTERNAL NETWORK INTERFACES: eth1, UP eth2, UP HA READY Detailed state of the device selected for HA storage: Chassis 1, serial: FOX1812GNZZ, state: active Chassis 2, serial: FOX1813GFT7, state: active Chassis 3, serial: FOX1814G5DR, state: active lavender-A(local-mgmt)# ================================================   Below is the output after shutting down the FI-A ================================================ lavender-B(local-mgmt)# show cluster extended-state Cluster Id: 0x7bce8766ecdc11e3-0xa1b4002a6ac23b41 Start time: Wed Jun 11 19:09:13 2014 Last election time: Sat Jun 14 13:45:18 2014 B: UP, PRIMARY, (Management services: SWITCHOVER IN PROGRESS) A: DOWN, INAPPLICABLE B: memb state UP, lead state PRIMARY, mgmt services state: INVALID A: memb state DOWN, lead state INAPPLICABLE, mgmt services state: DOWN    heartbeat state SECONDARY_FAILED INTERNAL NETWORK INTERFACES: eth1, DOWN eth2, DOWN HA NOT READY Management services: switchover in progress on local Fabric Interconnect Detailed state of the device selected for HA storage: Chassis 1, serial: FOX1812GNZZ, state: active Chassis 2, serial: FOX1813GFT7, state: active Chassis 3, serial: FOX1814G5DR, state: active lavender-B(local-mgmt)# ================================================ Its really strange that when I do the manual cluster lead change, its taking good amount of time to switch the VIP from FI-A to FI-B wise a versa   Regards, Amit Vyas ... View more