-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We are having an issue with our Cisco WiSM devices. When we model them,
they look like AirespaceBG models, which is expected as they are
basically re-branded Airespace controllers, however after a while they
will tend to throw "Unable to Identify Device" alarms. We can continue
to poll the devices, but if we try to hit "Reconfigure Model" it throws
an error like it can't read the sysObjID attribute. If we try to read it
directly through MIB Tools, it polls just fine. The only way we can seem
to remedy the issue is by deleting and remodeling.

Anybody had anything similar happen, or have any ideas on what could be
causing this?
- --
Brett Davis
IT Network and Security Operations
Cisco Certified Network Associate (CCNA)
Purdue University
YONG 605
Phone (765) 49-62304
[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkj0x5UACgkQ+j4RojbPFmBLywCgl11ddL2UyyABa0mKMGeCLxKP
1uYAn2+D9/Bif5aL/2ksJQDnuDE4Qgzp
=OVjQ
-----END PGP SIGNATURE-----

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to