This error was a real nuisance. I should have known though. This was one of those things I have seen before and just wasnt thinking. I was trying to ping the core switch when the 3550 gave me this error: "% Unrecognized host or address, or protocol not running." Well, if you looked at my config, you would see that I had no ip address on vlan 1 (or any vlan in the config). Turns out that if you put an IP address on vlan 1 and then try to ping, you will overcome this error. Interesting enough for me to post it, as Im sure someone will benefit from this.
config t
interface vlan 1
ip add 192.168.1.1 255.255.255.0
exit
This is the retired Shane Killen personal blog, an IT technical blog about configs and topics related to the Network and Security Engineer working with Cisco, Brocade, Check Point, and Palo Alto and Sonicwall. I hope this blog serves you well. -- May The Lord bless you and keep you. May He shine His face upon you, and bring you peace.
Monday, April 30, 2012
Brocade (Foundry) Switch Upgrade Firmware: Step-by-Step
BR-telnet@FWS624G Router#copy tftp flash 192.168.2.52 FGSL07202f.bin secondary
BR-telnet@FWS624G Router#Flash Memory Write (8192 bytes per dot)
........................................................................................................................................................................................................................................................................................................................
...........................................................................
TFTP to Flash Done.
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#s sh ver
SW: Version 04.3.03T7e1 Copyright (c) 1996-2008 Foundry Networks, Inc.
Compiled on Oct 29 2009 at 15:48:07 labeled as FGL04303
(3286355 bytes) from Secondary /foundry/FGS/os/FGL04303.bin
BootROM: Version 05.0.00T7e5 (FEv2)
HW: Stackable FWS624G
==========================================================================
STACKID 0: SL 1: FastIron WS 624G 24-port Management Module
Serial #: AN10XXXXXX
P-ASIC 0: type D814, rev 01
==========================================================================
400 MHz Power PC processor 8248 (version 130/2014) 66 MHz bus
512 KB boot flash memory
30720 KB code flash memory
256 MB DRAM
The system uptime is 13 days 22 hours 25 minutes 54 seconds
The system started at 14:13:48 GMT+00 Mon Apr 16 2012
The system : started=warm start reloaded=by "reload"
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#wr mem
Write startup-config done.
BR-telnet@FWS624G Router#reload
Are you sure? (enter 'y' or 'n'): y
Halt and reboot
***Switch Rebooted***
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#sh ver
Copyright (c) 1996-2010 Brocade Communications Systems, Inc.
UNIT 1: compiled on Feb 16 2012 at 20:20:31 labeled as FGSL07202f
(3172304 bytes) from Secondary FGSL07202f.bin
SW: Version 07.2.02fT7e1
Boot-Monitor Image size = 416213, Version:05.0.00T7e5 (Fev2)
HW: Stackable FWS624G
==========================================================================
UNIT 1: SL 1: FastIron WS 624G 24-port Management Module
Serial #: AN10XXXXXX
License: FWS_BASE_L3_SOFT_PACKAGE (LID: cpGFHKIHMG)
P-ENGINE 0: type D814, rev 01
==========================================================================
400 MHz Power PC processor 8248 (version 130/2014) 66 MHz bus
512 KB boot flash memory
30720 KB code flash memory
256 MB DRAM
STACKID 1 system uptime is 44 seconds
The system : started=warm start reloaded=by "reload"
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#Flash Memory Write (8192 bytes per dot)
........................................................................................................................................................................................................................................................................................................................
...........................................................................
TFTP to Flash Done.
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#s sh ver
SW: Version 04.3.03T7e1 Copyright (c) 1996-2008 Foundry Networks, Inc.
Compiled on Oct 29 2009 at 15:48:07 labeled as FGL04303
(3286355 bytes) from Secondary /foundry/FGS/os/FGL04303.bin
BootROM: Version 05.0.00T7e5 (FEv2)
HW: Stackable FWS624G
==========================================================================
STACKID 0: SL 1: FastIron WS 624G 24-port Management Module
Serial #: AN10XXXXXX
P-ASIC 0: type D814, rev 01
==========================================================================
400 MHz Power PC processor 8248 (version 130/2014) 66 MHz bus
512 KB boot flash memory
30720 KB code flash memory
256 MB DRAM
The system uptime is 13 days 22 hours 25 minutes 54 seconds
The system started at 14:13:48 GMT+00 Mon Apr 16 2012
The system : started=warm start reloaded=by "reload"
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#wr mem
Write startup-config done.
BR-telnet@FWS624G Router#reload
Are you sure? (enter 'y' or 'n'): y
Halt and reboot
***Switch Rebooted***
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#sh ver
Copyright (c) 1996-2010 Brocade Communications Systems, Inc.
UNIT 1: compiled on Feb 16 2012 at 20:20:31 labeled as FGSL07202f
(3172304 bytes) from Secondary FGSL07202f.bin
SW: Version 07.2.02fT7e1
Boot-Monitor Image size = 416213, Version:05.0.00T7e5 (Fev2)
HW: Stackable FWS624G
==========================================================================
UNIT 1: SL 1: FastIron WS 624G 24-port Management Module
Serial #: AN10XXXXXX
License: FWS_BASE_L3_SOFT_PACKAGE (LID: cpGFHKIHMG)
P-ENGINE 0: type D814, rev 01
==========================================================================
400 MHz Power PC processor 8248 (version 130/2014) 66 MHz bus
512 KB boot flash memory
30720 KB code flash memory
256 MB DRAM
STACKID 1 system uptime is 44 seconds
The system : started=warm start reloaded=by "reload"
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
BR-telnet@FWS624G Router#
Monday, April 23, 2012
How to add a ShoreGear switch into the ShoreTel network
How to add a ShoreGear switch into the ShoreTel network:
Go to Trunks --> Trunk Groups.
Select the appropriate trunk group to add device to, OR add a new trunk group.
Select the services that should be appropriate for the service.
Go to Platform Hardware --> Voice Switches/Service Appliances --> Primary
Select the location at the top drop down menu and the type of device.
Configure device appropriately (Name, Description, IP Address, Ethernet Address, Port Type, Trunk Group)
Go to Users --> User Groups.
Select the appropriate user group and add access to the trunk group for the user group under "Outgoing Trunk Groups (Access Code):"
Go to Trunks --> Trunk Groups.
Select the appropriate trunk group to add device to, OR add a new trunk group.
Select the services that should be appropriate for the service.
Go to Platform Hardware --> Voice Switches/Service Appliances --> Primary
Select the location at the top drop down menu and the type of device.
Configure device appropriately (Name, Description, IP Address, Ethernet Address, Port Type, Trunk Group)
Go to Users --> User Groups.
Select the appropriate user group and add access to the trunk group for the user group under "Outgoing Trunk Groups (Access Code):"
Tuesday, April 10, 2012
Brocade Wireless Controller and DHCP Option 189
Ive been doing an install of a Brocade RS6000 wireless controller system, and I wanted to address something very important for the APs. The APs have to be able to know where to go to, to get to the controller. This is so that they can get firmware, config, etc. This is done by configuring a DHCP option. Its called option 189. By configuring this option, we can tell the APs what IP address the controller is, so that it can get what config that it needs.
Keep in mind that this piece is just for dealing with DHCP for your APs. Nothing else will be covered in this section today. So, here is what you would do:
1. Create your vlans as necessary.
2. Locate your DHCP server, and get the IP address information of the server.
3. Make sure you use the ip helper-address command on the vlan interface.
4. See map below for the rest:
Keep in mind that this piece is just for dealing with DHCP for your APs. Nothing else will be covered in this section today. So, here is what you would do:
1. Create your vlans as necessary.
2. Locate your DHCP server, and get the IP address information of the server.
3. Make sure you use the ip helper-address command on the vlan interface.
4. See map below for the rest:
Subscribe to:
Posts (Atom)