Accessing An Irf Virtual Device; Accessing The Master; Accessing A Slave - 3Com Switch 4800G 24-Port Configuration Manual

Do not set the delay time to a very long time; otherwise, the IRF virtual device will not be aware of the
IRF topology changes in time and thus the service will be recovered slowly.

Accessing an IRF Virtual Device

Accessing the Master

Access an IRF virtual device in either of the following two ways:
Local login: Log in through the AUX or console port of a member device.
Remote login: Configure an IP address for a Layer 3 Ethernet interface of a member device and
make sure that the route is reachable, and then access the IRF virtual device remotely through
Telnet, Web, or SNMP.
When you log in to the IRF virtual device, actually you log in to the master. The master is the
configuration and control center of an IRF virtual device. When you configure the IRF virtual device on
the master, the IRF virtual device synchronizes the configurations to the slaves.

Accessing a Slave

When you log in to an IRF virtual device, actually you log in to the master. The operation interface of the
access terminal displays the master console. To print the logs or debugging information of a slave,
redirect to the specified slave device. After that, the user access terminal displays the console of the
slave device instead of that of the master device. The system enters user view of the salve device and
the command prompt is changed to <Sysname-Slave#X>, where X is the member ID of the device, for
example, <Sysname-Slave#2>. What you have input on the access terminal will be redirected to the
specified slave device for processing. At present, only the following commands are allowed to be
executed on a slave device:
display
quit
return
system-view
debugging
terminal debugging
terminal trapping
terminal logging
To return to the master console, use the quit command. At this time, the master console is reactivated
and can output logs.
Follow the step below to log in to the specified slave device:
1-19