No dBm value on gig satellite ports when doing a show controller gig x/x/x/x phy

[Peter L]

Hi

For some reason there isn't any dBm showing when you do a show controllers gigabitEthernet x/x/x/x phy on a satellite gig port in an ASR9K. All "normal" ports are showing dBm and if i log into the satellite and do a show satellite powerlevels port x you get the dBm value. Seems like someone forgot to add the conversion from Watt to dBm for satellite ports when executing the show controllers gig phy command.  Im running 5.2.4 at the moment.

No dBm value

RP/0/RSP0/CPU0:asr9k#show controllers gigabitEthernet 1000/0/0/0 phy

Thu Sep  3 10:39:37.871 CET


          Port: 0

          Xcvr Type: SFP

          Vendor Name: CISCO-SUMITOMO

          CLEI Code: WMOTB8UAAA

          Part Number: 10-2294-01V01

          Product Id: ONS-SI-100-LX10

        Thresholds:                    Alarm High         Warning High          Warning Low            Alarm Low

              Temperature:                 105C                   95C                  -45C                  -45C

                  Voltage:               4000mV                3600mV                3000mV                2800mV

                     Bias:              70mAmps               60mAmps                0mAmps                0mAmps

           Transmit Power:                316uW                 199uW                  25uW                  15uW <--------Missing (dBm)

            Receive Power:               6553uW                6553uW                   0uW                   0uW <--------Missing (dBm)

        Temperature: 29 C

        Voltage: 3347 mV

        Bias: 4 mAmps

        Tx Power: 60 uW <-------Missing (dbm)

        Rx Power: 449 uW <------Missing (dbm)

when logged into satellite i can see dBm but i would like to see this without logging into the satellite.

LC:Satellite#show satellite powerlevels port 1

SFP Measurement Values for port:1

------------------------------


Thresholds:               Alarm High               Warning High               Warning Low                  Alarm Low

Temperature:                105.0000C                   95.0000C                   -45.0000C                   -45.0000C

Voltage:                 4000.0000uV                3600.0000uV               3000.0000uV                2800.0000uV

Tx Bias:                   70.0000mA                  60.0000mA                  0.0000mA                   0.0000mA

Tx Power:       0.3161mW (-5.0003dBm)     0.1994mW (-7.0005dBm)     0.0250mW (-16.0032dBm)     0.0157mW (-18.0134dBm)

Rx Power:       6.5534mW (8.1647dBm)     6.5534mW (8.1647dBm)     0.0000mW (0.0000dBm)     0.0000mW (0.0000dBm)


Temperature: 28.9257C

Laser Bias: 4.1299mA

Voltage: 3347.3999uV


Tx Power: 0.0603mW (-12.1896dBm)

Tx State: Normal


Rx Power: 0.4349mW (-3.6151dBm)

Rx State: Normal

Regards Peter

[Aleksandar Vidakovic · Accepted solution]

Hi Peter,

indeed, this was missed out in earlier releases. Starting with release 5.3.0 power levels on satellite access ports are displayed in dBm.

Regards,

Aleksandar

[Peter L]

Hi Aleksandar

Thanks for that speedy reply. The IOS-XR supportforum rocks!

One more question about optical levels and the satellite. Seems to be some delay on the levels that are reported when doing the show controller xxxx phy command. Is there some polling interval going on in the background when it comes to fetching optical levels from the satellite?

/Regards Peter

[xthuijs]

hi peter,

yeah some commands are "cached" this is to improve scale. Many commands can access the hw directly (eg show controller np counters) especially if they are single shot ones, but some of them need to be cached in order to maintain speedy cli access, fast results but yeah in that case there is a lag between instant and read value...

The other reason why this is needed is that many CPU's or NP's are much faster now adays than what the memory can realistically handle. hence memory banking and more intelligent memory controllers. For instance stats memory (we use QDR) has some specifics in that regard taht we have to deal with, hence we use caching and banking in order to maintain that performance we need.

If you like to read more about caching and all check this article that describes teh snmp methodology for caching

https://supportforums.cisco.com/document/132706/asr9000xr-understanding-snmp-and-troubleshooting

cheers!

xander

[Peter L]

Hi Alexander.

Thanks for the info. Will check that link out.

Regards Peter