Configuring A Routable Ethernet Port - Siemens RUGGEDCOM ROX II User Manual

RUGGEDCOM ROX II
CLI User Guide
no on-demand
no alias
lldp
no notify
!
!
!
Section 3.18.2

Configuring a Routable Ethernet Port

To configure a routable Ethernet port, do the following:
1. Make sure the CLI is in Configuration mode.
2. Navigate to interface » eth » {interface}, where {interface} is the routable Ethernet port.
3. Configure the port settings by configuring the following parameter(s):
Parameter
enabled
auton
speed { speed }
duplex { duplex }
link-alarms
ip-address-src { ip-address-src }
proxyarp
Configuring a Routable Ethernet Port
Description
Synopsis: true or false
Default: true
Enables/Disables the network communications on this port.
Synopsis: typeless
Enables or disables IEEE 802.3 auto-negotiation. Enabling
auto-negotiation results in speed and duplex being negotiated
upon link detection; both end devices must be auto-negotiation
compliant for the best possible results.
Synopsis: { 10, 100, 1000 }
Speed (in Megabit-per-second or Gigabit-per-second). If auto-
negotiation is enabled, this is the speed capability advertised
by the auto-negotiation process. If auto-negotiation is disabled,
the port is explicitly forced to this speed mode. AUTO means
advertise all supported speed modes.
Synopsis: { half, full }
If auto-negotiation is enabled, this is the duplex capability
advertised by the auto-negotiation process. If auto-negotiation is
disabled, the port is explicitly forced to this duplex mode. AUTO
means advertise all supported duplex modes.
Synopsis: true or false
Default: true
Disabling link-alarms will prevent alarms and LinkUp and
LinkDown SNMP traps from being sent for that interface. Link
alarms may also be controlled for the whole system under
admin / alarm-cfg.
Synopsis: { static, dynamic }
Default: static
Determines whether the IP address is static or dynamically
assigned via DHCP or BOOTP. The DYNAMIC option is a
common case of a dynamically assigned IP address. It switches
between BOOTP and DHCP until it gets the response from the
relevant server. It must be static for non-management interfaces.
Synopsis: typeless
Chapter 3
Device Management
105