I'm new to the forum and I'm having issues with an old brocade 5000 I recently purchased (second-hand).
I can't install ezswitchsetup 6.2. It gets stuck at "Installing... Uninstall_EZSwitchSetup". Compatibility settings don't help and on linux it fails with "libc.so.6 cannot open shared object file" errors. v7 of the software does not discover the switch (nor does v8), what can I do to resolve this minor annoyance?
Windows 10 and Fedora 26 (x64)
Thanks and kind regards
for some extra info:
When switching over to the default subnet (255.0.0.0), when I ping the default IP (10.77.77.77) I get request timed out. So does navigating to it in the browser (time out)
So what could be the issue here?
under linux you might need 32 bit library to it to work (you are on a 64 version). This is a 32 bit application. For the setup, I would use 10.77.77.77 with the subnet 255.255.255.0. You can always connect via the serial cable to the console to switch (9600 baud, no flow, 8, N, 1 stop bit). Which version of Java are using? Last version for the 5000 is 6.4 (FOS and ezswitchup).
I tried the 32bit libs and then started getting java errors. I might need an older version of java for that.
Serial cable... will a cisco serial cable work? I didn't get a serial cable with the switch, unfortunately. If it works, I will need to find a device that has a rs-232/serial port... too bad modern day tech does not cover that anymore.
should I use 10.77.77.77 as my IP address? or is that the default IP for the device?
--->>>I'm new to the forum and I'm having issues with an old brocade 5000 I recently purchased (second-hand).
those switches since are used, at 99,999% is the IP not set as default 10.77.77.77
as the word say EZswitchsetup, the software can discovery setup the switch when the IP is set to default, which for sure is not.
at this point you need to connect trough the serial port as admin and check the IP address
as Antonio said - if it brand new or correctly reset, the 5000 would use 10.77.77.77 / 255.255.255.0 but since this a second hand, we cannot be sure. The serial port’s parameters are fixed at 9600 baud, 8 data bits, and no parity, with flow control set to None.
The pinout of the cable (RJ45) is as follows
1 Not supported NA2 Not supported NA3 UART1_TXD Transmit data4 GND Logic ground5 GND Logic ground6 UART1_RXD Receive data7 Not supported NA8 Not supported NA
As luck has it, I have 5000 standby beside and I do a test rum of EZswitchsetup 6.2
the Ezswitchsetup 6.2 hangs on my Windows 10, and I give up on that.
I managed to get the installation started on my Centos 7.3 machine by hacking the installation script:
$ chmod 755 * .
$ sed -e "s/linux_LD_ASSUME_KERNEL_hack=1/linux_LD_ASSUME_KERNEL_hack=0/" < install.bin >install.bin.hx
$ chmod 755 ./install.bin.hx
I realised my pfsense box has a serial port and used that.
Yeah, the device has not been reset, so the password is unknown. I spoke the the guy I bought it from and they will find out if he can get the password.
Ok, I got a replacement switch, which I can log into via the console cable.
however, the EZswitchsetup still does not detect the switch and I did set an IP address in my subnet and network.
Also if I go to my switches IP address in my browser (with java exception added) and nothing... times out
anything I am missing?
from the server / desktop which you run ezswitchup, can you use ssh to get into your switch - to verify login information and ip reachability? For the java error, can you please share a little information kind of error you are getting, please?
I checked now... nope.
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014debug1: Reading configuration data /etc/ssh/ssh_configdebug1: /etc/ssh/ssh_config line 19: Applying options for *debug2: ssh_connect: needpriv 0debug1: Connecting to xx.xx.xx.xx [xx.xx.xx.xx] port 22.debug1: connect to address xx.xx.xx.xx port 22: Resource temporarily unavailablessh: connect to host xx.xx.xx.xx port 22: Resource temporarily unavailable
but when I use ipaddrshow... it has the IP/subnet/gateway I need... which is not working, unfortunately
also the sshd_config looks like it is untouched
edit to add: I can't ping from the switch as well...
F2_SW52:root> ping 220.127.116.11PING 18.104.22.168 (22.214.171.124): 56 octets data
--- 126.96.36.199 ping statistics ---12 packets transmitted, 0 packets received, 100% packet loss
F2_SW52:root> chkconfig |grep sshdsshd on
Hostname will be changed, once I get it on the network.
iptables for ssh
Chain ssh0 (1 references)target prot opt source destinationACCEPT tcp -- anywhere anywhere tcp dpt:ssh
the only reject in iptables is for ICMP, which is fine by me in anyway
found the issue... my switch needed a restart. A bit odd, but that was the issue.
I noticed my network slowing down and decided to restart my switch and voila, fixed.