Showing posts with label Cisco. Show all posts
Showing posts with label Cisco. Show all posts
Friday, November 11, 2016
Nexus FEX Config
Wednesday, August 20, 2014
Cisco Bugid CSCul44421 Chassis seeprom local IO failure error on Switch
Symptom:
Error accessing shared-storage fault.
Problem Details:affected="sys/mgmt-entity-A"
cause="device-shared-storage-IO-error"
changeSet=""
code="E4196535"
created="2013-12-18T08:50:03"
descr="device Fxxxxxxxxxxxx, error accessing shared-storage"
dn="event-log/785673"
id="785673"
ind="state-transition"
From Cisco support :
The error accessing shared-storage fault is not harmful and does not affect system functionalities. In UCS chassis design, we build in a chip called, SEEPROM, on the backplane. SEEPROM is a permanent memory and used to store cluster database version to avoid the case of cluster database being overwritten by old version when failover happens.
The communication between IO module and SEEPROM is one way. We store the identical SAM DB version in three chassis rather than in one (so called three chassis redundancy). Because the communication between IO module and SEEPROM happens only one way, the error accessing shared-storage fault can happen sometimes - this is system behavior per specification and design. So, as long as one SEEPROM is readable, the UCS works normally.
If the error accessing shared-storage fault is currently in cleared state and does not raise again, do not apply the workaround and do not do anything.
If the error accessing shared-storage fault is raised state and is never cleared, or the fault keeps coming back, try the following workarounds:
* Reboot the IO module.
* If alert does not clear, reseat IO module. Make sure it's firmly seated.
https://tools.cisco.com/bugsearch/bug/CSCul44421
Other workaround mentioned in Cisco support forum:
https://supportforums.cisco.com/discussion/11349691/ucs-error-accessing-shared-storage-f0863
Error accessing shared-storage fault.
Problem Details:
cause="device-shared-storage-IO-error"
changeSet=""
code="E4196535"
created="2013-12-18T08:50:03"
descr="device Fxxxxxxxxxxxx, error accessing shared-storage"
dn="event-log/785673"
id="785673"
ind="state-transition"
The communication between IO module and SEEPROM is one way. We store the identical SAM DB version in three chassis rather than in one (so called three chassis redundancy). Because the communication between IO module and SEEPROM happens only one way, the error accessing shared-storage fault can happen sometimes - this is system behavior per specification and design. So, as long as one SEEPROM is readable, the UCS works normally.
If the error accessing shared-storage fault is currently in cleared state and does not raise again, do not apply the workaround and do not do anything.
If the error accessing shared-storage fault is raised state and is never cleared, or the fault keeps coming back, try the following workarounds:
* Reboot the IO module.
* If alert does not clear, reseat IO module. Make sure it's firmly seated.
- Reboot/Reseat IOM
- Reboot Chassis
Monday, July 28, 2014
SW ,HW,OS Compatibility note
I am trying to gather links and resource in terms of checking Compatibility when design, deploy or upgrade...
The VMware Compatibility Guide shows the certification status of operating system releases for use as a Guest OS by the following VMware products:
• VMware ESXi/ESX Server 3.0 and later
• VMware Workstation 6.0 and later
• VMware Fusion 2.0 and later
• VMware ACE 2.0 and later
• VMware Server 2.0 and later
http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf
VMware Compatibility Guide Portal:
VMware provides support only for the devices that are listed in this document
http://www.vmware.com/resources/compatibility/search.php
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014508
Enhanced vMotion Compatibility (EVC) processor support (1003212)
For hosts in cluster with different version of CPU
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003212
IBM servers OS support
http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/nos/vmware.html
The VMware Compatibility Guide shows the certification status of operating system releases for use as a Guest OS by the following VMware products:
• VMware ESXi/ESX Server 3.0 and later
• VMware Workstation 6.0 and later
• VMware Fusion 2.0 and later
• VMware ACE 2.0 and later
• VMware Server 2.0 and later
http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf
VMware Compatibility Guide Portal:
VMware provides support only for the devices that are listed in this document
http://www.vmware.com/resources/compatibility/search.php
Correlating VMware products build numbers to update levels (1014508)
VMware vSphere and vCloud suite build numbers table
This table provides a list of all VMware vSphere and vCloud suite build numbers and release dates. The build numbers are based on full installations. Patching ESXi/ESX hosts increments the build number that shows in vCenter Server.Enhanced vMotion Compatibility (EVC) processor support (1003212)
For hosts in cluster with different version of CPU
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003212
IBM servers OS support
http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/nos/vmware.html
Wednesday, June 4, 2014
How to update the UCS’s Capability Catalog to enable new server components to be displayed correctly
What is Capability Catalog
From UCS Release Note "Cisco UCS Manager uses the catalog to update the display and configurability of server components such as newly qualified DIMMs and disk drives. The Cisco UCS Manager Capability Catalog is a single image, but it is also embedded in Cisco UCS Manager. Cisco UCS Manager 2.1(x) releases work with any 2.1(x) catalog file, but not the 1.x or 2.0 catalog versions. If a server component is not dependent on a specific BIOS version, using it and having it recognized by Cisco UCS Manager is primarily a function of the catalog version. The catalog is released as a single image in some cases for convenience purposes in addition to being bundled with Cisco UCS infrastructure releases"
1. Go to UCS Manager Release Notes page to locate the corresponding “Capability Catalog” update content. http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-manager/products-release-notes-list.html
2. Click on “Capability Catalog” on the UCSM 2.0 Release Notes3. Download the "Capability Catalog”
4. Locate “Capability Catalog” tab under Admin in UCSM and Click “+” to start uploading the new Catalog file just downloaded
Thursday, May 15, 2014
networking device SIM note
For building a Lab consist of number of networks and cloud related products, i a am looking for some Router softwares which can connect different networks as the real router doing, There are some reference link below:
Cisco CSR1000v For Home Labs
http://www.fryguy.net/2013/12/27/cisco-csr1000v-for-home-labs/
Cisco CSR1000V vs the Fabled IOU
http://lamejournal.com/2013/12/28/cisco-csr1000v-vs-fabled-iou/
Cisco CSR1000v For Home Labs
http://www.fryguy.net/2013/12/27/cisco-csr1000v-for-home-labs/
Cisco CSR1000V vs the Fabled IOU
http://lamejournal.com/2013/12/28/cisco-csr1000v-vs-fabled-iou/
How to upgrade Titanium VMware image to 6.1.1
http://51sec.blogspot.hk/2013/03/how-to-upgrade-titanium-vmware-image-to.htmlTuesday, April 22, 2014
UCS bug CSCun10760 Legacy CD/DVD” not “Local” or “Remote” in your boot order policy
CSCun10760. The workaround for this issue is to set "Legacy CD/DVD” not “Local” or “Remote” in your boot order policy (see screenshot)
https://supportforums.cisco.com/discussion/12146621/service-profile-resource-issuehttp://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-2/b_UCSM_GUI_Configuration_Guide_2_2/b_UCSM_GUI_Configuration_Guide_2_1_chapter_011111.html#concept_F6AF7F0342224EF28B65ABC2C382FFB1
From Cisco Forum:
Second-level devices are only available for Cisco UCS M3 blade and rack servers using enhanced boot order. ForCisco UCS M1 and M2 blade and rack servers using standard boot order, you can choose only the top-level Add Local Disk.
|
If you select 'Add Local CD/DVD' or 'Add Remote CD/DVD' the service profile will fail to apply to a non-M3 blade, those options are uefi 2nd level boot. You must delete any CD/DVD from the service profile, then add the top level Add CD/DVD when Legacy Boot is checked.
CSCun10760 was opened so that second order boot options are greyed out when using legacy boot.
Tuesday, March 18, 2014
how to copy tech-support log with Putty
- In Putty Configurations > Session >Logging
- Select "All Session output"
- Select "Flush log file frequently" will overwrite the log file every time when start the session

- connect the device
- in the EXEC mode of the command prompt, type terminal length 0 which will make the command output at once without interrupt
vsg1#terminal length 0
vsg1#show tech-support all
6.then we will have the output in the Putty log file ^ ^
Ref:http://ccienet.wordpress.com/2012/01/22/how-to-copy-large-show-tech-support-from-cisco-device-using-putty/
Subscribe to:
Posts (Atom)





