Hello Baicells community,
I am trying to recover a Nova 227 LTE eNodeB (hardware module pBS11003, revision A, 2300–2400 MHz) running BaiBS_RTS_3.7.11.8. It uses a remote EPC. I do not have access to a Baicells OMC.
The local web GUI loads an unstyled login page and cannot complete login. I tested both HTTP and HTTPS in different Chromium browsers. The lighttpd server responds with HTTP 200 for the CSS and JS files, and their contents look like real CSS/JS, but it sends conflicting Content-Type headers. For example, a CSS file is returned with both “Content-Type: text/css; charset=utf-8” and “Content-Type: text/html; charset=utf-8”, together with “X-Content-Type-Options: nosniff”. JS files similarly receive both application/javascript and text/html. The browser reports errors such as “$ is not defined”, “MIBContainer is not defined”, and “doLogin is not defined”. This appears to explain the broken web GUI, but I have not established what adds the extra Content-Type header.
SSH on the device’s configured port still works with the admin account. I can enter enable mode (CELL#), run “show software version”, “show equipment”, and “show listenning port”, but “ls” and “cat /etc/lighttpd/lighttpd.conf” return “You are not permited to access file system”. “show syslog last-line 60” returns “Can not have required syslog!”. The CLI help lists “upgrade img URL” for an image accessible over HTTP(S)/FTP.
After I rebooted the eNodeB, the private LTE network also stopped working. SNMP is no longer responding; the output of “show listenning port” did not show UDP 161. HTTP/HTTPS and SSH are listening. I do not yet know whether the LTE failure is due to the eNodeB, its link to the remote EPC, or another configuration/service issue. I have several CellConfig backups, but each archive contains only config/mib-home-fap.nv, not a firmware image.
Could you advise on:
- The supported diagnostic commands for cell status, S1/MME connectivity, SNMP, and the web server on RTS 3.7.11.8, given the filesystem permission denial?
- How to correct the duplicate Content-Type response headers, or whether a firmware reinstall is the supported repair?
- An official, stable RTS .IMG compatible with Nova 227 pBS11003 and a remote EPC, including the download location and checksum? Should we remain on 3.7.11.8, update, or roll back?
- The supported recovery procedure via “upgrade img URL”, including configuration preservation and what to do if image validation or upgrade fails? Is rollback possible over SSH without OMC access?
I can provide more non-sensitive diagnostics if needed. Thank you.