Cisco Cisco UCS 6120XP 20-Port Fabric Interconnect 기술 매뉴얼
Configure
The Cisco UCS Manager starts the syslog daemon and makes certain that it is active in both UCS fabric
interconnects. Logs generated by the processes in the NXOS and UCS Manager are exported to the same
configured external collectors.
interconnects. Logs generated by the processes in the NXOS and UCS Manager are exported to the same
configured external collectors.
All UCS Manager events are stored in the same fabric they were generated. As expected the passive fabric
interconnect will generate less log entires than the active, but some events are still expected. In order to ease
the parsing of the logs, all entries by the UCS Manager include the UCS hostname while the NXOS entries
include the fabric hostname.
interconnect will generate less log entires than the active, but some events are still expected. In order to ease
the parsing of the logs, all entries by the UCS Manager include the UCS hostname while the NXOS entries
include the fabric hostname.
These are a few examples of situations that will generate a syslog entry:
DME lifecycle events
•
Faults
•
Ad−hoc messages
•
Events relayed by the BMC and CMC processes
•
Network Diagram
This is a typical topology used with Cisco UCS:
Steps to Configure Syslog to a Local File
This is the procedure:
Log in to Cisco UCS Manager.
1.
In the navigation pane, choose the Admin tab.
2.
Expand Faults, Events and Audit Log, then choose Syslog.
3.
In the work pane to the right, under File, choose enabled for the Admin State.
4.
Choose the alarm level from the drop down menu.
5.
Click Save Changes.
6.