Description of “Slot assignment” in /var/log/messages.
This informational message was added to assist in troubleshooting.
The message provides a history of the ap-vap-mapping and is automatically logged daily at midnight.
[I] Slot assignment: fw_a: 1->5 2m->6 fw_b: 1->7 2m->8 Spares: 9 10 11 12
fw_a_1 is running on slot 5
fw_a_2 is running on slot 6 (master vap)
fw_b_1 is running on slot 7
fw_b_2 is running on slot 8 (master vap)
Standby APMs: 9 10 11 12
error messages being reported by fw_a_2
After resetting some cards, the ap-vap-mapping has changed.
If error messages are being reported on a VAP group member, engineering will be able to determine the slot number. The slot number can always be determined at run time, but it is not possible to map the slot if cards are reset.
[I] Slot assignment: fw_a: 1m->5 2->4 fw_b: 1->6 2m->9 Spares: 3 7 8
fw_a_1 is running on slot 5 (master vap)
fw_a_2 is running on slot 4
fw_b_1 is running on slot 6
fw_b_2 is running on slot 9 (master vap)
Standby APMs: 3 7 8
In the above example, if error messages were being reported by fw_a_2 and after some cards were reset the same error message was being reported by fw_b_1, then engineering could focus on the APM in slot 6.