Alcatel-Lucent 7750 - Page 153

Interface Configuration
7750 SR Interface Configuration Guide Page 153
===============================================================================
Ethernet Interface
===============================================================================
Description : 10/100/Gig Ethernet SFP
Interface : 1/1/3 Oper Speed : N/A
Link-level : Ethernet Config Speed : 1 Gbps
Admin State : up Oper Duplex : N/A
Oper State : down Config Duplex : full
Reason Down : efmOamDown
Physical Link : Yes MTU : 1522
Single Fiber Mode : No Min Frame Length : 64 Bytes
IfIndex : 35749888 Hold time up : 0 seconds
Last State Change : 12/18/2012 15:58:29 Hold time down : 0 seconds
Last Cleared Time : N/A DDM Events : Enabled
Phys State Chng Cnt: 1
Configured Mode : access Encap Type : QinQ
Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
PBB Ethertype : 0x88e7
Ing. Pool % Rate : 100 Egr. Pool % Rate : 100
Ing. Pool Policy : n/a
Egr. Pool Policy : n/a
Net. Egr. Queue Pol: default
Egr. Sched. Pol : n/a
Auto-negotiate : true MDI/MDX : unknown
Oper Phy-tx-clock : not-applicable
Accounting Policy : None Collect-stats : Disabled
Acct Plcy Eth Phys : None Collect Eth Phys : Disabled
Egress Rate : Default Ingress Rate : Default
Load-balance-algo : Default LACP Tunnel : Disabled
Down-when-looped : Disabled Keep-alive : 10
Loop Detected : False Retry : 120
Use Broadcast Addr : False
Sync. Status Msg. : Disabled Rx Quality Level : N/A
Tx DUS/DNU : Disabled Tx Quality Level : N/A
SSM Code Type : sdh
Down On Int. Error : Disabled
CRC Mon SD Thresh : Disabled CRC Mon Window : 10 seconds
CRC Mon SF Thresh : Disabled
Configured Address : d8:ef:01:01:00:03
Hardware Address : d8:ef:01:01:00:03
The operator also has the opportunity to decouple the efm-oam protocol from the port state and
operational state. In cases where an operator wants to remove the protocol, monitor the protocol
only, migrate, or make changes the ignore-efm-state can be configured in the
port>ethernet>efm-oam context. When the ignore-efm-state command is configured on a port
the protocol continues as normal. However, ANY failure in the protocol state machine (discovery,
configuration, time-out, loops, etc.) will not impact the port on which the protocol is active and the
optional ignore command is configured. There will only be a protocol warning message if there
are issues with the protocol. The default behavior when this optional command is not configured