Foundry NetIron M2404C and M2404F Metro Access Switches
Network Administration Tools (Rev. 03)
Intermediate 802.3ah EFM OAM
© 2008 Foundry Networks, Inc.
Page 67 of 155
Forcing the EFM-OAM Remote Loopback Configuration
he
efm-oam force-loopback
command, in Interface Configuration mode, is used to force
permanent loopback configuration on the remote side in order to perform long term loopback
traffic analysis (for example, 24 hour-infrastructure testing).
In order for the
efm-oam
force-loopback remote
command to succeed, EFM-OAM must be
enabled in protocol mode. Additionally, EFM-OAM on the current interface must be in active
mode
By default, remote loopback is disabled.
When EFM-OAM goes to passive or disabled mode on the local port or EFM-OAM is disabled on
the device, the
efm-oam force-loopback remote
command should not succeed. However, if the
remote loopback has been already started an error message is returned “remote loopback is
removed from the device on port 1/1/1”.
The same error message with “error” severity will be sent to the Syslog server. Additionally, the
loopback state will be removed from the tables displayed on the console.
If the
efm-oam
force-loopback remote
command is configured on a local port, once EFM-OAM
negotiation takes place, loopback will always be forced on the remote port. If such a setting is
added after the EFM OAM negotiation is over, loopback will be immediately performed.
Command Syntax
device-name
(config-if
UU/SS/PP
)
#efm-oam force-loopback remote
device-name
(config-if
UU/SS/PP
)
#no efm-oam force-loopback
Argument Description
remote
Forces the port loopback on the remote device.
Example
device-name(
config-if 1/1/1)
#efm-oam force-loopback remote
Enabling/Disabling the EFM-OAM Enhancements on the Specified
Interface
The
efm-oam mode
command, in Interface Configuration mode, enables/disables the organization-
specific EFM-OAM enhancements on the specified interface.
In basic mode, no organization -specific OAM extensions are used.
When the remote device is identified as organization device, the enhanced mode will be used.
Otherwise, the basic mode will still be used even though enhanced mode is configured. The
enhanced mode offers ability to set/retrieve all the SNMP variables on the remote device.
If one of the two devices is in efm-oam basic mode neither of the devices will display remote port
and hostname. The two opposite interfaces should be performing in enhanced mode so that the
devices can exchange hostnames.
By default, EFM-OAM is using enhanced mode.
Command Syntax
device-name
(config-if
UU/SS/PP
)
#efm-oam mode
{
enhanced
|
basic
}