For more details, please see ourCookie Policy.

Fibre Channel (SAN)

Senior Member
Posts: 1
Registered: ‎10-08-2014

SNMP date format changed for connUnitREventTime ( from MMDDYYYY to DDMMYYYY in v8.1.x vs. v7.4.x

[ Edited ]

Hello Community,

we started updating all 16Gbit / Gen5 switches from v7.4.2a > v8.0.2f > v8.1.2f.

We regognised that our nagios monitoring via SNMP (default unsing v2) failed after both updates on a DCX8510-8 (not sure if it stopped on v8.0.2f or v8.1.2f).

Troubleshooting lead to a change in the date / timestamp format for connUnitREventTime ( from MMDDYYYY to DDMMYYYY in the answer fro the switch.


I've cheked the FOS MIB references and it seems that the now active format DDMMYYYY is the correct one since ever.

MIB references 6.4, 7.4, 8.1 and 8.2 are showing "DDMMYYYY HHMMSS" as only possible option. It seems  to be the default format after some googling.


It is the same behavior for SNMP v2 and v3:


FOS v8.1.2f
# snmpwalk -v 2c -c public tsfcs01
iso. = STRING: "13122018 131449"

# snmpwalk -v 3 -u snmpuser1 tsfcs01
iso. = STRING: "13122018 131449"

FOS v7.4.2a
# snmpwalk -v 2c -c public tsfcs04
iso. = STRING: "12132018 131710"

# snmpwalk -v 3 -u snmpuser1 tsfcs04
iso. = STRING: "12132018 212143"
iso. = STRING: "12142018 063731"




Is this "working as designed" and why?

Can we change the output format?
We have a mix of Gen4 and Gen5 switches and can't update all to FOS v8.1.x and don't want to hack the Nagios monitoring for every switch.


Thanks in advance!


Join the Broadcom Support Community

Get quick and easy access to valuable resources across the Broadcom Community Network.