Folks,
This is what we got back from TAC Thu, 6 Feb 2014:
---
Thank you for update. Here is what I found:
this is day 1 behavior (always was there), it's a known issue which is tracked
by bug CSCuh86588.
the fix is being tested and will be included in 520 release, which is due in
mid-June 2014.
workaround, as you've already found, is to use CLI to capture tx/rx dBm values.
Please, let me know if this clarifies.
Regards
---
We did discover there is an internal SMU, but couldn't for love or money get a
copy of it out of TAC.
For ref, our SR is 629053585. If anyone else has this problem and would be
prepared to
share their SR then please do sent me a copy so I can poke our SE team.
Steve
On Mon, 12 May 2014, Jared Mauch wrote:
It has not been fixed and has been junked by cisco as an “enhancement” vs “bug”
- Jared
On May 12, 2014, at 8:27 AM, gu...@golas.ru wrote:
Hello Nikolay,
I opened case for this issue for 4.3.1 in august 2013. Cisco promised fix in
5.1.1. Created DDTS CSCuh86588.
I can confirm that issue doesn't fixed in 5.1.1.
On Mon, 12 May 2014 15:49:54 +0400
Nikolay Shopik <sho...@inblock.ru> wrote:
Hey,
Does anyone have DOM information in SNMP on IOS XR (ASR9001)? All we got
is -32768 on all modules. So far we only tested on 4.3.2, just wonder if
they actually fixed on more recent releases.
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
Alexandr Gurbo
_______________________________________________
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
