No DDMI page in the web GUI on Zyxel XGS3700 and GS2210 while the GS1910 shows it
I look after a mixed Zyxel estate on one site and I am putting together a vrey basic optical health check for the fibre uplinks: temperature and Rx power per port, so I can see a link degrading before the users report it.
What is involved:
- Zyxel GS1910, older access switch with SFP uplinks
- Zyxel XGS3700 with SFP+ modules on the uplinks
- Zyxel GS2210 with 1G SFP modules
- all modules are Zyxel branded, nothing third party
On the GS1910 the DDMI figures sit right there in the web interface, which is where I got used to reading them. On the other two boxes I cannnot find that page anywhere:
# what each box gives me in the web GUI
GS1910 : DDMI page - temperature, supply voltage, bias current, Rx/Tx power
XGS3700 : nothing under the port pages
GS2210 : nothing under the port pages
What I already did:
- walked the whole monitoring and port section on both switches, page by page
- reseated one module in case the switch simply was not reading it
- went back to the GS1910 to be sure I was not chasing a page that never existed
So: is the DDMI data on the XGS3700 and GS2210 hidden under some menu I have not thought of, or do these series genuinely not expose it in the web interface at all? If there is another way to get at the numbers I would rather use that than scrape screens.
Comments 3
The page is not hidden, it is simply not there. On the XGS3700 and GS2210 the transceiver diagnostics are reachable only from the command line:
What comes back per port is a plain text block: the module identity first, then the five measured values - bias current, Tx power, Rx power, supply voltage and temperature. The same numbers the GS1910 draws for you, minus the page.
Why the boxes differ is a question of release history, not hardware. Zyxel put the DDMI page into the web interface in firmware 4.60, and neither of these two series was ever slated to receive that branch, so no update is going to bring the page to them. The CLI is the route there and it stays the route.
For the health check you are building that means two code paths in the poller: SNMP or the GUI wherever firmware 4.60 and later is available, and text parsing for these two series. Not elegant, but the CLI output is stable and easy enough to pick apart per port, and you end up with the same five values either way.
Before you keep hunting through menus, split the question in two: do you need that specific web page, or do you just need the numbers? On this family those are different problems with different answers.
It would also help to say which firmware branch each box is running, because that is what decides whether the GUI has a diagnostics page at all, and to confirm what the modules themselves support. A module without a diagnostic page will show nothing anywhere, GUI or command line, and then no amount of menu digging helps.
Worth knowing the other reason those fields go missing, because it looks identical from the monitoring side.
On a FortiGate here,
get system interface transceiverprints temperature, voltage, Tx bias, Tx power and Rx power, and a good half of the ports came back as N/A. Three different causes in the end: optics with no diagnostic page at all, which is normal for older or budget 1G SFPs, passive direct-attach copper, which is electrical and has nothing optical to report in the first place, and exactly one module that really was not being read - that one had a 'not detected' line beside it and turned out to be seating.Rule I use now: N/A next to a healthy link is not worth chasing, N/A together with 'not detected' is physical. Cisco has the same split at module level, GLC-SX-MM has no A2h diagnostics page so
show interface transceiver detailhas nothing to print for it, while the MMD variant does. Same optics otherwise.