SMA SNMP configuration problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2019 06:55 AM
I have a Cisco management appliance running version 13.0.0-187 and I am trying to configure snmp, when I type snmpconfig I get the error The session is closed immediately.
Has anyone seen this before?
- Labels:
-
Email Security

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2019 05:23 PM
Hey Mohamed,
Thank you for bringing this to my attention.
I found the issue and filed a new bug against -> CSCvr73392
This bug is still under review to go into customer facing in due time.
In the mean time, please open a cisco TAC ticket so we can apply the workaround fix for you.
We need the tunnel open to make this change.
Thanks,
Mathew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2019 11:54 PM
Hi Mathew,
thank you very much, I will open a TAC case.
thanks
Mohamed

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2019 12:24 AM
Can i quickly confirm if this is a Cloud Device or an on-prem/virtual?
Also which version was your SMA on prior to the upgrade.
Thanks,
Mathew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2019 12:37 AM
Hi Mathew,
This is an on-prem virtual appliance and the problem persists since we migrated to version 12.5 before that we were on version 11
Thanks
Mohamed

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2019 12:46 AM
Interesting - 12.5 on my lab environment had no issues, but when we took it to version 13 I saw this behaviour.
Keep me posted on your TAC issue if you could.
Thanks,
Mathew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2019 12:49 AM
Hi Mathew,
Okay I will.
We are running version 13 now yes but we also had the same problem on version 12.5
will keep you posted.
thanks

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2019 03:01 PM
If you have logged your CLI session when the traceback occurs you will see the traceback error:
m300v.lab> snmpconfig
Current SNMP settings:
Listening on interface "Management" 10.66.71.27/24 port 161.
SNMP v3: Enabled.
Traceback (most recent call last):
File "/usr/build/iproot/ap/ipoe/ipoe/bootstrap.py", line 55, in <module>
File "/data/lib/python2.6_10_amd64_nothr/runpy.py", line 128, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/data/lib/python2.6_10_amd64_nothr/runpy.py", line 34, in _run_code
exec code in run_globals
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/cli.py", line 40144, in <module>
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/cli.py", line 29245, in main
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/cli.py", line 892, in command_loop
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/cli.py", line 36827, in do_command
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/cli.py", line 37078, in main_input_run
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/cli.py", line 36840, in run_func
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/cli.py", line 29788, in snmpconfig
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/snmp/snmp_cli.py", line 231, in cli_main
File "build/bdist.freebsd-10.4-RELEASE-amd64/egg/snmp/snmp_cli.py", line 198, in show_status
IndexError: list index out of range
This is due to https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr73392
I updated the bug as it looks like the issue occurred on 12.5 and if upgraded to version 13, the issue carries forward.
Regards,
Mathew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2019 12:15 AM
Hi Mathew,
Thank you for your feedback.
I still couldn't contact the TAC because I am waiting for them to give me the contract number as it's a VM so there's no serial number.
and yes we upgraded from 12.5 to 13 so this seems to be our case.
thanks
