Nothing Special   »   [go: up one dir, main page]
Scribd Logo
Upload

Welcome to Scribd!

  • 15 views

    Brocade Switch Repair

    Uploaded by

    My GlobalHelp
    1. Backup the existing configuration using the cfgsave and configupload commands. 2. Determine which CP blade is active using hashow and fail over to the other CP if needed before replacement. 3. Replace the defective CP blade by disabling HA, powering off the blade, disconnecting cables, removing the old blade, and inserting the new blade.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Brocade Switch Repair

    Uploaded by

    My GlobalHelp
    15 views3 pages
    1. Backup the existing configuration using the cfgsave and configupload commands. 2. Determine which CP blade is active using hashow and fail over to the other CP if needed before replacement. 3. Replace the defective CP blade by disabling HA, powering off the blade, disconnecting cables, removing the old blade, and inserting the new blade.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    1. Backup the existing configuration using the cfgsave and configupload commands. 2. Determine which CP blade is active using hashow and fail over to the other CP if needed before replacement. 3. Replace the defective CP blade by disabling HA, powering off the blade, disconnecting cables, removing the old blade, and inserting the new blade.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    15 views3 pages

    Brocade Switch Repair

    Uploaded by

    My GlobalHelp
    1. Backup the existing configuration using the cfgsave and configupload commands. 2. Determine which CP blade is active using hashow and fail over to the other CP if needed before replacement. 3. Replace the defective CP blade by disabling HA, powering off the blade, disconnecting cables, removing the old blade, and inserting the new blade.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Brocade Switch Repair

    If Customer Does Not have a Backup of the Configuration


    1. Using Hyper-term or Telnet Log into the Known working CP
    2. Setup FTP Server (3cdv2r10)
    3. Create a .txt file on the Laptop or Server Example
    /Brocade/origconfig.txt
    4. Backup ,Save and Upload Current Configuration
    a. Log into CP(0) and issue the command cfgsave

    Example:
    FC_Switch:admin> cfgsave
    Updating Flash...
    NOTE: If nothing has changed since the most recent cfgsave, you
    will receive the message: “Nothing changed: nothing to save,
    returning…”
    b. Execute configupload

    FC_Switch:admin> configUpload
    Protocol (scp or ftp) [ftp]: ftp
    Server Name or IP Address [host]: {IP address of your host}
    User Name [user]: {Your login ID on the host,}
    File Name [config.txt]: {Path to the file} i.e./temp/brocade/origconfig.txt
    Password: {your password on the FTP server}
    Upload complete

    If Customer Does had a Backup of the configuration

    5. Replace the Defective CP(1) in slot 6

    To record critical director information

    a. Login into the functioning CP blade as admin, using either a


    Telnet or a serial console connection.
    b. Type haShow to determine which CP blade is active:

    Local CP (Slot 5, CP0) : Active


    Remote CP (Slot 6, CP1) : Standby, Healthy
    HA Enabled, Heartbeat Up, HA State Synchronized

    6. If the functioning CP (0) blade is performing as the active CP


    blade, then continue to Replace CP(1)
    7. If the functioning CP (1) blade is performing as the active CP
    blade, then you will need to fail over to the CP(0) by issuing
    the command hafailover
    8. Wait 5 minutes then type hashow from the functioning CP(0). You
    should now see

    Local CP (Slot 5, CP0) : Active


    Remote CP (Slot 6, CP1) : Standby, Healthy

    9. Proceed with the replacement of CP(1)

    How to replace the defective CP

    1. Type haDisable from the active CP (0) blade to prevent failover


    or communication between the CP blades during the replacement.
    2. Power off the blade by sliding the slider switch in the top
    ejector down to the off position
    3. Disconnect all cables from the faulty (standby) CP.
    4. Unscrew the thumb screw from both ejectors using the Phillips
    screwdriver.
    5. Lever open both ejector handles simultaneously to approximately
    45 degrees and pull the CP blade out of the chassis
    6. Replace the Defective Blade
    7. Turn the CP blade on by sliding the ON/OFF switch in the top
    handle up, to cover the thumb screw.
    8. Verify that the power LED is green. If not, ensure that the CP
    blade has power and is firmly seated and that the ejectors are in
    the locked position.
    9. Connect the cables to the new CP blade

    10. Log into the active CP as admin.


    11. Enable the redundancy feature using the haEnable command.
    12. Verify HA is enabled using the haShow command. The command
    output includes “HA Enabled
    Heartbeat Up” and “HA-state in sync.”

    If not, POST is not complete or the CP blades have not achieved


    redundancy. Wait one or two
    minutes and re-enter the command until you can verify that redundancy
    has been achieved.
    13. Type slotShow. The command output shows the new CP blade as
    “enabled”:

    Slot Blade Type ID Status


    ---------------------------------
    1 SW BLADE 17 ENABLED
    2 SW BLADE 17 ENABLED
    3 SW BLADE 17 ENABLED
    4 SW BLADE 17 ENABLED
    5 CP BLADE 16 ENABLED
    6 CP BLADE 16 ENABLED
    7 SW BLADE 17 ENABLED
    8 SW BLADE 17 ENABLED
    9 SW BLADE 17 ENABLED
    10 SW BLADE 17 ENABLED

    14. Determine the version by typing firmwareShow. Both CP’s


    should be at the same Version. If not you will need to update the
    firmware on the CP’s

    This example shows sample output for the firmwareShow command:

    Local CP (Slot 5, CP0): Active


    Primary partition: v5.3.0
    Secondary Partition: v5.3.0
    Remote CP (Slot 6, CP1): Standby
    Primary partition: v5.3.0
    Secondary Partition: v5.3.0

    You might also like