Raslog configuration, Brocade vcs fabric raslog, Displaying the raslog messages – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 75

Network OS NETCONF Operations Guide
43
53-1003231-02
RASlog configuration
3
<edit-config>
<target>
<running/>
</target>
<config>
<logging xmlns="urn:brocade.com:mgmt:brocade-ras">
<syslog-server xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
operation="delete">
<syslogip>192.168.163.236</syslogip>
</syslog-server>
</logging>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="326" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
RASlog configuration
RASlog messages record system events filtered by configured severity levels. Each message
includes a timestamp, a message ID, an external sequence number, a severity level, the chassis
name, and the message body. Using NETCONF interfaces, you can configure RASlog to filter
messages by severity level.
To clear RASlog messages requires the Network OS command line interface (CLI). For more
information on RASlog messages, refer to the Network OS Message Reference.
Brocade VCS Fabric RASlog
Brocade VCS Fabric RASlog messages are supported in the fabric cluster. A Brocade VCS Fabric
RASlog message can be generated from any node and is distributed to all nodes in the cluster. Its
primary use is to broadcast Fabric-wide events.
A Brocade VCS Fabric RASlog message has the same format as a normal RASlog message, with
additional attributes: Brocade VCS Fabric and RBridge ID.
Displaying the RASlog messages
To display the RASlog messages, issue the <show-raslog> custom RPC located in the
urn:brocade.com:mgmt:brocade-ras-ext namespace.
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="327">
<show-raslog xmlns="urn:brocade.com:mgmt:brocade-ras-ext"/>
</rpc>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="327">
<show-all-raslog xmlns="urn:brocade.com:mgmt:brocade-ras-ext">
<rbridge-id>tengigabitethernet</interface-type>
<number-of-entries>237</number-of-entries>
<raslog-entries>
<index>13187</index>
<message-id>NSM-2006</message-id>
<date-and-time-info>2000-03-11/20:12:03.1234</date-and-time-info>