ISWEB-RT3 Strange web / http access behaviour
 General questions - what UPS fits best for your use?   Started by NB-23   2024-09-04 13:15:51 +01:00   Comments: 2    Viewed: 93

  1. NB-23
    NB-23 Member Warrington
    We've recently worked on a strange aspect of the ISWEB card behaviour. I think other people will find the same thing, and posting here to hopefully save somone unneccessary effort spent + stress.

    Read the info from the bottom up as its an email chain.
    NB-23, 2024-09-04 13:15:51 +01:00
    #69
  2. NB-23
    NB-23 Member Warrington
    Hi Nathan,
     
    Sure thing, I hope this will be able to help save someone else a lot of
    head scratching!
     
    It is an odd one, the card is perfectly performant now it is up so the
    long load times don't make a lot of sense. Port 443 seems to have its
    own problems with outdated ciphers not supported by modern browsers, but
    I'll be sure to check if it comes up quicker next time I reboot. Either
    way I'm not going prod a good thing too much.
     
    All the best and thanks again!
     
    Christian
     
    On Thu, Aug 29, 2024 at 12:54:35PM +0000, UPS-Trader Shop wrote:
     
    Hi Christian
     
    its an odd thing! I feel I'm missing something still as it does not make
    sense yet.
    I wonder if 443 works better. I doubt it as its going to put extra load on a
    card with what is quite a small brain!
     
    Are you happy if I make a post in our forum showing all of this email? It
    will be google searchable and might help someone.
     
    I can zap the names.
     
    //Nathan
     
     
     
     
     
    ------ Original Message ------
    Date 29/08/2024 12:46:44
    Subject Re: IS-WEBRT3 access issue
     
    > Hi Nathan,
    >
    > That seems to be it! I rebooted the UPS and left it for a few hours connected
    > to an old router. Eventually the web interface came up an I was able to access
    > and set a static IP.
    >
    > After this I unplugged the network cable and moved it to my switch without
    > rebooting. I again had to wait around four hours for the web interface to
    > become accessible, but did come up again on the IP address I had set.
    > Interestingly, I was immediately able to ping and scan the UPS even though the
    > web interface was not yet accessible. The scan produced the following output:
    >
    > > PORT STATE SERVICE VERSION
    > > 21/tcp open ftp Power Shield UPS ftpd
    > > 23/tcp open telnet?
    > > | fingerprint-strings:
    > > | GenericLines:
    > > | <<<<< UPS SNMP IS-WEBRT3 Setup Program >>>>>
    > > | <<<<<--------------------------------------------->>>>>
    > > | Press any key to continue .......
    > > | User Name:
    > > | Password:
    > > | GetRequest:
    > > | <<<<< UPS SNMP IS-WEBRT3 Setup Program >>>>>
    > > | <<<<<--------------------------------------------->>>>>
    > > | Press any key to continue .......
    > > | User Name: ET / HTTP/1.0
    > > | Password:
    > > | <<<<< Main Menu >>>>>
    > > | <<<<<---------------------------------->>>>>
    > > | Address.
    > > | SNMP MIB System.
    > > | SNMP Access Control.
    > > | SNMP Trap Notification.
    > > | Properties.
    > > | Devices Connected.
    > > | System Time & Time Server.
    > > | Telnet User Account.
    > > | E-mail.
    > > | Reset Configuration to Default.
    > > | Save & Reboot.
    > > | Exit Without Saving.
    > > | Select =>
    > > | NULL:
    > > | <<<<< UPS SNMP IS-WEBRT3 Setup Program >>>>>
    > > | <<<<<--------------------------------------------->>>>>
    > > | Press any key to continue .......
    > > | tn3270:
    > > | <<<<< UPS SNMP IS-WEBRT3 Setup Program >>>>>
    > > | <<<<<--------------------------------------------->>>>>
    > > | Press any key to continue .......
    > > | User Name:
    > > |_ IBM-3279-4-E
    > > 80/tcp open http?
    > > 443/tcp open https?
    >
    > I don't know enough about SNMP to say if this is what is causing the hold up,
    > but I have never seen this sort of output on nmap before. Anyway, I hope it
    > may be of some use/interest for anyone else having this problem.
    >
    > Thank you again for your help on getting this up and running, I truly
    > appreciate it.
    >
    > Kind regards,
    > Christian
    >
    > On Thu, Aug 22, 2024 at 08:07:25AM +0000, UPS-Trader Shop wrote:
    > > Hi Christian
    > >
    > > re-reading my emails
    > >
    > > I will have let our Draytek hub/router assign the IP for the card
    > > then, at first it seems I couldn't find open ports and planned to
    > > investigate further. Later in the day it seems the the card was running
    > > without me having done any more investigating! We might be dealing with
    > > either long boot times, or a card fail over to default settings after a
    > > certain time. The timestamp differences on my emails is about an hour.
    > >
    > > //Nathan
    > >
     
    > >
    > > ------ Original Message ------
    > > Date 21/08/2024 17:20:40
    > > Subject Re: IS-WEBRT3 access issue
    > >
    > > > Hi Nathan,
    > > >
    > > > I emailed a few months ago about my UPS's network card. My sincere apologies:
    > > > your prompt reply got memory-holed by my overactive spam filter shorty before I
    > > > went on an overseas trip, so I completely missed it at the time. Thanks for
    > > > taking a look into this; its good to know at least this is a known issue!
    > > >
    > > > I have taken another look and tried to retrace your steps. I fear I may have
    > > > been too hasty saying I could ping the UPS--I think I actually assigned an IP
    > > > to the host interface and pinged my own machine rather than the UPS on the
    > > > other end (at least that's all I can do now, my bad). I used nmap to scan for
    > > > devices across the 192.168.0.0/16 address range but did not find anything.
    > > > However, I can see there is a carrier signal present when I plug in the network
    > > > cable. What were the steps you undertook to assign an IP and scan the UPS?
    > > > I'll try to recreate.
    > > >
    > > > If on the other hand it can be reset with a jumper I might be able to reset it
    > > > myself if I can get access. Can I just unscrew and pull it out or are there
    > > > some specific steps I need to do it safely?
    > > >
    > > > Other than that the UPS itself has been working wonderfully in the meantime!
    > > >
    > > > All the best,
    > > > Christian
    > > >
    > > > On Mon, Mar 11, 2024 at 04:18:30PM +0000, UPS-Trader Shop wrote:
    > > > > Ok this is weird, I got some time to investigate further, and its just
    > > > > working now.
    > > > > The card has been in a test UPS since earlier today.
    > > > > nmap standard shows only 443 open
    > > > > but with the -A flag I do get the http ports
    > > > >
    > > > > Nmap scan report for 192.168.2.112
    > > > > Host is up (0.0011s latency).
    > > > > Not shown: 985 filtered ports
    > > > > PORT STATE SERVICE VERSION
    > > > > 21/tcp open tcpwrapped
    > > > > |_ftp-anon: got code 500 "account error".
    > > > > 22/tcp closed ssh
    > > > > 53/tcp closed domain
    > > > > 80/tcp open tcpwrapped
    > > > > 110/tcp closed pop3
    > > > > 113/tcp closed ident
    > > > > 256/tcp closed fw1-secureremote
    > > > > 445/tcp closed microsoft-ds
    > > > > 700/tcp closed epp
    > > > > 993/tcp closed imaps
    > > > > 995/tcp closed pop3s
    > > > > 5718/tcp closed dpm
    > > > > 5900/tcp closed vnc
    > > > > 8080/tcp closed http-proxy
    > > > > 8180/tcp open tcpwrapped
    > > > >
    > > > >
    > > > >
    > > > >
    > > > >
    > > > > //Nathan
    > > > >
    >
    > > > >
    > > > >
    > > > >
    > > > > ------ Original Message ------
    > > > > Date 11/03/2024 15:06:50
    > > > > Subject Re: IS-WEBRT3 access issue
    > > > >
    > > > > > Howdy
    > > > > >
    > > > > > its not the first time! We have a draytek router which we use as a DHCP
    > > > > > server. We've had customers with cards that would not handshake, we get
    > > > > > them back with the intent of setting a static IP for them and they still
    > > > > > auto-assign on our network.
    > > > > >
    > > > > > You've got past the IP stage now it seems.
    > > > > >
    > > > > > I'll get another card out here and see what the nmap polls. I'm having
    > > > > > trouble this side too. Its a while since I've reset one of these. I'm
    > > > > > thinking some jumpers were left unset... let me investigate further and
    > > > > > come back to you when I have a solution.
    > > > > >
    > > > > > I initially saw plenty of ports open but now just Telnet/23, the same as
    > > > > > you.
    > > > > >
    > > > > > //Nathan
    > > > > >
     
    > > > > >
    > > > > >
    > > > > >
    > > > > > ------ Original Message ------
    > > > > > Subject IS-WEBRT3 access issue
    > > > > >
    > > > > > > Hello,
    > > > > > >
    > > > > > > I recently purchased a Liebert / Emerson PS1500 RT3 UPS with the
    > > > > > > IS-WEBRT3 network card (transaction ID: 6KC64870EN8993152). The UPS
    > > > > > > itself works great, but I have been unable to access it over a network.
    > > > > > >
    > > > > > > The attached note indicated it would use DHCP to obtain an IP address,
    > > > > > > and no password set. However, after plugging it in to my switch no IP
    > > > > > > address is assigned, and my DHCP server logs do not indicate any attempt
    > > > > > > is made to acquire one. I also tried plugging it into my ISP router
    > > > > > > which has its own DHCP server, with the same result.
    > > > > > >
    > > > > > > I was able to plug it into my laptop and assign a static IP address,
    > > > > > > this allowed me to ping the device. I port scanned it using nmap (log
    > > > > > > below) which shows only SSH (for which I don't have the key, and it does
    > > > > > > not ask for a password) and RPC are running. There does not appear to
    > > > > > > be a way to access the web interface for further configuration.
    > > > > > >
    > > > > > > Please could you let me know how to proceed, and if you need further
    > > > > > > diagnostics don't hesitate to ask.
    > > > > > >
    > > > > > > Many thanks in advance,
    > > > > > >
    > > > > > > Christian
    > > > > > >
    > > > > > >
    > > > > > >
    > > > > > > # nmap -A 192.168.0.80/32
    > > > > > >
    > > > > > > Nmap scan report for 192.168.0.80
    > > > > > > Host is up (0.000056s latency).
    > > > > > > Not shown: 998 closed tcp ports (reset)
    > > > > > > PORT STATE SERVICE VERSION
    > > > > > > 22/tcp open ssh OpenSSH 9.6 (protocol 2.0)
    > > > > > > | ssh-hostkey:
    > > > > > > | 256 77:75:e6:a0:d5:eb:87:2a:ec:5c:a0:3e:7d:78:23:51 (ECDSA)
    > > > > > > |_ 256 b1:83:63:6c:db:ca:11:ab:bf:02:68:79:2c:5a:2b:bc (ED25519)
    > > > > > > 111/tcp open rpcbind 2-4 (RPC #100000)
    > > > > > > | rpcinfo:
    > > > > > > | program version port/proto service
    > > > > > > | 100000 2,3,4 111/tcp rpcbind
    > > > > > > | 100000 2,3,4 111/udp rpcbind
    > > > > > > | 100000 3,4 111/tcp6 rpcbind
    > > > > > > | 100000 3,4 111/udp6 rpcbind
    > > > > > > | 100021 1,3,4 32885/udp6 nlockmgr
    > > > > > > | 100021 1,3,4 38575/tcp6 nlockmgr
    > > > > > > | 100021 1,3,4 43593/tcp nlockmgr
    > > > > > > | 100021 1,3,4 60269/udp nlockmgr
    > > > > > > | 100024 1 49915/tcp6 status
    > > > > > > | 100024 1 51389/tcp status
    > > > > > > | 100024 1 57280/udp status
    > > > > > > |_ 100024 1 59532/udp6 status
    > > > > > > No exact OS matches for host (If you know what OS is running on it, s
    > > > > > > TCP/IP fingerprint:
    > > > > > > OS:SCAN(V=7.94%E=4%D=3/2%OT=22%CT=1%CU=44188%PV=Y%DS=0%DC=L%G=Y%TM=65E286F1
    > > > > > > OS:%P=x86_64-pc-linux-gnu)SEQ(SP=105%GCD=1%ISR=109%TI=Z%CI=Z%II=I%TS=A)OPS(
    > > > > > > OS:O1=MFFD7ST11NW7%O2=MFFD7ST11NW7%O3=MFFD7NNT11NW7%O4=MFFD7ST11NW7%O5=MFFD
    > > > > > > OS:7ST11NW7%O6=MFFD7ST11)WIN(W1=8200%W2=8200%W3=8200%W4=8200%W5=8200%W6=820
    > > > > > > OS:0)ECN(R=Y%DF=Y%T=40%W=8200%O=MFFD7NNSNW7%CC=Y%Q=)T1(R=Y%DF=Y%T=40%S=O%A=
    > > > > > > OS:S+%F=AS%RD=0%Q=)T2(R=N)T3(R=N)T4(R=Y%DF=Y%T=40%W=0%S=A%A=Z%F=R%O=%RD=0%Q
    > > > > > > OS:=)T5(R=Y%DF=Y%T=40%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6(R=Y%DF=Y%T=40%W=0%S=A
    > > > > > > OS:%A=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=Y%T=40%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)U1(R=Y
    > > > > > > OS:%DF=N%T=40%IPL=164%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G%RUD=G)IE(R=Y%DFI=N%T
    > > > > > > OS:=40%CD=S)
    > > > > > >
    > > > > > > Network Distance: 0 hops
    > > > > > >
    > > > > > > OS and Service detection performed. Please report any incorrect results at
    > > > > > > Nmap done: 1 IP address (1 host up) scanned in 30.96 seconds
    > > >
    NB-23, 2024-09-04 13:19:54 +01:00
    #70
  3. (You must log in or sign up to post here)

Report Post

Write your reason

Log in | Sign up
Terms & Conditions!
Help!