12.07.2013 Views

Designing and Implementing a Junos Node Unifier Network

Designing and Implementing a Junos Node Unifier Network

Designing and Implementing a Junos Node Unifier Network

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

System Logging in the JNU <strong>Network</strong><br />

Related<br />

Documentation<br />

Copyright © 2013, Juniper <strong>Network</strong>s, Inc.<br />

Each device in the JNU group, including the controller, originates its own system log<br />

messages (called syslog messages). The hostname in messages sent from satellites<br />

<strong>and</strong> the controller is the hostname configured during the JNU initialization process. The<br />

syslog server uses the hostname to identify the JNU device that originated the message.<br />

Figure 7 on page 89 shows how log messages are processed for JNU satellites.<br />

Figure 7: System Logging Collection Process<br />

•<br />

NAT is<br />

applied<br />

2<br />

Syslog server<br />

3<br />

<strong>Network</strong> interface<br />

1<br />

Satellites<br />

Management Plane<br />

1— The satellite sends a syslog message to the 3— The controller sends the log message to the<br />

controller.<br />

syslog server.<br />

2—The controller applies NAT to the syslog<br />

message so that the message source is the<br />

management IP address of the controller.<br />

Centralized Collection of SNMP Statistics <strong>and</strong> Log Messages Overview on page 85<br />

• SNMP Get Process in the JNU <strong>Network</strong> on page 87<br />

• SNMP Trap Process in the JNU <strong>Network</strong> on page 88<br />

g041398<br />

Chapter 10: Monitoring in the JNU <strong>Network</strong><br />

89

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!