COGE1 Coge1 - r7b: User Manual

User Manual
COGE1 coge1_r7b
Control, Gb Ethernet switch, uplinks, sync
MileGate
MileGate
COGE1 User Manual
Copyright and Confidentiality Copyright in this document vests in KEYMILE. This document contains confi-
dential information which is the property of KEYMILE. It must be held in con-
fidence by the recipient and may not be used for any purposes except those
specifically authorised by contract or otherwise in writing by KEYMILE. This
document may not be copied in whole or in part, or any of its contents dis-
closed by the recipient to any third party, without the prior written agreement
of KEYMILE.
Disclaimer KEYMILE has taken reasonable care in compiling this document, however
KEYMILE accepts no liability whatsoever for any error or omission in the
information contained herein and gives no other warranty or undertaking as
to its accuracy.
KEYMILE reserves the right to amend this document at any time without
prior notice.
Document PEC EN/LZTBU 370 101/7 RC
Document release MileGate R3B | 24. June 2013
Published by KEYMILE
http://www.keymile.com
User Manual
COGE1
Table of Contents
1 Preface 12
1.1 Precautions and safety 12
1.2 Associated MileGate documents 14
1.3 Technical support 15
1.4 Product training 16
1.5 About this document 17
1.6 Document history 18
1.7 Symbols and notations 19
1.7.1 Symbols in syntax descriptions 19
1.7.2 Use of tab names in the MCST GUI 20
2 Introduction 22
2.1 General 22
2.2 Definition of terms 22
2.3 Specification 23
2.3.1 Feature licences 23
2.3.2 COGE1 function overview 23
2.3.3 Versions 26
2.4 Unit View 27
3 Architectural description 28
3.1 Block diagram 28
3.1.1 CPU 28
3.1.2 Switching 29
3.1.3 Synchronisation & redundancy control 29
3.1.4 GbE front interfaces 29
3.1.4.1 Management ports 29
3.1.4.2 VLAN trunk and subtending ports 29
3.1.4.3 Mirror ports 29
3.1.5 USB local management interface 30
3.1.6 Alarm block 30
3.1.7 Backplane access 30
3.1.8 Power 30
© KEYMILE June 2013 page 3 of 176 EN/LZTBU 370 101/7 RC

User Manual
COGE1
4 Installation 31
4.1 Prerequisites 31
4.2 Slots 32
4.3 Connections and cables 34
4.3.1 Front panel connections 34
4.3.2 SFP GbE optical modules cable 35
4.3.3 Electrical Ethernet interface cable (675.0461.00) 35
4.3.4 Synchronisation interface cable (675.0460.00) 37
4.3.5 USB management interface cable 37
4.3.6 Cable fixing 38
4.3.7 Cabling with COGE1 redundancy 38
5 Functional description 40
5.1 Applications 40
5.1.1 Hardware control 40
5.1.2 System management 40
5.1.3 Management traffic and network topologies 41
5.1.4 Switching 42
5.1.4.1 Switch characteristics 42
5.1.4.2 VLAN (802.1Q) 43
5.1.4.3 VLAN tagging 44
5.1.4.4 1:1 VLAN bridging mode 45
5.1.4.5 N:1 VLAN bridging mode 46
5.1.4.6 CoS, 802.1p 47
5.1.4.7 Multicasting (IGMP v2 and v3) 50
5.1.4.8 Packet buffer configuration for standard frames 51
5.1.4.9 Packet buffer configuration for jumbo frames 52
5.1.5 Link protection functions 53
5.1.5.1 RSTP, 802.1D-2004 53
5.1.5.2 MSTP, 802.1s (future release) 54
5.1.5.3 Link aggregation, 802.3ad 54
5.1.6 Security features 54
5.1.6.1 Access control list 55
5.1.6.2 Rapid MAC movement protection 55
5.2 Interfaces 57
5.2.1 Trunk ports 57
5.2.2 Management ports 58
5.2.2.1 USB 1.1 58
5.2.2.2 Ethernet 58
5.2.2.3 In-band management interface 59
5.2.3 Mirror ports 59
5.2.4 Service ports 59

User Manual
COGE1
5.2.5 Synchronisation interface 60

5.2.6 Backplane interfaces 60
5.2.6.1 GbE double star 60
5.2.6.2 CBUS 62
5.2.6.3 PBUS 62
5.2.7 External alarms I/O interface 62
5.2.7.1 Alarm state outputs 63
5.2.7.2 Inputs for external alarm signals 63
5.3 Equipment protection EQP (core unit redundancy) 65

5.3.1 EQP features 65
5.3.2 EQP prerequisites 67
5.3.3 EQP configuration and status 67
5.4 Synchronisation 69
5.5 Unit Optical Indicators 70
5.5.1 COGE1 unit status indications 71
5.5.1.1 Booting 71
5.5.1.2 Waiting 71
5.5.1.3 Active 71
5.5.1.4 Failure 72
5.5.1.5 Standby 72
6 Commissioning 73
6.1 Introduction 73
6.1.1 Definitions 73
6.1.2 Management concept 73
6.2 Managed object model (MOM) 74

6.2.1 MOM overview for the MileGate 25x0 74
6.2.2 MOM overview for the MileGate 23x0 74
6.2.3 MOM for COGE1 75
6.3 Commissioning of COGE1 76

6.3.1 Prerequisites 76
6.3.2 Configuring Ethernet ports 77
6.3.3 Commissioning RSTP 80
6.3.3.1 RSTP parameters 80
6.3.3.2 RSTP recommended values 80
6.3.3.3 Port and LAG RSTP parameters 81
6.3.4 Commissioning Link Aggregation (LA) 83
6.3.4.1 Prerequisites for LA 83
6.3.4.2 LA parameters 84
6.3.4.3 LA group settings 84
6.4 Core unit redundancy 85

User Manual
COGE1
6.4.1 Conditions for redundancy 85
7 Operation and maintenance 87

7.1 Redundancy 87
7.2 Maintenance 89
7.2.1 Inventory data 89
7.2.2 Unit ESW download 89
7.2.3 Setting up mirror ports 89
7.2.3.1 Using the MCST GUI 89
7.2.3.2 Using the CLI 90
7.3 RSTP status 91

7.3.1 RSTP bridge status 91
7.3.2 RSTP notifications 91
7.3.3 RSTP port status 91
7.4 Link Aggregation (LA) status 93

7.4.1 LA notifications 93
8 GUI and CLI reference 94

8.1 Introduction 94
8.2 Profiles 96
8.2.1 General 96
8.2.2 Packet buffer profiles 96
8.2.3 Scheduling profiles 99
8.3 AP: / unit-x: COGE1 104

8.3.1 AP: / unit-x, Main 104
8.3.1.1 AP: / unit-x, Main – General 104
8.3.1.2 AP: / unit-x, Main – Equipment 104
8.3.1.3 AP: / unit-x, Main – Inventory 104
8.3.1.4 AP: / unit-x, Main – Logbooks 104
8.3.1.5 AP: / unit-x, Main – Software 104
8.3.2 AP: / unit-x, Configuration 104
8.3.2.1 AP: / unit-x, Configuration - Filter 104
8.3.2.2 AP: / unit-x, Configuration - Priority Mapping 106
8.3.2.3 AP: / unit-x, Configuration - Packet Buffer 107
8.3.3 AP: / unit-x, Fault Management 107
8.3.4 AP: / unit-x, Status 109
8.3.4.1 AP: / unit-x, Status - QoS 109
8.3.4.2 AP: / unit-x, Status - Packet Buffer 110
8.3.4.3 AP: / unit-x, Status – Redundancy 111
8.4 AP: / unit-x / esi-y 113

User Manual
COGE1
8.4.1 AP: / unit-x / esi-y, Main 113

8.4.1.1 AP: / unit-x / esi-y, Main - General 113
8.4.2 AP: / unit-x / esi-y, Fault Management 113
8.5 AP: / unit-x / internalPorts 114

8.5.1 AP: / unit-x / internalPorts, Main 114
8.5.1.1 AP: / unit-x / internalPorts, Main – General 114
8.6 AP: / unit-x / internalPorts / cpu 115

8.6.1 AP: / unit-x / internalPorts / cpu, Main 115
8.6.1.1 AP: / unit-x / internalPorts / cpu, Main – General 115
8.6.1.2 AP: / unit-x / internalPorts / cpu, Main – Admin And Oper Status 115
8.6.2 AP: / unit-x / internalPorts / cpu, Fault Management 115
8.6.3 AP: / unit-x / internalPorts / cpu, Performance Management 116
8.6.3.1 PM group: RMON Ethernet Statistic 116
8.6.3.2 PM group: MISC Ethernet Statistic 117
8.6.3.3 PM group: MIB-2 Interface Table 117
8.6.3.4 PM group: IF-MIB IfXTable 118
8.6.4 AP: / unit-x / internalPorts / cpu, Status 118
8.6.4.1 AP: / unit-x / internalPorts / cpu, Status – MAC 118
8.6.4.2 AP: / unit-x / internalPorts / cpu, Status – PHY 119
8.7 AP: / unit-x / internalPorts / slot-b 120

8.8 AP: / unit-x / lag-z 121
8.8.1 AP: / unit-x / lag-z, Main 121
8.8.1.1 AP: / unit-x / lag-z, Main – Admin And Oper Status 121
8.8.2 AP: / unit-x / lag-z, Configuration 122
8.8.2.1 AP: / unit-x / lag-z, Configuration - RSTP 122
8.8.3 AP: / unit-x / lag-z, Fault Management 123
8.8.4 AP: / unit-x / lag-z, Status 123
8.8.4.1 AP: / unit-x / lag-z, Status – Aggregation 123
8.8.4.2 AP: / unit-x / lag-z, Status – QoS 126
8.8.4.3 AP: / unit-x / lag-z, Status – RSTP 128
8.9 AP: / unit-x / port-a 130

8.9.1 COGE1 ports 130
8.9.1.1 Port types and port modes 130
8.9.1.2 Port default configuration parameters 131
8.9.2 AP: / unit-x / port-a, Main 133
8.9.2.1 AP: / unit-x / port-a, Main – General 133
8.9.2.2 AP: / unit-x / port-a, Main – Admin And Oper Status 134
8.9.2.3 AP: / unit-x / port-a, Main – SFP 135
8.9.3 AP: / unit-x / port-a, Configuration 136
8.9.3.1 AP: / unit-x / port-a, Configuration – Port Mode 136
8.9.3.2 AP: / unit-x / port-a, Configuration – RSTP 140
8.9.3.3 AP: / unit-x / port-a, Configuration – VLAN list 142
8.9.3.4 AP: / unit-x / port-a, Configuration – VLAN list, Add… 144

User Manual
COGE1
8.9.3.5 AP: / unit-x / port-a, Configuration – VLAN list, Modify… 144

8.9.3.6 AP: / unit-x / port-a, Configuration – QoS 144
8.9.3.7 AP: / unit-x / port-a, Configuration – Multicast 146
8.9.3.8 AP: / unit-x / port-a, Configuration – Link Aggregation 147
8.9.3.9 AP: / unit-x / port-a, Configuration – PHY 151
8.9.3.10 AP: / unit-x / port-a, Configuration – EOAM 152
8.9.3.11 AP: / unit-x / port-a, Configuration – Priority Mapping 153
8.9.3.12 AP: / unit-x / port-a, Configuration – Mirroring 154
8.9.4 AP: / unit-x / port-a, Fault Management 155
8.9.5 AP: / unit-x / port-a, Performance Management 156
8.9.5.1 PM group: MCAST Port Statistics 157
8.9.5.2 PM group: RMON Ethernet Statistic 157
8.9.5.3 PM group: MISC Ethernet Statistic 157
8.9.5.4 PM group: Link Agg. LACP Port 158
8.9.5.5 PM group: MIB-2 Interface Table 158
8.9.5.6 PM group: IF-MIB IfXTable 158
8.9.6 AP: / unit-x / port-a, Status 159
8.9.6.1 AP: / unit-x / port-a, Status – Port Mode 159
8.9.6.2 AP: / unit-x / port-a, Status – MAC 159
8.9.6.3 AP: / unit-x / port-a, Status – PHY 160
8.9.6.4 AP: / unit-x / port-a, Status – RSTP 161
8.9.6.5 AP: / unit-x / port-a, Status – Link Aggregation 163
8.9.6.6 AP: / unit-x / port-1 … 2: 1000BASE-X SFP, Status - DDM 166
8.9.6.7 AP: / unit-x / port-a, Status – QoS 168
8.9.6.8 AP: / unit-x / port-a, Status – Multicast, Stream, Dynamic 169
8.9.6.9 AP: / unit-x / port-a, Status – Multicast, Stream, Static 170
8.9.6.10 AP: / unit-x / port-a, Status – Multicast, VLAN 171
8.10 AP: / unit-x / protocols 172

8.10.1 AP: / unit-x / protocols, Main 172
8.10.1.1 AP: / unit-x / protocols, Main - General 172
8.11 AP: / unit-x / protocols / rstp 173

8.11.1 AP: / unit-x / protocols / rstp, Main 173
8.11.1.1 AP: / unit-x / protocols / rstp, Main - General 173
8.11.2 AP: / unit-x / protocols / rstp, Configuration 173
8.11.2.1 AP: / unit-x / protocols / rstp, Configuration – Local Bridge 173
8.11.3 AP: / unit-x / protocols / rstp, Status 174
8.11.3.1 AP: / unit-x / protocols / rstp, Status – Local bridge 174
8.11.3.2 AP: / unit-x / protocols / rstp, Status – Root bridge 175

User Manual
COGE1
Figures
Figure 1: Front panel and top component view of the COGE1 27

Figure 2: Block diagram of COGE1 28
Figure 3: MileGate 25x0 with core unit COGE1 in slot 11 32
Figure 4: MileGate 23x0 with core unit COGE1 in slot 11 32
Figure 5: MileGate 25x0 with core unit COGE1 in slot 11 and redundant core unit COGE1 in slot 13 32
Figure 6: MileGate 23x0 with core unit COGE1 in slot 11 and redundant core unit COGE1 in slot 13 33
Figure 7: COGE1 front panel and interface connectors 34
Figure 8: Side view of the subrack including cabling and cable tray 38
Figure 9: VLAN tag stacking (Q-in-Q) in MileGate 44
Figure 10: 1:1 VLAN cross connect mode with double tagging 46
Figure 11: N:1 VLAN bridging, single tagging, with COGE1 and service units 47
Figure 12: VLAN priority to traffic queue mapping in downstream and upstream direction on COGE1 48
Figure 13: Multicast with IGMP snooping and proxy reporting 50
Figure 14: Buffer size configuration 51
Figure 15: Jumper position and setting for esi-1 and esi-2 60
Figure 16: 1:1 core unit equipment protection concept 66
Figure 17: Fault and status indication LEDs on the COGE1 unit 70
Figure 18: MOM for MileGate 25x0 74
Figure 19: MOM for COGE1 75
Figure 20: RSTP parameters relationship 81
Figure 21: Port types and port modes in MileGate 130
Figure 22: LAG port association example for unit-11 150

User Manual
COGE1
Tables
Table 1: Electrical interfaces and circuit categories 13

Table 2: Optical interfaces 13
Table 4: Delimiters in syntax descriptions 19
Table 5: Specific terms and abbreviations 22
Table 6: COGE1 function overview - system features 23
Table 7: COGE1 function overview - management interfaces 23
Table 8: COGE1 function overview - Ethernet switching 24
Table 9: COGE1 function overview - fault management 25
Table 10: COGE1 function overview - equipment features 25
Table 11: COGE1 function overview - other standards 25
Table 12: COGE1 mode of operation 36
Table 13: COGE1 RJ-45 cable connector pin specification 37
Table 14: COGE1 switch features 42
Table 15: Default traffic to priority mapping 48
Table 16: Traffic to priority mapping with and without standard queue mode 49
Table 17: Packet scheduling with and without standard queue mode 49
Table 18: LED signalling on COGE1 70
Table 19: Configuring Ethernet ports 77
Table 20: RSTP ring topology values 80
Table 21: Port path cost recommended values 81
Table 22: Port path cost 82
Table 23: LAG path cost 82
Table 24: Port priority recommended values 83
Table 25: Setting up mirror ports with the MCST GUI 89
Table 26: Setting up mirror ports with the CLI 90
Table 27: Profile applicability to managed objects 96
Table 28: Create New Profile, PktBufProfile_1.yy.yy 98
Table 29: Profile applicability to managed objects 99
Table 30: Create New Profile, CUWqProfile_1.yy.yy 101
Table 31: /unit-x, Configuration – Filter 105
Table 32: /unit-x, Configuration – Priority Mapping 106
Table 33: /unit-x, Configuration – Packet Buffer 107
Table 34: /unit-x, Fault Management 107
Table 35: /unit-x, Status - QoS 109
Table 36: /unit-x, Status - Packet Buffer 110
Table 37: /unit-x, Status - Redundancy 112
Table 38: /unit-x/esi-y, Fault Management 113
Table 39: /unit-x/internalPorts/cpu, Main – Admin And Oper Status 115
Table 40: /unit-x/internalPorts/cpu, Fault Management 115
Table 41: PM group: RMON Ethernet Statistic 116
Table 42: PM group: MISC Ethernet Statistic 117
Table 43: PM group: MIB-2 Interface Table 117
Table 44: PM group: IF-MIB IfXTable 118
Table 45: /unit-x/internalPorts/cpu, Status – MAC 118

User Manual
COGE1
Table 46: /unit-x/internalPorts/cpu, Status – PHY 119

Table 47: /unit-x/lag-z, Main – Admin And Oper Status 121
Table 48: /unit-x/lag-z, Configuration – RSTP 122
Table 49: /unit-x/lag-z, Fault Management 123
Table 50: /unit-x/lag-z, Status – Aggregation (1) 124
Table 51: /unit-x/lag-z, Status – Aggregation (2) 126
Table 52: /unit-x/lag-z, Status – QoS 127
Table 53: /unit-x/lag-z, Status – RSTP 128
Table 57: /unit-x/port-a, Main – Admin And Oper Status 134
Table 58: /unit-x/port-a, Main – SFP 135
Table 59: /unit-x/port-a, Configuration – Port Mode 138
Table 60: /unit-x/port-a, Configuration – RSTP 140
Table 61: /unit-x/port-a, Configuration – VLAN List 142
Table 62: /unit-x/port-a, Configuration – VLAN List, Add… 144
Table 63: /unit-x/port-a, Configuration – VLAN List, Modify… 144
Table 64: /unit-x/port-a, Configuration – QoS 145
Table 65: /unit-x/port-a, Configuration – Multicast 146
Table 66: /unit-x/port-a, Configuration – Link Aggregation 148
Table 67: LA port aggregation modes 150
Table 68: LA physical link conditions 151
Table 69: /unit-x/port-a, Configuration – PHY 152
Table 70: /unit-x/port-a, Configuration – EOAM 153
Table 71: /unit-x/port-a, Configuration – Priority Mapping 153
Table 72: /unit-x/port-a, Configuration – Mirroring 154
Table 73: /unit-x/port-a, Fault Management 155
Table 74: PM group: MCAST Port Statistics 157
Table 75: PM group: RMON Ethernet Statistic 157
Table 76: PM group: MISC Ethernet Statistic 157
Table 77: PM group: Link Agg. LACP Port 158
Table 78: PM group: MIB-2 Interface Table 158
Table 79: PM group: IF-MIB IfXTable 159
Table 80: /unit-x/port-a, Status – Port Mode 159
Table 81: /unit-x/port-a, Status – MAC 160
Table 82: /unit-x/port-a, Status – PHY 161
Table 83: /unit-x/port-a, Status – RSTP 162
Table 84: /unit-x/port-a, Status – Link Aggregation (1) 163
Table 87: /unit-x/port-1 … 2, Status – DDM 167
Table 88: /unit-x/port-a, Status – QoS, QoS Status 168
Table 89: /unit-x/port-a, Status – Multicast, Stream, Dynamic 169
Table 90: /unit-x/port-a, Status – Multicast, Stream, Static 170
Table 91: /unit-x/port-a, Status – Multicast, VLAN 171
Table 92: /unit-x/protocols/rstp, Configuration – Local Bridge 174
Table 93: /unit-x/protocols/rstp, Status – Local Bridge 175
Table 94: /unit-x/protocols/rstp, Status – Root Bridge 176

Preface User Manual
COGE1
1 Preface
1.1 Precautions and safety
Before you handle any unit of the type COGE1 you must comply with the fol-
lowing safety advices:
Please note the following safety precautions:
Hazardous voltages. Risk of electric shock!

Equipment might be connected to high voltages.
→ If a stationary battery is used as local power supply, the charging unit
must have a safety insulation acc. EN 60950-1.
→ If an AC/DC power supply is used instead of a stationary battery, this
must also provide a safety insulation acc. EN 60950-1.
→ Before manipulating anything at the device switch off the power sup-
ply.
Hazardous electric currents. Risk of flashover and electric shock!

When interrupting the power supply electric currents can cause a flashover
and an electric shock.
→ The positive (+) terminal of the local power supply must be connected
to earth. The negative (-) terminal of the local power supply must be
protected with a thermal-magnetic circuit breaker. The applicable cir-
cuit breaker current rating is specified in the installation user guide of
the MileGate subrack.
Electrostatic discharges. Risk of equipment damage!

To protect your equipment you must discharge any static charge from your
person before touching the unit or any components!
→ Wear a grounded, anti-ESD wrist-band when working with the hard-
ware.
Attention to temperature range!

Equipment has a high power dissipation. Insufficient ventilation causes hot
spots and overheating on the equipment. Overheating holds a high risk for
damage of the equipment.
→ A sufficient ventilation or cooling and ventilation must be provided by
the operator for the racks or subracks that guarantees for a maximum
ambient temperature of 60° C.

176
Preface User Manual
COGE1
Attention to proper earthing!

The subrack must be connected via the rack with the protective earth! The
plus (+) pole of the local power supply must be connected to earth. The
minus (-) pole of the local power supply must be protected with a thermal-
magnetic circuit breaker. The subracks may only be connected to a switcha-
ble power voltage.
Attention to access control!

Unrestricted access to equipment premises hold a risk of damaged equip-
ment and disrupted services.
→ The subrack should only be installed in locations with restricted
access.
Table 1: Electrical interfaces and circuit categories

COGE1 interface Circuit category according to Max. rating
EN 60950-1 Voltage Current
Local power supply TNV2 < 72 VDC < 1.25 A
Electrical Gigabit or SELV <3V < 10 mA
Fast Ethernet
Synchronisation SELV <3V < 10 mA
USB SELV <5V < 10 mA
Table 2: Optical interfaces

COGE1 interface Parameter Max. rating
Remarks
a
Optical Gigabit Laser class 1
Ethernet (according to EN 60825-1)
Optical transmitted power b - 7 dBm
Transmitted wavelength 850 nm, non-visible
1310 nm, radiation
1550 nm
a. As the laser protection class 1 is complied, dangerous radiation cannot be emitted.

Thus, special precautions for failures or laser warnings are not necessary.
b. Optical transmitted power, modulation and wavelengths are typical values for SFP
modules, however these values may vary depending on SFP types and manufac-
turers.
Please refer to SFP manufacturers data sheets for more details.

176
Preface User Manual
COGE1
1.2 Associated MileGate documents
[012] Release Note “MileGate R3B”
[201] System Description “MileGate R3B”
[301] User Guide “MileGate 2500/2510 Installation”
[302] User Guide “MileGate 2500/2510”
[303] User Guide “Triple Play Applications”
[304] User Guide “MileGate & MCST”
[314] User Guide “TDM Services and Cross Connections”
[316] User Guide “Ethernet OAM”
[401] User Manual “COGE1 coge1_r7b”
[506] User Manual “MileGate cables”
[915] Technical Bulletin “Feature Licences for MileGate”

176
Preface User Manual
COGE1
1.3 Technical support
Please refer to the KEYMILE Extranet (via http://www.keymile.com) for sup-

port contact information.

176
Preface User Manual
COGE1
1.4 Product training
Training courses are available for a wide range of KEYMILE products and
applications.
For contact information, course descriptions, locations and dates, go to the
Website: http://www.keymile.com, then select “Services - Training” from the
menu.

176
Preface User Manual
COGE1
1.5 About this document
The MileGate User Manual for COGE1 covers the aspects of the installation,
commissioning and operation of the COGE1 unit of MileGate. It handles also
the functional aspects and technical specification of the unit.
You find MileGate technical information and the description of the commis-
sioning procedures and operation as follows:
[201] System Description “MileGate R3B”.
The MileGate System Description describes the MileGate 2500, the
MileGate 2510, MileGate 2300 and the MileGate 2310, their features
and elements and the system architecture, and provides all the rele-
vant technical data and information for system planning.
[301] User Guide “MileGate 2500/2510 Installation”.
The Installation Guides cover the aspects of the MileGate equipment
installation.
[302] User Guide “MileGate 2500/2510”.
The MileGate User Guides describe the elements of the basic Mile-
Gate system (system control, software, alarms, synchronisation,
inventory function, etc.) and the principles of commissioning and oper-
ation of these subsystems.
[304] User Guide “MileGate & MCST”.
The User Guide “MileGate & MCST” provides all the information
required for the installation and commissioning of the MCST. It
describes the generic functions of MileGate and of the MCST GUI
(graphical user interface) and the CLI (command line interface).
User Guides for MileGate applications.
User Guides for MileGate applications are created and updated with
the implementation of new and/or enhanced functionality in the Mile-
Gate system. Application oriented User Guides provide dedicated
information on commissioning and operation of selected applications
and services provided with the MileGate (e.g. the user guide “Triple
Play Applications”).
Unit User Manuals (refer to the paragraph below) and the MileGate
User Guides together provide all information required for the basic unit
and system commissioning and operation.
User Manuals for MileGate units.
User Manuals are created for the individual MileGate control and ser-
vice units. The User Manuals provide information of the installation,
commissioning, and operation of the units in the MileGate system. The
User Manuals include also detailed unit specifications.
Service relevant unit parameters are not handled in the unit User Man-
uals but described in the application User Guides (refer to the para-
graph above).

176
Preface User Manual
COGE1
1.6 Document history
Table 3: Document history

KEYMILE PEC Date MileGate Changes since previous
release
LZTBU 370 101/7 RC April 2013 R3B FANU6 (R3) with alarm outputs added.
LZTBU 370 101/7 RB September 2012 R3B Profile creation also with CLI.
LZTBU 370 101/7 RA June 2011 R3B Support of jumbo frames.
Queue 7 is per default reserved for the internal man-
agement traffic.
Mirror port is no longer a status function but a configu-
ration.
LZTBU 370 101/6 RC December 2011 R3A No functional changes.
LZTBU 370 101/6 RB May 2011 R2G No functional changes.
LZTBU 370 101/6 RA 28-02-2011 R2G VLAN trunk mode on internal ports.
Static multicast.
Port VLAN.
IP DSCP to 802.1q priority mapping.
Packet buffer profile support.
Additional high capacity performance management
counters on ports.
LZTBU 370 101/5 RA 30-06-2010 R2F Mirror port for processor interface.
Flow control on front ports.
LZTBU 370 101/4 RA 23-08-2009 R2E Description of enhanced RSTP features added. Some
editorial changes.
LZTBU 370 101/3 RA 23-03-2009 R2D Description of new features added. MileGate 2300
added. Some editorial changes.
LZTBU 370 101/2 RE 14-11-2008 R2C Description of new features added. Document struc-
ture adapted.
LZTBU 370 101/2 RD 21-12-2007 R2B SP1
LZTBU 370 101/2 RC R2B
LZTBU 370 101/2 RB R2B Description of new features added.
LZTBU 370 101/2 RA R2A Description of new features added.
LZTBU 370 101/1 RA 01-02-2007 R1E
LZTBU 370 101 RC 22-12-2006 R1D
LZTBU 370 101 RB 15-07-2006 R1C
LZTBU 370 101 RX 31-01-2006 R1A

176
Preface User Manual
COGE1
1.7 Symbols and notations
This user manual uses the following symbols:
Please note:
Shows a significant information.
Indicates a possibly hazardous context. The possible hazard is indicated

with a symbol and a description.
A further description is added to describe the details of the hazard.
→ Possible actions are given as in this paragraph.
Warns of hazardous circumstances. The hazard is specified.

A description of the danger is added.
→ Possible actions are given as in this paragraph.
1.7.1 Symbols in syntax descriptions
MileGate can be operated using a text-only command line interface (CLI).

This user manual represents the syntax of the CLI as follows:
Syntax:shows a command and all its parameters
In addition to the command a number of delimiters serve to separate com-
mands, keywords and values or keywords as values:
Table 4: Delimiters in syntax descriptions

Delimiter Example Purpose
<> <Filename> Chevrons: Enclose a placeholder which must be
replaced by an item from a range of values or by
a user defined entry. The chevrons must not be
entered in the CLI.
| Up | Down Bar: Separates values and/or keywords as ele-
ments of a list of alternatives. One element of the
list has to be entered.
… 1 … 1000 Ellipsis: Separates the minimum value and maxi-
mum value of a continuous range of values. One
value of the range has to be entered in the CLI.
[] [Unit] Square brackets: Enclose the unit of the param-
eter values, e.g. [bytes]. Units must not be
entered in the CLI.
{} {a = 1, D = 2} Curly braces: enclose complex structures with
various elements.
KeyWord MaxNumber This is a keyword which has to be typed in as
shown.

176
Preface User Manual
COGE1
1.7.2 Use of tab names in the MCST GUI
The graphical user interface (GUI) in MCST uses tabs to present different
functional areas of the unit’s properties.
Please note:
The description of the path to access these tabs uses a syntax with man-
aged object names (see MOM description), management functions, and tabs
as follows:
/ managed object / child managed object, Management Function - Tab
Examples:
/ unit-9 / port-1, Configuration – Security
/ unit-9 / port-1 / interface-1, Configuration – Traceability
In the headings and CLI syntax statements, the unit numbers, port numbers,
and interface numbers are given with a variable name like “x”, “y”, “z”, or “u”.
Examples:
/ unit-x / port-y
/ unit-x / port-y / interface-z
For accessing the properties Proceed as follows:

in the MCST GUI, please fol- 1. With the pointing device, select a managed object or a child (subordi-
low these instructions:
nate) managed object in the AP tree of the MCST GUI (for details,
please refer to "[304] User Guide “MileGate & MCST”").
- The managed object is coloured. Example:
2. With the context menu button of your pointing device, click on the
selected managed object.
- The context menu opens. Example:
3. Select the management function from the context menu by clicking on its
name.

176
Preface User Manual
COGE1
- The dialogue window for this management function opens.

4. With the pointing device, select the required tab.
- The specific set of properties for this tab appears.
- Example:
 Now you are ready to configure the required properties.

5. Once you have changed the properties as required, you have the follow-
ing possibilities:
- If you only want to apply the changes without closing the dialogue
window, you click on the “Apply” button.
- If you want to get the actually configured properties from the network
element (NE), you click on the “Refresh” button.
- If you want to apply the changes and close the dialogue window, you
click on the “OK” button.
- If you don‘t want to apply any changes you click on the “Cancel” but-
ton. The “Apply” button must not have been clicked before.
End of instruction

176
Introduction User Manual
COGE1
2 Introduction
2.1 General
The COGE1 unit represents the core control unit for the multiservice access
nodes MileGate 2500, MileGate 2510, MileGate 2300 and MileGate 2310.
This unit combines the typical management functions of a core unit like
embedded software distribution, system alarming, performance monitoring,
etc., with an Ethernet switch including VLAN functionality.
The COGE1 unit provides several interface types in the front panel like SFP
cages for backhaul connectivity, electrical GbE as for subtending MileGate
systems or co-located Ethernet equipment, micro D-Sub 9 for synchronisa-
tion and USB 1.1 for management purposes.
All network elements MileGate 2500, MileGate 2510, MileGate 2300 and
MileGate 2310 permit full redundancy of the control unit and its traffic inter-
faces when operated in slot 11 by inserting and configuring a second control
unit in slot 13.
The details described in this document base on a specific COGE1 embed-
ded software (ESW) version. For more details about the ESW version
required for the described functionality, please refer to "[012] Release Note
“MileGate R3B”".
2.2 Definition of terms
Table 5: Specific terms and abbreviations

Term Explanation
MileGate In this user manual, the term “MileGate” is used to name the
network element types MileGate 2500, MileGate 2510, Mile-
Gate 2300 and MileGate 2310. Where certain features or char-
acteristics apply to a specific network element type only, the
respective network element type is named explicitly.
MileGate 23x0 The term “MileGate 23x0” is used to name the network element
types MileGate 2300 or MileGate 2310.
MileGate 25x0 The term “MileGate 25x0” is used to name the network element
types MileGate 2500 or MileGate 2510.

176
COGE1
2.3 Specification
2.3.1 Feature licences
Part of the MileGate functionality is subject to feature licences. For more

information on feature licences please refer to [012] Release Note “MileGate
R3B” and to [915] Technical Bulletin “Feature Licences for MileGate”.
2.3.2 COGE1 function overview
The COGE1 unit provides the following functions and supports the following
standards:
Table 6: COGE1 function overview - system features

Feature Rating or standard Release
Central management point for the complete MileGate r3a
23x0 system
Central management point for the complete MileGate r1
25x0 system
Embedded software download r1
Alarm collection and notification r1
Syslog, sources and destinations RFC 3164 r2j
External alarm interfacing via backplane and manage- r1
ment
Unit configuration delivery r1
Synchronisation interface r1
- Clock input signals 2
- Frequency 2.048 MHz
- Connector type Micro D-Sub
- Impedance 120 ohms according to ITU-T G.703
- Clock output signals 2
- Frequency 2.048 MHz
- Connector type Micro D-Sub
- Impedance 120 ohms according to ITU-T G.703
SFP modules INF-8074 (12th May 2001), Specification for SFP r1
(Small Form factor Pluggable) Transceiver
SFP DDM (Digital Diagnostic & Monitoring) r2j
COGE1 unit redundancy r2a
- Switchover time with RSTP root bridge not on COGE1 <1s r4a
- Switchover time with RSTP root bridge on COGE1 < 30 s r4a
- Switchover time with “Port Down For Standby” < 12 s r4a
- Switchover time when COGE1 removed <5s r4a
Table 7: COGE1 function overview - management interfaces

Electrical Gigabit Ethernet ports: 10BASE-T, 100BASE-TX, 1000BASE-T r1
- Number of ports 0 … 3 (configurable)
- Connector type RJ45
- Impedance 100 ± 15 Ω, frequency band 1 … 16 MHz

176
COGE1
Table 7: COGE1 function overview - management interfaces (continued)

Optical Gigabit Ethernet ports: 1000BASE-SX/-LX/-EX/-ZX r1
- Number of ports 0 … 2 (configurable)
- Connector type SFP, complying with [INF-8074] specification
USB port: USB 1.1 r1
- Connector type mini USB Type B, female, five-pin, keyed
- Speed full speed (12 Mbit/s)
- Mode slave
Remote authentication via RADIUS server r2j
Table 8: COGE1 function overview - Ethernet switching

Gigabit Ethernet switching IEEE 802.3-2002, CSMA/CD access method and r1
physical specifications
IEEE 802.3z-1998, Gigabit Ethernet
Electrical Gigabit Ethernet ports: 10BASE-T, 100BASE-TX, 1000BASE-T r1
- Number of ports 3
- Connector type RJ45
- Impedance 100 ± 15 Ω, frequency band 1 … 16 MHz
Optical Gigabit Ethernet ports: 1000BASE-SX/-LX/-EX/-ZX r1
- Number of ports 2
- Connector type SFP, complying with [INF-8074] specification
VLAN support IEEE 802.1Q-1998, Virtual bridged Local Area Net- r1
works
Port VLAN r6c
VLAN tag stacking, IEEE 802.1ad, Provider bridges
- Ethertype 8100 r2j
- Ethertype 88A8 r2j
- Ethertype 9100 r2j
VLAN QoS with Class of Service IEEE 802.1p, Traffic Class Expediting and Dynamic r1
Multicast Filtering (in 802.1D-1998)
QoS Priority scheduler, DSL Forum TR-101 r2e
- Strict priority
- Weighted Round Robin
Rapid Spanning Tree Protocol (RSTP), with configur- IEEE 802.1D-2004, Media Access Control (MAC) r1
able Bridges, section 17
- Port cost r4a
- Port priority
- Dynamic path cost
Spanning Tree Protocol (STP) compatibility IEEE 802.1D-1998, Media Access Control (MAC) r1
Bridges,
802.1t MAC bridges Amendment 1
Link Aggregation Control Protocol (LACP), with config- IEEE 802.3ad, Link Aggregation for parallel links r1
urable
- LAG cost r4a
- LAG priority
- Dynamic path cost
1:1 VLAN mode DSL Forum TR-101 r1
N:1 VLAN mode DSL Forum TR-101 r1
White list and black list (VLAN control access) DSL Forum TR-101 r1

176
COGE1
Table 8: COGE1 function overview - Ethernet switching (continued)

Access control list (MAC based access control) DSL Forum TR-101 r1
Protection against rapid MAC movement r4a
Multicast and IGMP snooping (v2 and v3), IGMP proxy RFC 2236, RFC 3376, IGMP v2, v3 (Internet r1
with report message suppression Group-Membership Protocol); DSL Forum TR-101
Multicast, support of IGMP transparent snooping with RFC 3376, DSL Forum TR-101 r2j
message suppression
Multicast group management DSL Forum TR-101 r2j
Static multicast r6c
Internet Protocol RFC 791, IP (Internet Protocol) r1
Internet Control Message Protocol RFC 792, ICMP (Internet Control Message Proto- r1
col)
Address Resolution Protocol RFC 826, ARP (Address Resolution Protocol) r1
IPoE (IP over Ethernet) RFC 894, IPoE (IP over Ethernet) r1
Bridge MIB RFC 1493, Bridge MIB r1
PPP (Point to Point Protocol) RFC 1548, PPP (Point to Point Protocol) r1
PPPoE (PPP over Ethernet) RFC 2516, PPPoE (PPP over Ethernet) r1
RMON Remote Monitoring MIB RFC 2819, RMON Remote Monitoring MIB r1
Multiple Spanning Tree Protocol IEEE 802.1s, Multiple Spanning Trees future
release
Table 9: COGE1 function overview - fault management

Fault management ITU-T X.733, Alarm Reporting r1
Table 10: COGE1 function overview - equipment features

Power consumption r1
- Power supply range Vbat refer to "[201] System Description “MileGate R3B”"
- Current consumption (typical with max. traffic load)
at Vbat = -48VDC 0.83 A
- Maximum total power requirements from battery,
at Vbat = nominal voltage 40 W
Mechanical parameters r1
- Construction practice 19 inches
- Height of the unit (1 HU = 44.45mm) 6 HU
- Width of the unit (1 TE = 5.08mm) 4 TE (1 slot)
- Size of the PCB (H x D) 233 mm x 220 mm
- Weight of the COGE1 unit 476 g
Reliability r1
- Calculated MTTF at 35 °C (MIL-HDBK-217F) 48 years
Table 11: COGE1 function overview - other standards

Emission refer to "[201] System Description “MileGate R3B”" r1
Immunity refer to "[201] System Description “MileGate R3B”" r1

176
COGE1
Table 11: COGE1 function overview - other standards (continued)

Safety refer to "[201] System Description “MileGate R3B”" r1
SFP modules:
according to the manufacturer’s data sheets (typi-
cally IEC 60825-1 Class 1 laser product)
Ambient conditions refer to "[201] System Description “MileGate R3B”" r1
Error free operation up to 70°C ambient tempera-
ture is only guaranteed with SFP modules specified
to work at 85°C.
2.3.3 Versions
For detailed information about the released COGE1 hardware (HW) and
embedded software (ESW) versions supporting all the previously mentioned
features, please refer to "[012] Release Note “MileGate R3B”"

176
COGE1
2.4 Unit View
The figure below shows the COGE1 unit with its front panel and interfaces.
Figure 1: Front panel and top component view of the COGE1

176
Architectural description User Manual
COGE1
3 Architectural description
3.1 Block diagram
The COGE1 functionality is implemented using the following blocks:

• CPU block with microprocessor and memory.
• Switch
• Synchronisation & redundancy control
• Backhaul interfaces
• Subtending interfaces
• Management interfaces
• Alarm block
• Backplane access
• Power
For more information regarding these functions, please refer to section Func-
tional description (on page 40).
The figure below shows the functional block diagram of the COGE1 unit.
COGE1
Optical
Alarm indicator
(4 LEDs )
1
Local
Alarm USB
Management IF
CPU
Power 1
Synchronisation
& Redundancy Sync
Control
PBUS
20
GbE Backplane
Trunk IF, 5
1 Subtending IF, GbE
Switching
CBUS Management IF
Management
internal IF
Figure 2: Block diagram of COGE1
3.1.1 CPU
The CPU functional block controls and monitors all the other functional
blocks of COGE1. The local CPU also processes external information arriv-
ing from other units or as external alarms.

176
COGE1
3.1.2 Switching
This functional block is responsible for the switching between all Ethernet
traffic arriving at the unit, including management traffic that will be processed
by the CPU. It also supports VLAN, prioritization of traffic, RSTP, etc. as
described in section General (on page 22).
3.1.3 Synchronisation & redundancy control
This block provides a PETS synchronisation system for the MileGate sys-
tem. The signal can be derived from different sources, e.g. external clock
source 2’048 kHz, internal oscillator, clock recovery from external interfaces,
etc.
It also provides a supervision of the redundant core unit that is plugged in
slot 13.
3.1.4 GbE front interfaces
Depending on the network topology, a GbE front interface can be configured

as management port, VLAN trunk port, or mirror port. A trunk port can also
be used as subtending interface; there are no differences in configuration.
For more details, refer to section Interfaces (on page 57).
3.1.4.1 Management ports
Any of the GbE interfaces can be configured as a management port. Man-

agement ports accept non-VLAN tagged frames only, and the frames are
internally tagged and forwarded with the configured management VLAN ID.
For more details refer to section AP: / unit-x / port-a, Configuration – Port
Mode (on page 136).
3.1.4.2 VLAN trunk and subtending ports
Any of the GbE interfaces can be configured as a trunk interface. Due to

their span of operation, optical interfaces are especially suitable for this pur-
pose when distances are in the range of hundreds of metres up to about 70
kilometres. Optical interfaces can provide a clock signal for the synchronisa-
tion of the system.
Subtending interfaces usually connect to local subtending equipment and
are therefore usually electrical interfaces.
Ethernet front ports support also the port VLAN feature.
3.1.4.3 Mirror ports
Any of the GbE front interfaces can be configured as mirror port. A mirror
port can mirror traffic from any of the other front ports, or from any of the
internal ports, or from the host processor port of the COGE1. The mode for
any of the mirrored ports can be ingress, egress, or both directions. For
more details, please refer to sections AP: / unit-x / port-a, Configuration –
Port Mode (on page 136) and AP: / unit-x / port-a, Configuration – Mirroring
(on page 154).

176
COGE1
3.1.5 USB local management interface
Provides management access from a locally connected PC that is running

the local manager MCST. It is connected via a mini-USB 1.1 connector.
3.1.6 Alarm block
It provides the interface to the fault indications system (four LEDs) situated in
the front panel. It is also in charge of processing the 12 external alarms con-
nected to the backplane via the fan unit FANU4 and delivering to it the two
possible output alarms if necessary.
3.1.7 Backplane access
It provides the control signals access to the backplane allowing the manage-
ment of the units. It also grants access to the double Gigabit Ethernet star for
every unit. The backplane is formed by the following buses:
• C-BUS (for control signals),
• Double GbE star (for customer traffic), and
• PBUS (PDH bus for voice and other applications).
COGE1 provides the PBUS timing circuits and uses the ICN circuits for
the network element internal communication.
3.1.8 Power
COGE1 is directly powered from battery (-48 VDC or -60 VDC nominal). A
power block is available on the unit for the conversion of these voltages into
those needed by the unit HW (5V, 3.3V, etc.).

176
Installation User Manual
COGE1
4 Installation
This section describes how to install the COGE1 core unit in a MileGate and
the connectors and cables that are required for installation.
4.1 Prerequisites
The required local manager (MCST) version to commission and operate the
MileGate system must be according to [012] Release Note “MileGate R3B”.
Along with this MCST version, an embedded software (ESW) according to
[012] Release Note “MileGate R3B” must be installed in the COGE1 unit.

176
COGE1
4.2 Slots
For MileGate systems with only one COGE1 unit, this unit must be placed in
slot 11, as shown in Figure 3 for the MileGate 25x0, and in Figure 4 for the
MileGate 23x0.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
S S S S S S S S S S C S S S S S S S S S S
U U U U U U U U U U U U U U U U U U U U U
Figure 3: MileGate 25x0 with core unit COGE1 in slot 11
7 8 9 10 11 12 13 14
S S S S C S S S
U U U U U U U U
Figure 4: MileGate 23x0 with core unit COGE1 in slot 11
In systems with an additional, redundant unit, the redundant COGE1 is

placed in slot 13 as shown in Figure 5 for MileGate 25x0, and Figure 6 for
MileGate 23x0:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
S S S S S S S S S S C S C S S S S S S S S
U U U U U U U U U U U U U U U U U U U U U
Figure 5: MileGate 25x0 with core unit COGE1 in slot 11 and redun-
dant core unit COGE1 in slot 13

176
COGE1
7 8 9 10 11 12 13 14
S S S S C S C S
U U U U U U U U
Figure 6: MileGate 23x0 with core unit COGE1 in slot 11 and redun-
dant core unit COGE1 in slot 13

176
COGE1
4.3 Connections and cables
4.3.1 Front panel connections
The COGE1 front panel connections are implemented as shown in Figure 7.

Fixing screw
Pull-out handle with

COGE1 R2C
37900005 identification label
Optical fault indications
mini-USB connector:
Local management interface
micro-D-Sub 9-pin female connector:

Synchronization interfaces
port-5
RJ-45 8-contact female connectors :

port-4 Electrical 10/100/1000BASE-T interfaces
(usable as trunk, subtending or management interface )
port-3
port-2
SFP module cages: optical GbE interfaces
(usable as trunk, subtending or management interface )
port-1 Tx
Rx
Pull-out handle
Fixing screw
Figure 7: COGE1 front panel and interface connectors

176
COGE1
4.3.2 SFP GbE optical modules cable
The 1000FX optical interfaces on COGE1 consist of two SFP (Small Form
factor Pluggable) cages.
The COGE1 unit only provides the mechanical infrastructure for such mod-
ules: This is a cage and a host board connector. COGE1 allows hot swap-
ping of SFP modules.
Please note:
SFP modules must be fully MSA (Multi-Source Agreement) compliant [INF-
8074]. Please note that only KEYMILE’s recommended SFP modules should
be used in order to guarantee inter-working with the COGE1 unit.
→ In order to get the latest list of KEYMILE’s recommended SFP mod-
ules please refer to the KEYMILE Extranet
(via http://www.keymile.com) → Documentation & Software → Mile-
Gate / MCST → Techn. Documentation → Bulletins.
Then go to Technical Bulletins, and open the “MileGate R2 supported
SFP transceivers” document once you have logged in.
The recommended SFP module types are:
• 1000BASE-SX (850 nm)
• 1000BASE-LX (1310 nm)
• 1000BASE-EX (1310 nm)
• 1000BASE-ZX (1550 nm)
The selection of the transceiver and the media type will determine the maxi-
mum distance allowed according to the transmission media specifications.
For details on connectors and pins for this interface, please refer to [INF-
8074].
SFP Modules plugged into the COGE1 operate by default in auto negotiation
mode.
Please note:
GbE optical interfaces only support 1000 Mbit/s Full Duplex fixed operation
mode.
SFP DDM (Digital Diagnostic & Monitoring) is supported on the SFP mod-
ules that are plugged in the SFP cages of the COGE1 unit provided that the
module itself is supporting this feature.
4.3.3 Electrical Ethernet interface cable (675.0461.00)
COGE1 provides 3 electrical Ethernet interfaces according to IEEE 802.3,

802.3u and 802.3ab specifications, and they support:
• 10BASE-T
• 100BASE-TX
• 1000BASE-T
All three interfaces are presented as RJ-45 connectors with automatic cross-
over functionality so they may be connected to both host and switch inter-
faces. Therefore both, crossover and straight cables can be used.

176
COGE1
Please note:
For error free transmission, category 5e Ethernet cables are required at
least. This assumes that the equipment on the remote end also supports
transmission on category 5e cables. If this is not the case, we recommend
the use of category 6 cables.
Electrical 10BASE-T/100BASE-TX/1000BASE-T ports on COGE1 support
auto-negotiation with parallel detection.
Auto-Negotiation allows the highest performance mode to be automatically
selected on a given link.
Please note:
COGE1 Ethernet electrical interfaces are configured in auto negotiation
mode by default.
Please note:
With auto negotiation switched off, a crossed cable has to be used to con-
nect to another COGE1 since the interface cannot automatically select the
mode.
The following table shows the behaviour of COGE1 when connecting an
external Ethernet device:
Table 12: COGE1 mode of operation

COGE1 mode External Equipment mode COGE1 election
Auto negotiation Auto negotiation 1000 Mbit/s Full Duplex
Auto negotiation 1000 Mbit/s Full Duplex 1000 Mbit/s Full Duplex
Auto negotiation 1000 Mbit/s Half Duplex 1000 Mbit/s Half Duplex
Please note:
When using LACP, full duplex is mandatory.
Please note:
When connecting Ethernet ports configured in manual mode (no auto-negoti-
ation) to Ethernet ports in auto-negotiation mode, the link may be up but the
duplex settings may be inconsistent. This can result in poor throughput per-
formance on the link.
The previous note applies to any Ethernet device and is a consequence of
the behaviour of Auto-Negotiation and Parallel Detection. When a port sup-
porting auto-negotiation is connected to a port not supporting auto-negotia-
tion, the port supporting auto-negotiation will revert to parallel detection: This
can detect the link type (10BASE-T or 100BASE-TX) but will assume half-
duplex operation (reference IEEE 802.3 clause 28.2.3.1 note 2). If the far
side port is manually configured in full-duplex mode, then there is an incon-

176
COGE1
sistent configuration and the side operating in half-duplex may experience

collisions while transmitting data.
The following table provides the pin allocation on the cable side.
Table 13: COGE1 RJ-45 cable connector pin specification

Cable side pins Signal connected
1 RX+
2 RX-
3 TX+
4 Terminated (Bob Smith)
6 TX-
EMI cage M_GND (chassis)
Please note:
This cable can be ordered from KEYMILE.
For details on available Ethernet cables, please refer to "[506] User Manual
“MileGate cables”".
4.3.4 Synchronisation interface cable (675.0460.00)
The synchronisation interface is implemented in the current COGE1 hard-

ware version.
This interface permits to connect the following signals according to ITU-T
G.703:
• two symmetrical clock inputs (2048 kHz)
• two symmetrical clock outputs (2048 kHz)
The interface is implemented in COGE1 by means of a micro D-Sub connec-
tor.
Please note:
This cable can be ordered from KEYMILE.
For details on available synchronisation cables, please refer to "[506] User
Manual “MileGate cables”".
4.3.5 USB management interface cable
This interface allows the operator to commission the MileGate system by

connecting its working PC via USB.
This interface is implemented as a USB 1.1 connection and supports full
speed.
The connection to the COGE1 unit is via a mini-USB type B connector (5
pin), and the PC end will need a USB termination.

176
COGE1
Please note:
A USB cable length above 5 m may lead to an unstable connection or may
not allow a connection at all. It is hence not recommended to use USB
cables longer than 5 m for the connection to the COGE1 unit.
4.3.6 Cable fixing
In the MileGate 25x0, cables connecting to the COGE1 unit or other units in
general should be guided and attached to the cable tray as indicated in the
following figure.
Figure 8: Side view of the subrack including cabling and cable tray
In the MileGate 23x0, cables connecting to the COGE1 unit or other units
should be guided and attached similarly to the way shown in Figure 8 above.
For more detailed information, please refer to "[310] User Guide “MileGate
2300/2310 Installation”".
4.3.7 Cabling with COGE1 redundancy
When using a redundant core unit in slot 13, cabling is different. Since the
core unit HW is duplicated, some of the front connections have to be dupli-
cated as well. The cables that have to be connected twice are the following:
• USB cable to the USB local management interface

176
COGE1
The USB cables to the two COGE1 units can be connected e.g. via a
USB hub to the local manager. Note that the two USB ports of the two
COGE1 units have different addresses on the local management PC.
• Synchronisation interface cable
The two cables need to be connected to an appropriate analogue switch
or multiplexer if a switch-over is required.
• Ethernet cables – for maximum protection against failures, also electrical
and optical cables from a switching or routing device to ports 1 to 5 of the
COGE1 unit need to be connected to both units, the working and the
standby COGE1. In this case, RSTP might be required. Please read the
important note on RSTP configuration in section Equipment protection
EQP (core unit redundancy) (on page 65).

176
Functional description User Manual
COGE1
5 Functional description
This section provides a functional description of the COGE1 core unit and its
interfaces. For a description of configuration parameters, refer to section
Commissioning (on page 73).
5.1 Applications
The COGE1 core unit controls the configuration and operation of the Mile-
Gate system, maintains an updated database with relevant information for
each configured unit and it performs switching between every traffic unit,
backhaul and subtending interfaces. It also provides redundancy through 1:1
equipment protection when two core units are plugged and configured. The
following sections cover these aspects in more detail.
5.1.1 Hardware control
One of the main functions of the COGE1 unit is to control the peripheral units
at hardware level. This comprises the following functions:
• Check the presence of peripheral units
• Supervise the core unit redundancy status
• Activate/deactivate the units
• Reset the units
• Read the unit alarm status
• Read the unit inventory data
• Provide clock information
• Control signals to the redundant COGE1
5.1.2 System management
System management is an important function that affects all units in a run-

ning system. Each unit of the NE contributes to the management functions:
• Inventory management
• Configuration management
• Status
• Fault management
• Performance management
The COGE1 core unit has some particular functions for the management of
the system:
• Loading a NE system configuration and making it effective (configuration
management)
• Monitoring all the unit functions, collection and classification of the fail-
ures and creation of triggers for consequent actions (fault management)

176
COGE1
• Management communication with the outside world to allow local and

remote operation and maintenance of the NE, i.e. support of all the pro-
vided management functions
NE management is a system level function and is described in [201] System
Description “MileGate R3B”.
5.1.3 Management traffic and network topologies
When connecting MileGate to a routed network, inband management traffic

can be forwarded to a VLAN trunk port of the COGE1. In this case, the
inband management traffic must be VLAN tagged, and its VLAN ID must be
the same as configured in MileGate.
The management traffic can also be untagged when using the port VLAN
feature of the COGE1 and setting the port VLAN ID to the same value as the
management VLAN ID.
Inband management traffic with the correct VLAN ID is then forwarded to the
COGE1 internal management interface.
Please note:
For the configuration of the management VLAN ID, refer to "[304] User
Guide “MileGate & MCST”".
Risk of operating trouble!

Changing the Management VLAN ID can result in loss of the management
connections, depending on the network topology.
Please note:
Care must be taken that the VLAN ID assignment follows a proper strategy.
When trying to re-configure the management VLAN ID, a warning is issued
by the management system.
In case of direct connection from a management system (UNEM or MCST)
to a MileGate using untagged traffic, the port must be configured as a ‘Man-
agement Port’ and will be accepting untagged traffic only. Once the manage-
ment traffic from the management system has reached the port, it will be
tagged with the management VLAN ID that is currently configured (for details
see sections AP: / unit-x / port-a, Configuration – Port Mode (on page 136)
and AP: / unit-x / port-a, Configuration – VLAN list (on page 142), and [304]
User Guide “MileGate & MCST”).
The third scenario is the case where there are subtending MileGate nodes.
In this case, ports connecting to and from the head end must be configured
as ‘VLAN trunk’ interfaces.
Please note:
COGE1 is a switch and not a routing gateway. Therefore it is not able to con-
vey routing information to hosts.
→ The COGE1 management IP address must not be configured as
default gateway in a connected host.

176
COGE1
Please note:
For further information on the management connection to the MileGate,
please refer to [302] User Guide “MileGate 2500/2510”, [317] User Guide
“MileGate 2300/2310”, and [304] User Guide “MileGate & MCST”.
5.1.4 Switching
The main traffic function of the MileGate system is switching customer’s traf-
fic towards the network and vice versa. This function is performed in the
COGE1 unit that implements a switch based on IEEE 802.1D with VLAN
support according to IEEE 802.1Q and IEEE 802.1ad.
This switch has five external Ethernet interfaces; three electrical GbE and
two SFP modules for optical or electrical GbE as described in the next sec-
tion. Moreover, it has 20 internal ports in the backplane of 1Gbit/s each
granting access to every other unit in the subrack, and it has one internal
port of 100 Mbit/s to the CPU.
COGE1 permits switching traffic at wire speed between all its ports.
Please note:
Under heavy load situations from the tributary side and when using the same
VLAN priority (CoS) for all or many traffic streams, congestion might occur in
upstream direction due to the limited packet buffer resources in the switching
circuit.
Please note:
Management traffic coming from the CPU and coming from a management
port is tagged with a VLAN priority CoS4.
→ To avoid collisions of tagged management traffic with user traffic it is
recommended to use other VLAN priorities for the user traffic.
5.1.4.1 Switch characteristics
The following table summarises the main features of the COGE1 switch.
Table 14: COGE1 switch features

Feature Details
Generic Main feature L2 switching
No. of ports 28 (26 currently used)
Internal packet buffer 1MB
MAC addresses 23’000
VLAN VLAN support (802.1Q) Yes
VLAN no. 4096 (0-4095) of which 6
are reserved for internal
use (4090-4095)
VLAN tag stacking support (802.1ad) Yes a
IVL (Independent VLAN Learning) b Yes
QoS CoS (802.1p) Yes

176
COGE1
Table 14: COGE1 switch features (continued)

Feature Details
Output queues 8
Weighted scheduling Yes
Shaping support Yes (future release)
Multicast IGMP v2 support Yes
IGMP v3 support Yes
Static multicast support Yes
Link functions RSTP according 802.1D-2004 Yes
MSTP according 802.1s Yes (future release)
Link aggregation (802.3ad) Yes
a. Ethertypes 8100, 88a8, and 9100.

b. MAC learning on a per VLAN basis.
The following sections cover in more detail the characteristics of the COGE1
switch.
5.1.4.2 VLAN (802.1Q)
Virtual LANs (VLANs) enable the interconnection of LAN segments that are
far apart, extending their reach. When the transport between VLAN seg-
ments is done over optical networks, the distance between segments is virtu-
ally unlimited.
Besides the ability to interconnect separated LAN segments, VLANs provide
an enhanced level of security compared to shared media LANs where traffic
can be seen by any other end station.
VLAN segments are connected to VLAN-aware switches, and upon configu-
ration (frame filtering, ingress rules, and filtering), they will forward frames
accordingly.
In general, in switched networks, the performance of the network is improved
by splitting collision domains. In this way, other end stations can still commu-
nicate because collisions are not passed to other segments of the network.
The links interconnecting VLAN segments are defined as:
• ‘Access’ links if they carry either:
− untagged frames or
− priority tagged frames (VLAN ID=0)
• ’Trunk’ links if they carry:
− tagged frames only
Ethernet front interfaces in COGE1 can be associated with trunk links, there-
fore all traffic expected in these interfaces should be VLAN tagged. Ingress
filtering is not enabled, hence all VLAN IDs are accepted, i.e. these ports are
transparent for all VLAN IDs.
When using the port VLAN feature of the COGE1 unit incoming untagged
traffic is assigned the port VLAN ID. Outgoing traffic with the port VLAN ID
gets the VLAN tag removed.
On subscriber interfaces like e.g. SUAD1 ADSL2+ interfaces, untagged or
priority tagged frames are assumed since these interfaces correspond to
access links.

176
COGE1
For nto1 services, tagged traffic is accepted on VDSL2 or G.SHDSL.bis

(EFM) ports to separate services if configured correspondingly, and is further
supported for the implementation of “transparent LAN services” on sub-
scriber interfaces. For more details, refer to "[303] User Guide “Triple Play
Applications”".
VLANs are classified depending on the rules they use to forward frames.
COGE1 supports port and tag based VLANs in the trunk links (external
ports). All VLAN IDs are associated to all external ports. The internal ports
support port based VLANs.
The VLAN ID is automatically associated to all the internal ports when creat-
ing and configuring a service.
All switches need to have an updated MAC table in order to perform the for-
warding. COGE1 uses IVL (Independent VLAN Learning) for the MAC learn-
ing process. This implies that COGE1 holds independent MAC tables for
each VLAN.
5.1.4.3 VLAN tagging
COGE1 supports VLAN tagging and VLAN tag stacking as proposed both in
IEEE 802.1Q and in IEEE 802.1ad.
VLAN tag stacking allows customer’s VLAN tags (C-VID) to be forwarded
through the operator’s network. This way, the internal virtual network struc-
ture is kept and priority information can be sent over.
Tag stacking adds a second VLAN tag (S-VID) as a tagged frame arrives to
the operator’s network from the customer. When arriving to the remote LAN
segment of the customer’s network, the second VLAN tagged is removed
again.
Customer Service Provider Customer
VLAN West LAN/VLAN VLAN East
Tagged frame Double-tagged frame Tagged frame
Destination Source VLAN VLAN Length

Payload FCS
Address Address VLAN VLAN Priority ID Type
Priority ID
S-Tag C-Tag
add / remove tag
Figure 9: VLAN tag stacking (Q-in-Q) in MileGate
VLAN tag stacking is also used to overcome the limitation of 4096 VLAN IDs
with single VLAN tagging.

176
COGE1
According to IEEE 802.1ad terminology, the outer or only tag is called S-tag
(Service tag) and the inner tag, used in case of tag stacking, is called C-tag
(Customer tag).
The resulting frames after applying tag stacking can be bigger than 1522
bytes and are called jumbo frames. Jumbo frames are supported by the
COGE1 switch up to a maximum packet length of 10’000 octets.
The bridging mode (802.1Q, or 802.1ad) can be configured in the MileGate
on network element level. Note that the mode selection should be done care-
fully since the two modes are not compatible.
5.1.4.4 1:1 VLAN bridging mode
With service units as e.g. SUAD1, two VLAN configuration modes are availa-
ble:
• 1:1 VLAN bridging
• N:1 VLAN bridging
With the 1:1 VLAN bridging mode, a unique VLAN ID is assigned to each
service of each subscriber in the service unit. This allows the isolation of the
traffic from different subscribers and the control of the connectivity between
the subscriber and the service provider.
The main disadvantage of this single tagging method is the poor scalability
due to the range of VLAN IDs being limited to 4089.
However, the scalability problem can be overcome by using 1:1 double
VLAN tagging. In that case both, the C-tag and the S-tag are assigned in the
service unit, e.g. SUAD1. The COGE1 only supervises the VLAN tags.
Please note:
An S-tag can be assigned to 1:1 double tagged services from different ser-
vice units.
The following figure illustrates this concept.

176
COGE1
SUAxx, SUSD1 COGE1

Line/Channel ATM VCC VLAN VLAN
802.1Q
Termination Termination C-tag S-tag
DSL port Bridging
1 5/38 34 500
101
GbE
5/39 35 500 102 GbE trunk
backplane
DSL port 1 27
2 5/38 36 500
5/39 37 500
500
ATM VCC
SUVxx, SUExx, SUSE1

Line/Channel VLAN VLAN
Termination C-tag S-tag
DSL port
1 2021 1811
Eth port GbE
2022 1812 backplane 1811 GbE trunk
DSL port 20 28
2 2023 1811 1812
Eth port
500
2024 500
EFM Customer VLAN Service VLAN
Figure 10: 1:1 VLAN cross connect mode with double tagging
1:1 VLAN cross connect mode with double tagging is the typical VLAN mode
used with the Broadband Internet Access service based on PPPoE encapsu-
lation.
5.1.4.5 N:1 VLAN bridging mode
With the N:1 VLAN bridging mode, a service delivered to several subscribers
is assigned to a single VLAN, as shown in the following figure.

176
COGE1
SUAxx, SUSD1 COGE1
Line/Channel ATM VCC VLAN Single 802.1Q

Termination Termination Tagging Bridging
DSL port
1 5/38* 101 101
GbE 102
5/39 102 GbE trunk
backplane
1 103 27
DSL port
2 5/38 104
5/39 105
ATM VCC
SUVxx, SUExx, SUSE1
Line/Channel VLAN Single Tagging or

Termination Transparent
DSL port
1** 1
Eth port GbE
backplane GbE trunk
DSL port 20 28
2 101
Eth port 3998
DSL port 3999
3 102
Eth port
Subscriber VLAN or Subscriber / Service VLAN
Note *: PPPoE and IPoE via one ATM VCC, mapping to two VLANs based on the Ethertype value
Note **: three VLANs based on one DSL or Ethernet port
Figure 11: N:1 VLAN bridging, single tagging, with COGE1 and service
units
This mode is typically used with single tagging only (tag assigned in the traf-
fic unit, e.g. SUAD1). In downstream direction, the identification of the sub-
scriber is achieved with its MAC address.
Security and filter mechanisms are implemented in MileGate to parry attacks
like source MAC flooding or source MAC spoofing etc.
N:1 VLAN cross connect with single tagging is the typical VLAN mode used
with connections to IP edge routers, TV servers and Voice Gateways, based
on IPoE encapsulation.
Please note:
Mixed VLAN modes (N:1-single tagging / 1:1-single tagging and N:1-single
tagging / 1:1-double tagging) are supported in the same unit.
5.1.4.6 CoS, 802.1p
MileGate supports Class of Service (CoS) handling, according to IEEE

802.1p. This allows the prioritisation of “critical” traffic like voice or video over
“uncritical traffic” like e-mail or internet access. This approach is considered
as relative Quality of Service (QoS).
According to 802.1p, there are 8 priority levels that are mapped to traffic
classes. The traffic classes correspond to queues in the switch.
COGE1 has eight queues (= 8 traffic classes) in upstream direction (towards
the network) and eight queues in downstream direction (towards the internal
backplane interface).
For both directions, each of the queues can be configured for

176
COGE1
• Strict Priority scheduling, or for

• Weighted Round Robin (WRR) scheduling,
with a weight assigned to each queue. Configuration of the scheduler is
done via profiles. The scheduling type (strict or weighted queuing) can be
mixed on any of the ports, i.e. some queues can have strict priority, some
can be weighted. Also refer to the figure below.
COGE1
priority to
queue Ethernet 0
mapping Switch Eth.
GbE priority to port
backplane 7 queue
mapping
Figure 12: VLAN priority to traffic queue mapping in downstream and

upstream direction on COGE1
The default mapping of the user priority levels to the 8 traffic classes
(queues) is shown in Table 15.
Note that the queue 7 is reserved by default for the MileGate internal man-
agement communication and is therefore not used for service traffic. This
avoids that the internal management communication could be disturbed by
the service traffic or external management traffic. Nevertheless the default
mapping can be modified in the MileGate according to the operator’s prefer-
ences.
Table 15: Default traffic to priority mapping

User priority Acronym Traffic type Queue
level (CoS)
1 BK Background 0
2 - Spare 0
0 (default) BE Best Effort 1
3 EE Excellent Effort 2
4 CL Controlled Load 3
5 VI Video, < 100 ms latency and jitter 4
6 VO Voice, < 10 ms latency and jitter 5
7 NC Network Control 6
The queue 7 reservation is controlled by the configuration parameter “Stand-

ard Queue Mode - Enable Queue mode in COGE”, accessible at the AP: /,
Configuration - QoS”.
With the standard queue mode disabled, the queue handling is according to
the configuration:
• 802.1p priority to queue mapping, configured at the at AP: /, Configura-
tion - QoS.
The effective priority to queue mapping can be checked at the AP: /unit-x,
Status - QoS, x = 11 or 13.
• Queue scheduling, configured with a profile at the AP: /unit-x/port-y, Con-
figuration - QoS, x = 11 or 13.
The effective scheduling can be checked at the AP: /unit-x/port-y, Status -
QoS and at the AP: /unit-x/lag-y, Status - QoS, x = 11 or 13.

176
COGE1
With the standard queue mode enabled (default) the priority to queue map-
ping is modified so that the queue 7 is reserved for the internal management
traffic. The user packets are mapped to the next lower queue. Packets that
are mapped to queue 0 and queue 1 according to the configuration will all be
mapped to queue 0. For an example refer to Table 16.
Table 16: Traffic to priority mapping with and without standard queue
mode
Priority to queue mapping Effective packet priority mapping,
configuration (example) Standard Queue Mode
Queue Priority disabled or enabled
queue 7 priority 7 priority 7 internal management
queue 6 priority 6 priority 6 priority 7
queue 0 priority 1 priority 1 priority 1 and priority 2
With the standard queue mode enabled (default) the packet scheduling is
modified so that the queue 7, which is reserved for the internal management
traffic, will have strict scheduling. The lower queues inherit the scheduling
type of the next higher queue, the configured scheduling type of the queue 0
is discarded. The weight of the remaining weighted queues is adapted pro-
portionally so that the total weight remains at 100%. For an example refer to
Table 17.
Table 17: Packet scheduling with and without standard queue mode
Packet scheduling profile configura- Effective Scheduling,
tion (example) Standard Queue Mode
Queue Scheduling Weight disabled or enabled
queue 7 Strict - Strict Strict
queue 6 Weighted 4 Weighted 40% Strict
queue 5 Strict - Strict Weighted 44.4%
MileGate supports Differentiated Services Code Point (DSCP) lookup and

mapping to IEEE 802.1p. In this case, the priority level of the traffic is set at
the egress port according to the received DSCP value. This mapping is con-
figurable per VLAN.

IP/DSCP mapping works fine for known unicast traffic. It does not work if the
traffic is flooded within the VLAN also to ports without activated IP/DSCP
mapping, i.e. for unknown unicast or broadcast traffic.

176
COGE1
Traffic management with per-flow shaping functions on COGE1 are planned

for future releases. Policing will be part of the service unit, e.g. SUAD1. With
this approach, it will be possible to have mixed operation with committed traf-
fic (high priority, but “policed”) and best effort traffic (not “policed”, using only
the available bandwidth).
5.1.4.7 Multicasting (IGMP v2 and v3)
MileGate supports multicast based on IGMP (v2,v3) snooping and IGMP

proxy reporting for applications like broadcast TV.
IGMP snooping is used to manage the multicast-traffic of the video broad-
cast service and optimizes the distribution of multicast-traffic within a broad-
cast domain. IGMP snooping is realized with message suppression.
To achieve this, it listens to the IGMP protocol messages (layer 3) and auto-
matically determines to which ports multicast-traffic shall be forwarded.
In the MileGate, the multicast function is used with N:1 VLAN mode and
IPoE encapsulation.
The basic scheme for the multicast proxy reporting function within the Mile-
Gate IP DSLAM is shown in the following figure.
MileGate
IP DSLAM Video
Server
IGMP Host IGMP
(Set Top Box) Modem Router
PIM / SSM
IGMP
IGMP Host: IGMP snooping with proxy reporting: IGMP Router:
 Initiates IGMP oper-  monitors IGMP packets, and sends  Processing of IGMP oper -
ations to receive or IGMP reports to the IGMP router, ations, i.e. IGMP requests from
stop receiving multi- hosts are terminated in the
cast flows  builds multicast forwarding tables IGMP Router
accordingly ,
 e .g. join a multicast  IGMP Router requests for the
group to receive its  distributes multicast flows (content traffic) appropriate video stream from
multicast stream, or to all members of a group according to the video server
leave a group to stop multicast forwarding tables. (with PIM / SSM) .
its multicast stream
Figure 13: Multicast with IGMP snooping and proxy reporting
With the proxy reporting functionality, reports and queries are intercepted
and processed in COGE1 in order to reduce the signalling traffic to the IGMP
router.
The MileGate supports also static multicast. Static multicast can forward
specific multicast streams directly to member ports without any interaction
required from the subscriber or from a network server.
For more details, please refer to "[303] User Guide “Triple Play Applica-
tions”".

176
COGE1
5.1.4.8 Packet buffer configuration for standard frames
The packet buffer sizes for all switch ports on the COGE1 unit can be config-
ured. The configuration is done with a profile.
The total available buffer memory of 1’048’576 bytes is distributed to
• the incoming traffic for all ports and priorities per unit,
• the outgoing traffic, per port and per priority.
Queue0 Queue0 Queue0

Outgoing buffer Maxi- Maxi- Maxi-
Queue4 mum Queue4 mum Queue4 mum
sizes per port
and queue Queue5 buffer Queue5 buffer Queue5 buffer
size size size
any any any

CoS CoS CoS
Outgoing and port-1 port-2 ... slot-1 ... slot-21 cpu incoming buffer size
incoming buffer
sizes per unit Total available buffer
Figure 14: Buffer size configuration
The packet buffer profile allows an operator to configure the buffer sizes of
all outgoing switch ports, i.e.
• the 5 front ports (port-1 to port-5),
• the 20 ports to the service units (slot-1 to slot-10, slot-11/slot-13, slot-12,
slot-14 to slot-21), and
• the processor port (cpu).
On each port the buffer size for each priority (queue) can be given, together
with a maximum buffer size. If the sum of the priority buffer sizes is smaller
than the maximum buffer size, the difference buffer memory is used for any
priority.
The buffer size for all incoming switch ports is the total available buffer
size minus the sum of all outgoing port maximum buffer sizes.
When configuring the packet buffer profile some rules must be observed:
• All buffer sizes must be multiples of 64 bytes.
• On each port the sum of the priority buffer sizes must be equal or smaller
than the maximum buffer size.
• The incoming buffer size must be at least 79’664 bytes, i.e. the sum of all
maximum buffer sizes of the outgoing ports must be equal or smaller than
968’912 bytes.
• The maximum buffer size of the cpu port should be at least 30’720 bytes
to be able to handle all management traffic.

176
COGE1
Please note:
There is no check of the above rules when a packet buffer profile is created,
but a profile with invalid settings will be rejected when applying it in the unit
configuration (AP: /unit-x, Configuration - Packet Buffer).
The default packet buffer profiles assigns the packet buffer sizes as follows:
• port-1 to port-5:
− Queue7 to Queue0: 4*1’536 = 6’144 Bytes,
− Maximum buffer size: 49’152 Bytes.
• slot-1 to slot-21, slot-11/slot-13:
− Maximum buffer size: 32’256 Bytes.
• cpu:
− Queue7: 7’808 Bytes,
− Queue6 to Queue0: 0 Bytes,
− Maximum buffer size: 59’136 Bytes,
− Buffer for any CoS: 51’328 Bytes.
• Total packet buffer for outgoing traffic:
− Sum of all port, slot and cpu maximum buffer sizes =
5*49’152 + 20*32’256 + 59’136 = 950’016 Bytes.
• Total packet buffer for incoming traffic:
− 1’048’576 - 950’016 = 98’560 Bytes.
5.1.4.9 Packet buffer configuration for jumbo frames
Jumbo frames with a packet size up to 10’000 octets are supported by the
MileGate on specific ports:
• Between 2 COGE1 front ports, or
• Between 1 COGE1 front port and up to 2 Ethernet ports on a service unit,
or
• Between 1 COGE1 front port and 1 Ethernet ports on two service units
and between 2 COGE1 front ports.

Special care must be taken when jumbo frames >2000 octets must be for-
warded.
→ The buffer sizes of the ports receiving and transmitting jumbo frames
must be adapted to ensure error free operation.
Due to the restricted amount of available buffer memory the buffer sizes of
unused ports and queue buffers should be set to 0.
The following example shows a buffer profile for an application with jumbo
frames at 2 front ports of the active COGE1 unit and at the redundant port to
the standby COGE1 unit. Five Ethernet units in slot-1 to slot-5 support nor-
mal sized frames with an MTU of 1’536 Bytes.
Note that the buffer sizes of the Queue2 to Queue0 are all set to 0 Bytes.
Frames with these priority values share a common buffer.
• port-1 to port-2, jumbo frames with MTU = 10’000 Bytes:

176
COGE1

• slot-11/slot-13, jumbo frames with MTU = 10’000 Bytes:
− Queue7 to Queue3: 3*10’000 = 30’016 Bytes (multiple of 64 Bytes),
− Buffer for any Queue: 49’920 Bytes.
• slot-1 to slot-5, normal frames with MTU = 1’536 Bytes:
• slot-6 to slot-21, no frames:
− Maximum buffer size: 0 Bytes,
− Buffer for any CoS: 0 Bytes.
• cpu:
− Queue7: 7’808 Bytes,
• Total packet buffer for outgoing traffic:
− Sum of all port, slot and cpu maximum buffer sizes =
2*260’032 + 1*200’000 + 5*32’256 + 59’136 = 940’480 Bytes.
• Total packet buffer for incoming traffic:
− 1’048’576 - 940’480 = 108’096 Bytes.
5.1.5 Link protection functions
5.1.5.1 RSTP, 802.1D-2004
In switched networks, where availability is important, redundant paths must

be created to allow redundancy. However, this type of network configuration
can result in frames circulating indefinitely and consequently crashing the
network. In order to avoid this problem, the spanning tree protocol (STP,
IEEE 802.1D-1998) has traditionally been implemented on switches.
STP reduces the physical topology to an active tree topology that reaches all
segments of the network. To achieve this, the switches/bridges exchange
BPDU (Bridge Packet Data Units) protocol frames to coordinate which ports
will be active (designated or root port) and forwarding traffic, and which will
remain as backup (alternate, backup or disabled port) and discarding traffic.
When a port failure is detected on a designated port then an alternate port
will become designated. The election of designated, alternate, and backup
(second port on a switch) ports is done according to the path cost, physical
topology, and port priority assigned.
The time STP requires to reconfigure the network topology (convergence
time) is dependent on the network topology and number of switches. This
time is relatively long in STP and therefore an improved version of this proto-

176
COGE1
col was proposed in IEEE 802.1D-2004, reducing significantly the conver-

gence time. In order to profit from RSTP all switches have to work on this
mode, otherwise they will work in 802.1D-1998 mode (STP) to keep compati-
bility.
The COGE1 switch implements RSTP 802.1D-2004 (compatible with STP
802.1D-1998).
Please note:
RSTP is applied per COGE1 port or link aggregation group, and not per
VLAN.
5.1.5.2 MSTP, 802.1s (future release)
Multiple Spanning Tree Protocol (MSTP), according to IEEE 802.1s will allow
having multiple active spanning tree topologies on one physical network.
5.1.5.3 Link aggregation, 802.3ad
Link aggregation is specified in IEEE 802.3ad. It allows the aggregation of

several parallel links in an Ethernet point-to-point configuration to form a “link
aggregation group”. From a logical point of view, a link aggregation group is
considered as one single link. This logical link is in operation when at least
one physical link of the group is active. Accordingly, the bandwidth and the
availability of an Ethernet point-to-point connection can be increased with
this concept.
However, it has to be noted that one single Ethernet frame flow cannot be
distributed over several physical links, i.e. the increased bandwidth can be
utilised only when there is more than one flow at the same time. With link
aggregation, the reconfiguration time in the case of a failure or recovery of a
physical link is up to 3.2 s.
Link aggregation can co-exist with RSTP, i.e. link aggregation groups are
considered as single links by RSTP.
Link aggregation is supported on the entire network and subtended Ethernet
interfaces on the COGE1 unit, i.e. a link aggregation group can be made up
of up to five physical Ethernet links.
COGE1 supports Link Aggregation Control Protocol (LACP) detecting the
presence and capabilities of aggregation devices, and automatic configura-
tion of the link aggregation group.
5.1.6 Security features
COGE1 together with service units offers security features (according to DSL
Forum TR-101) to protect the NE from attacks of a malicious user.
These security features are appropriate for N:1 VLAN mode, but several also
apply to 1:1 VLAN mode, and some of the security features that are applica-
ble for residential users may not be applicable to some business customer
configurations.

176
COGE1
5.1.6.1 Access control list
Within the MileGate we can differentiate two types of access control func-
tions:
• MAC access control list for N:1 single tagged VLAN services:
At system level, it is possible to set up a black list with MAC addresses of
devices not allowed to access the network. Their messages will be
blocked before reaching the BRAS. This is a system feature performed
by COGE1 in cooperation with a service unit (e.g. SUAD1).
• White and black lists of VLANs per Ethernet port:
COGE1 allows defining whitelists or blacklists of VLANs per Ethernet
port, allowing the operator to set up a number of VLANs which will not be
allowed (blacklist), or to set up the list with the only VLANs permitted
(whitelist). This feature is not available on management ports. Also refer
to section AP: / unit-x / port-a, Configuration – VLAN list (on page 142).
For more details, please refer to "[302] User Guide “MileGate 2500/2510”",
or refer to "[317] User Guide “MileGate 2300/2310”".
Please note:
Other security features like protection from source MAC spoofing or from L2
peer-to-peer forwarding are implemented in the service units, e.g. SUAD1.
5.1.6.2 Rapid MAC movement protection
Rapid MAC movement is a risk that may occur because of a broadcast storm
or if a malicious subscriber tries to hijack a MAC address from a running ses-
sion of another subscriber.
The MileGate supports a protection against rapid MAC movement. A learned
MAC address is valid on a port as long as an aging timer of 5 minutes has
not expired. This MAC address is prohibited to access another port on the
MileGate. The MAC address can be learned on another MileGate port only
after the expiry of the aging timer.
The rapid MAC movement protection is a network element feature:
• GUI: AP: ne, Configuration – Packet, MAC Movement Protection = 
• CLI: set /cfgm/MACMovement true
Please note:
On a COGE1 port with RSTP enabled the MAC addresses are only learned
if the port is active. The MAC address table on an inactive port is cleared.
→ Port switching within a spanning tree is possible also when MAC
movement protection is enabled.
Please note:
A COGE1 port which is member of a link aggregation group (LAG) the MAC
addresses are only learned with the port number of the leading port of the
LAG.
→ Traffic load distribution within a LAG is possible also when MAC
movement protection is enabled.

176
COGE1
Please note:
When enabling the rapid MAC movement protection the actual MAC address
table on an inactive port is cleared.
→ Only MAC addresses newly learned after the enabling are protected
against rapid MAC movement.
For more details, please refer to "[303] User Guide “Triple Play Applica-
tions”".
Please note:
Note that the aging timer is reset also when a learned MAC address
accesses another COGE1 port than the port it has been learned. In this case
the learned MAC address will not be removed from the MAC address table
and the access to another COGE1 port will not be possible.
→ The traffic with a learned MAC address must be stopped on all
COGE1 ports for 5 minutes to automatically remove the corresponding
entry in the MAC address table. If required the MAC address table can
be cleared manually by one of the following procedures:
• Disable the rapid MAC movement protection feature and enable it again.
Note that this clears the MAC address tables on all units of the MileGate.
• Disable the port mode:
− set the administrative state of the port to “down”,
− configure the port mode to “Not Configured”,
− configure the port mode to “VLAN Trunk Port” or “Management Port”
again, and
− set the administrative state of the port to “up”.
Note that all traffic on this port will be interrupted.

176
COGE1
5.2 Interfaces
The interfaces in the COGE1 unit can be classified as follows:

• Trunk (for trunking or subtending purposes)
• Management
• Mirror
• Service
• Synchronisation
• Backplane
• External alarms
5.2.1 Trunk ports
When configured as VLAN trunk ports, these interfaces receive / deliver the
traffic from / towards the network. They concentrate the totality of customer
traffic.
Because of the wide range of available distances that can be covered with
optical interfaces, the SFP interfaces (ports 1 and 2) are considered as back-
haul interfaces.
These interfaces support 1000BASE-SX/-LX/-EX/-ZX according to their
respective standards.
COGE1 provides two SFP cages (port-1 and port-2) where different SFP
modules can be inserted to satisfy network needs. For details about SFP
modules, refer to section SFP GbE optical modules cable (on page 35).
The selection of the transceiver and the media type (single mode or multi
mode fibre) will determine the maximum distance allowed according to SFP
provider specifications.
For details on connectors and pins for this interface please refer to [INF-
8074].
The SFP modules provide duplex LC connectors.
Please note:
SFP modules are hot swappable. This means that you can plug or remove
the modules during operation of the unit. We strongly recommend however
to remove the fibre before plugging or unplugging an SFP module.
In principle, when configured as trunk port, any of the electrical or optical
Ethernet front ports can be used as subtending interface, i.e. a further Mile-
Gate can be connected to this port. However, electrical interfaces have a
limited reach compared with the optical interfaces and are therefore normally
used in subtending configurations.
The three electrical Ethernet interfaces (port-3, port-4, and port-5) support
10/100/1000BASE-T/TX according to IEEE 802.3 specifications. Any of the
interfaces can be used for management communications.
Every one of these three interfaces (ports 3 … 5) is implemented by means
of an RJ-45 connector with auto-negotiation. Fixed operation modes (half/full
duplex modes) are also available.
These interfaces support automatic cross over functionality allowing straight
or cross over cables to be connected.

176
COGE1
They support frames bigger than 1522 bytes called jumbo frames, which can
be the result of double VLAN tag stacking. Maximum packet length sup-
ported is 10’000 octets (also refer to section AP: / unit-x / port-a, Status –
MAC (on page 159)).
The internal ports (GbE star) connecting the service units to the Ethernet
switch on the COGE1 unit can also be configured as VLAN trunk port. This
makes it possible to use e.g. an SDH port on an SDH unit as uplink port
towards the network.
Please note:
The internal backplane port to the redundant COGE1 unit has the fixed port
mode “VLAN Trunk Port”.
All of the five Ethernet front ports and the internal ports to the service units
support RSTP and LACP. For more details about RSTP on the Ethernet
ports, please refer to:
• section Commissioning RSTP (on page 80) for RSTP parameters,
• section AP: / unit-x / port-a, Configuration – RSTP (on page 140) for
RSTP configuration, and
• section AP: / unit-x / port-a, Status – RSTP (on page 161) for the RSTP
status.
5.2.2 Management ports
There are two types of interfaces for management, one for local commission-
ing of the NE, and the other one for inband or out-of-band management
communications.
5.2.2.1 USB 1.1
The local commissioning interface is implemented with a mini-USB 1.1 sup-

porting Full Speed operation mode (12 Mbit/s). It is used for a direct local
connection to a PC.
Please note:
The maximum recommended cable length for this connection is 5 m.
5.2.2.2 Ethernet
Any of the five Ethernet ports (optical, electrical) and the internal ports to the
service units can be configured as a management port.
In order to have a dedicated interface for management it has to be config-
ured as “Management Port” via the MCST GUI or via the CLI. This implies
that the port will only accept untagged frames. Accepted frames will then be
tagged with the VLAN ID for internal use (4089 by default or the configured
management VLAN ID; for details refer to "[304] User Guide “MileGate &
MCST”").
The VLAN ID for management can be configured in the range 1 … 4089. It is
not recommended to use the default VLAN ID 1 as the management VLAN
ID.

176
COGE1
This interface will allow the user to access the MileGate system via its con-
figured IP address (192.168.0.1 by default) in the COGE1 unit.
Please note:
To reduce susceptibility of the management connection to broadcast storms,
the COGE1 controls layer 2 multicast and broadcast traffic by counting the
number of broadcast and/or multicast packets within a certain time period. If
a count limit is exceeded, the packets are discarded.
→ The control feature is fixed to a maximum of 16 packets in a 100 ms
time frame for the management VLAN ID.
5.2.2.3 In-band management interface
This is a logical interface that allows embedded management communica-

tions frames to be extracted from traffic interfaces. This can be done by
using appropriate VLAN tagging functionality. Per default, the VLAN ID used
for in-band management communication is 4089. It can be configured on NE
level; refer to "[304] User Guide “MileGate & MCST”".
Management VLAN tagged frames will be carried in-band, together with the
user traffic, over the MileGate trunk interfaces. They will be identified when
arriving to the switch and forwarded to the COGE1 CPU.

A loop in the Ethernet network can lead to a broadcast storm and other
unexpected behaviour. The management connection would be lost.
→ Avoid loops in the Ethernet network.
→ Avoid loops in the SDH network when using EoS (Ethernet over SDH).
5.2.3 Mirror ports
Any of the five Ethernet front ports and the internal ports to the service units
can be configured to be a mirror port. In this case, frames from any of the
other front ports, or from any of the backplane GbE ports, or from the host
processor port can be mirrored to this port. For each of the ports to be mir-
rored, you can select the direction, i.e. ingress frames, egress frames, or
both.
This is specially helpful if you need to monitor frames that are processed by
the built-in switch on the COGE1 unit. For details, please refer to:
• section AP: / unit-x / port-a, Configuration – Port Mode (on page 136),
and
• section AP: / unit-x / port-a, Configuration – Mirroring (on page 154) and
following.
5.2.4 Service ports
Any of the internal ports to the service units can be configured to be a ser-
vice port. This is the typical port mode for the connection between a service
unit and the COGE1 unit.

176
COGE1
Frames from a subscriber port on a service unit are forwarded to the switch
on the COGE1 unit and vice versa. This requires the configuration of a ser-
vice on the MileGate network element.
5.2.5 Synchronisation interface
This interface is implemented by means of a micro D-Sub connector. It pro-

vides two symmetrical clock signal inputs of 2.048 MHz with an impedance
of 120 Ohms according to ITU-T G.703 (esi-1 and esi-2), and two symmetri-
cal clock signal outputs of 2.048 MHz with the same impedance (eso-1 and
eso-2).
The impedance of the input interface can be determined by a jumper on the
board. This is necessary when a redundant COGE1 is placed in slot 13. In
this case, you have to connect a synchronisation source to two COGE1 syn-
chronisation input interfaces in parallel (e.g. to both esi-1 on unit-11 and esi-
1 on unit-13).
When using an external line termination, you have to set the synchronisation
inputs on the two COGE1 boards to high impedance. This is done with the
jumper situated just behind the synchronisation interface connector on the
COGE1 board. The upper jumper is for esi-1 whilst the lower jumper is for
esi-2. If plugged on the two pins closer to the COGE1 front panel, the inter-
face impedance is set to 120 Ohms. If plugged on the two pins closer to the
back of the COGE1 board, the interface impedance is set to “high”.
jumper for esi -1,

set to high impedance
jumper for esi -2,

set to impedance 120 Ohm
jumper set to high impedance
jumper set to impedance 120 Ohm
Figure 15: Jumper position and setting for esi-1 and esi-2
5.2.6 Backplane interfaces
5.2.6.1 GbE double star
Slot 11 and 13 have 20 point-to-point connections of 1 Gbit/s each to every

unit via the backplane allowing the interconnection of the traffic units to the
switch located in the COGE1 unit.

176
COGE1
In the typical application when connecting subscriber traffic from a service

unit the port mode of the backplane ports must be configured to “Service
Port”.
When the service unit provides the aggregation interface towards the net-
work, the port mode of the backplane ports must be configured to “VLAN
Trunk Port”.
It is also possible to configure a backplane port to “Management Port” or to
“Mirror Port”.

When changing the port mode of a backplane port to a service unit that is
managed via the GbE star (inband management), the service unit will be
reset. If there are any unsaved configuration changes on the service unit
these changes will be lost.
→ Save any configuration changes before changing the port mode of a
backplane interface.
The internal ports support RSTP. For details, please refer to:
• section AP: / unit-x / port-a, Configuration – RSTP (on page 140) for the
RSTP configuration, and to
• section AP: / unit-x / port-a, Status – RSTP (on page 161) for the RSTP
status of the internal port to the redundant COGE1 unit.
The internal ports support link aggregation. For details, please refer to:
• section AP: / unit-x / port-a, Configuration – Link Aggregation (on
page 147) for the link aggregation configuration, and to
• section AP: / unit-x / port-a, Status – Link Aggregation (on page 163) for
the link aggregation status of the internal port to the redundant COGE1
unit.

When activating RSTP on a backplane port to a service unit that is managed
via the GbE star (inband management), the management connection to the
service unit might be lost.
→ Do not activate RSTP.

When activating LA (Link Aggregation) on a backplane port to a service unit
that is managed via the GbE star (inband management), the management
connection to the service unit will be lost.
→ Do not activate LA.
Please note:
The list of service units that are managed via the GbE star (inband manage-
ment) can be found in section 4.1.1 of the [201] System Description “Mile-
Gate R3B”.

176
COGE1
Please note:
The internal backplane port to the redundant COGE1 unit has the fixed port
mode “VLAN Trunk Port”.
The connection with slot 13 is available to allow the 1:1 equipment protection
concept.
5.2.6.2 CBUS
The CBUS (Control BUS) contains signals used for the interworking of the
units in a subrack like slot select control signals, alarms, power supply, and
inventory information.
5.2.6.3 PBUS
The PBUS contains signals for synchronisation, distribution of PDH signals,

and internal communication (ICN).
COGE1 and all service units have access to the PBUS in order to exchange
information using KEYMILE proprietary protocol ICN (Internal Communica-
tion Network).
The ICN is used for the management communication between the core unit
and peripheral units within the subrack.
Among others the main functions of the ICN bus are:
• Peripheral unit configuration and fault management
Configuration, monitoring, alarm collection, and software installation with
the peripheral units.
• Broadcasting of operational parameters
Time and date, synchronisation signals, etc.
• Exchange of data between working and redundant control unit
Update or exchange of information between control units including status
and alarm information.
• Peripheral unit to peripheral unit communication
The communication of the ICN uses a proprietary protocol stack. The lower
layers of the stack rely on an HDLC synchronous bus with a speed of 5 Mbit/
s. The communication of the ICN is based on a multi master principle.
5.2.7 External alarms I/O interface
The interfaces for external alarms (inputs, outputs) of the MileGate 25x0 are
situated on the FANU4 fan unit, providing a total of 12 alarm inputs and 2
alarm outputs. They are physically connected to the backplane and pro-
cessed on the COGE1 unit.
For more information on these alarm interfaces, please refer to "[302] User
Guide “MileGate 2500/2510”".
The interface for external alarm inputs of the MileGate 23x0 are situated on
the FANU6 fan unit, providing a total of 12 alarm inputs and 2 alarm outputs
(FANU6 R3 only). They are physically connected to the backplane and pro-
cessed on the COGE1 unit.

176
COGE1
For more information on this alarm interface, please refer to "[317] User
5.2.7.1 Alarm state outputs
The COGE1 unit provides two output signals, indicating the NE alarm status,
for processing in external equipment. In the MileGate the outputs are gener-
ated and controlled by the COGE1 unit and interfaced
• to the fan unit FANU4 for the MileGate 25x0,
• to the fan unit FANU6 (R3) for the MileGate 23x0.
Please note:
The FANU6 (R1, R2) provides no alarm outputs.
The FANU4 unit is connected to the COGE1 unit via backplane signals and
a D-Sub 15 connector located at the bottom of the subrack.
The FANU6 (R3) unit is connected to the COGE1 unit via backplane signals.
In the event of a failure the COGE1, through the fan unit, will report as exter-
nal alarm one of the following:
• Non-service affecting alarm:
When the NE highest alarm severity or highest propagated alarm severity
is minor, warning, or indeterminate.
• Service affecting alarm:
When the NE highest alarm severity or highest propagated alarm severity
is critical or major.
Please note:
For more information on external input/output alarm interface and features
please refer to the “FANU4” section in [302] User Guide “MileGate 2500/
2510”, or to the “FANU6” section in [317] User Guide “MileGate 2300/2310”.
5.2.7.2 Inputs for external alarm signals
The COGE1 unit processes external alarms from equipment that is con-
nected to the alarm inputs
• on the fan unit FANU4 for the MileGate 25x0,
• on the fan unit FANU6 for the MileGate 23x0.
From the FANU4, these alarms are connected to the COGE1 unit via cabling
and the backplane D-Sub 15 connector.
From the FANU6, these alarms are connected to the COGE1 via the back-
plane.
A total of 12 external input alarm signals can be integrated into the NE fault
management. For each of these 12 alarm inputs it is possible to:
• enable or disable the input
• configure the active signal level for the input to:
− active ground
− active open

176
COGE1
Please note:
For more information on external input/output alarm interface and features
please refer to the “FANU4” section in [302] User Guide “MileGate 2500/
2510”, or to the “FANU6” section in [317] User Guide “MileGate 2300/2310”.

176
COGE1
5.3 Equipment protection EQP (core unit redundancy)
5.3.1 EQP features
In order to protect the functions and interfaces that are provided by the core
unit it is possible to implement redundancy for the COGE1 unit (in slot 11) by
placing a second COGE1 unit into the subrack, i.e. in slot 13 of the MileGate.
This is called 1:1 equipment protection.
The redundant core unit is in warm standby mode. The MAC address table
on the redundant core unit is continuously updated and thus identical to the
information on the working core unit. The configuration and the MIB data-
base are updated with a “Save” operation on the network element. Any
changes after the “Save” operation will be lost after a protection switching
event.
The ARP table is not mirrored. It is built up from scratch after a protection
switching event.
The basic scheme for 1:1 equipment protection for COGE1 is shown in
Figure 16.
The redundant core unit works as an independent active switch containing
an active RSTP switch; this means that all Ethernet front interfaces are
active for management and subtending.

Connecting both, the working and the redundant core unit to an external
switch without having activated RSTP on the switch ports, or without having
set the COGE1 trunk ports to “down for standby” will cause a broadcast
storm and will have a severe impact on both the services provided by your
MileGate and the management connection to your MileGate.
Therefore, make sure that…
• either you have activated RSTP on both the remote equipment connect-
ing to the COGE1 ports, and the COGE1 ports, before plugging the
Ethernet cables or fibres,
• or, if you do not want to operate the trunk ports with RSTP activated, you
need to activate the option to switch off the trunk port(s) of the COGE1
when in standby mode before connecting remote equipment to the
COGE1 ports. For details, please refer to more detailed information in
− section AP: / unit-x / port-a, Configuration – Port Mode (on page 136),
and
− section AP: / unit-x / protocols / rstp, Configuration – Local Bridge (on
page 173).
The active unit accommodates an active switch and performs the control
functions of the subrack. All service units are connected to the switch of the
active unit.
The switches of the active and the standby core unit are connected via the
GbE point-to-point link of the backplane.
The following hardware states will cause a protection switch-over:
• Processor failure
• HW unavailable (on the active unit)
• Node synchronisation signal failure

176
COGE1
A switch-over can also be initiated manually via the MCST GUI or the CLI.
For more details, refer to "[302] User Guide “MileGate 2500/2510”" or to
[317] User Guide “MileGate 2300/2310”.
When a protection switch-over occurs, the standby unit and the connected
service units are informed via hardware connection. The following steps will
follow in order to complete the protection switching:
• The service units switch over to the standby core unit (via the redundant
Ethernet star).
• The standby core unit takes control of the MileGate subrack and
becomes the active unit.
• Fault management delivers the appropriate alarms.
• RSTP will establish a new tree accordingly.
• Update of dynamically learnt information, like MAC address table.
MileGate MileGate
GbE ring
connection
blocked by
RSTP*
MileGate
COGE1 COGE1
working unit redundant unit
CPU CPU
active standby
links links
service unit 1 … 20 service unit
* it depends on the definition of the

root-bridge, which link is blocked
Figure 16: 1:1 core unit equipment protection concept

The switch-over can affect traffic for a short period.
Please note:
The switch-over due to an equipment failure is non-revertive.

176
COGE1
Please note:
Be aware that switching (automatic or forced) between the working and
redundant core units may imply an impact on configured services, i.e. ser-
vices may be unavailable for a short time period.
5.3.2 EQP prerequisites
To enable equipment protection for the COGE1 unit some prerequisites must
be met:
• The redundant COGE1 unit must be in the assigned state.
• The redundant unit must be hardware compatible with the working unit.
Check the hardware compatibility status in the AP: /, Status - Redun-
dancy: Core Units Status, Equipments Compatible.
• The redundant unit must be software compatible with the working unit. A
compatible software must be of the same ESW release state, e.g. both
units must use an ESW coge1_r7bxyy.

Operation of two COGE1 units running with different ESW releases is not
supported and will cause unpredictable behaviour. Make sure you operate
COGE1 redundant units with the same ESW version only.
5.3.3 EQP configuration and status
The COGE1 unit in slot-11 is assigned and configured the same way as an
unprotected COGE1 unit.
The redundant COGE1 unit in slot-13 is running with the same ESW as the
working unit and must be in the assigned state. The unit has to be config-
ured according to the used port connections and switch functions.

The network element (NE) configuration with an assigned redundant COGE1
unit must be saved (AP: / Configuration - Configuration Management: Save).
→ Otherwise, in case of a NE or COGE1 unit restart, the NE will load an
outdated configuration from the internal configuration database with-
out the redundant COGE1 unit.
→ The restore operation of the outdated configuration will not be com-
plete, i.e. a redundant COGE1 unit in the unassigned state will still be
partially active. You will loose the management communication.

The network element (NE) configuration with a removed or unassigned
redundant COGE1 unit must be saved (AP: / Configuration - Configuration
Management: Save).
→ Otherwise, in case of a NE or COGE1 unit restart, the NE will load an
outdated configuration from the internal configuration database includ-
ing the redundant COGE1 unit.

176
COGE1
The 1+1 EQP function needs no configuration. A COGE1 unit plugged in

slot-13 is automatically recognized as a redundant COGE1 unit. The EQP
status is available in the AP: /, Status - Redundancy.
For further details please refer to "[304] User Guide “MileGate & MCST”".

176
COGE1
5.4 Synchronisation
The synchronisation interface on a micro D-Sub connector provides symmet-

rical clock signals of 2.048 MHz (two inputs, two outputs) on COGE1 as
described in sections Synchronisation interface cable (675.0460.00) (on
page 37) and Synchronisation interface (on page 60).
The synchronisation parameters concerning the MileGate system are config-
ured with MCST or with the CLI under the NE root (“/”) access point, man-
agement function “Configuration”. For more details, refer to "[302] User
At COGE1 level, you can define the esi-1, esi-2 labels (Label 1, Label 2, and
Description). In addition, in case of loss of signal, this port will generate an
alarm from this access point.
Please note:
For details on the synchronisation aspects and configuration details at sys-
tem level, please refer to "[314] User Guide “TDM Services and Cross Con-
nections”".

176
COGE1
5.5 Unit Optical Indicators
The COGE1 unit has four LED optical indicators showing information about
the unit, traffic, status and lock state.
The following figure shows the LED layout on the unit.
COGE1
control unit
UNIT TRAFFIC
ACTIVE LOCKED
Figure 17: Fault and status indication LEDs on the COGE1 unit
The operating state of the COGE1 unit can be known by reading the unit
LED optical indicator from the NE.
The following table shows the signalling of the COGE1 LEDs and their
meaning.
Table 18: LED signalling on COGE1

LED Name Colour State Meaning
UNIT Red Failure Unit is not in service.
The unit is not able to provide
the requested function due to
- equipment failure (total
breakdown)
- mismatch of HW and/or SW
Recovery from this error situa-
tion is done usually by replace-
ment of unit HW or ESW.
Green / Red Booting / waiting Unit has not been taken into
(blinking 1 Hz) service yet or the unit has not
been provisioned;
Recovery from this situation is
done by taking this unit into
service with MCST.
Green Running Unit is up and running, it is
ready to provide the required
service.
Off Failure System is not powered or out-
age of power supply on unit or
outage of LED.

176
COGE1
Table 18: LED signalling on COGE1 (continued)

LED Name Colour State Meaning
TRAFFIC Red Failure One or more active failures on
unit, independent of the sever-
ity.
More detailed information is
provided by MCST.
Note: This definition is valid for
both, active and standby unit.
Off Normal Normal (error free) operation.
This is the default state.
ACTIVE Green Active Unit is active, i.e. controls the
other units in the subrack.
Off Standby Unit is standby. If the UNIT
LED is green, the unit is ready
to take over the operation in
case the active unit will fail.
LOCKED Green Locked NE is locked to a synchronisa-
tion source.
Off Not locked NE is not locked to a synchro-
nisation source.
Please note:
When COGE1 is started up for the first time (from factory default settings),
all LEDs will be “ON”. This state means that the bootloader is active but
there is no application software (ESW) to launch.
For the installation of application software (ESW), please refer to "[304] User
Guide “MileGate & MCST”".
5.5.1 COGE1 unit status indications
5.5.1.1 Booting
The initial software installation is progressing on the control unit.

The COGE1 will not respond to management communications as long as it
is in the booting state.
5.5.1.2 Waiting
The control unit is waiting for configuration. The waiting state lasts as long as
the COGE1 has no configuration.
In this status, the COGE1 can only provide the “point to point” type of man-
agement communication. This means that only the USB port will allow a
direct connection for initial commissioning.
5.5.1.3 Active
The internal resources are available and the COGE1 controls the NE. The
“active” state is characterised by a constant active green UNIT LED.

176
COGE1
All management functions, e.g. configuration management, performance

monitoring, fault management and software management are available.
5.5.1.4 Failure
The unit has failed and is not operating. The unit is either
• faulty, or
• the ESW and the unit hardware are not compatible.
5.5.1.5 Standby
The control unit is waiting to take over the control of the NE. The “standby”
operation state is only possible for the redundant unit in an NE with 1+1
equipment protection for the control unit.

176
Commissioning User Manual
COGE1
6 Commissioning
This section presents how to configure and bring into operation the COGE1
unit and its main functions. For operation, i.e. status and maintenance func-
tions refer to section Operation and maintenance (on page 87).
6.1 Introduction
This section describes the managed object model used in MileGate as it

defines the whole functionality of the unit and the concept is common to the
entire system.
To find a description on how to configure system services and inter-work
functionality with traffic units please refer to "[303] User Guide “Triple Play
Applications”" for MileGate general aspects, to [302] User Guide “MileGate
2500/2510” for MileGate 25x0 specific aspects, and to [317] User Guide
“MileGate 2300/2310” for MileGate 23x0 specific aspects.
6.1.1 Definitions
• MO (Managed Object):
Management view of a resource in the NE, e.g. COGE1
• AP (Access Point):
Addressable part of a MO, e.g. port-1: 1000BASE-X/10000BASE-R SFP
• MF (Management Function):
Predefined category of management operations, e.g. configuration, sta-
tus, etc
• Unit-x:
In this context, the COGE1 unit in slot 11 (unit-11, core unit) or in slot 13
(unit-13, redundant core unit).
6.1.2 Management concept
Please refer to "[304] User Guide “MileGate & MCST”" for information on the
management of a MileGate with the COGE1 as core unit.

176
COGE1
6.2 Managed object model (MOM)
6.2.1 MOM overview for the MileGate 25x0
The following figure shows the first two levels of the Managed Object Model
(MOM) for MileGate 25x0 with the “unit-x” specially coloured. Each one of
these entries on the tree represents an Access Point (AP). The COGE1 is a
specific “unit-x” instance.
<ap >
MileGate 25x0
<ap >
eoam
<ap >
fan
<ap >
multicast
<ap >
services
<ap >
tdmConnections
1...21 <ap >

unit-x
Figure 18: MOM for MileGate 25x0
As it can be seen from the above model, the MileGate provides an AP for
every plugged unit and APs to configure NE level functions like services.
Every AP provides Management Functions (MF) like “Main”, “Configuration”
(cfgm), “Fault Management”, etc.
6.2.2 MOM overview for the MileGate 23x0
The Managed Object Model (MOM) for MileGate 23x0 is essentially identical
to the MOM of the MileGate 25x0. Please refer to Figure 18 above.

176
COGE1
6.2.3 MOM for COGE1
The following figure shows the AP tree for the COGE1 unit in a MileGate.
<ap >
MileGate
1...2 <ap >

unit-x: COGE1
2 <ap>
esi-y
1 <ap>
internalPorts
1 <ap>
cpu
20 <ap>
slot-b
3 <ap>
lag-z
5 <ap>
port-a
1 <ap>
protocols
1 <ap>
rstp
Figure 19: MOM for COGE1
The AP “port-a” includes both, 1000BASE-X SFP Ethernet ports (port-1 and
port-2), and electrical 10/100/1000BASE-T Ethernet ports (port-3 to port-5).
For a description of the functionality included within these managed objects,
please refer to sections Commissioning (on page 73) and Operation and
maintenance (on page 87).
Please note that service related operations like VLAN tagging, filtering, etc.
are part of the managed object “services” on NE level, which is described in
[303] User Guide “Triple Play Applications”.

176
COGE1
6.3 Commissioning of COGE1
6.3.1 Prerequisites
The following prerequisites must be fulfilled for the commissioning of a

COGE1 unit:
• a COGE1 must be physically plugged in slot 11 of the MileGate subrack.
Please make sure the HW fulfils the requirements stated in [012] Release
Note “MileGate R3B”.
Please note:
When you power up the COGE1 unit for the first time (from factory default
settings), all LEDs will be “ON”. This state means that the bootloader is
active but there is no application software (ESW) to launch. You will need to
install an appropriate ESW. Please refer to "[302] User Guide “MileGate
2500/2510”" or to [317] User Guide “MileGate 2300/2310” for a guide on how
to install ESW the first time.
• a redundant COGE1 unit (if required) must be physically plugged in slot
13 of the MileGate subrack. This is mandatory if you want to implement
core unit redundancy. It is not required if you do not want core unit redun-
dancy.
• MCST must be installed on a PC that is locally available and started. For
more details about MCST installation, refer to "[304] User Guide “Mile-
Gate & MCST”".
• USB and Ethernet cabling must be connected to the corresponding ports.
For details about the installation of a USB driver on your PC, and the ini-
tial connection to your MileGate, please refer to "[302] User Guide “Mile-
Gate 2500/2510”" or to [317] User Guide “MileGate 2300/2310”.
Please note:
Ethernet cabling should be connected to both the master and the redundant
COGE1 if redundancy is implemented.
→ In this case, special care must be taken to correctly configure RSTP
settings in order to avoid broadcast storms (see warning note in sec-
tion Equipment protection EQP (core unit redundancy) (on page 65)).
If you do not want to enable RSTP, you should configure the front
port(s) of the core unit such that they are automatically disabled while
the unit is in the standby mode. For details refer to section AP: / unit-x
/ port-a, Configuration – Port Mode (on page 136).
• You need to create a suitable connection in the MCST to be able to con-
nect to your MileGate. For more details, please refer to "[304] User Guide
“MileGate & MCST”".
• You need to connect to the MileGate in order to be able to install valid
ESW. For more details, please refer to "[304] User Guide “MileGate &
MCST”".
• You need to install valid ESW on the COGE1 unit in slot 11. If you imple-
ment core unit redundancy, you need to install the identical ESW on the
COGE1 units in both slot 11 and slot 13. For details regarding the man-
agement and installation of ESW refer to "[304] User Guide “MileGate &

176
COGE1
MCST”". Please make sure the ESW version fulfils the requirements
stated in [012] Release Note “MileGate R3B”.
6.3.2 Configuring Ethernet ports
In order to configure one of the Ethernet front ports in COGE1, the following
steps should be adhered to. If you are using a redundant COGE1, the steps
must be performed on both COGE1, the active core unit (unit-11) and the
standby core unit (unit-13).
The “unit-x” stands for either “unit-11”, or “unit-13”, or for both in a sequential
order; the “port-a” stands for any of the front ports “port-1” … “port-5”.
In the CLI command lines shown below, the vertical bar character “|” means
a delimiter of several possible options. The expression “GUI AP” means the
access point (AP) for the respective action in the MCST GUI.
Table 19: Configuring Ethernet ports

Step Action
1 Assign the COGE1 unit (also see section AP: / unit-x, Main – Equipment (on page 104) and [304] User Guide
“MileGate & MCST”)
GUI AP: /unit-x, Main – Equipment, command button: “Assign”
CLI:/> /unit-x/main/Assign
2 Define the management VLAN (also see [304] User Guide “MileGate & MCST”)
GUI AP: ne, Configuration – Management Interface, Management VLAN
Enter the management VLAN ID according to the network planning, or leave the default (4089).
CLI:/> set /cfgm/VlanId <VlanId>
3 Define the port mode (also see section AP: / unit-x / port-a, Configuration – Port Mode (on page 136))
GUI AP: /unit-x/port-a, Configuration – Port Mode, select either of the port modes:
- Mode = Management Port
- Mode = VLAN Trunk Port
CLI:/> set /unit-x/cfgm/PortMode <Mode>
Note: for mirror ports, refer to sections AP: / unit-x / port-a, Configuration – Port Mode (on page 136) and
AP: / unit-x / port-a, Configuration – Mirroring (on page 154).
Enable “Port Down For Standby” if RSTP is disabled:
- Port Down For Standby = 
CLI:/> set /unit-x/cfgm/Redundancy true
Disable the port VLAN:
- Enable Port VLAN = 
CLI:/> set /unit-x/cfgm/PortVlan false <VlanId> <CoS>
4 Define the port RSTP mode (also see section AP: / unit-x / port-a, Configuration – RSTP (on page 140))
GUI AP: /unit-x/port-a, Configuration – RSTP
- RSTP Enabled =  (recommended)
CLI:/> set /unit-x/port-a/cfgm/Rstp true
For the configuration of the RSTP parameters please refer to section Port and LAG RSTP parameters (on
page 81).

176
COGE1
Table 19: Configuring Ethernet ports (continued)

Step Action
5.1 Configure the VLAN blacklist or VLAN whitelist (also see section AP: / unit-x / port-a, Configuration – VLAN list
(on page 142))
GUI AP: /unit-x/port-a, Configuration – VLAN List, select either of the two list types:
- List Type = Blacklist
- List Type = Whitelist
CLI:/> set /unit-x/port-a/cfgm/ListType Blacklist|Whitelist
5.2 If required, add VLANs to the list, otherwise leave the defaults (empty lists).
CLI:/> set /unit-x/port-a/cfgm/VlanList {<RangeStart> <RangeEnd>;}
e.g.:/> set /unit-11/port-1/cfgm/VlanList {112 120; 212 220}
Note that by default, all ports will become members of all VLANs created. This assignment is done transpar-
ently to the user.
6 Select the scheduling profile (also see section AP: / unit-x / port-a, Configuration – QoS (on page 144))
GUI AP: /unit-x/port-a, Configuration – QoS, Scheduling Profile, Name; select the profile name.
Note that with the default profile, strict priority scheduling with equal weight for each queue is applied. If you
want to have a weighted scheduling, you need to create a profile as described in section Scheduling profiles
(on page 99) and download that profile to the MileGate, then select it from the “Scheduling Profile” list.
CLI:/> set /unit-x/port-a/cfgm/SchedulingProfileName <Name>
7.1 Define the Multicast configuration (also see section AP: / unit-x / port-a, Configuration – Multicast (on
page 146))
GUI AP: /unit-x/port-a, Configuration – Multicast:
- Enable IGMP =  (this makes the port multicast capable using IGMP)
- Enable IGMP =  (this disables the support of IGMP on the port)
CLI:/> set /unit-x/port-a/cfgm/ EnableIgmpClassifier true|false
Note that you need to enable processing of IGMP router queries if you intend to configure dynamic multicast
services via this port, otherwise disable IGMP.
7.2 - Allow Static Streams=  (the corresponding static multicast groups must be configured at the AP: / “multi-
cast”. For further information refer to "[303] User Guide “Triple Play Applications”".
- Allow Static Streams=  (no static multicast groups are required).
CLI:/> set /unit-x/port-a/cfgm/ AllowStaticStreams false
7.3 - Multicast Port Mode = Hybrid (recommended for most setups)
- Multicast Port Mode = Trunk (if no IGMP queries shall be sent on this port)
- Multicast Port Mode = Subtending Access (if no IGMP reports shall be sent on this port)
CLI:/> set /unit-x/port-a/cfgm/ MulticastPortMode SubtendingAc-
cess|Trunk|Hybrid
8 Configure Link Aggregation (also see section AP: / unit-x / port-a, Configuration – Link Aggregation (on
page 147))
GUI AP: /unit-x/port-a, Configuration – Link Aggregation, select the link aggregation group membership
- LAG Member = None (the port isn’t a member of any of the three link aggregation groups)
- LAG Member = lag-1 (the port is a member of LA group 1)

176
COGE1
Table 19: Configuring Ethernet ports (continued)

Step Action
and enable LACP if necessary (LACP Enabled = )
CLI:/> set /unit-11/port-5/cfgm/LinkAggregation <LagMember> <LacpEnabled>
e.g.:/> set /unit-11/port-5/cfgm/LinkAggregation lag-1 true
Note that the port mode cannot be changed any more if you have configured the port as member of a LAG.
Note that the port cannot be configured for a LAG if there are different settings configured on two ports that
shall become member of the same LAG.
9 Configure the physical layer settings (also see section AP: / unit-x / port-a, Configuration – PHY (on page 151))
GUI AP: /unit-x/port-a, Configuration – PHY, select the speed and duplex settings.
CLI:/> set /unit-11/port-5/cfgm/PhyMode <SpeedAndDuplex>
If required, select one of the fixed modes, otherwise leave the default “Autonegotiation On” (recommended)
10 Configure the EOAM settings (also see section AP: / unit-x / port-a, Configuration – EOAM (on page 152))
GUI AP: /unit-x/port-a, Configuration – EOAM
EOAM NNI Mode Enabled = 
EOAM NNI Mode Enabled = 
CLI:/> set /unit-x/port-a/cfgm/NetworkNetworkInterface true|false
Note that this setting only affects the behaviour of the port with respect to Ethernet OAM messages. For more
details refer to section AP: / unit-x / port-a, Configuration – EOAM (on page 152), and to [316] User Guide
“Ethernet OAM”.
11 Configure the DSCP to Ethernet priority mapping (also see section AP: / unit-x / port-a, Configuration – Priority
Mapping (on page 153))
GUI AP: /unit-x/port-a, Configuration – Priority Mapping
DSCP To 802.1q Tx Priority Mapping Enabled = 
DSCP To 802.1q Tx Priority Mapping Enabled = 
CLI:/> set /unit-x/port-a/cfgm/DSCPTo802Dot1qTxPriorityMapping true|false
Note that the VLAN priority of outgoing packets is set according to the IP DSCP value. The mapping is config-
ured at the unit AP and is done per VLAN ID and per DSCP.
12 Activate the port (also see section AP: / unit-x / port-a, Main – Admin And Oper Status (on page 134))
GUI AP: /unit-x/port-a, Main – Admin And Oper Status
Select Administrative Status, State = Up
CLI:/> set /unit-x/port-a/main/AdministrativeStatus Up
Note: once the port is “Up”, no more configuration changes are allowed unless the port administrative state is
set back to “Down”.
End

176
COGE1
6.3.3 Commissioning RSTP
6.3.3.1 RSTP parameters
The following RSTP parameters will allow you to tune the performance of
your switching network:
• Bridge priority
It is used to form the ‘bridge identifier’ (priority + bridge MAC address).
The default value is 32’768. The bridge with the lowest identifier will
become ‘root bridge’ in RSTP.
Please note:
The root bridge should be close to the network resources (e.g. servers, etc.)
in your network to ensure smooth traffic flow. Also refer to more information
given in section AP: / unit-x / protocols / rstp, Configuration – Local Bridge
(on page 173).
• Hello interval
Time between two configuration BPDUs sent on a port. Its default value
is 2 seconds.
• Forwarding delay
Time spent in the listening and learning states. Its default value is 15 sec-
onds.
This value has no big impact in pure RSTP networks. It may need to be
increased if the maximum age is also increased.
• Max age time
Maximum period of time a bridge holds and uses information in a configu-
ration BPDU. Its default value is 20 seconds.
This parameter is important to support large RSTP networks.
Please note:
In the 802.1Q bridging mode (AP: /, Configuration - Packet), the RSTP
BPDU destination address is the 802.1D bridge group address.
Please note:
In the 802.1ad bridging mode (AP: /, Configuration - Packet), the RSTP
BPDU destination address is the provider bridge group address.
6.3.3.2 RSTP recommended values
For a ring topology network, the recommended values in a switch network

are according to the following table.
Table 20: RSTP ring topology values

Default values Optimized values
(up to 13 bridges) (up to 19 bridges)
Hello time 2 1
Forwarding delay 15 15
Maximum age 20 23

176
COGE1
The next figure shows the recommended ‘maximum age’ values for different
LAN sizes according to 802.1w when the ‘hello time’ is 1 and 2 seconds.
LAN Diameter (helloTime=1) LAN Diameter (helloTime=2)
20 20
18 18
LAN Diameter (bridges)
LAN Diameter (bridges)

16 16
14 14
12 12
10 10
8 8
6 6
4 4
2 2
0 0
4 8 12 16 20 24 28 32 36 40 44 4 8 12 16 20 24 28 32 36 40 44
Maxim um Age (seconds) Maxim um Age (seconds)
LAN Diameter (Standard) LAN Diameter (Standard)
Figure 20: RSTP parameters relationship
In Figure 20, the maximum age depends on the end-to-end BPDU propaga-
tion delay and a message age overestimate (which accounts for the age of
the BPDU since its origination), and from the hello time and the number of
hops (switches). Only the first (leftmost) slope of the diagrams is relevant
however.
6.3.3.3 Port and LAG RSTP parameters
The following RSTP parameters will allow you to configure the active topol-
ogy of your switching network:
• Port cost
Every bridge has a root path cost associated with it. It is the sum of the
port path costs on the least cost path to the root bridge.
The port path cost is the contribution of the port, when it is the root port,
to the root path cost for the bridge.
IEEE 802.1D-2004 recommends the following port path cost values for
the different link speeds:
Table 21: Port path cost recommended values

Link speed Recommended value Recommended range
10 Gbit/s 2’000 200 … 20’000
1 Gbit/s 20’000 2’000 … 200’000
100 Mbit/s 200’000 20’000 … 2’000’000
10 Mbit/s 2’000’000 200’000 … 20’000’000
If dynamic path cost calculation is disabled the configured port path cost
is the effective port path cost irrespective of the actual link speed.
If dynamic path cost calculation is enabled the configured port path cost
is taken as the cost value of a 1 Gbit/s link. If the link speed is set to
100 Mbit/s the effective port path cost is 10 times the configured port path
cost. If the link speed is set to 10 Mbit/s the effective port path cost is 100
times the configured port path cost:

176
COGE1
Table 22: Port path cost

Link speed Configured port cost Effective path cost
1 Gbit/s 20’000 20’000
100 Mbit/s 20’000 200’000
10 Mbit/s 20’000 2’000’000
• LAG per link cost

For a LAG, the per link path cost overrides any configured or default port
path costs of the individual links being aggregated into a LAG.
If dynamic path cost calculation is disabled the configured per link path
cost is the effective LAG cost irrespective of the number of active LAG
members and of the actual link speed.
If dynamic path cost calculation is enabled the per link path cost is
divided by the number of active links to get the effective path cost and
multiplied with the factor 10 for the 100 Mbit/s link speeds, or multiplied
with the factor 100 for the 10 Mbit/s link speeds:
Table 23: LAG path cost

Number of links Link speed Configured LAG Effective link speed Effective path cost
per link cost
1 1 Gbit/s 20’000 1 Gbit/s 20’000
2 1 Gbit/s 20’000 2 Gbit/s 10’000
3 1 Gbit/s 20’000 3 Gbit/s 6’666
4 1 Gbit/s 20’000 4 Gbit/s 5’000
1 100 Mbit/s 20’000 100 Mbit/s 200’000
2 100 Mbit/s 20’000 200 Mbit/s 100’000
3 100 Mbit/s 20’000 300 Mbit/s 66’666
4 100 Mbit/s 20’000 400 Mbit/s 50’000
1 10 Mbit/s 20’000 10 Mbit/s 2’000’000
2 10 Mbit/s 20’000 20 Mbit/s 1’000’000
3 10 Mbit/s 20’000 30 Mbit/s 666’666
4 10 Mbit/s 20’000 40 Mbit/s 500’000
Please note:
Remember that all members of a LAG must have the same link speed.
• Dynamic path cost calculation
If the dynamic path cost enabled parameter is set to  (true), the path
cost of a port or a LAG is calculated according to the effective link speed
and the number of active LAG members.
Please refer to the “port cost” and “LAG per link cost” description above.
By using the dynamic path cost calculation it will be ensured that always
the highest bandwidth path will be taken by the traffic, thereby preventing
loss of traffic over a link failure period.
A disadvantage of dynamic path cost calculation is that RSTP has to con-
verge each time the bandwidth changes, which could lead to traffic loss.
• Port priority
Each port has a unique identifier consisting of two parts,
− the port priority, and
− the port number.

176
COGE1
The more significant octet of the port identifier is the port priority.
If a bridge has two or more ports with the same root path cost, then the
port with the best port identifier is selected as the root port.
If a designated bridge has two or more ports connected to the LAN, then
the bridge port with the best port identifier is selected as the designated
port.
The lower numerical value indicates the better port identifier.
IEEE 802.1D-2004 recommends the following port priorities:
Table 24: Port priority recommended values

Recommended value Recommended range
128 0 … 240 in steps of 16
• LAG priority
For a LAG, the priority overrides any configured or default port priority of
the individual links being aggregated into a LAG.
6.3.4 Commissioning Link Aggregation (LA)
6.3.4.1 Prerequisites for LA
In order to commission link aggregation on the COGE1 front ports and the
internal ports, you need to have at least two ports available for link aggrega-
tion. These two ports need to be configured identically, but since this is not
done automatically, you have to either use the default configuration or apply
your individual configuration to all link aggregation group member ports
before enabling LA.
Please note:
You have to make sure that the following settings need to be identical on all
member ports for a LAG before activating LA for the member ports:
• the port mode (see section AP: / unit-x / port-a, Configuration – Port
Mode (on page 136)),
• the RSTP mode, the RSTP port cost, port priority and dynamic path cost
enabled parameters (see section AP: / unit-x / port-a, Configuration –
RSTP (on page 140)),
• the VLAN list (see section AP: / unit-x / port-a, Configuration – VLAN list
(on page 142)),
• the QoS settings (see section AP: / unit-x / port-a, Configuration – QoS
(on page 144)), and
• the multicast settings (see section AP: / unit-x / port-a, Configuration –
Multicast (on page 146)).
Please also note that after having configured and applied all parameters
from the above mentioned dialogues, you go to the “Link Aggregation” dia-
logue (also refer to section AP: / unit-x / port-a, Configuration – Link Aggre-
gation (on page 147)) and set the LA parameters as described in section LA
parameters (on page 84) below.

176
COGE1
6.3.4.2 LA parameters
The following parameters can be set when configuring two or more ports for
LA:
• the LA group (“lag-1”, “lag-2”, “lag-3” or “None”)
• the enable state of LACP on each of the ports (enable, disable)
Both of these parameters are set per port as described in section AP: / unit-x
/ port-a, Configuration – Link Aggregation (on page 147).
Please note:
Make sure you set both properties (the LAG membership and the LACP ena-
ble state) as required before applying the changes. Do not apply one after
the other since the two properties depend on each other.
6.3.4.3 LA group settings
Once the group has been configured for each of the member ports, the LA
group’s administrative state can be set to “up”. This is done as described in
section AP: / unit-x / lag-z, Main – Admin And Oper Status (on page 121).

176
COGE1
6.4 Core unit redundancy
For the implementation of core unit redundancy, you need a total of two core
units. The position of the first core unit in the MileGate subrack, with or with-
out redundancy, is slot 11. The redundant core unit is placed in slot 13.
Once the redundant core unit is plugged into slot 13 and has started up, you
need to make sure that the following conditions for a correct operation are
fulfilled.
6.4.1 Conditions for redundancy
In order to provide core unit redundancy, the two COGE1 units need to:
• be assigned; for unit assignment, you …
− execute the command “Assign” from the context menu on the AP:
“unit-11” and on the AP: “unit-13” (MCST GUI),
or
− execute the command “/unit-13/main/assign” in the CLI.
For equipment handling, also refer to "[304] User Guide “MileGate &
MCST”";
• run the same ESW version (for ESW installation refer to "[304] User
Guide “MileGate & MCST”");
• have the same configuration, i.e.
− the front port settings should be identical. For front port configuration
refer to section AP: / unit-x / port-a, Configuration (on page 136);
• have the same signals connected to their front ports, i.e.
− when connecting the element manager via the serial interface (USB),
they both need an USB connection; an USB hub can be used for this
purpose;
− when using synchronisation signals, the signals need to be connected
to both COGE1 ESI and/or ESO ports;
− the Ethernet cables or fibres need to be connected to both COGE1
units. In this case, please make sure that RSTP is activated on both
ends, the two COGE1 front ports, and the remote equipment.

Connecting both, the active and the redundant core unit to an external switch
without having activated RSTP on the switch ports will cause a broadcast
storm and will have a severe impact on your services.
→ Therefore, make sure that…
• either you have activated RSTP on both the remote equipment connect-
ing to the COGE1 ports, and the COGE1 ports, before plugging the
Ethernet cables or fibres,
• or, if you do not want to operate the trunk ports with RSTP activated, you
need to activate the option to switch off the trunk port(s) of the COGE1
when in standby mode (“Port Down For Standby”, see section AP: / unit-x
/ port-a, Configuration – Port Mode (on page 136)) before connecting
remote equipment to the COGE1 ports. Please refer to more detailed
information in
− section Equipment protection EQP (core unit redundancy) (on
page 65),

176
COGE1
− section AP: / unit-x / port-a, Configuration – Port Mode (on page 136),
and
− section AP: / unit-x / protocols / rstp, Configuration – Local Bridge (on
page 173).
Once these conditions are fulfilled, the two core units appear as a pair of
units where the unit in slot 13 provides equipment protection for the unit in
slot 11.

176
Operation and maintenance User Manual
COGE1
7 Operation and maintenance

This section presents how to operate the COGE1 unit once it has been com-
missioned. For a description on how to configure and bring into operation the
COGE1 unit and its main functions, refer to section Commissioning (on
page 73).
7.1 Redundancy
Provided that you have commissioned your MileGate for core unit redun-
dancy, you have the following information available for redundant operation
of the COGE1 unit:
• unit status overview (also see section AP: / unit-x, Status – Redundancy
(on page 111))
• unit fault status (also see section AP: / unit-x, Fault Management (on
page 107))
• redundancy status overview (available on NE level, refer to "[304] User
Guide “MileGate & MCST”")
• database storage overview (available on NE level, refer to "[304] User
Guide “MileGate & MCST”")
The unit status (AP: /unit-11, Status – Redundancy, or AP: /unit-13, Status -
Redundancy) provides you with information of the selected unit. Provided
that core unit redundancy is implemented, the currently active unit shows its
status as “Active” while the standby unit shows “Stand-By”. Both units show
their common information about the presence of the redundant core unit, and
about their synchronisation status:
For more information, refer to section AP: / unit-x, Status – Redundancy (on
page 111).
The unit fault status provides two fault causes related to redundancy that can
activate an alarm if the related conditions are fulfilled. The two fault causes
are
• REDSBN (Redundancy: Standby core unit is not synchronised)
• REDSWF (Redundancy: Switch-over failed)
These two fault causes can be generated by the active core unit and provide
information about the redundancy status.
Both the redundancy status overview and the database storage overview are
NE level status functions that are available on the root AP: ne. They provide
information about
• the core unit status,
• the core unit roles,
• the NE database save status,
• the NE database mirror status,
and they also provide the commands for
• isolating units from protection groups,
• joining units to protection groups,

176
COGE1
• manually perform a protection switch-over.

In case of a switch-over to stand-by or switch-over to active of the unit-11 or
of the unit-13, a notification is issued to the NE event logbook.
For more information, please refer to
• [304] User Guide “MileGate & MCST”.

176
COGE1
7.2 Maintenance
7.2.1 Inventory data
It is possible to read inventory data from the COGE1 unit via the MCST GUI
by performing the following action:
AP: / unit-11 / Main / Inventory
or (with a redundant core unit implemented)
AP: / unit-13 / Main / Inventory
In the CLI, you enter the following command line for getting inventory infor-
mation from the COGE1 unit:
Syntax:/> get /unit-11/main/EquipmentInventory
or (with a redundant core unit implemented):
Syntax:/> get /unit-13/main/EquipmentInventory
This will output the inventory information on the CLI.
7.2.2 Unit ESW download
When new ESW is needed, it is possible to perform a download of these files

as it is described in [304] User Guide “MileGate & MCST”.

The assignment of new ESW to COGE1 requires a restart of the unit. Thus,
the installation of new ESW on the unit affects all traffic functions.
7.2.3 Setting up mirror ports
In certain situations, you may need to monitor frames on any of the internal
or external ports of the COGE1 unit. For this purpose, any of the five Ether-
net front ports or any of the 20 internal ports to a service unit can be config-
ured to be a mirror port.
Assuming the case where you want to monitor all frames that are sent by
two service units in slots 1 and 20 to the COGE1 switch (unit-11), and you
have one front port of the COGE1 yet unused (e.g. port-5), you may proceed
as follows to get the frames to a monitoring equipment connected to that
spare front port.
7.2.3.1 Using the MCST GUI
If you are using the MCST GUI for managing your MileGate, please proceed
as follows (this is an example):
Table 25: Setting up mirror ports with the MCST GUI

Step Action
1 Configure the port-5 as mirror port
GUI AP: /unit-11/port-5, Configuration – Port Mode, Mode = Mirror Port
Press “Apply” in the “GUI AP: /unit-11/port-5, Configuration – Port Mode” dialogue to apply the configuration.

176
COGE1
Table 25: Setting up mirror ports with the MCST GUI (continued)
Step Action
2 Define the ports to be mirrored
GUI AP: /unit-11/port-5, Configuration – Mirroring, Port Table, Add
New Entry, Port = Backplane Port 1, Mode = Incoming; press “Apply” to apply
New Entry, Port = Backplane Port 20, Mode = Incoming; press “OK” to apply and close.
Press “OK” in the “GUI AP: /unit-11/port-5, Configuration – Mirroring” dialogue to apply the ports to be mir-
rored.
3 Set the port-5 admin state to “up”
GUI AP: /unit-11/port-5, Main – Admin And Oper Status, Administrative Status, State = “Up”
Press “OK” in the “GUI AP: /unit-11/port-5, Main – Admin And Oper Status” dialogue.
End
Now you connect your monitoring equipment to port-5 of the COGE1 unit
and start monitoring.
7.2.3.2 Using the CLI
If you are using the CLI for managing your MileGate, please proceed as fol-
lows (this is an example):
Table 26: Setting up mirror ports with the CLI

Step Action
1 Configure the port-5 as mirror port
CLI:/> set /unit-11/port-5/cfgm/PortMode MirrorPort
2 Define the ports to be mirrored
CLI:/> set /unit-11/port-5/cfgm/MirrorPortList {BacPort1 Incoming;
BacPort20 Incoming}
3 Set the port-5 admin state to “up”
CLI:/> set /unit-11/port-5/main/AdministrativeStatus Up
End
Now you connect your monitoring equipment to port-5 of the COGE1 unit
and start monitoring.

176
COGE1
7.3 RSTP status
7.3.1 RSTP bridge status
When you are using RSTP, you check the RSTP status of the COGE1
unit(s) on the AP “unit-11/protocols/rstp, Status”, and optionally (if you oper-
ate a redundant core unit) on the AP “unit-13/protocols/rstp, Status” (please
refer to section AP: / unit-x / protocols / rstp, Status (on page 174)).
The status information displayed in this dialogue shows you the MAC address
and the configured priority for both the local bridge and the root bridge.
For the root bridge, you get additional information, as
• whether the root bridge is local or remote,
• the hello interval,
• the forwarding delay, and
• the max age time.
7.3.2 RSTP notifications
When network topology changes affecting the RSTP status and causing a
change of the root bridge, a notification indicating “root bridge changed” is
issued and written to the NE event logbook.
The NE event logbook can be found in the “Main” dialogue on NE level. For
more information, please refer to "[304] User Guide “MileGate & MCST”".
7.3.3 RSTP port status
The bridge ports and link aggregation groups provide the RSTP status infor-
mation on the following APs:
• “unit-11/port-a, Status - RSTP”, refer to section AP: / unit-x / port-a, Sta-
tus – RSTP (on page 161),
• “unit-11/internalPorts/slot-x, Status - RSTP, refer to section AP: / unit-x /
port-a, Status – RSTP (on page 161), and
• “unit-11/lag-z, Status - RSTP, refer to section AP: / unit-x / lag-z, Status –
RSTP (on page 128).
If you operate a redundant core unit the RSTP status is available also on the
corresponding APs of unit-13.
The status information displayed in this dialogue shows the following information:
• Port state or LAG state
Each bridge port or LAG has an operational port or LAG state that gov-
erns whether or not it forwards MAC frames. A port or LAG can have the
following states:
− Disabled
“Disabled” is a state used in the STP algorithm. A port can be disabled
by the management or by a failure. All received frames are discarded
by a disabled port or LAG.
− Discarding
Any port that is not enabled, or has been excluded from the active
topology by the management or has been dynamically excluded from
forwarding and learning from MAC frames.
− Learning

176
COGE1
Any port or LAG that has learning enabled but forwarding disabled.
− Forwarding
A port or LAG that learns and forwards frames.
• Port role or LAG role
The RSTP algorithm assigns one of the following roles to each bridge
port or LAG:
− Root,
A forwarding port or LAG that has been selected for the spanning-tree
topology. The root port or LAG connects the bridge to the root bridge.
− Designated
A forwarding port or LAG for every LAN segment.
− Alternate
An alternate path to the root bridge. This path is different than using
the root port or LAG. The alternate port or LAG is not forwarding.
− Backup
A backup/redundant path to a segment where another bridge port
already connects. Backup ports access a shared medium. The backup
port is not forwarding.
− Disabled.
The disabled port or LAG role is assigned if the port or LAG is not
operational or is excluded from the active topology by the manage-
ment. The disabled port or LAG is not forwarding.
• Port cost or LAG cost
Display of the “Port Cost” or “LAG Cost” configuration parameter if
dynamic path cost calculation is disabled.
If dynamic path cost calculation is enabled, the effective cost according to
the link speed and the number of active LAG members is displayed.
Please refer to section Port and LAG RSTP parameters (on page 81).
• Port priority or LAG priority
Display of the “Port Priority” or “LAG Priority” configuration parameter.
Please refer to section Port and LAG RSTP parameters (on page 81).
• Port enabled or LAG enabled
Display of the “RSTP Enabled” configuration parameter.
• Edge
Ports are edge ports if they are attached to a LAN that has no other
bridges attached, e.g. if they are connected to a PC.
As soon as the bridge detects a BPDU coming to an edge port, the port
becomes a non-edge port.
• Point-to-point
The port or LAG is attached to a point-to-point link, as opposed to a
shared link.
A port or LAG operating in full duplex mode is a point-to-point port or LAG
and can be switched fast.
A port or LAG operating in half duplex mode accessing a shared link
requires a time consuming RSTP negotiation between all attached
bridges when it has to be switched.
• Dynamic path cost enabled.
Display of the “Dynamic Path Cost Enabled” parameter. Please refer to
section Port and LAG RSTP parameters (on page 81).

176
COGE1
7.4 Link Aggregation (LA) status
When you are using Link Aggregation, you can check the status of each of
the three LA groups. The information provided in the status dialogue (refer to
section AP: / unit-x / lag-z, Status (on page 123)) includes
• the “Aggregation” status (see section AP: / unit-x / lag-z, Status – Aggre-
gation (on page 123)),
• the “QoS” status (see section AP: / unit-x / lag-z, Status – QoS (on
page 126)), and
• the “RSTP” status (see section AP: / unit-x / lag-z, Status – RSTP (on
page 128)).
All information displayed in these status dialogues is applicable to the whole
virtual LA link.
7.4.1 LA notifications
When all LA group members are in operation, a notification is issued by the

unit indicating that “all member ports are operational”. The notification can be
read from the NE event logbook. If one or several LA group members are not
in operation, a notification indicating that “at least one member port is not
operational” is issued and written to the event logbook.
The NE event logbook can be found in the “Main” dialogue on NE level. For
more information, please refer to "[304] User Guide “MileGate & MCST”".

176
GUI and CLI reference User Manual
COGE1
8 GUI and CLI reference

This section gives a complete reference of the managed objects, properties,
and commands of the COGE1 core unit of the MileGate.
In this section, you will find the following information:
• An introduction (section Introduction (on page 94)),
• Profile configuration parameters (section Profiles (on page 96)),
• Unit management commands and parameters (section AP: / unit-x:
COGE1 (on page 104)),
• ESI parameters (section AP: / unit-x / esi-y (on page 113)),
• Internal ports management commands and parameters (sections AP: /
unit-x / internalPorts (on page 114), AP: / unit-x / internalPorts / cpu (on
page 115) and AP: / unit-x / internalPorts / slot-b (on page 120)),
• Link aggregation group management commands and properties (sections
AP: / unit-x / lag-z (on page 121)).
• Ethernet Front port management commands and parameters (section
AP: / unit-x / port-a (on page 130)).
• RSTP protocol management commands and parameters (sections AP: /
unit-x / protocols (on page 172) and AP: / unit-x / port-a (on page 130)).
8.1 Introduction
Below, you will find a detailed description of all the configuration parameters
and operations belonging to the managed objects model (MOM) for the
COGE1 core unit operated in a MileGate.
The descriptions provide both screen views and descriptions for the MCST
GUI, and a reference for the command line interface (CLI).
The order of appearance of the management functions in this reference is in
accordance with the context menu order for each of the APs in the MCST
GUI AP tree.
A full context menu may look as follows:
Most of the APs only offer a part of the menu items shown above since each
AP provides an individual set of management functions out of the ones
shown above.

176
COGE1
For each of the managed objects, properties, and commands, both the GUI
view and the CLI syntax are given. In order to clearly identify the CLI syntax,
a different font is used for the CLI.
This reference section comprises the management functions (CLI names
in brackets):
• “Main” (main),
• “Configuration” (cfgm),
• “Fault Management” (fm),
• “Performance Management” (pm), and
• “Status” (status).
In the tables of the sections below, the parameter default values for proper-
ties are underlined.
Please note:
In the CLI syntax shown for each of the operations, there may be line feeds
applied in this user guide although the command is entered without line
feeds in the CLI. This is due to the restricted line length available in this user
guide.
Please note:
For better legibility of numbers in this user guide, inverted commas are used
when the number’s size exceeds three digits (e.g. 40’000). In parameter
entry fields of the MCST GUI or the CLI, these inverted commas must not be
entered. Instead, the numbers are entered without these inverted commas
(e.g. 40000).
Please note:
Screenshots presented in this reference may show configurations or data
that may not correspond to the GUI you see when managing your MileGate
equipment.
Please note:
Please refer to "[304] User Guide “MileGate & MCST”" for the description of
the MCST functions (GUI and CLI) and refer to "[302] User Guide “MileGate
2500/2510”" for the specific characteristics of the MileGate 25x0 and refer to
"[317] User Guide “MileGate 2300/2310”" for the specific characteristics of
the MileGate 23x0.

176
COGE1
8.2 Profiles
8.2.1 General
A profile is a set of configuration parameters that can be applied to a certain

managed object. On the core unit, profiles are used to
• configure parameters for the packet buffer usage on the COGE1 unit, and
• configure parameters of the QoS scheduler on both the Ethernet front
ports and the Ethernet internal ports.
Profiles can be generated offline with a tool contained in the MCST GUI
(menu “Tools/Profile Tool…”) and are, in a first step, stored in the element
manager (MCST). In a second step, they need to be downloaded from the
element manager to the NE in order to make them applicable on the Mile-
Gate.
To download the profile(s) from the MCST GUI to the NE, start the MCST
GUI, connect to your MileGate, and open the Profile Tool. Now use the
download button in the Profile Tool to load selected profiles to the NE. For
more information refer to "[304] User Guide “MileGate & MCST”".
For information on how to download the profile(s) from the local manager to
the network element using the CLI, please refer to "[304] User Guide “Mile-
Gate & MCST”".
Please note:
Alternatively profiles can be created with the CLI directly on the NE.
8.2.2 Packet buffer profiles
Packet buffer profiles are applicable to the managed objects named “unit-11”
or “unit-13”. The packet buffer profiles are applicable to the layer 2 switch of
the COGE1 unit:
Table 27: Profile applicability to managed objects

Profile Profile type Applicable to MO
PktBuf PktBufProfile_1.01.00 unit-x
To create a packet buffer profile from a template, start the Profile Tool in the
MCST GUI Tools menu, and click on the “Create…” button.
To modify an existing scheduling profile, start the Profile Tool, select an
existing profile from the “Profiles on Management System” list, and click on
the “Create From…” button. To import an existing profile, click on the
“Import” button in the Profile Tool. For more information on the profile tool,
please refer to "[304] User Guide “MileGate & MCST”".
In the Create New Profile dialogue, select a PktBufProfile_x.yy.yy (where
x.yy.yy is an available version number) as template for a COGE1 unit. Make
sure that the profile type corresponds to the type required by the ESW ver-
sion running on your COGE1 unit. Refer to Table 27.
The packet buffer profile allows you to configure the packet buffer sizes for
all outgoing switch ports and for all priority levels.

176
COGE1
CLI syntax for the PacketBuffer profile creation:

Syntax: cd /
Syntax: profile create PktBufProfile_1.01.00
<ProfileName> <ProfileDescription> {<Port>
<Queue7> <Queue6> <Queue5> <Queue4> <Queue3>
<Queue2> <Queue1> <Queue0> <PortMaxBuffer>;}

When creating a packet buffer profile with the CLI, be aware to configure all
available parameters.
→ Otherwise the missing parameters (ports or queues) are undefined.

176
COGE1
Table 28: Create New Profile, PktBufProfile_1.yy.yy

Operation Name Parameter Name Range Descriptions / Details
Profile Templates Template PktBufProfile_1.yy.yy Select the packet buffer profile template as a
base for the parameter editing. This is the core
unit packet buffer profile template you need to
select.
Profile, Information Name 3 … 64 characters User editable name for the profile
ProfileName 3 … 64 characters
Description 0 … 64 characters User editable description for the profile
ProfileDe- 3 … 64 characters
scription
Profile, Data, PktBuff- Port port-1 … port-5, Identifies the front port (port-1 to port-5), the
Profile, Packet Buffer Port slot-1 … slot-21 backplane port (slot-1 to slot-21) and the cpu
Table cpu port (cpu).
port-1 … port-5, The settings for a selected port can be modi-
slot-1 … slot-21 fied with the “Modify…” command button
below the table.
cpu
Queue7 … Queue0 0 … 968’912 These columns configure the packet buffer
Queue7 … 0 … 968912 sizes of the front port or the backplane port or
Queue0 the cpu port in Bytes.
The packet buffer sizes must be a multiple of
64 bytes.
The default values are indicated in the screen-
shot above.
For further information please refer to section
Packet buffer configuration for standard
frames (on page 51).
Port Max Buffer 0 … 968’912 This column configures the maximum packet
PortMaxBuffer 0 … 968912 buffer sizes for all packet buffers per port.
Port Max Buffer must be equal or higher than
the sum of the CoS0 to CoS7 packet buffer
sizes.
The sum of all Port Max Buffer values of all
ports must 968’912 bytes or smaller.
The Port Max Buffer size must be a multiple of
64 bytes.
The default values are indicated in the screen-
shot above.
For further information please refer to section
Packet buffer configuration for standard
frames (on page 51).
Modify… Opens the MCST GUI dialogue to modify the
parameters of the port selected in the packet
buffer table.

176
COGE1
CLI syntax: there is no CLI command for this function.

Once all packet buffers are configured, you store the profile in the element
manager by clicking the “OK” button, or, in case you want to create a set of
different profiles, by clicking the “Apply” button and continue with the creation
of a further profile.
When you have finished creating profiles, you download the profiles to the
NE to make them selectable and applicable on your MileGate.
The packet buffer profile can be applied to the COGE1 unit as described in
section AP: / unit-x, Configuration - Packet Buffer (on page 107).
8.2.3 Scheduling profiles
Scheduling profiles are applicable to the managed objects named “port-a”

where a is the port number on unit-x, and to the managed objects named
“slot-b” where b is the slot number on the internal ports of the unit-x. On the
core unit COGE1, scheduling profiles are applicable to all front ports and to
the internal ports towards the backplane:
Table 29: Profile applicability to managed objects

Profile Profile type Applicable to MO
Scheduling CUWqProfile_1.01.00 unit-x/port-y
unit-x/internalPorts/slot-y
To create a scheduling profile from a template, start the Profile Tool in the
MCST GUI / Tools menu, and click on the “Create…” button.
To modify an existing scheduling profile, start the Profile Tool, select an
existing profile from the “Profiles on Management System” list, and click on
the “Create From…” button. To import an existing profile, click on the
“Import” button in the Profile Tool. For more information on the profile tool,
please refer to "[304] User Guide “MileGate & MCST”".
In the Create New Profile dialogue, select a CUWqProfile_x.yy.yy (where
x.yy.yy is an available version number) as template for a COGE1 port. Make
sure that the profile type corresponds to the type required by the ESW ver-
sion running on your COGE1 unit. Refer to Table 29.

176
COGE1
The scheduling profile allows you to select a queuing mode for each of the
eight output queues of the port. The eight queues correspond to eight traffic
classes. It also allows you to select a weight for each of the eight queues
when using weighted round robin (WRR) scheduling. With strict scheduling,
the weight is fixed.
Please note:
Per default the queue 7 (highest priority queue) is reserved for the MileGate
internal management traffic. Nevertheless you have to configure a schedul-
ing profile as if all eight queues would be available for user traffic. The
remapping of the scheduling type and weight is done automatically.
→ The effective scheduling can be checked at the AP: /unit-x/port-y, Sta-
tus - QoS and at the AP: /unit-x/lag-y, Status - QoS, x = 11 or 13.
→ For further information please refer to section CoS, 802.1p (on
page 47).
Please note:
To use the queue 7 also for user traffic the standard queue mode must be
disabled at the AP: /, Configuration - QoS.

176
COGE1
CLI syntax for the CUWq profile creation:

Syntax: cd /
Syntax: profile create CUWqProfile_1.01.00
<ProfileName> <ProfileDescription>
{<QueueNr> <QueuePrio> <Scheduling> <Weight>;}
{<QueueNr> <QueuePrio> <Scheduling> <Weight>;}

When creating a scheduling profile with the CLI, be aware to configure all
available parameters.
→ Otherwise the missing parameters (ports or queues) are undefined.
Table 30: Create New Profile, CUWqProfile_1.yy.yy

Profile Templates Template CUWqProfile_1.yy.yy Select the scheduler profile template as a
base for the parameter editing. This is the core
unit scheduler profile template you need to
select.

176
COGE1
Table 30: Create New Profile, CUWqProfile_1.yy.yy (continued)

Profile, Information Name 3 … 64 characters User editable name for the profile
ProfileName 3 … 64 characters
Description 0 … 64 characters User editable description for the profile
ProfileDe- 3 … 64 characters
scription
Profile, Data, Schedul- Queue Number 7 Identifies the queue with the highest priority on
ing Profile, Schedul- QueueNr 7 this port. The settings for queue 7 cannot be
ing Table Fixed changed.
Settings Queue Priority Highest Queue number 7 has highest priority. This set-
QueuePrio highest ting cannot be changed.
Scheduling Strict Queue number 7 uses strict priority scheduling
Scheduling strict only. This setting cannot be changed.
Weight 1 The weight for this queue is set to 1 and can-
Weight 1 not be changed.
Profile, Data, Schedul- Queue Number 6…0 Identifies the queues 6 … 0 on this port. The
ing Profile, Schedul- QueueNr 6 … 0 settings for queues 6 … 0 can be modified with
ing Table the “Modify…” command button below the
table.
Queue Priority – … Lowest This column indicates that queue 7 has high-
QueuePrio – … lowest est priority while queue 0 has lowest priority
(also refer to Default traffic to priority mapping
(on page 48)).
Scheduling Strict This queue has strict priority scheduling.
Scheduling strict
Weighted This queue has weighted round robin (WRR)
weighted scheduling.
Weight 1 … 10 For the weighted round robin queues, this indi-
Weight 1 … 10 cates the weight of each of the WRR queues.
The total of all WRR weights corresponds to
100%.
The relative percentage of each queue will be
calculated as ratio between individual weight
value and sum of all weight values.
Modify… Opens the MCST GUI dialogue to modify the
parameters of the queue selected in the
scheduling table.
CLI syntax: there is no CLI command for this function.

Once all queues are configured, you store the profile in the element manager
by clicking the “OK” button, or, in case you want to create a set of different

176
COGE1
profiles, by clicking the “Apply” button and continue with the creation of a fur-
ther profile.
When you have finished creating profiles, you download the profiles to the
NE to make them selectable and applicable on your MileGate.
The scheduling profile can be applied to COGE1 ports as described in sec-
tion AP: / unit-x / port-a, Configuration – QoS (on page 144) (front ports and
internal ports).

176
COGE1
8.3 AP: / unit-x: COGE1
In this section, all the commands and properties are described that are
required to configure and commission the COGE1 unit level. The parameters
are sorted as they are found in the access point tree.
The name “unit-x” stands for:
• the “unit-11” if only one COGE1 is operated in the MileGate, or
• the “unit-13” if, in addition to unit-11 a redundant COGE1 is operated in
the MileGate.
8.3.1 AP: / unit-x, Main
8.3.1.1 AP: / unit-x, Main – General
For a description of the “Main – General” management function, please refer

to "[304] User Guide “MileGate & MCST”".
8.3.1.2 AP: / unit-x, Main – Equipment
For a description of the “Main – Equipment” management function, please

refer to "[304] User Guide “MileGate & MCST”".
8.3.1.3 AP: / unit-x, Main – Inventory
For a description of the “Main – Inventory” management function, please

8.3.1.4 AP: / unit-x, Main – Logbooks
For a description of the “Main – Logbooks” management function, please

8.3.1.5 AP: / unit-x, Main – Software
For a description of the “Main – Software” management function, please

8.3.2 AP: / unit-x, Configuration
8.3.2.1 AP: / unit-x, Configuration - Filter
The downstream broadcast filtering dialogue allows you to assign up to 20

filters to the COGE1 unit.
Typically all broadcast messages received on a service unit (subscriber
interface) or a trunk unit are forwarded to all service units. To protect the ser-

176
COGE1
vice units from a large amount of broadcast messages which need not be
forwarded by them, these broadcast messages can be filtered.
Syntax:cd /unit-x/cfgm
Syntax:set BroadcastFilter {<VlanId> <PPPoE>
<DHCPRequest> <DHCPResponse>;}(0 … 20)
Syntax:get BroadcastFilter
Table 31: /unit-x, Configuration – Filter

Operation Name Parameter Range Descriptions / Details
Name
Downstream Broadcast Vlan Id 2 … 4089 VLAN identifier of the VLAN the broadcast fil-
Filtering VlanId 2 … 4089 ters below will be applied to.
BroadcastFilter PPPoE  Filter any PPPoE broadcast messages coming
PPPoE true from a host from being forwarded towards
other service units.

The PPPoE broadcast message will neverthe-
false less being forwarded towards the trunk inter-
face.
DHCP Request  Filter any DHCP request broadcast messages
DHCPRequest true coming from a host (DHCPDISCOVER,
DHCPREQUEST, DHCPINFORM) from being

forwarded towards other service units.
false The DHCP request broadcast message will
nevertheless being forwarded towards the
trunk interface.
DHCP Response  Filter any DHCP response broadcast mes-
DHCPResponse true sages coming from a DHCP server (DHCPOF-
FER, DHCPACK) from being forwarded

towards any service unit.
false This requires that the DHCP server must send
its responses as unicast messages.

176
COGE1
8.3.2.2 AP: / unit-x, Configuration - Priority Mapping
On the unit AP it is possible to configure the priority mapping in outgoing

direction of DSCP values to Ethernet priority values. The configuration is
done per VLAN. In double tagged VLANs the priority of the outer VLAN tag
is modified.
Up to 100 mapping entries can be configured.
The priority mapping can then be enabled at the front ports and the internal
ports.

Syntax:set DSCPTo802Dot1qPriorityMapping {<VlanId>
<DscpField> <CoS>;} (0 … 100)
Syntax:get DSCPTo802Dot1qPriorityMapping
Table 32: /unit-x, Configuration – Priority Mapping

Name
DSCP to 802.1q Priority VLAN ID 1 … 4089 VLAN identifier of the VLAN the priority map-
Mapping VlanId 1 … 4089 ping will be applied to.
DSCPTo802Dot1qPri DSCP Field 0 … 63 DSCP value controlling the VLAN priority.
orityMapping
DscpField 0 … 63
CoS CoS0 … CoS7 VLAN priority value.
CoS CoS0 … CoS7

176
COGE1
8.3.2.3 AP: / unit-x, Configuration - Packet Buffer
The switch packet buffer sizes on the COGE1 unit can be configured in the
outgoing direction per switch port and per priority. The configuration is done
via a profile.
Please refer to section Packet buffer profiles (on page 96) for a description
of the profile creation.
Syntax:set PacketBufferProfileName <Name>
Syntax:get PacketBufferProfileName
Table 33: /unit-x, Configuration – Packet Buffer

Name
Packet Buffer Profile Name <List of available pro- Select a profile from the list of previously down-
PacketBufferPro- Name files> loaded or created profiles.
fileName <List of availa- The default profile is the “default” profile which
ble profiles> is available without prior download.
With the CLI you get a list of all available pro-
files with the following command:
> help set PacketBufferProfile-
Name
Preview… Display the selected profile.
8.3.3 AP: / unit-x, Fault Management
For a description of the general aspects of the fault management, please

refer to "[304] User Guide “MileGate & MCST”". In the CLI, the path to this
management function is as follows:
/unit-11/fm
/unit-13/fm
The following table lists the fault causes of the current AP.
Table 34: /unit-x, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
SWM Software Mismatch Equipment false Minor The running ESW does not match the
Alarm assigned ESW.
SSWNA Scheduled Software Equipment false Minor The ESW that is scheduled for installa-
Not Available Alarm tion is not available on the unit. Make
sure that the ESW is downloaded to the
unit.

176
COGE1
Table 34: /unit-x, Fault Management (continued)

Affecting Severity
SWIN Software Incompatible Equipment true Major The running ESW is not compatible with
With Network Element Alarm the version required by the NE type or
version.
REDSBN CU Redundancy Stand- Equipment false Major The database of the redundant core unit
By Not In Sync Alarm is not synchronised to the database of
the master core unit. This may appear
for a short time, when configuration
changes are made, until the database is
updated, or due to a malfunction of the
update process.
REDSWF CU Redundancy Equipment false Major The switch-over to the redundant
Switch-Over Failed Alarm COGE1 has failed. This might be due to
a missing redundant COGE1, or due to a
malfunction on the redundant unit.
TEU Temperature Unaccep- Environmen- false Major The temperature detected by the unit is
table tal Alarm exceeding the range required for normal
operation.
EQM Equipment Malfunction Equipment false Critical The COGE1 controller detects any
Alarm anomalies on the unit, e.g. a voltage is
missing, a chip does not respond, etc.
HWIC Hardware Incompatible Equipment true Major The plugged HW is not compatible with
With Configuration Alarm the unit configuration HW stored in the
database. You may need to change the
HW or re-create the configuration for the
unit.
SWIC Software Incompatible Equipment true Major The ESW running on the unit is not com-
With Configuration Alarm patible with the unit configuration stored
in the database. You may need to
upgrade, or downgrade the ESW, or re-
create the configuration with the cur-
rently running ESW.
GSW General Software Equipment false Major The MileGate has detected an unspecific
Alarm Alarm problem with the ESW running on this
unit.
MFA Maintenance Function Communica- true Warning An operator initiated maintenance func-
Active tion Alarm tion is active on this unit.
UNAV Unit Not Available Equipment true Critical The unit that is configured is either not
Alarm plugged or not recognized due to a fail-
ure.
NSW No Application Soft- Equipment true Major There is no application ESW installed on
ware Alarm the unit, or the application ESW has not
yet finished its boot process.
UNAS Unit Not Assigned Equipment false Warning The unit is not assigned and cannot be
Alarm configured. To assign the unit, execute
the “Assign” command in the “Main”
function of the unit.
UIC Unit Incompatible Equipment true Major The inserted unit is not compatible with
Alarm the assigned unit.

176
COGE1
Table 34: /unit-x, Fault Management (continued)

Affecting Severity
PWRSVE Battery Power Saving Equipment true Critical Power saving is active on the unit, i.e. it
Alarm is kept in the “reset” state during battery
power backup.
Power saving is not supported on the
COGE1 unit.
8.3.4 AP: / unit-x, Status
8.3.4.1 AP: / unit-x, Status - QoS
Syntax:cd unit-x/status
Syntax:get QosPriorityMappingStatus
Table 35: /unit-x, Status - QoS

802.1p Priority Mapping Packet Priority 0…7 802.1p priority of the packet to be sent.
QosPriorityMap- PackPrio 0 … 7
pingStatus Core Unit Queue Priority Priority 0 … Priority 7 Queue priority the packet is stored before
CUPrio Priority0 … being sent.
Priority7 Queue (priority) 7 has the highest priority,
queue (priority) 0 has the lowest priority.
Please note:
The packet priority to queue priority assignment shown in the table reflects
the fact that per default the queue 7 is reserved for the MileGate internal
management traffic.
page 47).

176
COGE1
Please note:
8.3.4.2 AP: / unit-x, Status - Packet Buffer
Syntax:cd unit-x/status
Syntax:get PacketBufferStatus
Table 36: /unit-x, Status - Packet Buffer

Packet Buffer Stat, Packet- Port port-1 … port-5 Indicates the front ports (port-1 to port-
Buffer Status Table port slot-1 … slot-21 5) and the backplane ports (slot-1 to
PacketBufferStatus cpu slot-21 and cpu) of the Ethernet switch
port-1 … port-2 circuit.
slot-1 … slot-21
cpu
Cos7 … Cos0 0 … 968’912 Indicates the buffer size in bytes for
Cos7 … CoS0 0 … 968912 every queue in outgoing direction.

176
COGE1
Table 36: /unit-x, Status - Packet Buffer (continued)

Port Max Buffer 0 … 968’912 Indicates maximum packet buffer size
PortMaxBuffer 0 … 968912 in bytes for all queues in outgoing
direction.
Free For All 0 … 968’912 Indicates the difference between “Port
FreeForAll 0 … 968912 Max Buffer” and the sum of all queue
buffer sizes in outgoing direction.
The “Free for All” buffer can be used
for any CoS.
Packet Buffer Stat Total Packet Buffer Out- 0 … 968’912 Indicates the buffer size available for
PacketBufferStatus going Traffic 0 … 968912 outgoing traffic, i.e. this is the sum of
TotPktBufOutgoing the “Port Max Buffer” values of all
ports.
The buffer size is given in bytes.
Total Packet Buffer 79’664 … 1’048’576 Indicates the buffer size available for
Incoming Traffic 79664 … 1048576 incoming traffic.
TotPktBufIncoming
Total Available Packet 1’048’576 Indicates the total available buffer
Buffer Memory 1048576 memory size in bytes.
TotavailPktBuf This value is fixed.
8.3.4.3 AP: / unit-x, Status – Redundancy
If core unit redundancy is implemented, the currently active core unit shows
its status as follows:
Syntax:cd /unit-x/status
Syntax:get Status

176
COGE1
Table 37: /unit-x, Status - Redundancy

Status State Active Indicates that this unit is active in the redun-
Status State Active dancy setup.
Await Role Indicates that this unit is not active in the redun-
AwaitRole dancy setup. This is the case if core unit redun-
dancy is not implemented.
Stand-By Indicates that core unit redundancy is imple-
Standby mented, and that this unit is in standby mode.
Redundant Unit Present  Indicates that a redundant unit is present.
RedundantUnitPresent true
 Indicates that no redundant unit is present.
false
All Components Synchronised  Indicates that the standby unit is synchronised
AllComponentsSynchro- true with the master unit.
nised  Indicates that the standby unit is not synchro-
false nised with the master unit, or that there is no
standby unit available.
The core unit that is currently in redundancy standby mode shows its status
as follows:
For the operation names, parameters and their ranges, please refer to the
description above.

176
COGE1
8.4 AP: / unit-x / esi-y
8.4.1 AP: / unit-x / esi-y, Main
8.4.1.1 AP: / unit-x / esi-y, Main - General
For the Main / General dialogue, refer to "[304] User Guide “MileGate &
MCST”".
Please note:
The esi operational state is up, i.e. the icon in the AP tree turns green, when
the esi input is used as a PDH clock source.
→ For more information please refer to "[314] User Guide “TDM Services
and Cross Connections”"
8.4.2 AP: / unit-x / esi-y, Fault Management

/unit-x/esi-y/fm
Table 38: /unit-x/esi-y, Fault Management

Affecting Severity
LOS Loss Of Signal Communica- true Major There is no signal applied on the ESI
tion Alarm interface.

176
COGE1
8.5 AP: / unit-x / internalPorts
8.5.1 AP: / unit-x / internalPorts, Main
8.5.1.1 AP: / unit-x / internalPorts, Main – General
For the “Main – General” management function description, please refer to

"[304] User Guide “MileGate & MCST”".

176
COGE1
8.6 AP: / unit-x / internalPorts / cpu
8.6.1 AP: / unit-x / internalPorts / cpu, Main
8.6.1.1 AP: / unit-x / internalPorts / cpu, Main – General

8.6.1.2 AP: / unit-x / internalPorts / cpu, Main – Admin And Oper Status
This dialogue shows the operational status of the switch internal port to the
CPU.
Syntax:cd /unit-x/internalPorts/main
Syntax:get OperationalStatus
Table 39: /unit-x/internalPorts/cpu, Main – Admin And Oper Status

Operational Status State Up The port is up. This should always be the case.
OperationalStatus State Up
Down The port is down. This means that there is a sys-
Down tem failure.
8.6.2 AP: / unit-x / internalPorts / cpu, Fault Management

/unit-x/internalPorts/cpu/fm
Table 40: /unit-x/internalPorts/cpu, Fault Management

Affecting Severity
LOS Loss Of Signal Communica- true Major There is no signal applied on the internal
tion Alarm port between the switch and the CPU.
This may be due to a HW defect only. If
this happens, you might need to reboot
or replace the unit.

176
COGE1
8.6.3 AP: / unit-x / internalPorts / cpu, Performance Management
This section covers the PM parameters for the internal switch port to the cpu.
The PM parameters are presented in different groups. For the general view
on a PM dialogue of the MCST GUI, refer to "[304] User Guide “MileGate &
MCST”". The following three basic PM properties appear in every PM dia-
logue:
• Status (valid|invalid|incomplete)
• Timestamp
• Elapsed Time
Also, in each of the PM dialogues, the following counter intervals are availa-
ble:
• User Counter
• History 15min
• History 24h
The following counter groups are available for the COGE1 internal port
towards the cpu:
• “RMON Ethernet Statistic” group, see section PM group: RMON Ethernet
Statistic (on page 116),
• “MISC Ethernet Statistic” group, see section PM group: MISC Ethernet
• “MIB-2 Interface Table” group, see section PM group: MIB-2 Interface
Table (on page 117).
• “IF-MIB IfXTable” group, see section PM group: IF-MIB IfXTable (on
page 118).
Please note:
Performance alarm thresholds are not implemented in this release.
Please note:
Performance monitoring intervals are marked as “invalid” while the port’s
administrative state is “down”.
8.6.3.1 PM group: RMON Ethernet Statistic
Table 41: PM group: RMON Ethernet Statistic

PM parameter Description
In Drop Events This parameter counts the drop events at the ingress
In Octets This parameter counts the ingress octets
In Packets This parameter counts the ingress packets
In Broadcast Packets This parameter counts the ingress broadcast packets
In Multicast Packets This parameter counts the ingress multicast packets
In CRC Align Errors This parameter counts the ingress CRC alignment errors
In Undersized Packets This parameter counts the ingress undersized packets (< 64 bytes)
In Oversized Packets This parameter counts the ingress oversized packets (> 1518 bytes)
In Fragments This parameter counts the ingress fragments
In Jabbers This parameter counts the ingress jabbers

176
COGE1
Table 41: PM group: RMON Ethernet Statistic (continued)

In Estimated Collisions This parameter counts the ingress estimated collisions
In Packets 64 Octets This parameter counts the ingress octets with a size of 64 octets
In Packets 65 to 127 Octets This parameter counts the ingress octets with a size of 65 to 127 octets
In Packets 1519 and more This parameter counts the ingress octets with a size of more than 1518 octets
Octets
8.6.3.2 PM group: MISC Ethernet Statistic
Table 42: PM group: MISC Ethernet Statistic

Out Octets This parameter counts the egress octets
Out Packets This parameter counts the egress packets
Out Packets 64 Octets This parameter counts the egress octets with a size of 64 octets
Out Packets 65 to 127 Octets This parameter counts the egress octets with a size of 65 to 127 octets
Out Packets 1024 to 1518 This parameter counts the egress octets with a size of 1024 to 1518 octets
Octets
Out Packets 1519 and more This parameter counts the egress octets with a size of more than 1518 octets
Octets
8.6.3.3 PM group: MIB-2 Interface Table
Table 43: PM group: MIB-2 Interface Table

In Unicast Packets This parameter counts the ingress unicast packets
In Non-unicast Packets This parameter counts the ingress non-unicast packets
In Discards This parameter counts the ingress discarded packets
In Errors This parameter counts the ingress errors
In Unknown Protocol This parameter counts the ingress packets with an unknown protocol type
Out Unicast Packets This parameter counts the egress unicast packets
Out Non-unicast Packets This parameter counts the egress non-unicast packets
Out Discards This parameter counts the egress discarded packets
Out Errors This parameter counts the egress errors

176
COGE1
8.6.3.4 PM group: IF-MIB IfXTable
All HC counters are high capacity counters with a counter width of 64 bit.
Table 44: PM group: IF-MIB IfXTable

HC In Octets This parameter counts the ingress octets
HC In Unicast Packets This parameter counts the ingress unicast packets
HC In Multicast Packets This parameter counts the ingress multicast packets
HC In Broadcast Packets This parameter counts the ingress broadcast packets
HC Out Octets This parameter counts the egress octets
HC Out Unicast Packets This parameter counts the egress unicast packets
HC Out Broadcast Packets This parameter counts the egress broadcast packets
8.6.4 AP: / unit-x / internalPorts / cpu, Status
8.6.4.1 AP: / unit-x / internalPorts / cpu, Status – MAC
Syntax:cd /unit-x/internalPorts/cpu/status
Syntax:get PortMacStatus
Table 45: /unit-x/internalPorts/cpu, Status – MAC

Port MAC Status Max Packet Length 2’000 octets Shows the maximum length of packets for-
PortMACSta- MaxPack- 2000 warded on this port. Default value is 2000
tus etLength octets.
MAC Address 00:e0:df:00:00:00 … Shows the MAC address of the port
MacAddress 00:e0:df:ff:ff:ff
00edf0000000 …
00e0dfffffff

176
COGE1
8.6.4.2 AP: / unit-x / internalPorts / cpu, Status – PHY
Syntax:cd /unit-x/internalPorts/cpu/status
Syntax:get PortLinkStatus
Table 46: /unit-x/internalPorts/cpu, Status – PHY

Port Link Status Speed 10 Mbit/s Shows the speed currently used on the internal
PortLinkStatus Speed 10MBitpers port. The internal port to the CPU is always at 100
Mbit/s.
100 Mbit/s
100MBitpers
1000 Mbit/s
1000MBitpers
Invalid
Invalid
Link Down
LinkDown
Mode Half Duplex Shows the duplex mode of the port. The internal
Mode HalfDuplex port to the CPU is always in full duplex mode.
Full Duplex
FullDuplex
Duplex Invalid
DuplexInvalid
Link Down
LinkDown
Flow Control  Shows if flow control is enabled (true) or disabled
FlowControl true (false).
On this internal port, flow control is disabled.

false

176
COGE1
8.7 AP: / unit-x / internalPorts / slot-b
Internal ports, slot-b characteristics are identical for

• b = 1 … 10, 12, 14 … 21 in a MileGate 25x0,
• b = 7 … 10, 12, 14 in a MileGate 23x0,
which are assigned for the connection to service units.
Internal ports, slot-b characteristics are special for
• b = 11 and 13,
when these slots are assigned for the connection between the core unit(s)
COGE1. With a COGE1 placed in slot 11, and a redundant core unit COGE1
placed in slot 13, the AP: / unit-11 / internalPorts / slot-13 and the AP: / unit-
13 / internalPorts / slot-11 are fixed to the port mode “VLAN Trunk Port”.
Please note:
On the internal ports slot-13 and slot-11 some parameters differ from the
parameter handling of the other internal ports configured as “VLAN Trunk
Port”.
→ Differences are outlined in section Port default configuration parame-
ters (on page 131).
Please note:
Slot 13 can also hold a service unit.
The management functions of the internal ports (AP: / unit-x / internalPorts /
slot-b) are nearly identical to the management functions of the front ports
(AP: / unit-x / port-a). Differences are outlined in the parameter descriptions
of the front ports. Please refer to section AP: / unit-x / port-a (on page 130).

176
COGE1
8.8 AP: / unit-x / lag-z
8.8.1 AP: / unit-x / lag-z, Main

8.8.1.1 AP: / unit-x / lag-z, Main – Admin And Oper Status
Syntax:cd /unit-x/lag-z/main
Syntax:get AdministrativeStatus
Table 47: /unit-x/lag-z, Main – Admin And Oper Status

Administrative Status State Up The administrative state is “up”. This property is
AdministrativeStatus State Up read-only. The administrative state follows the
administrative state of the ports that are member
of this LAG.
Down The administrative state is “down”. This property is
Down read-only. The administrative state follows the
administrative state of the ports that are member
of this LAG.
Operational Status State Up Shows that the operational state is up. The state
OperationalStatus State Up can only be up if there are currently no failures and
if there is at least one active member.
Down Shows that the operational state is down.
Down

Both link aggregation groups (LAGs) and LAG member ports have two
states (administrative state and operational state) and can therefore be up or
down. When a port is down, the member will become “not active” as shown
in the status of the respective LAG (see section AP: / unit-x / lag-z, Status –
Aggregation (on page 123)).
No alarm indication is given when the administrative state of a port member

is set to down and therefore the LAG will not be complete. This might result
in a non-working link aggregation.

176
COGE1
Please note:
LAG operational state is up when at least one member is active.
8.8.2 AP: / unit-x / lag-z, Configuration
8.8.2.1 AP: / unit-x / lag-z, Configuration - RSTP

RSTP on a link aggregation group is only active if the LAG members have
RSTP enabled.
→ All LAG members must be configured to “RSTP Enabled” = true.
Syntax:cd /unit-x/lag-z/cfgm
Syntax:set LagRstp <LagCost> <LagPriority>
<DynamicPathCostEnabled>
Syntax:get LagRstp
Table 48: /unit-x/lag-z, Configuration – RSTP

RSTP LAG Per Link Cost 1 … 20’000 … 200’000’000 The LAG per link cost assigned to each
LagRstp LagCost 1 … 20000 … member of the LAG.
200000000 If dynamic path cost calculation is disa-
bled, the resulting LAG cost is directly the
“LAG Per Link Cost”.
If dynamic path cost is enabled, the
resulting LAG cost is calculated by multi-
plying the “LAG Per Link Cost” by 1, 10 or
by 100 if the Ethernet link speed of the
LAG members is 1000, 100 or 10 Mbit/s,
and dividing it by the number of active
LAG members.
The LAG cost is the contribution of the
LAG to the root path cost of the bridge,
when it is the root port.
LAG Priority 0 … 128 … 240 The LAG priority is the manageable com-
LagPriority 1 … 128 … 240 ponent of the LAG identifier. It is a multi-
ple of 16.

176
COGE1
Table 48: /unit-x/lag-z, Configuration – RSTP (continued)

Dynamic Path Cost Ena-  The dynamic path cost parameter adjusts
bled true the LAG cost according to the effective
DynamicPath Cos- Ethernet link speed and according to the

tEnabled number of active LAG members.
false The basic value is the configured “LAG
Per Link Cost” value, assuming that all
LAG members have a link speed of 1
Gbit/s.
With a link speeds of 100 Mbit/s, the
“LAG Cost” value is multiplied by 10.
With a link speed of 10 Mbit/s, the “Port
Cost” value is multiplied by 100.
The result is divided by the number of
active LAG members.
Using the dynamic path cost adjust-

ment can lead to unwanted RSTP topol-
ogy changes.
8.8.3 AP: / unit-x / lag-z, Fault Management

/unit-x/lag-1/fm
/unit-x/lag-2/fm
/unit-x/lag-3/fm
Table 49: /unit-x/lag-z, Fault Management

Affecting Severity
LOS Loss Of Signal Communica- true Major The signal has been lost on all members
tion Alarm of the LAG. Make sure the connectors
are plugged and the remote equipment is
transmitting a signal.
8.8.4 AP: / unit-x / lag-z, Status
8.8.4.1 AP: / unit-x / lag-z, Status – Aggregation
Due to the large size of the dialogue window, the screenshot shown below is
split into two parts. Part 1 shows the “Member Status” and the “Aggregator
Information”:

176
COGE1
Syntax:cd /unit-x/lag-z/status
Syntax:get MemberStatusTable
Syntax:get AggregateInfo
Table 50: /unit-x/lag-z, Status – Aggregation (1)

Member status Member port-1 … port-5 Shows the LAG members.
MemberStatus- Member port-1 … port-5
Table slot-1 … slot-21
slot-1 … slot-21
Active  Shows the member’s LA port is active.
Active true The state is only active if the port is func-
tional and LACP is enabled on both sides
of the link.
 Shows the member’s LA port is inactive.
false The state is inactive if the port is not func-
tional or LACP is disabled at one or both
sides of the link.

176
COGE1
Table 50: /unit-x/lag-z, Status – Aggregation (1) (continued)

Aggregator Informa- ID <string of up to 256 charac- Shows the ID string of the aggregator.
tion Id ters> Per default, the ID for the lag-1 group is
AggregateInfo <string of up to “30”, for the lag-2 group “31”, and for the
256 characters> lag-3 group “32”.
Description <string of up to 256 charac- Shows the description for the aggregator.
Description ters>
<string of up to
256 characters>
Aggregate Or Individual Aggregate Shows that the aggregator does aggre-
AggOrIndividual Aggregate gate.
Individual Shows that the aggregator does not
Individual aggregate but provides an individual link.
Time Of Last Oper <yyyy-mm-dd hh:mm:ss> Shows the date and time of the last
Change <yyyy-mm- change in operation status.
TimeOfLastOper- ddThh:mm:ss>
Change
MAC Address 00:e0:df:00:00:00 … Shows the lowest MAC address in hexa-
MacAddress 00:e0:df:ff:ff:ff decimal format of the port members.
000000000000 …
ffffffffffff
Part 2 shows the “Actor Information” and the “Partner Information”:
Syntax:get ActorInformation
Syntax:get PartnerInformation

176
COGE1
Table 51: /unit-x/lag-z, Status – Aggregation (2)

Name
Actor Information System Priority 0 … 65’535 Shows the actor system priority. This value is
ActorInformation SystemPrior- 0 … 65535 assigned by default.
ity Default is 32768
System ID 00:e0:df:00:00:00 Shows the lowest MAC address of the port mem-
SystemId … bers; six hexadecimal fields
00:e0:df:ff:ff:ff
00e0df000000 …
00e0dfffffff
Admin Key 0 … 65’535 Shows the reference to the LAG; actor and partner
AdminKey 0 … 65535 Admin Key must be the same.
Values of 30 … 33 are used by lag-1 … lag-4 per
default.
Oper Key 0 … 65’535 Shows the reference to the LAG; actor and partner
OperKey 0 … 65535 Oper Key must be the same.
Values of 30 … 33 are used by lag-1 … lag-4 per
default.
Partner Information SystemPriority 0 … 65’535 Shows the partner system priority.
PartnerInforma- SystemPrior- 0 … 65535
tion ity
System ID 00:00:00:00:00:00 Shows the lowest MAC address of the port mem-
SystemId … bers; six hexadecimal fields
ff:ff:ff:ff:ff:ff
000000000000 …
ffffffffffff
Oper Key 0 … 65’535 Shows the reference to the LAG; actor and partner
OperKey 0 … 65535 Oper Key must be the same.
8.8.4.2 AP: / unit-x / lag-z, Status – QoS
Please note:
The scheduling status table is empty in the current release.
→ It will be filled with information in a future release.

176
COGE1
Syntax:cd /unit-x/lag-z/status
Syntax:get QosStatus
Table 52: /unit-x/lag-z, Status – QoS

Name
QoS Status, Scheduling Queue Number 7…0 Identifies the queue on this port
Status QueueNr 7 … 0
SchedulingSta- Queue Priority High … Low This column indicates that queue 7 has highest
tus priority while queue 0 has lowest priority.
QueuePrio Highest … Low-
est
Scheduling strict Note that queue number 7 is fixed to “strict”.
Weighted This queue has weighted round robin queuing.
weighted
Weight 1.6% … 62.5% For the weighted round robin queues, this indi-
Weight 1.6 … 62.5 cates the weight of each of the WRR queues. The
total of all weights is 100%. The maximum possi-
ble weight for one queue is 62.5%, the minimum
1.6%, given by the number of queues and the
weight that can be configured per queue.
Please note:
The scheduling type and weight shown in the table reflects the fact that per
default the queue 7 is reserved for the MileGate internal management traffic.
page 47).
Please note:

176
COGE1
8.8.4.3 AP: / unit-x / lag-z, Status – RSTP
Syntax:get /unit-x/lag-z/status/LagRstp
Table 53: /unit-x/lag-z, Status – RSTP

RSTP Status LAG State Disabled Shows that the RSTP LAG is disabled.
LagRstp LagState Disabled
Discarding Shows that the RSTP LAG is discarding packets.
Discarding
Learning Shows that the RSTP LAG is in the learning
Learning phase.
Forwarding Shows that the RSTP LAG is forwarding pack-
Forwarding ets.
LAG Role Disabled Shows that the RSTP LAG is “disabled”.
LagRole Disabled
Alternate Shows that the RSTP LAG is an alternate port.
Alternate
Backup Shows that the RSTP LAG is a backup port.
Backup
Root Shows that the RSTP LAG is a root port.
Root
Designated Shows that the RSTP LAG is the designated
Designated port.
LAG Cost 0 … 200’000’000 Shows the RSTP LAG cost.
LagCost 0 … 200000000
LAG Priority 0 … 240 Shows the configured RSTP LAG priority.
LagPriority 0 … 240

176
COGE1
Table 53: /unit-x/lag-z, Status – RSTP (continued)

LAG Enabled  Shows that RSTP on the LAG is enabled.
LagEnabled true
 Shows that RSTP on the LAG is disabled.
false
Edge  Shows that the LAG is at the edge of an RSTP
Edge true tree. A port connected to an end station is allow-
ing fast transition in case of a link failure.
 Shows that the LAG is not at the edge of but
false inside an RSTP tree.
Point-to-Point  Shows that the device connected at the other
PointToPoint true end is running RSTP.
 Shows that the device at the other end is not
false running RSTP.
Dynamic Path Cost  Shows the configured “Dynamic Path Cost Ena-
Enabled true bled” parameter.
DynamicPath- 
CostEnabled
false

176
COGE1
8.9 AP: / unit-x / port-a
This section not only shows the management functions of the front ports but
also the management functions of the backplane ports and the redundant
ports, since they are very similar.
The descriptions in the following sections use the access point designations
of the front ports. For the internal port management function replace the AP
“/unit-x/port-a” by the AP “/unit-x/internalPorts/slot-b”.
8.9.1 COGE1 ports
8.9.1.1 Port types and port modes
The COGE1 has different port types used for the Ethernet traffic:
• Front port on the COGE1 unit for the connection to an external equip-
ment.
• Backplane port for the connection to a service unit plugged in the same
network element via the GbE star.
• Redundant port for the connection to the redundant COGE1 unit via the
GbE star.
Depending of the port type the available port modes differ and the handling
of some parameters may differ as well. The figure below shows the available
port modes for the different port types used in the MileGate:
Front Port: MileGate

- VLAN Trunk Port
- Management Port
- Mirror Port
COGE1 COGE1
working redundant
unit Redundant Port: unit
- VLAN Trunk Port
Backplane Port:
- Service Port
- VLAN Trunk Port
- Management Port
- Mirror Port
service unit 1 … 20 service unit
Figure 21: Port types and port modes in MileGate
The access points of the different port types are as follows:

• Front Port:
AP: / unit-x / port-a, a = 1 to 5
• Backplane Port:
AP: / unit-x / internalPorts / slot-b, b = 1 to 10, 12, 13 (without core unit
redundancy), 14 to 21

176
COGE1
• Redundant Port:
AP: / unit-x / internalPorts / slot-b, b = 11, 13 (with core unit redundancy)
8.9.1.2 Port default configuration parameters
The tables below show the default configuration parameter values for the dif-
ferent port types, depending of the port mode. Green shaded entries can be
modified, grey shaded entries are fixed.
Table 54: Default configuration parameters for Front Ports

Parameter Port Mode
VLAN Trunk Management Mirror Port
Port Port
Port Mode, Redundancy, Port Down For Standby false false false
Port Mode, Port VLAN, Enable Port VLAN true false false
Port Mode, Port VLAN, VLAN ID 1 1 1
Port Mode, Port VLAN, CoS CoS0 CoS0 CoS0
Port Mode, MTU Size 2000 2000 2000
RSTP, RSTP Enabled true false false
RSTP, RSTP Parameters, Port Cost 20’000 20’000 20’000
RSTP, RSTP Parameters, Port Priority 128 128 128
RSTP, RSTP Parameters, Dynamic Path Cost Enabled false false false
VLAN List, Management VLAN, VLAN ID from NE config from NE config from NE config
VLAN List, List Type, Type Blacklist Blacklist Blacklist
VLAN List, VLAN List, Add/Modify/Remove Table empty Table empty Table empty
VLAN List, Flush VLAN List Function No function No function
QoS, Scheduling Profile, Name default default default
Multicast, Enable IGMP true false false
Multicast, Allow Static Streams false false false
Multicast, Multicast Port Mode Hybrid Subtending Subtending
Access Access
Link Aggregation, Link Aggregation, LAG Member None None None
Link Aggregation, Link Aggregation, LACP Enabled false false false
PHY, Mode, Speed And Duplex Autonegotiation Autonegotiation Autonegotiation
On On On
PHY, Flow Control Enabled false false false
EOAM, Network Network Interface, EOAM NNI Mode Enabled false false false
Priority Mapping, DSCP To 802.1q Tx Priority Mapping, DSCP To false false false
802.1q Tx Priority Mapping Enabled
Mirroring, Port List, Port Table Table empty Table empty Table empty
Table 55: Default configuration parameters for Backplane Ports

Parameter Port Mode
Service Port VLAN Trunk Management Mirror Port
Port Port
Port Mode, Redundancy, Port Down For true false true false
Standby
Port Mode, Port VLAN, Enable Port VLAN false true false false

176
COGE1
Table 55: Default configuration parameters for Backplane Ports (continued)

Parameter Port Mode
Service Port VLAN Trunk Management Mirror Port
Port Port
Port Mode, Port VLAN, VLAN ID 1 1 1 1
Port Mode, Port VLAN, CoS CoS0 CoS0 CoS0 CoS0
Port Mode, MTU Size 2000 2000 2000 2000
RSTP, RSTP Enabled false true false false
RSTP, RSTP Parameters, Port Cost 20’000 20’000 20’000 20’000
RSTP, RSTP Parameters, Port Priority 128 128 128 128
RSTP, RSTP Parameters, Dynamic Path Cost false false false false
Enabled
VLAN List, Management VLAN, VLAN ID from NE config from NE config from NE config from NE config
VLAN List, List Type, Type Blacklist Blacklist Blacklist Blacklist
VLAN List, VLAN List, Add/Modify/Remove Table empty Table empty Table empty Table empty
VLAN List, Flush VLAN List No function Function No function No function
QoS, Scheduling Profile, Name default default default default
Multicast, Enable IGMP true true false false
Multicast, Allow Static Streams true false false false
Multicast, Multicast Port Mode Subtending Hybrid Subtending Subtending
Access Access Access
Link Aggregation, Link Aggregation, LAG Mem- None None None None
ber
Link Aggregation, Link Aggregation, LACP Ena- false false false false
bled
PHY, Mode, Speed And Duplex Autodiscovery Autodiscovery Autodiscovery Autodiscovery
PHY, Flow Control Enabled false false false false
EOAM, Network Network Interface, EOAM NNI false false false false
Mode Enabled
Priority Mapping, DSCP To 802.1q Tx Priority true false false false
Mapping, DSCP To 802.1q Tx Priority Mapping
Enabled
Mirroring, Port List, Port Table Table empty Table empty Table empty Table empty
Table 56: Default configuration parameters for Redundant Ports

Parameter Port Mode
VLAN Trunk
Port
Port Mode, Redundancy, Port Down For Standby false
Port Mode, Port VLAN, Enable Port VLAN true
Port Mode, Port VLAN, VLAN ID 1
Port Mode, Port VLAN, CoS CoS0
Port Mode, MTU Size 2000
RSTP, RSTP Enabled true
RSTP, RSTP Parameters, Port Cost 20’000
RSTP, RSTP Parameters, Port Priority 128
RSTP, RSTP Parameters, Dynamic Path Cost Enabled false

176
COGE1
Table 56: Default configuration parameters for Redundant Ports

Parameter Port Mode
VLAN Trunk
Port
VLAN List, Management VLAN, VLAN ID from NE config
VLAN List, List Type, Type Blacklist
VLAN List, VLAN List, Add/Modify/Remove Table empty
VLAN List, Flush VLAN List Function
QoS, Scheduling Profile, Name default
Multicast, Enable IGMP true
Multicast, Allow Static Streams true
Multicast, Multicast Port Mode Hybrid
Link Aggregation, Link Aggregation, LAG Member None
Link Aggregation, Link Aggregation, LACP Enabled false
PHY, Mode, Speed And Duplex Autodiscovery
PHY, Flow Control Enabled false
EOAM, Network Network Interface, EOAM NNI Mode Enabled false
Priority Mapping, DSCP To 802.1q Tx Priority Mapping, DSCP To false
802.1q Tx Priority Mapping Enabled
Mirroring, Port List, Port Table Table empty
Please note:
If a port has the default configuration or not is indicated in the port status dia-
logue:
→ Status - Port Mode - Default Config Enabled.
8.9.2 AP: / unit-x / port-a, Main
8.9.2.1 AP: / unit-x / port-a, Main – General

Please note:
The COGE1 implements two different types of Ethernet ports, 2 SFP based
ports, and 3 electrical ports. The SFP based ports are SFP cages for imple-
mentation of SFP modules. The standard SFP modules recommended for
use with COGE1 are Gigabit Ethernet modules supporting only the speed of
1000 Mbit/s (1 Gbit/s). The ports are therefore called
• ”port-x: 1000BASE-X SFP”
in both the MCST GUI and the CLI. The electrical ports provide speeds of
10, 100 or 1000 Mbit/s and are therefore called
• “port-x: 10/100/1000BASE-T”
in both the MCST GUI and the CLI.
The parameters available for the two types of GbE interfaces (“1000BASE-
FX SFP” and “10/100/1000BASE-T”) are identical except

176
COGE1
• for the tab “Main - SFP” which is only available for the SFP ports (port-1
and port-2),
• for the tab “Status - DDM” which is only available for the SFP ports (port-
1 and port-2), and
• for the SFP equipment specific alarms
Please note:
The COGE1 implements one type of Ethernet internal ports, 1GbE electrical
ports. The speed of the ports is fixed.
The ports are therefore called
→ ”slot-b: 1 Gbit/s Ethernet”
in both the MCST GUI and the CLI.
The parameters available for the Ethernet internal interfaces are identical to
the Ethernet electrical front ports.
8.9.2.2 AP: / unit-x / port-a, Main – Admin And Oper Status
Syntax:cd /unit-x/port-a/main
Syntax:set AdministrativeStatus <State>
Syntax:get AdministrativeStatus
Table 57: /unit-x/port-a, Main – Admin And Oper Status

Name
Administrative Status State Up Select “Up” to bring the port into service
AdministrativeSta- State Up
tus Down Select “Down” to take the port out of service. This
Down is required to configure some properties of the port
(e.g. the port mode, see section AP: / unit-x /
port-a, Configuration – Port Mode (on
page 136)).
Operational Status State Up Shows the operational state is up. The state can
OperationalStatus State Up only be up if the administrative state is up and
there are currently no failures.
Down Shows the operational state is down
Down
Testing Shows the port is in a testing state
Testing

176
COGE1
8.9.2.3 AP: / unit-x / port-a, Main – SFP
The following dialogue is applicable only to the ports that can be equipped
with an SFP, i.e. “port-1” and “port-2”. The dialogue shows SFP information
of the SFP module that is plugged in this Ethernet port. Some fields may be
empty or unavailable, depending on the inventory information provided by
the manufacturer.
Syntax:cd /unit-x/port-a/main
Syntax:get EquipmentInventory
Table 58: /unit-x/port-a, Main – SFP

Equipment Inventory Equipment State Unknown Displays the equipment state is unknown: no
EquipmentInven- EquipmentState Unknown SFP plugged in ever.
tory
Empty Shows that there was an SFP before, but it has
Empty been removed.
Plugged Shows that an SFP is present.
Plugged
GbE Compliance Code 0 … 16 The following fields display the content of vendor
GbeComplianceCode 0 … 16 inventory information of the SFP’s EEPROM.
Link Length 0 … 32 Reachable link length according to the SFP
LinkLength 0 … 32 specification (short, intermediate, long distance).
Transmitter Technology 0 … 32 Shows the technology used for the transmitter
TransmitterTechnol- 0 … 32 part.
ogy
Transmission Media 0 … 32 Shows the media for which the module is fore-
TransmissionMedia 0 … 32 seen.
Speed 0 … 20 Shows the speed supported by the module.
ChannelSpeed 0 … 20

176
COGE1
Table 58: /unit-x/port-a, Main – SFP (continued)

Manufacturer Serial Number 0 … 16 Shows the serial number of the module.
manufacturerSerial- 0 … 16
Number
Manufacturer ID 0 … 16 Shows the module’s manufacturer ID.
ManufacturerID 0 … 16
Manufacturer Part Number 0 … 16 Shows the part number provided by the manu-
ManufacturerPartNum- 0 … 16 facturer.
ber
8.9.3 AP: / unit-x / port-a, Configuration
The information in this section is basically valid for both front port types,
1000BASE-X SFP ports (port-1, port-2) and 10/100/1000BASE-T ports (port-
3, port-4 and port-5), for the backplane port types (slot-1 to slot-10, slot-12,
slot-14 to slot-21), and for the redundant port types (slot-11, slot-13).
Differences are stated explicitly where applicable.
Please note:
Configuration parameter default values are listed in section Port default con-
figuration parameters (on page 131).
8.9.3.1 AP: / unit-x / port-a, Configuration – Port Mode

When changing the port mode the port parameters will have the default val-
ues applied. The port mode change requires therefore a two step procedure:
→ 1. step: Change the port mode and apply the change. The port param-
eters have the default values applied. Any port parameter modification
is lost.
→ 2. step: Modify the port parameters and apply the modification. The
port parameters have the modified values applied.

176
COGE1
Syntax:cd /unit-x/port-a/cfgm
Syntax:set PortMode <Mode>
Syntax:get PortMode
Syntax:set Redundancy <PortDownForStandby>
Syntax:get Redundancy
Syntax:set PortVlan <EnablePortVlan> <VlanId> <CoS>
Syntax:get PortVlan
Syntax:set MTUSize <MTUSize>
Syntax:get MTUSize

176
COGE1
Table 59: /unit-x/port-a, Configuration – Port Mode

Mode Mode Not Configured The port mode is not set.
PortMode Mode NotConfigured
Management Port The port is a pure management port. Any untagged
Management- traffic will be forwarded to/from the internal manage-
Port ment VLAN. Tagged frames will be discarded.
This mode is available for front ports and for back-
plane ports.
VLAN Trunk Port The port is a VLAN trunk port. All traffic is expected
VlanTrunkPort to be VLAN tagged. All VLAN tagged traffic is
accepted and delivered. Use black and white VLAN
lists to define what traffic should be allowed or not
be allowed (see section AP: / unit-x / port-a, Config-
uration – VLAN list (on page 142)).
This mode is available for front ports, backplane
ports and redundant ports.
Service Port The port is a VLAN service port. It connects a ser-
VlanService- vice unit to the COGE1 unit.
Port All traffic is VLAN tagged. All VLAN tagged traffic is
accepted and delivered.
This mode is available for backplane ports.
Mirror Port The port is a mirror port. It is mirroring traffic from
MirrorPort any other front port of the COGE1 unit, or from any
other internal port, or from the host processor port of
the COGE1 unit. For setting the port(s) to be mir-
rored, refer to section AP: / unit-x / port-a, Config-
uration – Mirroring (on page 154)”.
This mode is available for front ports and for back-
plane ports.
Redundancy Port Down For Standby  Sets the port to the administrative state “down” if
Redundancy PortDownFor- true COGE1 redundancy is implemented and the unit is
Standby in the “standby” mode. Sets the port to the config-
ured administrative state when the unit is in the
“active” mode.
The default value is dependent of the port mode.
 Does not set the port to the administrative state
false “down” if COGE1 redundancy is implemented and
the unit is in the “standby” mode, but leaves the port
always at the configured administrative state.
Port VLAN Enable Port VLAN  True: Enable port VLAN. Incoming untagged traffic
PortVlan EnablePortVlan true is assigned the port VLAN ID. Outgoing traffic with
the port VLAN ID gets the VLAN tag removed.

False: Disable port VLAN. Incoming untagged traffic
false at a VLAN trunk port is dropped.
The default value is dependent of the port mode.
VLAN ID 1 … 4089 VLAN ID to be assigned to untagged traffic.
VlanId 1 … 4089
CoS CoS0 … CoS7 CoS to be assigned to untagged traffic.
CoS CoS0 … CoS7

176
COGE1
Table 59: /unit-x/port-a, Configuration – Port Mode (continued)

MTU Size MTU Size 1518 … 2000 … Maximum Transmission Unit (MTU) size.
MTUSize MTUSize 10’000 octets, The MTU size is calculated without the VLAN tag(s).
only even values MTU sizes >2000 octets are also known as jumbo
1518 … 2000 … frames.
10000
only even values The MileGate supports jumbo frames for traffic
between 1 COGE1 trunk port and up to 2 service
ports, or between 2 COGE1 trunk ports.
Note: The configuration of jumbo frames requires a
correspondingly modified packet buffer profile.
Please refer to section Packet buffer configuration
for jumbo frames (on page 52).

When changing the port mode of a backplane port to a service unit that is
managed via the GbE star (inband management), the service unit will be
reset. If there are any unsaved configuration changes on the service unit
these changes will be lost.
→ Save any configuration changes before changing the port mode of a
backplane interface.
Please note:
Gate R3B”.
Please note:
The “Redundancy” property in the above dialogue provides you with the
means to prevent loops even with RSTP not being activated. While RSTP is
a good measure for loop prevention, the “Redundancy” property sets the
Ethernet front port of the core unit that is in the standby mode to “down” and
hence allows you to connect both core units to a remote equipment. With
RSTP switched off, this only works if you have just one port per core unit
connected to the remote equipment. Having activated (i.e. administrative
state set to “Up”) more than one front port per core unit absolutely requires
RSTP to be configured on both the two core units and the remote equipment
if more than one front port per core unit is connected to the same remote
equipment.
Please note:
For an overview on the specific characteristics of trunk ports, service ports,
management ports and mirror ports, please refer to section Interfaces (on
page 57).

176
COGE1
8.9.3.2 AP: / unit-x / port-a, Configuration – RSTP
Syntax:set Rstp <RstpEnabled>
Syntax:get Rstp
Syntax:set RstpParams <PortCost> <PortPriority>
<DynamicPathCostEnabled>
Syntax:get RstpParams
Table 60: /unit-x/port-a, Configuration – RSTP

RSTP RSTP Enabled  Enable RSTP on the port.
Rstp RstpEnabled true The default value is dependent of the port mode.
 Disable RSTP on the port.
false
RSTP Parameters Port Cost 1 … 20’000 … The port (path) cost is the contribution of the port
RstpParams PortCost 200’000’000 to the root path cost of the bridge, when it is the
1 … 20000 … root port.
200000000
Port Priority 0 … 128 … 240 The port priority is the manageable component of
PortPriority 1 … 128 … 240 the port identifier. It is a multiple of 16.
Dynamic Path Cost  The dynamic path cost parameter adjusts the port
Enabled true (path) cost according to the effective Ethernet link
DynamicPath speed.

CostEnabled The basic value is the configured “Port Cost”
false value, assuming a link speed of 1 Gbit/s.
With a link speed of 100 Mbit/s, the “Port Cost”
value is multiplied by 10.
With a link speed of 10 Mbit/s, the “Port Cost”
value is multiplied by 100.
Using the dynamic path cost adjustment can

lead to unwanted RSTP topology changes.

176
COGE1

When activating RSTP on a backplane port to a service unit that is managed
via the GbE star (inband management), the management connection to the
service unit might be lost.
→ Do not activate RSTP.
Please note:
Gate R3B”.

Disabling RSTP on a trunk port or management port might lead to loops and
might completely interrupt both user traffic and management traffic through
your MileGate. In such a case, you might only be able to connect to your
MileGate via the local serial interface.
Please note:
In order to prevent loops, we strongly recommend to activate RSTP, i.e. to
set the parameter “RSTP Enabled” to “” in the MCST GUI, or to set the
parameter “RstpEnabled” to “true” in the CLI. Please also activate RSTP on
the remote equipment connected to the COGE1 front port(s) in this case,
and carefully read and follow the instructions in section Commissioning
RSTP (on page 80).
Please note:
In case of a broadcast storm that is occurring due to a loop, you may need to
connect locally to your MileGate and enable RSTP on the ports causing the
loop, or to interrupt one of the Ethernet links causing the loop, by unplugging
the Ethernet cable or fibre. After the loop has been broken, you may recon-
nect to your MileGate and enable RSTP, then re-connect the cabling.

176
COGE1
8.9.3.3 AP: / unit-x / port-a, Configuration – VLAN list
Syntax:get ManagementVlan
Syntax:set ListType <Type>
Syntax:get ListType
Syntax:set VlanList {<RangeStart> <RangeEnd>;}
Syntax:get VlanList
Syntax:FlushVlanList
Table 61: /unit-x/port-a, Configuration – VLAN List

Name
Management VLAN VLAN ID 1 … 4’089 Shows the configured VLAN ID for the management
ManagementVlan VlanId 1 … 4089 network. This is just for information in order to minimize
the risk of blacklisting the management VLAN ID, or for-
getting to whitelist the management VLAN ID. For the
configuration of the management VLAN ID, refer to
List Type Type Blacklist Select this to block all traffic in all VLANs listed in the
ListType Type Blacklist VLAN List.
Whitelist Select this to only allow traffic forwarding in listed
Whitelist VLANs.

176
COGE1
Table 61: /unit-x/port-a, Configuration – VLAN List (continued)

Name
VLAN List Range Start 1 … 4’089 Set the first VLAN ID of the range to be added to the list.
VlanList RangeStart 1 … 4089
Range End 1 … 4’089 Set the last VLAN ID of the range to be added to the list.
RangeEnd 1 … 4089
Add… (see section AP: / Command to add a VLAN range to the list (GUI only).
unit-x / port-a, Con- In the CLI, the full VLAN list has to be entered when
figuration – VLAN changing the list.
list, Add… (on
page 144))
Modify… (see section AP: / Command to modify a selected VLAN range in the list
unit-x / port-a, Con- (GUI only).
figuration – VLAN In the CLI, the full VLAN list has to be entered when
list, Modify… (on changing the list.
page 144))
Remove Command to remove a selected VLAN range from the
list (GUI only).
Please note:
To remove several entries from the VLAN Blacklist or Whitelist, press and
hold the left-hand mouse button while selecting entries in the table, then click
“Remove”.

If you configure the VLAN list on a port with the port mode set to “Manage-
ment Port”, you risk to block management access to the MileGate network
element. Blacklisting the management VLAN ID or not adding the manage-
ment VLAN ID to the whitelist would disable an inband management connec-
tion to the network element.
Please note:
In order to lower the risk of blocked VLANs, the VLAN list should not be con-
figured on a port configured as “Management Port”.
→ If you configure the VLAN list on a management port, make sure you
do not blacklist the management VLAN ID configured for the network
element, or, if using the whitelist, make sure to add the management
VLAN ID to the whitelist.

176
COGE1
8.9.3.4 AP: / unit-x / port-a, Configuration – VLAN list, Add…
Table 62: /unit-x/port-a, Configuration – VLAN List, Add…

New Entry Range Start 1 … 4’089 Set the first VLAN ID of the range to be added to
the list (GUI only).
Range End <Range Start> … 4’089 Set the last VLAN ID of the range to be added to
the list (GUI only).
The entry range is checked, i.e. if you enter a range with the range end that
is smaller than the range start and apply the list, an error message “Range
check of VLAN IDs: Start and/or end of range are not valid.” is issued (GUI
only).
If you enter a range that is overlapping with an already existing range and
apply the list, an error message “Range check of VLAN IDs: Start and/or end
of range are interfering with other ranges.” is issued (GUI only).
Please note:
In the CLI, no such error messages are issued since the CLI only allows
entering a full list, but not adding, modifying, or removing entries from the
list; i.e. in the CLI, you always have to enter the full new VLAN list if you
want to make changes to the VLAN list.
8.9.3.5 AP: / unit-x / port-a, Configuration – VLAN list, Modify…
Table 63: /unit-x/port-a, Configuration – VLAN List, Modify…

Modify Entry Range Start 1 … 4’089 Set the first VLAN ID of the range to be modified
(GUI only).
Range End <Range Start> … 4’089 Set the last VLAN ID of the range to be modified
(GUI only).
For possible error messages refer to section AP: / unit-x / port-a, Configuration –
VLAN list, Add… (on page 144) above.
8.9.3.6 AP: / unit-x / port-a, Configuration – QoS
The QoS dialogue allows you to assign a scheduling profile to the port.

176
COGE1
In order to select a specific scheduling profile, you need to create that profile
in the Profile Tool, and download it to the MileGate or you need to create
that profile on the NE. Please refer to section Scheduling profiles (on
page 99) above.
Once the scheduling profile is created and downloaded to the NE, you can
select it and apply it to a port:
Syntax:set SchedulingProfileName <Name>
Syntax:get SchedulingProfileName
Table 64: /unit-x/port-a, Configuration – QoS

Name
Scheduling Profile Name default Select the default scheduling profile
SchedulingPro- Name default
fileName <list of scheduling pro-
Select a scheduling profile that has been
files> downloaded to MileGate or has been created
<list of schedul- with the CLI.
ing profiles> With the CLI you get the list of available pro-
files with the command:
help set SchedulingProfileName
Preview… This command opens a window displaying the
parameters of the currently selected schedul-
ing profile (GUI only).

176
COGE1
The preview dialogue shows the settings in the scheduling profile. This infor-
mation is displayed read-only.
8.9.3.7 AP: / unit-x / port-a, Configuration – Multicast
Syntax:set EnableIgmpClassifier <EnableIgmp>
Syntax:get EnableIgmpClassifier
Syntax:set AllowStaticStreams <AllowStaticStreams>
Syntax:get AllowStaticStreams
Syntax:set MulticastPortMode <MulticastPortMode>
Syntax:get MulticastPortMode
Table 65: /unit-x/port-a, Configuration – Multicast

Enable IGMP  Select this to accept IGMP messages on this
EnableIgmpClas- EnableIgmp true port.
sifier The default value is dependent of the port
mode.
 Select this to discard IGMP messages on this
false port.

176
COGE1
Table 65: /unit-x/port-a, Configuration – Multicast (continued)

Allow Static Streams  Support static multicast. Static multicast makes
AllowStatic- AllowStatic- true it possible to forward specific multicast streams
Streams Streams directly to member ports without any interaction

required from the subscriber or from a network
false server.
The default value is dependent of the port
mode.
Multicast Port Mode Subtending Access Select this if the COGE1 port is being used to
MulticastPort- MulticastPort- SubtendingAc- connect subtending users or subtending equip-
Mode Mode cess ment. The MileGate will only accept IGMP
reports and send IGMP queries on this port.
The default value is dependent of the port
mode.
Trunk Select this if the COGE1 port is used to connect
Trunk only multicast routers or servers. The MileGate
will only accept IGMP queries and send IGMP
reports on this port.
Hybrid Select this if the COGE1 port is potentially
Hybrid being used to connect multicast subtending
equipment or multicast routers or servers.
The MileGate will learn its role from the first
received query, which results in the hybrid-trunk
mode, or from the first received join report,
which results in the hybrid-subtending access
mode.
8.9.3.8 AP: / unit-x / port-a, Configuration – Link Aggregation
Syntax:set LinkAggregation <LagMember> <LacpEnabled>
Syntax:get LinkAggregation

176
COGE1
Table 66: /unit-x/port-a, Configuration – Link Aggregation

Link Aggregation LAG Member None Select this if you do not want to assign a LA group.
LinkAggregation LagMember None
lag-1 Select this if the port shall be member of LA group
lag-1 1.
lag-2 2.
lag-3 3.
LACP Enabled  Select to enable LACP on this port.
LacpEnabled true This parameter can only be modified if the port is
not member of a LAG, i.e. you have to remove the
port from the LAG and add it after the LACP
parameter modification.
The LACP setting of all members of a LAG must
be the same.
 Select to disable LACP on this port.
false

When activating LA (Link Aggregation) on a backplane port to a service unit
that is managed via the GbE star (inband management), the management
connection to the service unit will be lost.
→ Do not activate LA.
Please note:
Gate R3B”.

If you enable Link Aggregation on a port without having set the port mode,
you get an error message saying “Error - Cause: Port type is neither trunk
nor redun.”.
Please note:
For enabling Link Aggregation on a port you need to set its port mode to
“VLAN Trunk Port” or “Service Port” before activating LA on that port. For
more information on the port mode, please refer to section AP: / unit-x / port-
a, Configuration – Port Mode (on page 136).

If you try to enable Link Aggregation on a port that has an RSTP mode or
port cost or port priority or dynamic path cost enabled parameter that is dif-
ferent from the LAG requirement, you get an error message saying “Error -
Cause: Membership denied, due to RSTP mismatch”.

176
COGE1
Please note:
Make sure that the RSTP mode (“RSTP Enabled” in the GUI, or RstpEna-
bled” in the CLI) and the RSTP port cost, port priority and dynamic path cost
enabled parameters are identical on all ports that shall be member of a spe-
cific LAG instance before activating LA on that port.

If you try to enable Link Aggregation on a port that has VLAN settings that
are different from the LAG requirement, you get an error message saying
“Error - Cause: Membership denied, due to VLAN mismatch”.
Please note:
Make sure that the VLAN settings are identical on all ports that shall be
member of a specific LAG instance. This includes the settings for the List
Type and the VLAN ranges entered into the VLAN List. For more information
on VLAN list settings, please refer to section AP: / unit-x / port-a, Configura-
tion – VLAN list (on page 142).

If you try to enable Link Aggregation on a port that has a different scheduling
profile applied in the tab “QoS” (see section AP: / unit-x / port-a, Configura-
tion – QoS (on page 144)), you get an error message saying “Error - Cause:
Membership denied, due to QoS mismatch”.
Please note:
Make sure that the selected scheduling profile is identical on all ports that
shall be member of a specific LAG instance before activating LA on that port.
For more information on setting a scheduling profile, refer to section AP: /
unit-x / port-a, Configuration – QoS (on page 144).

If you try to enable Link Aggregation on a port with multicast settings applied
in the tab “Multicast” (see section AP: / unit-x / port-a, Configuration – Multi-
cast (on page 146)) that are different from the requirements of the LAG, you
get an error message saying “Error - Cause: Membership denied, due to
MCAST port mode mismatch” or “Error - Cause: Membership denied, due to
MCAST STATIC MODE mismatch” or “Error - Cause: Membership denied,
due to MCAST IGMP MODE mismatch”.
Please note:
Make sure that the multicast settings are identical on all ports that shall be
member of a specific LAG instance. For more information on configuring the
port multicast settings, refer to section AP: / unit-x / port-a, Configuration –
Multicast (on page 146).

176
COGE1
Please note:
When moving a port from one LAG instance to another LAG instance the
port LAG member configuration must first be set to “None” before the port
can become a member of the other LAG instance.
The following figure illustrates an example on how COGE1 ports can be
associated with link aggregation groups (LAGs).
port-5
port-4 lag-1
port-3
lag-2
port-2
port-1 lag-3
slot-13
Figure 22: LAG port association example for unit-11
LAGs represent logical ports that replace the individual ports for the pur-
poses of RSTP, VLAN bridging, etc. Once a port becomes a member of a
LAG it will not participate as an individual port in RSTP or VLAN bridging.
A port that is a member of a LAG can become an:
• active member: if the link is up and all remaining LACP conditions are
met. The port can be used to transfer LAGs traffic.
• inactive member: if the link is down or some LACP conditions are not
met. No traffic will pass this port and L2 protocols (RSTP, etc.) will ignore
it.
All five front ports in COGE1, the backplane ports and the redundant ports
can become members of a LAG.
Every port can be configured to be in one of the following aggregation
modes:
Table 67: LA port aggregation modes

Port LA mode configuration
LAG Member LACP Enabled Port LA Configuration Result (Working
Mode)
none - No Aggregation
lag-z No Static Link Aggregation (no LACP)
Yes Dynamic Link Aggregation (LACP active
mode)
Ports can be associated with a LAG either as a static LAG (LACP disabled)
or a dynamic LAG (LACP enabled).
The LA working mode is configured per port as shown in the screenshot fur-
ther above.

176
COGE1
Please note:
A LAG cannot contain members with a mixture of LACP enabled and disa-
bled. The working mode of the first member will determine the working mode
of the group. If it is required to modify the group working mode the group
must be recreated.
Please note:
All ports in a LAG must be configured with the same attributes (VLAN and
RSTP mode together with IGMP configuration). MileGate (via the MCST GUI
or via the CLI) will not allow LAG members to come together if the previous
conditions are not met.
The following physical link conditions are enforced:
Table 68: LA physical link conditions

Link Parameter Condition
Speed All ports must use the same value (10/100/1000)
Operating mode Must be full duplex (point-to-point link)
8.9.3.9 AP: / unit-x / port-a, Configuration – PHY
This dialogue allows you to select the physical operation mode for the Ether-
net port.
Syntax:set PhyMode <SpeedAndDuplex>
Syntax:get PhyMode
Syntax:set PhyFlowControl <PhyFlowControl>
Syntax:get PhyFlowControl

176
COGE1
Table 69: /unit-x/port-a, Configuration – PHY

Mode Speed And Duplex Unknown Do not select this entry.
PhyMode SpeedAndDuplex Unknown The default value is dependent of the port type.
Autodiscovery Select this for automatic mode setting accord-
Autodiscovery ing to the capability of the connected service
unit (for backplane ports only).
Autonegotiation On Select this for autonegotiation of the mode
AutonegotiationOn
Speed10 Full Duplex Select this for 10 Mbit/s, full duplex
Speed10FullDuplex
Speed10 Half Duplex Select this for 10 Mbit/s, half duplex
Speed10HalfDuplex
Speed100 Full Duplex Select this for 100 Mbit/s, full duplex
Speed100FullDuplex
Speed100 Half Duplex Select this for 100 Mbit/s, half duplex
Speed100HalfDuplex
Speed1000 Full Duplex Select this for 1000 Mbit/s, full duplex (for SFP
Speed1000FullDuplex modules only)
Flow Control Enabled  Port Ethernet flow control according to IEEE
PhyFlowCon- PhyFlowControl true 802.3x.
trol Flow control is a mechanism which allows the

receiving party of a connection to control the
false rate of the sending party.
Please note:
SFP modules only support the “Speed 1000 Full Duplex” mode.
Electrical Ethernet interfaces of the front ports support the whole range of
modes. The 1000 Mbit/s, full duplex mode can be obtained via the speed
and duplex selection “Autonegotiation On” if the remote end also supports
1000 Mbit/s.
Please note:
Electrical Ethernet interfaces of the backplane and redundant ports only sup-
port the 1000 Mbit/s, full duplex mode.
→ This mode can be obtained via the speed and duplex selection “Auto-
discovery”, “Autonegotiation On” or “Speed1000 Full Duplex”.
8.9.3.10 AP: / unit-x / port-a, Configuration – EOAM

176
COGE1
Syntax:set NetworkNetworkInterface <EoamNniModeEnabled>

Syntax:get NetworkNetworkInterface
Table 70: /unit-x/port-a, Configuration – EOAM

Network Network Interface EOAM NNI Mode Ena-  The MileGate is at the network boundary
NetworkNet- bled true between access network and transport net-
workInterface EoamNniModeEna- work, i.e. at the NNI towards the transport net-
bled work.
Enables the filtering of EOAM messages on
this port so that they are not forwarded to the
network.
 The MileGate is inside the access network,
false and hence does not provide an NNI.
Disables the filtering of EOAM messages on
this port. EOAM messages are forwarded on
this port.
Please note:
For more information about Ethernet operation, administration, and mainte-
nance (EOAM), please refer to "[316] User Guide “Ethernet OAM”".
8.9.3.11 AP: / unit-x / port-a, Configuration – Priority Mapping

Syntax:set DSCPTo802Dot1qTxPriorityMapping
<DSCPTo802Dot1qTxPriorityMappingEnabled>
Syntax:get DSCPTo802Dot1qTxPriorityMapping
Table 71: /unit-x/port-a, Configuration – Priority Mapping

DSCP To 802.1q Tx Priority DSCP To 802.1q Tx Pri-  In outgoing direction enable the mapping of
Mapping ority Mapping Enabled true DSCP value to VLAN priority according to the
DSCPTo802Dot1qTxPri DSCPTo802Dot1qTxP  configuration on the unit layer. Refer to section
orityMapping riorityMappingEn- AP: / unit-x, Configuration - Priority Mapping
false (on page 106).
abled
The default value is depending of the port
mode.

176
COGE1
8.9.3.12 AP: / unit-x / port-a, Configuration – Mirroring
Syntax:cd /unit-x/port-a/status
Syntax:set MirrorPortList {<port> <mode>;}
Syntax:get MirrorPortList
Table 72: /unit-x/port-a, Configuration – Mirroring

Name
Port List, Port Table Port Front Port 1 … Front Port 5 The port to be mirrored is the COGE1
MirrorPortList port FroPort1 … FroPort5 front port with the address “/unit-11/
port-a”.
Backplane Port 1 … Backplane Port The port to be mirrored is a COGE1
10 backplane port with the address
BacPort1 … BacPort10 “/unit-11/internalPorts/slot-1” … “slot-
10”.
Backplane Port 12 The port to be mirrored is a COGE1
BacPort12 backplane port with the address
“/unit-11/internalPorts/slot-12”.
Backplane Port 14 … Backplane Port The port to be mirrored is a COGE1
21 backplane port with the address
BacPort14 … BacPort21 “/unit-11/internalPorts/slot-14” … “slot-
21”.
Backplane Redundant Port The port to be mirrored is a COGE1
RedunPort backplane port towards the redundant
core unit.
When you configure unit-11, this is the
port with the address
When you configure unit-13, this is the
port with the address
CPU Port The port to be mirrored is the COGE1
CPUPort internal port towards the unit’s host pro-
cessor.

176
COGE1
Table 72: /unit-x/port-a, Configuration – Mirroring (continued)

Name
Mode Outgoing The egress direction shall be mirrored.
mode Outgoing
Incoming The ingress direction shall be mirrored.
Incoming
InOut Both direction (ingress and egress)
InOut shall be mirrored.
Add… Command that opens a dialogue to add
a port and a mode to the port table (GUI
only).
Modify… Command that opens a dialogue to
modify a selected entry in the port table
(GUI only).
Remove Command that removes a selected
entry from the port table (GUI only).
Please note:
In the CLI, the commands “Add…”, “Modify…”, and “Remove” are not sup-
ported. Instead of using these commands, the port table can be configured
or modified by using the CLI command syntax given above. The whole set of
ports and modes has to be entered every time you want to configure or mod-
ify the port table.
8.9.4 AP: / unit-x / port-a, Fault Management

/unit-x/port-a/fm
/unit-x/internalPorts/slot-b/fm
Table 73: /unit-x/port-a, Fault Management

Affecting Severity
TRF Transmitter Failure Equipment true Major The transmitter part of the SFP module
Alarm reports a failure. This may be due to a
HW failure. You may need to replace the
SFP module.
Only available for the front ports
equipped with SFP.
ENA Equipment Not Availa- Equipment true Major There is no SFP module plugged, or the
ble Alarm SFP module cannot be recognized.
Make sure you are using a compatible
SFP module on this port.
Only available for the front ports
equipped with SFP.

176
COGE1
Table 73: /unit-x/port-a, Fault Management (continued)

Affecting Severity
LOS Loss Of Signal Communica- true Major The signal has been lost on the front
tion Alarm port, backplane port or redundant port.
Make sure the connector is plugged on
the front port and the remote equipment
is transmitting a signal.
On an internal port there is no signal
applied between the switch and the
backplane GbE star. This may be due to
a unit not sending a signal on this inter-
face. If this failure persists, you might
need to reboot the respective unit.
8.9.5 AP: / unit-x / port-a, Performance Management
The PM parameters are presented in different groups. For the general view
on a PM dialogue of the MCST GUI, refer to "[304] User Guide “MileGate &
MCST”". The following three basic PM properties appear in every PM dia-
logue:
• Status
• Timestamp
• Elapsed Time
Also, in each of the PM dialogues, the following counter intervals are availa-
ble:
• User Counter
• History 15min
• History 24h
The following counter groups are available for COGE1 front ports, backplane
ports and redundant ports:
• “MCAST Port Statistics” group, see section PM group: MCAST Port Sta-
tistics (on page 157),
• “RMON Ethernet Statistics” group, see section PM group: RMON Ether-
net Statistic (on page 157),
• “MISC Ethernet Statistics” group, see section PM group: MISC Ethernet
• “Link Agg. LACP Port” group, see section PM group: Link Agg. LACP
Port (on page 158).
• “MIB-2 Interface Table” group, see section PM group: MIB-2 Interface
Table (on page 158),
• “IF-MIB IfXTable” group, see section PM group: IF-MIB IfXTable (on
page 158).
Please note:
Performance alarm thresholds are not implemented in this release.
Please note:
Performance monitoring intervals are marked as “invalid” while the port’s
administrative state is “down”.

176
COGE1
8.9.5.1 PM group: MCAST Port Statistics
Table 74: PM group: MCAST Port Statistics

IGMP RX Total Packets This parameter counts the total number of received IGMP packets.
IGMP RX Version Errors This parameter counts the ingress dropped packets with IGMP version error.
IGMP RX CRC Errors This parameter counts the ingress dropped packets with a CRC error.
IGMP RX Type Errors This parameter counts the ingress dropped packets with IGMP type error.
IGMP RX Discarded Packets This parameter counts the ingress discarded IGMP packets.
IGMP TX Total Packets This parameter counts the total number of egress IGMP packets.
IGMP TX Discarded Packets This parameter counts the egress discarded IGMP packets.
8.9.5.2 PM group: RMON Ethernet Statistic
Table 75: PM group: RMON Ethernet Statistic

In Drop Events This parameter counts the drop events at the ingress
In Packets This parameter counts the ingress packets
In Broadcast Packets This parameter counts the ingress broadcast packets
In Multicast Packets This parameter counts the ingress multicast packets
In CRC Align Errors This parameter counts the ingress CRC alignment errors
In Undersized Packets This parameter counts the ingress undersized packets (< 64 bytes)
In Oversized Packets This parameter counts the ingress oversized packets (> 1518 bytes)
In Fragments This parameter counts the ingress fragments
In Jabbers This parameter counts the ingress jabbers
In Estimated Collisions This parameter counts the ingress estimated collisions
In Packets 64 Octets This parameter counts the ingress octets with a size of 64 octets
In Packets 1519 and more This parameter counts the ingress octets with a size of more than 1518 octets
Octets
8.9.5.3 PM group: MISC Ethernet Statistic
Table 76: PM group: MISC Ethernet Statistic

Out Packets This parameter counts the egress packets
Out Packets 64 Octets This parameter counts the egress octets with a size of 64 octets

176
COGE1
Table 76: PM group: MISC Ethernet Statistic (continued)

Out Packets 1024 to 1518 This parameter counts the egress octets with a size of 1024 to 1518 octets
Octets
Out Packets 1519 and more This parameter counts the egress octets with a size of more than 1518 octets
Octets
8.9.5.4 PM group: Link Agg. LACP Port
Table 77: PM group: Link Agg. LACP Port

LACP PDUs Rx This parameter counts the ingress LACP protocol data units
LACP Marker PDUs Rx This parameter counts the ingress marker protocol data units (specific LACP packets)
LACP Marker Response PDUs This parameter counts the ingress marker response protocol data units (specific LACP
Rx packets)
LACP Unknown Rx This parameter counts the unknown ingress LACP packets
LCAP Illegal Rx This parameter counts the illegal ingress LACP packets
LACP PDUs Tx This parameter counts the egress LACP protocol data units
LACP Marker PDUs Tx This parameter counts the egress marker protocol data units (specific LACP packets)
LACP Marker Response PDUs This parameter counts the egress marker response protocol data units (specific LACP
Tx packets)
8.9.5.5 PM group: MIB-2 Interface Table
Table 78: PM group: MIB-2 Interface Table

In Unicast Packets This parameter counts the ingress unicast packets
In Non-unicast Packets This parameter counts the ingress non-unicast packets
In Discards This parameter counts the ingress discarded packets
In Errors This parameter counts the ingress errors
In Unknown Protocol This parameter counts the ingress packets with an unknown protocol type
Out Unicast Packets This parameter counts the egress unicast packets
Out Non-unicast Packets This parameter counts the egress non-unicast packets
Out Discards This parameter counts the egress discarded packets
Out Errors This parameter counts the egress errors
8.9.5.6 PM group: IF-MIB IfXTable
All HC counters are high capacity counters with a counter width of 64 bit.

176
COGE1
Table 79: PM group: IF-MIB IfXTable

HC In Octets This parameter counts the ingress octets
HC In Unicast Packets This parameter counts the ingress unicast packets
HC In Multicast Packets This parameter counts the ingress multicast packets
HC In Broadcast Packets This parameter counts the ingress broadcast packets
HC Out Octets This parameter counts the egress octets
HC Out Unicast Packets This parameter counts the egress unicast packets
HC Out Broadcast Packets This parameter counts the egress broadcast packets
8.9.6 AP: / unit-x / port-a, Status
8.9.6.1 AP: / unit-x / port-a, Status – Port Mode
Syntax:get DefaultConfigEnabled
Table 80: /unit-x/port-a, Status – Port Mode

Port Mode Default Config Ena-  Shows if the port is configured according to
PortMode bled true the default setting, dependent of the port type
DefaultConfi-  and the port mode.
gEnabled Refer to section Port default configuration
false parameters (on page 131).
8.9.6.2 AP: / unit-x / port-a, Status – MAC
Syntax:get PortMacStatus

176
COGE1
Table 81: /unit-x/port-a, Status – MAC

Port MAC status Max Packet Length 0 … 2’000 … 10’000 octets Shows the maximum length of packets trans-
PortMacSta- MaxPack- 0 … 2000 … 10000 ferred across this port. Default value is 2000
tus etLength octets.
MAC Address 00:e0:df:00:00:00 … Shows the physical (MAC) address of this
MacAddress 00:e0:df:ff:ff:ff port.
00e0df000000 …
00e0dfffffff
8.9.6.3 AP: / unit-x / port-a, Status – PHY
Syntax:get PortLinkStatus

176
COGE1
Table 82: /unit-x/port-a, Status – PHY

Port Link Status Speed 10 Mbit/s Shows that the wire speed is 10 Mbit/s.
PortLinkStatus Speed 10MBitpers
100 Mbit/s Shows that the wire speed is 100 Mbit/s.
100MBitpers
1000 Mbit/s Shows that the wire speed is 1000 Mbit/s.
1000MBitpers
Invalid Shows that the wire speed is invalid.
Invalid
Link Down Shows that the link is down, either by a missing
LinkDown receive signal or by setting the administrative state
to down.
Mode Half Duplex Shows that the transmission mode of this port is
Mode HalfDuplex half duplex.
Full Duplex Shows that the transmission mode of this port is
FullDuplex full duplex.
Duplex Invalid Shows that the duplex mode is invalid.
DuplexInvalid
Link Down Shows that the link is down, either by a missing
LinkDown receive signal or by setting the administrative state
to down.
Flow Control  Shows that flow control is enabled on this port.
FlowControl true
 Shows that flow control is disabled on this port.
false
8.9.6.4 AP: / unit-x / port-a, Status – RSTP
Syntax:get PortRstpStatus

176
COGE1
Table 83: /unit-x/port-a, Status – RSTP

RSTP Status Port State Disabled Shows that the RSTP port is disabled.
PortRstpSta- PortState Disabled
tus
Discarding Shows that the RSTP port is discarding packets.
Discarding
Learning Shows that the RSTP port is in the learning
Learning phase.
Forwarding Shows that the RSTP port is forwarding packets.
Forwarding
Port Role Disabled Shows that the RSTP port is “disabled”.
PortRole Disabled
Alternate Shows that the RSTP port is an alternate port.
Alternate
Backup Shows that the RSTP port is a backup port.
Backup
Root Shows that the RSTP port is a root port.
Root
Designated Shows that the RSTP port is the designated port.
Designated
Port Cost 0 … 200’000’000 Shows the configured RSTP port (path) cost.
PortCost 0 … 200000000 If dynamic path cost has been enabled, the
RSTP port (path) cost is dynamically updated
according to the Ethernet link speed.
If the port is member of a LAG, the port cost is
taken over from the LAG cost.
Port Priority 0 … 240 Shows the configured RSTP port priority.
PortPriority 0 … 240
Port Enabled  Shows that RSTP on the port is enabled.
PortEnabled true
 Shows that RSTP on the port is disabled.
false
Edge  Shows that the port is at the edge of an RSTP
Edge true tree. A port connected to an end station is allow-
ing fast transition in case of a link failure.
 Shows that the port is inside an RSTP tree.
false
Point-To-Point  Shows that the device connected at the other
PointToPoint true end is running RSTP.
 Shows that the device at the other end is not
false running RSTP.
Dynamic Path Cost  Shows the configured “Dynamic Path Cost Ena-
Enabled true bled” parameter.
DynamicPath- 
CostEnabled
false

176
COGE1
8.9.6.5 AP: / unit-x / port-a, Status – Link Aggregation
This dialogue shows the Link Aggregation Operational Status of both the
Actor and the Partner. Due to the large size of the dialogue window, it is split
into three parts.
Part 1 is the “Actor Operational Status”:
Syntax:get Status
Table 84: /unit-x/port-a, Status – Link Aggregation (1)

LA Status / Actor Opera- LACP Activity LACP Active Active mode: port will emit LACP messages on a
tional Status ActorOpera- LacpActive periodic basis regardless of the partner’s mode.
Status tionalSta- This mode is the (invisible) LACP configuration
tus.LacpActiv of the port.
ity Note that LACP messages are only sent when
LACP is enabled in the port configuration.
LACP Passive Passive mode: port will emit LACP messages
LacpPassive only if partner system is doing so.
LACP Timeout Short Timeout Short timeout: 3 second timeout corresponding
ActorOpera- ShortTimeout to a 1 second transmission period.
tionalSta- Long Timeout Long timeout: 90 second timeout corresponding
tus.LacpTimeo to a 30 second transmission period.
ut LongTimeout
Aggregation Aggregatable Link can be aggregated.

ActorOpera- Aggregatable
tionalSta- Individual Link cannot be aggregated with others.
tus.Aggregati
on Individual

176
COGE1
Table 84: /unit-x/port-a, Status – Link Aggregation (1) (continued)

Synchronisation In Sync Port is bound to an appropriate aggregator.
ActorOpera- InSync
tionalSta- Out of Sync Port is not bound to an appropriate aggregator.
tus.Synchroni
OutOfSync
sation
Collecting Yes The collector for this link is enabled and will not
ActorOpera- Yes be disabled unless instructed to do so (by man-
tionalSta- agement or LACP).
tus.Collectin No The collector for this link is either disabled or
g No maybe in the process of being disabled.
Distributing Yes The distributor for this link is enabled or may be
ActorOpera- Yes in the process of being enabled.
tionalSta- No The distributor for this link is disabled and will not
tus.Distribut be enabled unless instructed to do so (by man-
No
ing agement or LACP).
Defaulted Yes The device is using Partner information from
ActorOpera- Yes received LACP messages.
tionalSta- No The device is using administratively-configured
tus.Defaulted default Partner information.
No
Expired Yes The device’s LACP receive state machine is in
ActorOpera- Yes the expired state.
tionalSta- No The device’s LACP receive state machine is not
tus.Expired in the expired state.
No
Part 2 is the “Partner Operational Status”:
Syntax:get Status

176
COGE1

LA Status / Partner Opera- LACP Activity LACP Active Port will emit LACP messages on a periodic
tional Status PartnerOpera- LacpActive basis regardless of the partner’s mode
Status tionalSta- LACP Passive Port will emit LACP messages only if partner
tus.LacpActiv system is doing so
ity LacpPassive
LACP Timeout Short Timeout 3 second timeout corresponding to a 1 second

PartnerOpera- ShortTimeout transmission period.
tionalSta- Long Timeout 90 second timeout corresponding to a 30 second
tus.LacpTimeo transmission period
LongTimeout
ut
Aggregation Aggregatable Link can be aggregated
PartnerOpera- Aggregatable
tionalSta- Individual Link cannot be aggregated with others.
tus.Aggregati
on Individual
Synchronisation In Sync In Sync: port is bound to an appropriate aggre-

PartnerOpera- InSync gator
tionalSta- Out of Sync Port is not bound to an appropriate aggregator
tus.Synchroni
sation OutOfSync
Collecting Yes The collector for this link is enabled and will not
PartnerOpera- Yes be disabled unless instructed to do so (by man-
tionalSta- agement or LACP)
tus.Collectin No The collector for this link is either disabled or
g No maybe in the process of being disabled
Distributing Yes The distributor for this link is enabled or may be
PartnerOpera- Yes in the process of being enabled.
tionalSta- No The distributor for this link is disabled and will not
tus.Distribut be enabled unless instructed to do so (by man-
ing No
agement or LACP)
Defaulted Yes The device is using Partner information from
PartnerOpera- Yes received LACP messages
tionalSta- No The device is using administratively-configured
tus.Defaulted default Partner information
No
Expired Yes The device’s LACP receive state machine is in
PartnerOpera- Yes the expired state
tionalSta- No The device’s LACP receive state machine is not
tus.Expired in the expired state
No
Part 3 are some more “LA Status” properties:

176
COGE1
Syntax:get Status

LA Status Actor Oper Key 0 … 4’294’967’295 Key value associated with the port from which
LaStatus ActorOperKey 0 … 4294967295 the LACP message is being sent,
Key 30 = LAG-1,
Key 31 = LAG-2,
Key 32 = LAG-3.
Partner Oper Key 0 … 4’294’967’295 Key value that the Partner has associated with
PartnerOperKey 0 … 4294967295 this, from the Actor’s perspective,
Key 30 = LAG-1,
Key 31 = LAG-2,
Key 32 = LAG-3.
Actor Port Priority 0 … 4’294’967’295 Actor port priority from which the message is
ActorPortPrior- 0 … 4294967295 being sent.
ity
Partner Port Priority 0 … 4’294’967’295 Partner’s port priority from which the message is
PartnerPortPri- 0 … 4294967295 being sent.
ority
8.9.6.6 AP: / unit-x / port-1 … 2: 1000BASE-X SFP, Status - DDM
The following dialogue is applicable only to the ports that can be equipped
with an SFP, i.e. “port-1” and “port-2”.

176
COGE1
Syntax:get DdmStatus
Table 87: /unit-x/port-1 … 2, Status – DDM

Name
DDM Status DDM Interface Unknown Digital Diagnostic Monitoring interface support.
DdmStatus Support Unknown
DdmInter- Supported
faceSupport
Supported
Not Supported
NotSupported
Module Tempera- -2147483648 … SFP module internal temperature.
ture 2147483647 °C
ModuleTem- -2147483648 …
perature 2147483647
Supply Voltage -Infinity … Infinity V SFP power supply voltage.
SupplyVolt- -Infinity …
age Infinity
TX Bias Current -Infinity … Infinity mA SFP laser bias current
TxBiasCur- -Infinity …
rent Infinity
TX Output Power -2147483648 … SFP transmitted optical power.
TxOutput- 2147483647 dBm
Power -2147483648 …
2147483647
RX Input Power -2147483648 … SFP received optical power.
RxInputPower 2147483647 dBm
-2147483648 …
2147483647

176
COGE1
8.9.6.7 AP: / unit-x / port-a, Status – QoS
Syntax:get QosStatus
Table 88: /unit-x/port-a, Status – QoS, QoS Status

Name
Scheduling Status Queue Number 7…0 Identifies the queue on this port.
table QueueNr 7 … 0
QosStatus Queue Priority Highest … - … Lowest This column indicates that queue 7 has highest
QueuePrio Highest … - … priority while queue 0 has lowest priority.
Lowest
Scheduling strict Note that queue number 7 is fixed to “strict”.
Weighted This queue has weighted round robin queuing.
weighted
Weight 1.6% … 62.5% For the weighted round robin queues, this indi-
Weight 1.6 … 62.5 cates the weight of each of the WRR queues. The
total of all weights is 100%. The maximum possi-
ble weight for one queue is 62.5%, the minimum
1.6%, given by the number of queues and the
weight that can be configured per queue.
Please note:
The scheduling type and weight shown in the table reflects the fact that per
default the queue 7 is reserved for the MileGate internal management traffic.
page 47).
Please note:

176
COGE1
8.9.6.8 AP: / unit-x / port-a, Status – Multicast, Stream, Dynamic
CLI syntax for displaying the list of active streams:

Syntax:get ActiveStreams
CLI syntax for clearing all active streams:
Syntax:ClearActiveStreams
Table 89: /unit-x/port-a, Status – Multicast, Stream, Dynamic

Active Streams Number Of Active 0 … 255 Shows the number of currently active dynamic
ActiveStreams Streams 0 … 255 multicast streams on this port.
numberOfAc-
tiveStreams
List Of Streams, 2 … 4’088 Shows the VLAN ID of the currently active group.
VLAN ID 2 … 4088
VlanId
List Of Streams, <multicast IP address> Shows the multicast IP address of the currently
Group <multicast IP active group.
group address>
List Of Streams, <string of up to 10 Shows the alloted bandwidth in [kbit/s] of the cur-
Alloted Bandwidth characters> rently active group.
allotedBand- <string of up The bandwidth range is 100 kbit/s …
width to 10 charac- 1’000’000 kbit/s.
ters>
Clear Active Streams Command that clears all active multicast streams
ClearActiveS- on this port.
treams

176
COGE1
8.9.6.9 AP: / unit-x / port-a, Status – Multicast, Stream, Static
CLI syntax for displaying the list of active streams:

Syntax:get StaticStreams
Table 90: /unit-x/port-a, Status – Multicast, Stream, Static

Active Streams Number Of Active 0 … 255 Shows the number of static multicast streams on
StaticStreams Streams 0 … 255 this port.
numberOfAc-
tiveStreams
List Of Streams, 2 … 4’088 Shows the VLAN ID of the active group.
VLAN ID 2 … 4088
VlanId
List Of Streams, <multicast IP address> Shows the multicast IP address of the active
Group <multicast IP group.
group address>
List Of Streams, <string of up to 10 Shows the alloted bandwidth in [kbit/s] of the
Alloted Bandwidth characters> active group.
allotedBand- <string of up The bandwidth range is 100 kbit/s …
width to 10 charac- 1’000’000 kbit/s.
ters>

176
COGE1
8.9.6.10 AP: / unit-x / port-a, Status – Multicast, VLAN
Syntax:get AttachedVlans
Table 91: /unit-x/port-a, Status – Multicast, VLAN

Attached VLANs Number Of Attached 0 … 4’086 Shows the number of currently attached multicast
AttachedVlans VLANs 0 … 4086 VLANs on this port.
NumberOfAttachedV-
lans
List Of VLANs, VLAN ID 2 … 4’088 Shows a list of the currently attached multicast
vlanId 2 … 4088 VLANs on this port.

176
COGE1
8.10 AP: / unit-x / protocols
8.10.1 AP: / unit-x / protocols, Main
8.10.1.1 AP: / unit-x / protocols, Main - General
MCST”".

176
COGE1
8.11 AP: / unit-x / protocols / rstp
8.11.1 AP: / unit-x / protocols / rstp, Main
8.11.1.1 AP: / unit-x / protocols / rstp, Main - General
MCST”".
8.11.2 AP: / unit-x / protocols / rstp, Configuration
8.11.2.1 AP: / unit-x / protocols / rstp, Configuration – Local Bridge
CLI syntax for the local bridge configuration:

Syntax:cd /unit-x/protocols/rstp/cfgm
Syntax:set LocalBridge <MacAddress> <Priority>
<HelloInterval> <ForwardingDelay> <MaxAgeTime>
Syntax:get LocalBridge

176
COGE1
Table 92: /unit-x/protocols/rstp, Configuration – Local Bridge

Operation Parameter Range Descriptions / Details
Name Name
Local Bridge MAC Address 00:e0:df:00:00:00 … Shows the MAC address of the local bridge in
LocalBridge MacAddress 00:e0:df:ff:ff:ff hexadecimal format.
00e0df000000 …
00e0dfffffff
Priority 0 … 32’768 … 61’440 Set the priority of the local bridge (lower number
Priority 0 … 32768 … 61440 is higher priority).
The priority is a multiple of 4’096.
Hello Interval 1…2…9s Set the time interval in seconds between two
HelloInter- 1 … 2 … 9 RSTP hello messages.
val
Forwarding Delay 4 … 15 … 30 s Set the time in seconds a message is hold
Forward- 4 … 15 … 30 before forwarded.
ingDelay
Max Age Time 6 … 20 … 40 s Set the maximum time in seconds after which an
MaxAgeTime 6 … 20 … 40 RSTP entry gets outdated.

RSTP bridge priorities may have a big impact on the stability and the perfor-
mance of your network if they are not set correctly.
Please note:
The bridge priorities have to be set with care on all equipment that provide
RSTP. You should plan your RSTP settings for the whole RSTP tree in order
to have a stable network. Remember that a lower priority number means a
higher priority, and that the root bridge should have the highest priority, i.e.
the lowest priority value. This applies to both the MileGate and the remote
equipment.
8.11.3 AP: / unit-x / protocols / rstp, Status
8.11.3.1 AP: / unit-x / protocols / rstp, Status – Local bridge
CLI syntax for the local bridge status:

Syntax:cd /unit-x/protocols/rstp/status
Syntax:get LocalBridge

176
COGE1
Table 93: /unit-x/protocols/rstp, Status – Local Bridge

Name
Local Bridge MAC Address 00:e0:df:00:00:00 … Shows the MAC address of the local bridge.
LocalBridge MacAddress 00:e0:df:ff:ff:ff
00e0df000000 …
00e0dfffffff
Priority 0 … 61’440 Shows the priority of the local bridge (lower num-
Priority 0 … 61440 ber is higher priority) as configured (see section
AP: / unit-x / protocols / rstp, Configuration –
Local Bridge (on page 173)).
8.11.3.2 AP: / unit-x / protocols / rstp, Status – Root bridge
CLI syntax for the root bridge status:

Syntax:cd /unit-x/protocols/rstp/status
Syntax:get RootBridge

176
COGE1
Table 94: /unit-x/protocols/rstp, Status – Root Bridge

Operation Parameter Name Range Descriptions / Details
Name
Root Bridge Root Bridge Local Indicates that the local bridge is the root bridge.
Root- RootBridge Local
Bridge Remote Indicates that the local bridge is not the root
Remote bridge.
MAC Address 00:00:00:00:00:00 … ff:ff:ff:ff:ff:ff Shows the MAC address of the root bridge.
MacAddress 000000000000 …
ffffffffffff
Priority 0 … 61’440 Shows the priority of the root bridge (lowest
Priority 0 … 61440 number is highest priority).
Hello Interval 1…9s Shows the time in seconds between two consec-
HelloInter- 1 … 9 utive HELLO messages.
val
Forwarding Delay 4 … 30 s Shows the time in seconds a message is hold
Forward- 4 … 30 before forwarded.
ingDelay
Max Age Time 6 … 40 s Shows the maximum time in seconds after which
MaxAgeTime 6 … 40 an RSTP entry gets outdated.

176

COGE1 Coge1 - r7b: User Manual

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

COGE1 Coge1 - r7b: User Manual

Încărcat de

Drepturi de autor:

Formate disponibile

User Manual

Control, Gb Ethernet switch, uplinks, sync

Document PEC EN/LZTBU 370 101/7 RC

Document release MileGate R3B | 24. June 2013

2.4 Unit View 27

© KEYMILE June 2013 page 3 of 176 EN/LZTBU 370 101/7 RC

© KEYMILE June 2013 page 4 of 176 EN/LZTBU 370 101/7 RC

5.2.5 Synchronisation interface 60

5.3 Equipment protection EQP (core unit redundancy) 65

6.2 Managed object model (MOM) 74

6.3 Commissioning of COGE1 76

6.4 Core unit redundancy 85

© KEYMILE June 2013 page 5 of 176 EN/LZTBU 370 101/7 RC

6.4.1 Conditions for redundancy 85

7 Operation and maintenance 87

7.3 RSTP status 91

7.4 Link Aggregation (LA) status 93

8 GUI and CLI reference 94

8.3 AP: / unit-x: COGE1 104

8.4 AP: / unit-x / esi-y 113

© KEYMILE June 2013 page 6 of 176 EN/LZTBU 370 101/7 RC

8.4.1 AP: / unit-x / esi-y, Main 113

8.5 AP: / unit-x / internalPorts 114

8.6 AP: / unit-x / internalPorts / cpu 115

8.7 AP: / unit-x / internalPorts / slot-b 120

8.9 AP: / unit-x / port-a 130

© KEYMILE June 2013 page 7 of 176 EN/LZTBU 370 101/7 RC

8.9.3.5 AP: / unit-x / port-a, Configuration – VLAN list, Modify… 144

8.10 AP: / unit-x / protocols 172

8.11 AP: / unit-x / protocols / rstp 173

© KEYMILE June 2013 page 8 of 176 EN/LZTBU 370 101/7 RC

Figure 1: Front panel and top component view of the COGE1 27

© KEYMILE June 2013 page 9 of 176 EN/LZTBU 370 101/7 RC

Table 1: Electrical interfaces and circuit categories 13

© KEYMILE June 2013 page 10 of 176 EN/LZTBU 370 101/7 RC

Table 46: /unit-x/internalPorts/cpu, Status – PHY 119

© KEYMILE June 2013 page 11 of 176 EN/LZTBU 370 101/7 RC

1.1 Precautions and safety

Hazardous voltages. Risk of electric shock!

Hazardous electric currents. Risk of flashover and electric shock!

Electrostatic discharges. Risk of equipment damage!

Attention to temperature range!

© KEYMILE June 2013 page 12 of 176 EN/LZTBU 370 101/7 RC

Attention to proper earthing!

Attention to access control!

Table 1: Electrical interfaces and circuit categories

Table 2: Optical interfaces

a. As the laser protection class 1 is complied, dangerous radiation cannot be emitted.

© KEYMILE June 2013 page 13 of 176 EN/LZTBU 370 101/7 RC

1.2 Associated MileGate documents

[012] Release Note “MileGate R3B”

[201] System Description “MileGate R3B”

[301] User Guide “MileGate 2500/2510 Installation”

[302] User Guide “MileGate 2500/2510”

[310] User Guide “MileGate 2300/2310 Installation”

[317] User Guide “MileGate 2300/2310”

[303] User Guide “Triple Play Applications”

[304] User Guide “MileGate & MCST”

[314] User Guide “TDM Services and Cross Connections”

[316] User Guide “Ethernet OAM”

[401] User Manual “COGE1 coge1_r7b”

[506] User Manual “MileGate cables”

[915] Technical Bulletin “Feature Licences for MileGate”