1 / 44

Upgrade Controller from 4.x to 5.2

Upgrade Controller from 4.x to 5.2. Upgrade Controller from 4.x to 5.2. Using the console port What version’s currently running? Log into the CLI Don’t know the admin password? Privileged mode Check image files on the controller Upload 5.2 image file Optional extra steps

burton-saunders
Download Presentation

Upgrade Controller from 4.x to 5.2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Upgrade Controller from 4.x to 5.2

  2. Upgrade Controller from 4.x to 5.2 • Using the console port • What version’s currently running? • Log into the CLI • Don’t know the admin password? • Privileged mode • Check image files on the controller • Upload 5.2 image file • Optional extra steps • Copy configfile • Configure controller’s IP address • Upload 5.2 image file using web GUI

  3. Using the console port

  4. Using the console port • Console port settings • 19200 bps N-8-1, no flow control • Same for all devices that have a console port • RFS4000, RFS6000, RFS7000 Controllers • 7131 Access Point • Doesn’t have console port: 650 & 6511 Access Point • Same for all firmware versions • Controllers ship with a console cable • It’s a Cisco compatible DB9 to RJ45 console cable

  5. What version’s currently running? • Connect to the console port. • Power cycle and from the console port look for: • Or: This means it’s running version 4.x This means it’s running version 5.x

  6. Log into the CLI • For Controller version 4.x • Don’t forget to enter cliat the login: prompt! Important! For controller running 4.x, enter cli at login: admin123 is the factory default admin password admin123

  7. Don’t know the admin password? • For Controller version 4.x • Restore the factory default config • Don’t forget to enter cliat the login:prompt! Important! For controller running 4.x, enter cli at login: restoreDefaultPassword

  8. Privileged mode Important! For controller running 4.x, enter cli at login: admin123 is the factory default admin password The # prompt means you are now in privileged mode

  9. Check image files in the controller

  10. Upload 5.2 image file • Connect your USB memory device that has the 5.2 image file on it to your controller: RFS7000 actually has 2 USB ports!

  11. Optional Extra Steps

  12. Copy config file BR-RFS4000#copy ? FILE File from which to copy Files: flash:/path/file usb1:/path/file nvram:startup-config system:running-config URL URL from which to copy URLs: tftp://<hostname|IP>[:port]/path/file ftp://<user>:<passwd>@<hostname|IP>[:port]/path/file sftp://<user>:<passwd>@<hostname|IP>[:port]>/path/file http://<hostname|IP>[:port]/path/file BR-RFS4000#copy nvram:/startup-config ? FILE File to which to copy Files: flash:/path/file usb1:/path/file nvram:site-layout nvram:startup-config running-config (merges with current configuration) URL URL to which to copy URLs: tftp://<hostname|IP>[:port]/path/file ftp://<user>:<passwd>@<hostname|IP>[:port]/path/file sftp://<user>:<passwd>@<hostname|IP>[:port]>/path/file BR-RFS4000#copy nvram:/startup-config usb1:/ BR-RFS4000#

  13. Configure controller’s IP address • Can’t use USB? • Uploading image files via TFTP, FTP, SFTP, HTTP all require the controller to have an IP address • So let’s go configure the controller’ IP address

  14. Configure controller’s IP address • Connect the UPLINK port to your network RFS7000 uplinks are called GE ports (GE1 to GE4)

  15. Configure controller’s IP address

  16. Configure controller’s IP address • Configuring DHCP client for VLAN1 on an RFS7000 in factory default configuration

  17. Configure controller’s IP address • Gotchas when configuring IP addresses • How to configure static IP address

  18. Configure controller’s IP address • On my RFS4000, my UPLINK is UP • And I know for sure there’s a DHCP server • So why am I not getting an IP address? • If your DHCP server is giving IP addresses in the 192.168.0.x/24 scope then it’s not going to work • You can’t assign more than one IP address from the same subnet

  19. Configure controller’s IP address • RFS4000: Releasing a VLAN’s IP address and renew another VLAN’s IP addresss Optional. Just to check what I’m doing. Optional. Just to check what I’m doing. Optional. Just to check what I’m doing. Optional. Just to check what I’m doing.

  20. Configure controller’s IP address • Similar thing for the RFS6000 • If your DHCP server is giving IP addresses in the 10.1.1.x/24 scope then it’s not going to work • You can’t assign more than one IP address from the same subnet

  21. Configure controller’s IP address • RFS6000: Releasing a VLAN’s IP address and renew another VLAN’s IP address Optional. Just to check what I’m doing. Optional. Just to check what I’m doing. Optional. Just to check what I’m doing. Optional. Just to check what I’m doing.

  22. Configure controller’s IP address • And similar thing for the RFS7000 • If you configure VLAN 1 as a DHCP client, and • If your DHCP server is giving IP addresses in the 10.1.1.x/24 scope then it’s not going to work • You can’t assign more than one IP address from the same subnet

  23. Configure controller’s IP address • RFS7000: Releasing a VLAN’s IP address and renew another VLAN’s IP address Optional. Just to check what I’m doing. Optional. Just to check what I’m doing. Optional. Just to check what I’m doing. Optional. Just to check what I’m doing.

  24. How to configure static IP address BR-RFS4000(config-if)#ip add 192.168.0.101/24 BR-RFS4000(config-if)#show ip int vlan2100 br Interface IP-Address/Mask Status Protocol vlan2100 192.168.0.101/24 up up BR-RFS4000(config-if)#exit BR-RFS4000(config)#ip route 0.0.0.0/0 192.168.0.1 BR-RFS4000(config)#show ip route Codes: K - kernel/icmp, C - connected, S - static, D - DHCP * - candidate default Gateway of last resort is 192.168.0.1 to network 0.0.0.0 S* 0.0.0.0/0 [5/0] via 192.168.0.1, vlan2100 C 192.168.0.0/24 is directly connected, vlan2100 BR-RFS4000(config)#ip name-server 192.168.0.1 BR-RFS4000(config)#show ip name-server 192.168.0.1 static BR-RFS4000(config)#end BR-RFS4000#ping brocade.com PING brocade.com (144.49.210.200): 100 data bytes 128 bytes from 144.49.210.200: icmp_seq=0 ttl=58 time=36.6 ms 128 bytes from 144.49.210.200: icmp_seq=1 ttl=58 time=35.9 ms 128 bytes from 144.49.210.200: icmp_seq=2 ttl=58 time=36.0 ms 128 bytes from 144.49.210.200: icmp_seq=3 ttl=58 time=36.3 ms 128 bytes from 144.49.210.200: icmp_seq=4 ttl=58 time=36.0 ms --- brocade.com ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 35.9/36.1/36.6 ms BR-RFS4000# Optional. Just to check what I’m doing. Optional. Just to check what I’m doing. Optional. Just to check what I’m doing. Optional. Just to check what I’m doing.

  25. Gotcha: Static IP addr on RFS4000 • The factory default config for 4.x on RFS4000 includes an enabled DHCP server (but not on the RFS6000 and RFS7000) • If you configure a static IP address in the 192.168.0.x/24 (just like I did in the example on the previous slide), this DHCP server will become active on that VLAN (but not if you use an IP address from any other subnet) • To disable it, simply enter the CLI command:

  26. Upload 5.2 image file • Don’t like using the CLI? • You can use the web GUI to upload 5.2 image file too!

More Related