Table of Contents
Advertisement
Chapter 5
Setup and Configuration
Where:
• name is the name of the GOOSE tunnel
Type commit and press Enter to save the changes, or type revert and press Enter to abort.
3.
Section 5.31.6
Managing Remote Daemons for GOOSE Tunnels
In place of a local Ethernet interface for the tunnel egress, IP addresses for a remote daemon can be specified.
Several endpoints may be added with these fields using successive edits of the tunnel configuration.
The following sections describe how to configure and manage remote daemons for GOOSE tunnels:
•
Section 5.31.6.1, "Viewing a List of Remote Daemons"
•
Section 5.31.6.2, "Adding a Remote Daemon"
•
Section 5.31.6.3, "Deleting a Remote Daemon"
Section 5.31.6.1
Viewing a List of Remote Daemons
To view a list of remote daemons configured for a GOOSE tunnel, type:
show running-config tunnel l2tunneld goose tunnel name remote-daemon
Where:
• name is the name of the GOOSE tunnel
If tunnels have been configured, a table or list similar to the following example appears:
ruggedcom# show running-config tunnel l2tunneld goose tunnel 1 remote-daemon
tunnel
l2tunneld goose tunnel 1
remote-daemon 192.168.10.2
!
!
!
If no remote daemons have been configured, add daemons as needed. For more information, refer to
Section 5.31.6.2, "Adding a Remote
Section 5.31.6.2
Adding a Remote Daemon
To configure a remote daemon for a GOOSE tunnel, do the following:
1.
Make sure the CLI is in Configuration mode.
2.
Add the remote daemon by typing:
tunnel l2tunneld goose tunnel remote-daemon address
Where:
• address is the IP address of the remote daemon
484
Daemon".
Managing Remote Daemons for GOOSE Tunnels
RUGGEDCOM ROX II
CLI User Guide
Advertisement
Table of Contents
Troubleshooting
