11-16-2018 07:01 AM - edited 03-01-2019 03:44 AM
# show chassis environment detail Chassis 1: Overall Status: Operable Operability: Operable Power State: Ok Thermal Status: Ok
Cisco Firepower Extensible Operating System (FX-OS) Software
# show system version FPRM: Running-Vers: 4.3(1.74) Package-Vers: 2.3(1.56) Activate-Status: Ready
11-16-2018 07:58 AM
This is what you looking for i guess :
11-16-2018 08:14 AM
Hi Balaji,
Thanks for the reply. Yes, I think a subset of those is what I'd need. Does the following indicate that I have to have someone enable these MIBs on the device or am I attempting to query this information incorrectly? I appreciate the assistance.
$ snmpwalk -v2c -c ${COMMUNITY} ${DEVICE} CISCO-FIREPOWER-POWER-MIB No log handling enabled - turning on stderr logging CISCO-FIREPOWER-POWER-MIB: Unknown Object Identifier (Sub-id not found: (top) -> CISCO-FIREPOWER-POWER-MIB)
11-16-2018 09:50 AM
Before loading FXOS MIBs into an NMS, you must first load the prerequisite MIBs into the NMS. This enables you to receive the FXOS Fault Traps in the NMS.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide