FCM9003 User Manual Version 9 · 2016. 7. 12. · FCM9003 USER MANUAL 76-02-100 Rev.A Page 1 of 216...

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

FCM9003 User Manual Version 9.2

DATE: 10th November 2015

DOCUMENT NO: 76-02-100

REVISION: A

PREPARED BY: Ian Banbrook

Metrodata Ltd

Laxton House, Crabtree Office Village Eversley Way, Egham Surrey, TW20 8RY, UK

Tel +44 1 784 744700

Fax: +44 1 784 744730 E-Mail: [email protected]

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

METRODATA LTD

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of

Metrodata Ltd, Laxton House,

Crabtree Office Village, Eversley Way,

Egham, Surrey, TW20 8RY, United Kingdom.

DISCLAIMER

Metrodata Ltd makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties or merchantability or fitness for any particular purpose. Further, Metrodata Ltd reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Metrodata Ltd to notify any person of such revision or changes.

Copyright © 2015 by Metrodata Ltd,

All Rights Reserved

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

Document History

25/8/2015 XA Document Created

10/11/2015 A Document updated for 9.2 software

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

1 INTRODUCTION ............................................................................................... 21

1.1 FCM9003 EDD ........................................................................................... 22

1.2 Safety ......................................................................................................... 22

1.3 Electro Magnetic Compatibility ................................................................... 22

1.3.1 EN55022 Statement ........................................................................... 23

1.3.2 FCC Declaration ................................................................................. 23

1.4 WEEE Directive ......................................................................................... 23

1.5 RoHS Compliance ..................................................................................... 23

2 INSTALLATION ................................................................................................. 24

2.1 FCM9003 Rear Panel ................................................................................ 24

2.1.1 Mains Power ....................................................................................... 24

2.1.2 DC Power ........................................................................................... 24

2.2 Base Label and Bit Switches ...................................................................... 25

2.2.1 WAN Port Configuration...................................................................... 25

2.2.1.1 Switch 1, WAN Mode ..................................................................... 26

2.2.1.2 Switch 2, Auto Negotiation ............................................................. 26

2.2.1.3 Switch 3/4, Speed .......................................................................... 26

2.2.2 Switch 5, Duplex ................................................................................. 27

2.2.3 Zero Touch Configuration Control ....................................................... 27

2.2.3.1 Switch 6, TAG Mode / Proxy Mode ...Error! Bookmark not defined.

2.2.3.1.1 ZTC TAG Mode Selection ............Error! Bookmark not defined.

2.2.3.1.2 Normal Boot, Proxy Mode ............Error! Bookmark not defined.

2.2.3.2 Switch 7, Boot Location / (Autoboot) .............................................. 27

2.2.4 Switch 8, Master Boot Control / (Factory Default) ............................... 28

2.3 Rackmounting ............................................................................................ 32

3 OPERATING MODES ....................................................................................... 33

3.1 C-Tag Mode ............................................................................................... 33

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

3.2 S-Tag Mode ............................................................................................... 35

3.2.1 Pushing S-Tag onto Untagged Frame ................................................ 36

3.2.2 Pushing S-Tag onto Tagged Frame .................................................... 37

3.3 Double Tag Mode ...................................................................................... 38

3.3.1 Untagged Frame Ingress .................................................................... 39

3.3.2 Tagged Frame Ingress........................................................................ 40

4 CONFIGURATION ............................................................................................ 41

4.1 System Configuration ................................................................................. 42

4.1.1 Setting the Time and Date .................................................................. 43

4.1.1.1 Time Zone ...................................................................................... 43

4.1.1.2 NTP Server .................................................................................... 43

4.1.1.3 Sync Now ....................................................................................... 44

4.1.2 Setting the Node Name....................................................................... 44

4.1.3 Access Control .................................................................................... 44

4.1.3.1 Setting the Local Password ............................................................ 45

4.1.3.1.1 Default Unit Password .............................................................. 45

4.1.3.1.2 Password Recovery .................................................................. 45

4.1.3.2 View User ....................................................................................... 46

4.1.3.3 Super Me ....................................................................................... 46

4.1.3.4 TACACS+ ...................................................................................... 46

4.1.3.4.1 Authentication ........................................................................... 47

4.1.3.4.2 Timeout ..................................................................................... 47

4.1.3.4.3 Retries ...................................................................................... 47

4.1.3.4.4 Server ....................................................................................... 47

4.1.3.4.5 Backup Server .......................................................................... 48

4.1.3.4.6 Encryption Key .......................................................................... 48

4.1.3.5 Welcome Screen ............................................................................ 49

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.3.6 Display Screen ............................................................................... 50

4.1.4 Software Version ................................................................................ 50

4.1.5 Serial Number ..................................................................................... 50

4.1.6 Warm Start .......................................................................................... 51

4.1.7 Auto Warm Start ................................................................................. 51

4.1.8 Cold Start ............................................................................................ 51

4.1.9 Maintenance ....................................................................................... 52

4.1.9.1 System Event Log .......................................................................... 52

4.1.9.2 Alarm Event Log............................................................................. 53

4.1.9.3 Config Event Log............................................................................ 53

4.1.9.4 Full Event Log ................................................................................ 54

4.1.9.5 Output Config ................................................................................. 55

4.1.9.6 Input Config .................................................................................... 56

4.1.10 Zero Touch Configuration ................................................................... 56

4.1.10.1 Provider ID .................................................................................... 57

4.1.10.2 Zero Touch State ........................................................................... 57

4.1.10.3 Software Upgrade Time ................................................................ 58

4.2 Management Entity .................................................................................... 59

4.2.1 Interface .............................................................................................. 59

4.2.1.1 Mode .............................................................................................. 61

4.2.1.1.1 Mode: Normal IP ....................................................................... 61

4.2.1.1.1.1 Physical Address ................................................................ 61

4.2.1.1.1.2 DHCP ................................................................................. 61

4.2.1.1.1.3 IP Address .......................................................................... 62

4.2.1.1.1.4 Net Mask ............................................................................ 62

4.2.1.1.1.5 AT Table ............................................................................. 62

4.2.1.1.1.6 Default Gateway ................................................................. 63

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.1.1.1.7 C-VLAN .............................................................................. 63

4.2.1.1.1.8 S-VLAN .............................................................................. 63

4.2.1.1.1.9 Tag Priority ......................................................................... 64

4.2.1.1.2 Mode : Proxy Client .................................................................. 64

4.2.1.1.2.1 Learn Servers ..................................................................... 64

4.2.1.1.2.2 IP Address / NET Mask ...................................................... 64

4.2.1.1.3 Mode : Proxy Server ................................................................. 65

4.2.1.1.3.1 DHCP ................................................................................. 65

4.2.1.1.3.2 IP Address .......................................................................... 65

4.2.1.1.3.3 Net Mask ............................................................................ 65

4.2.1.1.4 Mode : Disabled ........................................................................ 65

4.2.2 IP Configuration .................................................................................. 66

4.2.2.1 Default TTL .................................................................................... 66

4.2.2.2 DSCP Priority ................................................................................. 66

4.2.2.4 Routing Table ................................................................................. 67

4.2.2.4.1 Display Table ............................................................................ 67

4.2.2.4.2 Editing Routes .......................................................................... 68

4.2.2.4.3 Adding Routes .......................................................................... 68

4.2.2.5 Forwarding ..................................................................................... 68

4.2.2.6 IP Statistics .................................................................................... 69

4.2.3 UDP .................................................................................................... 70

4.2.3.1 SNMP Ports ................................................................................... 70

4.2.3.2 Statistics ......................................................................................... 71

4.2.4 TCP..................................................................................................... 71

4.2.4.1 Statistics ......................................................................................... 72

4.2.4.2 Connection Table ........................................................................... 72

4.2.5 SNMP ................................................................................................. 73

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.5.1 Communities .................................................................................. 73

4.2.5.2 Managers ....................................................................................... 74

4.2.5.2.1 Dying Gasp Trap ....................................................................... 75

4.2.5.3 Contact Person .............................................................................. 75

4.2.5.4 Node Name .................................................................................... 75

4.2.5.5 Location ......................................................................................... 75

4.2.5.6 SNMP Statistics ............................................................................. 76

4.2.5.7 Trap Alarms ................................................................................... 77

4.2.6 Telnet/SSH/HTTP ............................................................................... 78

4.2.6.1 TELNET ......................................................................................... 78

4.2.6.2 SSH ................................................................................................ 78

4.2.6.3 HTTP .............................................................................................. 79

4.2.6.4 Timeout .......................................................................................... 79

4.2.7 TFTP ................................................................................................... 80

4.2.7.1 Client Mode .................................................................................... 80

4.2.7.1.1 Remote IP ................................................................................. 80

4.2.7.1.2 Get New Software ..................................................................... 81

4.2.7.1.2.1 Failsafe Upgrade ................................................................ 82

4.2.7.1.3 Boot Software Upgrade ............................................................ 82

4.2.7.1.4 Get Config ................................................................................. 83

4.2.7.1.5 Put Config ................................................................................. 83

4.2.7.1.6 Put Report ................................................................................. 83

4.2.7.2 Server Mode .................................................................................. 84

4.2.7.2.1 Remote IP ................................................................................. 84

4.2.7.2.2 Software File Name .................................................................. 84

4.2.7.2.3 Config File Name ...................................................................... 84

4.2.8 TWAMP .............................................................................................. 85

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.9 Ping..................................................................................................... 85

4.3 V.24 Set-up ................................................................................................ 86

4.3.1 Usage ................................................................................................. 86

4.3.2 Console set-up .................................................................................... 86

4.3.2.1 Terminal Type ................................................................................ 87

4.3.2.2 Via Modem ..................................................................................... 87

4.3.2.3 Baud Rate ...................................................................................... 87

4.3.2.4 Parity .............................................................................................. 88

4.3.2.5 Data Bits ........................................................................................ 88

4.3.2.6 Stop Bits ......................................................................................... 88

4.3.2.7 Load New Config............................................................................ 88

4.4 Port Set Up Menu ...................................................................................... 89

4.4.1 User LAN Port Configuration ............................................................. 90

4.4.1.1 Interface Name .............................................................................. 90

4.4.1.2 State ............................................................................................... 90

4.4.1.3 Link Status ..................................................................................... 91

4.4.1.4 Port Management........................................................................... 91

4.4.1.4.1 Cable Tester ............................................................................. 91

4.4.1.4.2 (max) Speed ............................................................................. 92

4.4.1.4.3 Duplex....................................................................................... 92

4.4.1.4.4 Auto Negotiation ....................................................................... 93

4.4.1.4.5 Negotiated ................................................................................ 93

4.4.1.5 MDI / MDIX .................................................................................... 94

4.4.1.6 Negotiated ...................................................................................... 94

4.4.1.7 Layer 2 Management ..................................................................... 95

4.4.1.7.1 Tagging and Priority .................................................................. 95

4.4.1.7.1.1 Add C-Tag to ...................................................................... 96

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.1.2 C-Tag VID .......................................................................... 96

4.4.1.7.1.3 Priority Source .................................................................... 97

4.4.1.7.1.4 Default Priority .................................................................... 97

4.4.1.7.2 L2CP Management ................................................................... 98

4.4.1.7.2.1 Bridge Group ...................................................................... 99

4.4.1.7.2.1.1 OAM ............................................................................ 99

4.4.1.7.2.1.2 STP/RSTP/MSTP ........................................................ 99

4.4.1.7.2.1.3 LACP / LACP Marker ................................................. 100

4.4.1.7.2.1.4 MD Proxy ................................................................... 100

4.4.1.7.2.1.5 LLDP .......................................................................... 100

4.4.1.7.2.1.6 Other Bridge .............................................................. 101

4.4.1.7.2.2 GARP Group .................................................................... 101

4.4.1.7.2.2.1 GMRP ........................................................................ 101

4.4.1.7.2.2.2 GVRP ........................................................................ 101

4.4.1.7.2.2.3 Other GARP............................................................... 102

4.4.1.7.2.3 Cisco Group ..................................................................... 102

4.4.1.7.2.4 Metrodata Group .............................................................. 103

4.4.1.7.2.4.1 Beacon ...................................................................... 103

4.4.1.7.2.4.2 L2CP Tunnel .............................................................. 103

4.4.1.7.2.4.3 Other Metrodata ......................................................... 103

4.4.1.7.2.5 Other Group ..................................................................... 104

4.4.1.7.2.6 L2CP Flow ........................................................................ 104

4.4.1.7.3 OAM ....................................................................................... 105

4.4.1.7.3.1 OAM Mode ....................................................................... 105

4.4.1.7.3.2 OAM Status ...................................................................... 106

4.4.1.7.3.3 OAM Statistics .................................................................. 106

4.4.1.7.3.4 OAM Events ..................................................................... 107

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.8 Link Loss Forwarding ................................................................... 107

4.4.1.9 Suppress All Alarms ..................................................................... 107

4.4.1.10 Rate Limiting ............................................................................... 108

4.4.1.10.1 Mode ..................................................................................... 108

4.4.1.10.2 Broadcast .............................................................................. 108

4.4.1.10.2.1 Limiting ........................................................................... 109

4.4.1.10.2.2 CIR ................................................................................. 109

4.4.1.10.2.3 CBS ................................................................................ 109

4.4.1.10.3 Priority Queue Settings ......................................................... 109

4.4.1.11 Counters ...................................................................................... 110

4.4.2 User SFP Port Configuration ........................................................... 111

4.4.2.1 Interface Name ............................................................................ 111

4.4.2.2 State ............................................................................................. 111

4.4.2.3 Link Status ................................................................................... 112

4.4.2.4 SFP Type ..................................................................................... 112

4.4.2.5 Speed ........................................................................................... 112

4.4.2.6 Duplex .......................................................................................... 112

4.4.2.7 Auto Negotiation........................................................................... 113

4.4.2.8 Negotiated .................................................................................... 113

4.4.2.9 SFP Management ........................................................................ 113

4.4.2.9.1 Device Details ......................................................................... 114

4.4.2.9.2 Notifications ............................................................................ 115

4.4.2.10 Layer 2 Management .................................................................. 116

4.4.2.10.1 Tagging and Priority .............................................................. 116

4.4.2.11 L2CP Management ..................................................................... 116

4.4.2.12 OAM ............................................................................................ 117

4.4.2.13 Link Loss Forwarding .................................................................. 117

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.2.14 Counters ...................................................................................... 118

4.4.3 WAN Port .......................................................................................... 119

4.4.3.1 Interface Name ............................................................................ 120

4.4.3.2 State ............................................................................................. 120

4.4.3.3 Link Status ................................................................................... 120

4.4.3.4 Interface ....................................................................................... 120

4.4.3.5 Port Management ( Copper Only ) ............................................... 121

4.4.3.5.1 Cable Tester ........................................................................... 121

4.4.3.5.3 (max) Speed ........................................................................... 122

4.4.3.5.4 Duplex..................................................................................... 122

4.4.3.5.5 Auto Negotiation ..................................................................... 123

4.4.3.6 Negotiated .................................................................................... 123

4.4.3.7 MDI / MDIX .................................................................................. 124

4.4.3.8 SFP Type ..................................................................................... 124

4.4.3.9 Max Speed ( SFP Mode ) ............................................................. 124

4.4.3.10 Max Duplex (SFP Mode ) ............................................................ 125

4.4.3.11 Auto Negotiation (SFP Mode ) ..................................................... 125

4.4.3.12 Negotiated ................................................................................... 125

4.4.3.13 SFP Management ....................................................................... 126

4.4.3.13.1 Device Details ....................................................................... 127

4.4.3.13.2 Notifications .......................................................................... 128

4.4.3.13.3 OTDR SFP module Support ................................................. 129

4.4.3.13.3.1 OTDR Log ...................................................................... 130

4.4.3.13.3.2 OTDR SFP Trap Support ............................................... 130

4.4.3.14 Layer 2 Management .................................................................. 131

4.4.3.14.1 Tagging and Priority .............................................................. 131

4.4.3.14.2 OAM ..................................................................................... 131

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.14.3 OAM Mode ............................................................................ 132

4.4.3.14.4 OAM Status .......................................................................... 132

4.4.3.14.5 OAM Statistics ...................................................................... 133

4.4.3.14.6 OAM Events .......................................................................... 133

4.4.3.15 Suppress All Alarms .................................................................... 133

4.4.3.16 Rate Shaping ............................................................................... 134

4.4.3.17 Counters ...................................................................................... 134

4.5 Operational Modes ................................................................................... 135

4.5.1 VLAN Mode ...................................................................................... 135

4.5.1.1 VLAN Mode – STag ..................................................................... 136

4.5.1.2 VLAN Mode – CTag ..................................................................... 137

4.5.1.3 VLAN Mode – Double Tag ........................................................... 137

4.5.2 L2CP Tunnel Mode ........................................................................... 138

4.5.3 Max Frame Size ................................................................................ 138

4.5.4 SLA/POLICING ................................................................................. 139

4.5.4.1 Count CFM ................................................................................... 139

4.5.5 Count L2CP ...................................................................................... 139

4.5.5.1 Bandwidth .................................................................................... 140

4.5.5.2 Include S-Tag ............................................................................... 140

4.5.5.3 Include C-Tag .............................................................................. 141

4.5.5.4 Coupling ....................................................................................... 141

4.5.5.5 Colour Mode ................................................................................ 141

4.5.5.6 Colour Marking ............................................................................. 142

4.5.5.6.1 Mode ....................................................................................... 142

4.5.5.6.2 PCP->Green ........................................................................... 143

4.5.5.6.3 Yellow->PCP .......................................................................... 143

4.5.5.6.4 Green->PCP ........................................................................... 143

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.5.7 Delay Percentile ........................................................................... 143

4.5.5.8 External Tags ............................................................................... 144

4.5.5.9 MTU ............................................................................................. 144

4.5.6 Priority Management ......................................................................... 145

4.5.6.1 DSCP->C-Tag Mapping ............................................................... 145

4.5.6.2 Queue Priorities ........................................................................... 146

4.5.6.3 VLAN Override ............................................................................. 146

4.5.6.4 Scheduling Mode ......................................................................... 147

4.5.7 CFM Domains ................................................................................... 148

4.5.7.1 Multicast Address ......................................................................... 149

4.5.7.2 Add Maintenance Domain ............................................................ 149

4.5.7.2.1 Domain Name ......................................................................... 149

4.5.7.2.2 Domain Name Format ............................................................ 150

4.5.7.2.3 Domain Level .......................................................................... 150

4.5.7.2.4 Domain Status Summary ........................................................ 151

4.5.7.2.5 Remove Domain ..................................................................... 151

4.5.7.3 Edit a Domain .............................................................................. 152

4.6 Flow ( Services ) ...................................................................................... 153

4.6.1 Add New Flow or View / Edit / Remove Flow ................................... 153

4.6.1.1 Flow Number ................................................................................ 154

4.6.1.2 Flow Name ................................................................................... 154

4.6.1.3 Flow State .................................................................................... 154

4.6.1.4 S-VLAN ID ................................................................................... 155

4.6.1.5 User Port ...................................................................................... 156

4.6.1.6 C-VLAN Allocation ....................................................................... 156

4.6.1.7 Control C-Vlan ............................................................................. 157

4.6.1.8 SLA/Policing Definition ................................................................. 157

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.8.1 CIR ......................................................................................... 158

4.6.1.8.2 CBS ........................................................................................ 158

4.6.1.8.3 EIR .......................................................................................... 158

4.6.1.8.4 EBS ........................................................................................ 159

4.6.1.8.5 Maximum Frame Loss ............................................................ 159

4.6.1.8.6 Max Delay ............................................................................... 159

4.6.1.8.7 Max Delay Variation ................................................................ 160

4.6.1.8.8 Availability ............................................................................... 160

4.6.1.8.9 Policing ................................................................................... 160

4.6.1.9 Flow CFM Configuration .............................................................. 161

4.6.1.9.1 MA, Maintenance Association Configuration .......................... 162

4.6.1.9.1.1 MA Name ......................................................................... 162

4.6.1.9.1.2 MA Name Format ............................................................. 163

4.6.1.9.1.3 MA Domain ...................................................................... 163

4.6.1.9.2 MEP, Maintenance End Point Configuration ........................... 164

4.6.1.9.2.1 MEP ID ............................................................................. 164

4.6.1.9.2.2 MEP State ........................................................................ 164

4.6.1.9.2.3 MEP CCM ........................................................................ 165

4.6.1.9.2.4 MEP LMM ........................................................................ 165

4.6.1.9.2.5 MEP SLM ......................................................................... 166

4.6.1.9.2.6 MEP DMM ........................................................................ 166

4.6.1.9.3 Counters ................................................................................. 167

4.6.1.9.4 Remove Flow .......................................................................... 168

4.7 Performance Monitoring ........................................................................... 169

4.7.1 Adding a New, or Editing a Current PM Session .............................. 170

4.7.1.1 Adding/Editing a Layer 2 PM Session .......................................... 170

4.7.1.1.1 Name ...................................................................................... 170

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.1.2 State ....................................................................................... 171

4.7.1.1.3 Type ........................................................................................ 171

4.7.1.1.4 Flow ........................................................................................ 171

4.7.1.1.5 Y.1731 Performance Display .................................................. 172

4.7.1.2 Adding/Editing a Layer 3 PM Session .......................................... 173

4.7.1.2.1 Name ...................................................................................... 173

4.7.1.2.2 State ....................................................................................... 173

4.7.1.2.3 Type ........................................................................................ 173

4.7.1.2.4 Peer IP .................................................................................... 174

4.7.1.2.5 TWAMP Setup ........................................................................ 174

4.7.1.2.5.1 DSCP ............................................................................... 174

4.7.1.2.5.2 Message Length ............................................................... 175

4.7.1.2.5.3 Padding ............................................................................ 175

4.7.1.2.5.4 Transmit Rate ................................................................... 175

4.7.1.2.5.5 Receive Timeout .............................................................. 176

4.7.1.2.6 SLA ......................................................................................... 176

4.7.1.2.6.1 Availability ........................................................................ 177

4.7.1.2.6.1.1 Threshold ................................................................... 177

4.7.1.2.6.1.2 SLA Alarm ................................................................. 177

4.7.1.2.6.1.3 Integration Period ...................................................... 177

4.7.1.2.6.1.4 Minimum Data............................................................ 178

4.7.1.2.6.2 Frame Loss Ratio, FLR .................................................... 178

4.7.1.2.6.2.1 Threshold ................................................................... 178

4.7.1.2.6.2.2 SLA Alarm ................................................................. 178


4.7.1.2.6.2.4 Minimum Data............................................................ 179

4.7.1.2.6.3 Frame Transfer Delay, FTD ............................................. 179

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2.6.3.1 Maximum Value ......................................................... 179

4.7.1.2.6.3.2 Threshold ................................................................... 180

4.7.1.2.6.3.3 SLA Alarm ................................................................. 180


4.7.1.2.6.3.5 Minimum Data............................................................ 180

4.7.1.2.6.4 Inter Frame Delay Variation, IFDV ................................... 181

4.7.1.2.6.4.1 Maximum Value ......................................................... 181

4.7.1.2.6.4.2 Threshold ................................................................... 181

4.7.1.2.6.4.3 SLA Alarm ................................................................. 181


4.7.1.2.6.4.5 Minimum Data............................................................ 182

4.7.1.2.7 Reports ................................................................................... 182

4.7.1.2.8 Remove .................................................................................. 182

4.8 Circuit / Flow Tests .................................................................................. 183

4.8.1 Port Loops ........................................................................................ 183

4.8.2 SAM Flow Testing, Service Assurance Module ................................ 184

4.8.2.1 SAM Mode ................................................................................... 184

4.8.2.2 Loopback Operation ..................................................................... 185

4.8.2.2.1 Layer 2 Loopback ................................................................... 185

4.8.2.2.2 Layer 3 Loopback ................................................................... 185

4.8.2.3 Flow Testing ................................................................................. 186

4.8.2.4 SAM Test Regime ........................................................................ 186

4.8.2.5 Y.1564 Testing ............................................................................. 187

4.8.2.5.1 Test Parameters ..................................................................... 187

4.8.2.5.1.1 Layer ................................................................................ 188

4.8.2.5.1.2 Flows/Peers ..................................................................... 188

4.8.2.5.1.3 UDP Port .......................................................................... 188

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.1.4 Background Rate ............................................................. 188

4.8.2.5.1.5 Colour Aware ................................................................... 189

4.8.2.5.1.6 Stop on Fail ...................................................................... 189

4.8.2.5.1.7 Frame Size / Mix .............................................................. 189

4.8.2.5.1.8 User Defined Size ............................................................ 190

4.8.2.5.1.9 Remote MAC .................................................................... 190

4.8.2.5.1.10 Configuration Test .......................................................... 191

4.8.2.5.1.10.1 Test Time ................................................................. 191

4.8.2.5.1.10.2 CIR Test .................................................................. 192

4.8.2.5.1.10.3 EIR Test ................................................................... 192

4.8.2.5.1.10.4 Policing Test ............................................................ 192

4.8.2.5.1.10.5 CBS Test ................................................................. 193

4.8.2.5.1.10.6 EBS Test ................................................................. 193

4.8.2.5.1.11 Performance Test ........................................................... 193

4.8.2.5.1.11.1 Performance Test .................................................... 194

4.8.2.5.1.11.2 Test Time ................................................................. 194

4.8.2.5.1.11.3 Green Rate .............................................................. 194

4.8.2.5.1.11.4 Green Burst ............................................................. 194

4.8.2.5.1.11.5 Yellow Rate ............................................................. 194

4.8.2.5.1.11.6 Yellow Burst ............................................................. 195

4.8.2.5.2 Report Header ........................................................................ 195

4.8.2.5.2.1 Display Screen ................................................................. 196

4.8.2.5.3 State ....................................................................................... 196

4.8.2.5.4 View Results ........................................................................... 197

4.8.2.5.5 Report File Name .................................................................... 199

4.8.2.5.6 Send Report ............................................................................ 199

4.8.2.6 Manual Mode Testing ................................................................... 200

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.6.1 Test Duration .......................................................................... 200

4.8.2.6.2 State ....................................................................................... 201

4.8.2.6.3 Manual Setup .......................................................................... 201

4.8.2.6.3.1 Frame Content ................................................................. 202

4.8.2.6.3.1.1 Remote MAC ............................................................. 202

4.8.2.6.3.1.2 Local MAC ................................................................. 202

4.8.2.6.3.1.3 Flow ........................................................................... 203

4.8.2.6.3.1.4 S-VLAN / C-VLAN ...................................................... 203

4.8.2.6.3.1.5 PCP ........................................................................... 203

4.8.2.6.3.1.6 DEI ............................................................................. 203

4.8.2.6.3.1.7 Frame Size(s) ............................................................ 203

4.8.2.6.3.1.8 Payload ...................................................................... 204

4.8.2.6.3.1.9 DSCP ......................................................................... 204

4.8.2.6.3.2 Frame Rates .................................................................... 205

4.8.2.6.3.2.1 Frame Rate ................................................................ 205

4.8.2.6.3.2.2 Information Rate (IR) ................................................. 205

4.8.2.6.3.2.3 Frames/Burst ............................................................. 205

4.8.2.6.3.3 Burst Size (BS) ................................................................. 206

4.8.2.6.3.4 Monitor ............................................................................. 206

4.8.2.6.4 Test Summary ........................................................................ 207

4.8.2.6.5 Clear Results .......................................................................... 207

4.8.2.7 RFC2544 Testing ......................................................................... 208

4.8.2.7.1 Test Parameters ..................................................................... 208

4.8.2.7.1.1 Layer ................................................................................ 209

4.8.2.7.1.2 Flows ................................................................................ 209

4.8.2.7.1.3 Remote MAC .................................................................... 209

4.8.2.7.1.4 Remote IP ........................................................................ 209

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.7.1.5 UDP Port .......................................................................... 209

4.8.2.7.1.6 Throughput Test Time ...................................................... 210

4.8.2.7.1.7 Throughput Test Retries ................................................... 210

4.8.2.7.1.8 Latency Test Rate ............................................................ 210

4.8.2.7.1.9 Latency Test Time ............................................................ 210

4.8.2.7.2 Report Header ........................................................................ 211

4.8.2.7.2.1 Display Screen ................................................................. 211

4.8.2.7.3 Flows ...................................................................................... 212

4.8.2.7.4 State ....................................................................................... 212

4.8.2.7.5 View Results ........................................................................... 212

4.8.2.7.6 Report File Name .................................................................... 213

4.8.2.7.7 Send Report ............................................................................ 213

APPENDIX 1 Initial Serial Connection to the FCM9003 ..................................... 214

APPENDIX 2 Initial LAN connection to FCM9003 .............................................. 215

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

1 INTRODUCTION

The Metrodata MetroConnect FCM9003 is a highly featured, cost effective Ethernet Service Demarcation Device (EDD) which allows carriers, or aggregate service providers to manage the service effectively.

The FCM9003 presents three physical ports, two copper ports on RJ45 connectors and a fibre port supporting an SFP module. All copper ports support 10/100/1000BaseT with auto negotiation and auto switching, whilst the Fibre port supports both 1000BaseX and 100BaseFX SFP modules. Allocation of User and Network ports is configurable, leading to the FCM9002 supporting the following modes of operation:

Copper to Copper

Copper to Fibre ( + Copper )

Fibre to Copper ( + Copper )

The FCM9003 uses a flow based architecture with flows being supported with either single tag push/pop operation for either tagged (QinQ) or untagged user traffic streams. Both IEEE 802.1q VLAN C-Tags and IEEE 802.1ad Service Tags are supported with a fully programmable S-Tag for maximum compatibility.

The TAG push pop functionality enables the FCM9003 to support E-LINE, E-LAN and E-TREE services at both port and virtual level.

Extensive operational diagnostic information is available through the use of OAM, both IEEE802.3 clause 57 Link OAM, and IEEE 802.1ag / Y.1731 Connectivity and Fault Management OAM (CFM). Y.1731 also offers in service verification of Service Level Agreements through the measurement of packet delays with sub microsecond accuracy and Frame loss / Frame Loss Ratios. For Layer 3 networks TWAMP Light is offered as both controller or reflector for latency and jitter monitoring.

To assist Service Providers in provisioning customer circuits the FCM9003 includes a highly featured packet generator and packet monitor allowing for RFC2544 and Y.1564 testing at both layer 2 and 3(IP). The FCM9003 also includes a loopback facility with MAC and IP DA/SA swapping as well as UDP port swapping capability.

The FCM9003 offers a “Zero Touch Configuration” facility whereby a unit will listen for a beacon and then automatically determine the management connection and load a configuration file from a central server.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

1.1 FCM9003 EDD

The FCM9003 is a compact unit as shown occupying half a shelf in a traditional 19inch rack. All connectors and LED status indicators are accessible from the rear of the unit.

1.2 Safety

The FCM9003 must not be connected to cabling which would be required by BS6701 to equipped with over voltage protection. The following ports on the FCM9003 are designated SELV ( Safety Extra Low Voltage ) within the scope of EN41003

Terminal Port 9 Way D-Type

LAN Port(s) RJ45 10/100/1000BaseT

SFP

These ports must only be connected to SELV ports on other equipment in accordance with EN60950 clause 2.3

1.3 Electro Magnetic Compatibility

In order to ensure EMC compliance, all signal and data cables must be shielded and use screened connector shells. The cable screens must be terminated to the screened connector shell and not connected to any pins of the connector. Failure to use the correct connectors may compromise EMC compliance.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

1.3.1 EN55022 Statement

The FCM9003 is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user will be required to take adequate measures.

1.3.2 FCC Declaration

This equipment has been tested and found to comply with the limits of the Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the Installation and Operation manual, may cause harmful interference to the radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

1.4 WEEE Directive

The FCM9003 is covered by Directive 2002/96/EC ( OJ:L37/24/2003 ) on Waste Electrical and Electronic Equipment ( WEEE ) Units must therefore not be disposed of in standard landfill.

1.5 RoHS Compliance

The FCM9003 is compliant with the EU RoHS Directive 2002/95/EC. The RoHS directive bans the use of six hazardous materials in products placed on the market after July 1st 2006. The six banned materials are Lead, Mercury, Hexavalent Chromium, Polybrominated Biphenys, Polybrominated Diphenyl Ethers and Cadmium.

The FCM9003 is manufactured using a lead free soldering process and as such is fully RoHS 6/6 compliant.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2 INSTALLATION

2.1 FCM9003 Rear Panel

The FCM9003 is available with either Single or Dual AC Mains or DC power options.

2.1.1 Mains Power

The FCM9003 has an internal power supply and is supplied via an IEC mains power socket. The FCM9003 operates over the wide range 100 to 250V AC and draws less than 6 watts.

The dual AC supply version provides resiliance agains power supply failure to increase service availability through the use of dual internal load sharing supply modules with separate external power feeds. The dual supplies operate over the wide range 100 to 250V AC, and drwa less than 8 watts. Power status is displayed on rear panel LEDS, and in addition, SNMP traps may be issued to warn of failures.

2.1.2 DC Power

The FCM9003 is available with an internal DC power supply with two variants available,

DC -48V ( 36 to 72V DC )

DC 24V ( 7 to 36V DC )

DC powered units have an external earth stud which must be securely connected to an earth connection to ensure EMC compliance.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2.2 Base Label and Bit Switches

On the underside of the FCM9003 there are bit switches which may be used to configure certain functions within the unit.

The bit switches are ONLY used to configure the default settings following a cold start. A cold start may be triggered by setting switch 8 to the OFF position and power cycling before returning SW8 to the normal ON position. Alternately, a cold start may be requested from the User Interface.

2.2.1 WAN Port Configuration

Bit switches 1 to 5 are used to configure the default setting for the WAN Network port of the device and are used on installation to ensure the FCM9003 physical interface matches that of the network port it will connect to.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2.2.1.1 Switch 1, WAN Mode

The WAN mode switch selects between the two physical interfaces for the WAN port.

ON Select LAN1 as the WAN copper interface, presenting a 10/100/1000BaseT interface on RJ45

OFF Select SFP as the WAN Fibre interface, presenting either 100Base-FX or 1000Base-X when an SFP module is inserted.

2.2.1.2 Switch 2, Auto Negotiation

The Auto Negotiation switch controls whether the switch port is configured automatically, or manually.

ON Auto Negotiation Enabled

OFF Manual controlled selection of speed and duplex

Note,

When the Fibre interface has been selected, Auto negation must be enabled for 1000BaseX, however must be disabled for 100Base-FX operation.

2.2.1.3 Switch 3/4, Speed

There are two bit switches used to select the speed control of the WAN port. When auto negotiation is enabled, these switches control the options that are advertised, whereas in manual mode, the speed switches actually select the interface speed.

BitSw 3 BitSw4 Speed Auto Neg Advertise

ON Don’t Care 1000M 10/100/1000

OFF ON 100M 10/100

OFF OFF 10M 10

Note,

When the fibre interface is used, only 1000M and 100M options are valid.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2.2.2 Switch 5, Duplex

This switch controls the duplex mode of the port. When auto negotiation is enabled this controls the advertised options, whilst in manual mode, it controls the duplex mode.

ON Full Duplex

OFF Half Duplex

Note,

When the fibre interface is selected, only Full Duplex modes are supported.

2.2.3 Proxy Mode Management Control

2.2.3.1 Switch 6, Proxy

Proxy mode management allows the FCM9003 to act as a proxy client where it is accessed using the Enterprise extensions of IEEE802.3ah OAM. In proxy mode the central proxy server, usually a MetroConnect MC12000 chassis, is configured with the IP address details and the remote FCM9003 is managed without configuration.

ON Proxy Disabled

OFF Proxy Enabled, access via the WAN port

2.2.4 Zero Touch Configuration Control

There are two bit switches concerned with the setup of the unit to support the zero touch configuration mode. When the FCM9003 uses the Zero Touch, Auto Boot intialisation it will listen for a beacon on the WAN.

The beacon allows the FCM9003 to determine the correct tag values to use for a management connection to DHCP/TFTP/SNMP servers.

2.2.4.1 Switch 7, Boot Location / (Autoboot)

This switch enables the autoboot, Zero Touch Configuration mode.

ON Auto Boot, ZTC enabled

OFF Disabled, boot from local configuration

When auto boot is enabled the FCM9003 will listen for a beacon on the WAN port and then use the information gathered from this beacon to set up a management channel connection to DHCP and TFTP servers, and also to an SNMP manager.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2.2.5 Switch 8, Master Boot Control / (Factory Default)

This bit switch will return the unit back to the factory default settings and will also read the bit switches and configure the operating mode of the WAN port and Auto Boot operation.

ON Normal Operation

OFF Return the unit to Factory Default on power up.

When a unit is returned to the factory default, the password will be returned to the default, “fcm9003” and all IP and remote access configurations will be lost.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2.3 Rear Panel LED Indicators

The FCM9002 has eight LED indicators on the rear panel which show the port and unit status.

2.3.1 RJ45 Led Indicators

Each RJ45 connector has two LED’s, one green and one yellow and these are combined to show the Link State, Link Activity and Link Speed as shown below:

If the LED(s) are ON, it indicates the Link is up, and the combination of Green and Yellow LED’s indicates the speed.

If the LED(s) are Flashing, this indicates that the link is up, and activity is detected on the link, ie frames are being received or transmitted.

All LED’s off indicates the link is down.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2.3.2 SFP LED’s

The SFP interface has two status LED’s as described below

2.3.2.1 SFP Link (LK) LED

This Green LED indicates the state of the link.

OFF Link Down

ON Link UP

FLASH Link Up and Activity Detected

2.3.2.2 SFP Signal Detect (SD) LED

This bicolour LED indicates the status of the optical connection and has the following options:

OFF No SFP Fitted

RED SFP Fittted, but no signal detected

GREEN Optical Signal Detected

Note, the initial model of FCM9002 using the Rev.XA PCB does not support the RED LED, such that both Loss of Signal, and Not Fitted are shown by the LED being OFF.

2.3.3 Power (PWR) LED

The Power LED is GREEN ON to indicate that the unit is powered up.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2.3.4 Unit Status (OK) LED

The OK LED is a bicolour LED with the following states

OFF Unit not powered up

RED ON The selected WAN port has alarms

RED FLASH Both the selected WAN and User Ports have alarms

GREEN FLASH The User ports have alarms

GREEN ON No Alarms present.

The OK LED, gives an indication of the status of the device, and if it is not displaying GREEN ON, ie normal operation, the user should view the Global Status Screen on the user interface to determine the current alarm state.

It is advisable to change the state of unused ports to down as this will prevent them from generating alarms which will show on the OK LED.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

2.4 Rackmounting

The FCM9003 is a standalone, desktop unit however it may be mounted in a standard 19 inch rack using the rack mounting kit, part number 80-05-256.

To mount the FCM9003 in the 19 inch rack mount adaptor first remove the two M3x12 screws and washers from the rear panel of the unit. Then align the FCM9003 rear panel with the mounting bracket, and secure the unit to the adaptor using the previously removed screws.

When rackmounting, please ensure that the bitswitches on the underside are correctly configured prior to mounting the units in the rack.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

3 OPERATING MODES

The FCM9003 supports multiple modes of operation with support for pushing or popping tags. The FCM9003 supports two types of VLAN Tag, the basic IEEE 802.1q tag with Ethertype 8100, and referred to as C-Tag or Customer Tag within this manual. A second Tag type is referred to as the Service Tag, or S-Tag which has a configurable Ethertype with the default value of 9100.

The operating mode of the FCM9003 is defined in the traffic management section of the Data Port Setup Menu, see section 4.5.1

3.1 C-Tag Mode

In C-Tag mode, the FCM9003 will either push an IEEE 802.1q VLAN Tag onto a previously tagged or untagged frame, or will pass unchanged already tagged frames. The FCM9003 capabilities in C-Tag mode are shown below:

In C-Tag mode, flows are defined as groups of C-Tag VLAN ID’s. A VLAN ID may be in the range 1 to 4095. In the above example, there are five flows defined as well as a management channel connection.

The user ports have the option of operating as an Access port where untagged frames will have a C-Tag pushed on ingress, and popped on egress. This is shown for C-TAG 512 which is pushed onto all untagged frames ingressing port 4.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

Ports may also be configured to act as trunk ports where they will pass frames that ingress already containing VLAN Tags, and will discard any untagged frames.

Ports may also be configured for mixed mode operation where they will pass tagged frames and push a tag onto untagged frames.

A port may also operate as a QinQ access port pushing a tag onto all incoming frames including those already tagged, as shown for C-Tag 128 above.

The action of pushing a C-Tag is shown below:

where a four byte VLAN Tag is inserted into the frame after the source address and before the Ethertype.

A C-Tag is made up of four bytes as shown below:

Where

8100 A 2 byte Ethertype to identify IEEE 802.1q VLAN Tags

Pri A 3 bit priority marker, 0 lowest – 7 highest

C CFI, Canonical Form Indicator normally set to 0.

ID A 12 bit identifier in range 1 to 4095

When a tag is constructed the ID is taken from the default setting for the port. The Tag Priority may either be set to the port default setting, or for IP packets with DSCP priorities the tag priority may be based on the packet DSCP value.

8100 PRI C ID

DA SA ET Payload FCS

DA SA ET Payload FCSCT

Push C-Tag

IP (DSCP)

IP (DSCP)

Default IDDefault ID

Pri C ID8100

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

3.2 S-Tag Mode

In the FCM9003 Service Tags are used when an extra tag is to be pushed onto an already tagged frame. The Service Tag has a configurable Ethertype which by default is set to 9100. QinQ mode is supported by simply configuring the service tag ethertype to 8100.

The operation of the FCM9003 in the S-Tag mode is shown below:

In this mode, both tagged and untagged frames are supported on the user ports. In the example above, port 1 is set to push the Stag 101 onto untagged frames at ingress.

On port 2, frames ingress already tagged and all have the Stag 102 pushed to give a packet with two tags, an Stag and a CTag

Port 4 shows the service multiplexing ability of the FCM9003 where which S-Tags is pushed is determined by the incoming CTag to give the multiple flows with Stag 104/106/107.

Manager

Untagged

C-TAG 1-4095

C-TAG 1-4095

C-TAG 1-127

C-TAG 128-255

C-TAG 256-4095

Push

S-TAG

Push

S-TAG

Push

S-TAG

Push

S-TAG 104

S-TAG 106

S-TAG 107

S-TAG 101

S-TAG 102 C-TAG 1-4095

S-TAG 103 C-TAG 1-4095

S-TAG 104 C-TAG 1-127

S-TAG 106 C-TAG 128-255

S-TAG 107 C-TAG 256-4095

S-TA

G 105 O

ptional C-TA

G

S-TAG

101,102,103,104,105,106, 107

WAN USERFLOWS

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

3.2.1 Pushing S-Tag onto Untagged Frame

When an untagged frame ingresses a user port in Stag mode it will have an Stag pushed as shown below:

Where

9100 S-Tag Ethertype

PRI Priority

D Discard Eligibity, 0 – Green, 1 = Yellow

ID Stag ID in range 1 to 4095

When the pushed Stag is constructed it gains the Ethertype from the configured value. The default value is 9100, and setting this to 8100 will give QinQ operation, effectively VLAN within VLAN encapsulation.

The priority for an untagged frame may either be set to the default port priority, or be set to inherit a value based on the incoming IP DSCP priority.

The D or DEI bit will be set by the policer to colour mark the packet on egress on the WAN port.

The ID is the value defined for the flow assigned to the port.

9100 PRI D ID


DA SA ET Payload FCSST

Push S-Tag

IP (DSCP)

IP (DSCP)


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

3.2.2 Pushing S-Tag onto Tagged Frame

When a tagged frame ingresses a user port in Stag mode it will have an Stag pushed as shown below:

Where


PRI Priority




The priority for an tagged frame may either be set to the default port priority, or be set to inherit a value based on the incoming C-Tag priority.



9100 PRI D ID



DA SA ET Payload FCSCTST

Push S-Tag

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

3.3 Double Tag Mode

Double tag mode allows the FCM9003 to push both a C-Tag and S-Tag onto a user frame. The double tag mode will push both C-Tag and S-Tags onto untagged frames at ingress. For tagged frames, if the ID is within the allocated range, the C-Tag will be passed, and the S-Tag will be pushed. In this mode, the allowable C-Tag ID’s are limited to the range 1 to 4095 across all ports and flows.

The diagram below shows the operation of Double Tag mode

As can be seen in double tag mode, there are two separate tag processing functions, one on ingress to the user port and one on egress from the network port.

On ingress to a user port, an untagged frame may either be discarded or have a C-Tag pushed into the frame. A tagged frame ingressing a user port may have a QinQ tag pushed, may be passed unchanged if the ID is within a flow allocation, otherwise it will also be discarded.

One, or more, flows may be defined per user port with the flow being defined by the C-Tag range. In the example above, port 1 has a flow defined which includes C-Tag ID 1 to 127, whilst port 3 has two flows defined, one including ID’s 256 to 383, and one including 384 to 511. Port 4, on the other hand is set to push the tag 512 onto incoming un tagged frames.

On egress from the WAN port, each flow has a defined S-Tag pushed onto it. Each flow may use a different S-Tag ID, or one or more flows may share S-Tag ID’s.

A typical application of this mode would be to push C-Tags onto the user frames to identify which port or service the frames belonged to, whilst all frames had the same S-Tag pushed to identify the customer within the core network.

The construction of the frames traversing the FCM9003 in the double tag mode are as follows:

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

3.3.1 Untagged Frame Ingress

When an untagged frame ingresses a user port it will have both a C-Tag and S-Tag pushed onto the frame.

Here the untagged frame first has a C-Tag pushed. The ID used is the configured value for the port, whilst the priority may either be inherited from the incoming DSCP, or set to the default port value.

On egress, an S-Tag is then pushed into the frame using the configured values for ETYPE (9100) and ID. The priority for the S-Tag may be inherited from the C-Tag priority, or use the default value for the flow.

9100 PRI D ID

Default IDDefault PRI

DA SA ET FCSCT

DA SA ET FCSCTST

Push S-Tag

8100 PRI C ID


Push C-Tag

IP (DSCP)

Default IDDefault PRI

IP (DSCP)

IP (DSCP)

Payload

Payload

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

3.3.2 Tagged Frame Ingress

In double tag mode, when a tagged frame ingresses a user port, it will have an S-Tag pushed onto it. The priority within the S-Tag may be either defined for all frames, or be set to be inherited from the C-Tag as shown below:

Where


PRI Priority




The priority for a tagged frame may either be set to the default port priority, or be set to inherit a value based on the incoming C-Tag priority.



9100 PRI D ID




Push S-Tag

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4 CONFIGURATION

The FCM9003 is configured and managed using a simple, menu driven user interface accessible using either a local craft terminal or remotely using TELNET, HTTP or securely via SSH.

Once you log onto the device the top level menu is as below:

Metrodata FCM9003 “FCM9003” Alarms: Major

MAIN SET-UP

Global status <display>

Operational Modes <menu>

Flows (services) <menu>

peRf monitoring <menu>

Port set-up <menu>

V.24 set-up <menu>

Management Entity <menu>

System <menu>

Update EEPROM

Circuit/Flow Tests <menu>

First CAPITAL – select item

<escape> - exit menu

To select a particular menu item, type the first, or highlighted, capital letter in the menu description, for example <d> for the Data port set-up, or <m> for Management.

The type of item is displayed alongside the description:

<menu> There is a sub menu system below this item

<display> There is a status display screen below this item

“value” This item is a direct value which may be modified.

Value items come in two different types, those where a character string must be entered, or where a list of possible items may be toggled through. For toggle list items, use <SPACE> to select the next option and <ENTER> to accept.

To exit a menu, and return to the previous level type <ESCAPE>

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1 System Configuration

Menu Tree: Main Set-Up / System

The system menu provides the basic administrative configuration items for the FCM9003. The system menu is shown below:


SYSTEM

Time & date <menu>

Node name FCM9003

Access control <menu>

Software version Main 9.2 / Boot 5.7

Serial Number 77293

Warm start

aUto warm start -

Cold start

Maintenance <menu>

Zero-touch config <menu>



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.1 Setting the Time and Date

Menu Tree: Main Set-Up / System / Time & Date

The FCM9003 does not have a non volatile real time clock, instead it uses NTP to set the date and time following power up. In applications where NTP is not available, the FCM9003 defaults to providing a simple uptime display.

To configure the NTP parameters select the “Time and Date” menu from the system menu. The menu is shown below:


TIME & DATE

local Time 10:37:25

local Date Mon 14/09/2015

system up time 0d1h14m25s

time Zone GMT+1

NTP server 192.168.0.100

last sync 09:21:22 Mon 14/09/2015

Sync now



If NTP is available, then the time zone and NTP server address must be configured.

4.1.1.1 Time Zone

Menu Tree: Main Set-Up / System / Time & Date / time Zone

Since NTP uses GMT as the baseline time, time zone adjustment is required to enable the correct time to be displayed wherever the unit is deployed globally, and to allow for daylight saving.

The time zone may be adjusted by +/- 12 hours from GMT.

4.1.1.2 NTP Server

Menu Tree: Main Set-Up / System / Time & Date / NTP Server

For NTP to operate correctly, the FCM9003 must be configured with the IP address of an authoritative NTP time server.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.1.3 Sync Now

Menu Tree: Main Set-Up / System / Time & Date / Sync now

If the NTP server has not yet synchronised, it is possible for the user to force a manual synchronisation by issuing a Sync Now command.

Following power up, the NTP standard calls for a random delay before the NTP client will request sync from the server, manual sync will speed this process up if necessary.

4.1.2 Setting the Node Name Menu Tree: Main Set-Up / System / Node name

To enable identification of the FCM9003 it is useful to enter a meaningful name for the unit. The node name is entered as a string of upto 32 alpha numeric or printable control characters including spaces.

4.1.3 Access Control

Menu Tree: Main Set-Up / System / Access Control

The access control menu configures the user access security parameters for the unit. The Access Control Menu is shown below:

Metrodata FCM9003 "FCM9003" Alarms: Major

ACCESS CONTROL

Password ********

'View' user Enabled

Super Me No

TACACS+ <menu>

Welcome screen <menu>

First CAPITAL - select item


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.3.1 Setting the Local Password

Menu Tree: Main Set-Up / System / Access Control / Password

The local password for the FCM9003 may be changed using the system menu. The default password is, all lower case, “FCM9003”, however, for deployment a more secure password may be required.

To change the unit password, select “Password” from the system menu. The FCM9003 will display the following:

Enter new password

Password >

Enter the new password, upto 32 alphanumeric or printable control characters1. For security each character is shown on screen as an asterisk “*”. Once the new password is entered the display changes to:

Enter new password

Password > ********

Verify >

Re enter the new password to verify the change. If the password is verified the unit will assume the new password for the next logon.

4.1.3.1.1 Default Unit Password

The default unit password is “FCM9003” and must be entered in lower case.

4.1.3.1.2 Password Recovery

If the unit password is lost, access to the device will only be possible by cold starting the unit using the bit switches on the underside of the unit. A cold start will erase the unit configuration and return the unit to factory default, with password “FCM9003”.

1 The password may be constructed from the following characters : abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789`¬!”$%^^&**()-_=+[{]};:’@#~\|,<.>/?

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.3.2 View User

Menu Tree: Main Set-Up / System / Access Control / ‘View’ User

The FCM9003 supports two levels of access, Admin and View. An ADMIN user has full access rights over the FCM9003 configuration. A View user has read only access to the configuration.

For security, it may be desirable to disable the view user, non password protected read only access to the unit. This can be achieved by selecting the View User menu item and toggling the option to Disabled. When disabled, it will not be possible to view the configuration without the correct password.

4.1.3.3 Super Me

Menu Tree: Main Set-Up / System / Access Control / Super Me

The Super Me menu option provides a facility to promote an admin user to super user. In super user mode some further diagnostic menu options are made available. Super user Mode will only normally be required when instructed by Metrodata Technical Support in order to extract detailed status information from the unit.

4.1.3.4 TACACS+

Menu Tree: Main Set-Up / System / Access Control / Tacacs+

Where greater access control and security is required, the FCM9003 units support TACACS+ for central password authentication.


TACACS+

Authentication TACACS+,Local

Timeout 3

Retries 3

Server 192.168.100.45

Backup Server 192.168.100.54

Encryption key ***********



Formatted: Heading 4

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.3.3.14.1.3.4.1 Authentication

Menu Tree: Main Set-Up / System / Access Control / Tacacs+ / Authentication

The FCM9003 supports three modes of password access control and authentication. The options are:

Local (Default) The password access control is handled locally by the FCM9003 unit and the unit local password should be used to log in.

TACACS+, Local In this mode, the FCM9003 unit will attempt to contact the TACACS+ server(s) for authentication, however if the server(s) cannot be accessed, it will fall back to local password administration.

TACACS+ Use TACACS+ for password authentication. If the server(s) are unavailable, access to the unit will not be allowed.

4.1.3.3.24.1.3.4.2 Timeout

Menu Tree: Main Set-Up / System / Access Control / Tacacs+ / Timeout

The timeout defines how long the FCM9003 unit will wait for a response from the TACACS+ server. The timeout is specified in seconds in the range 1 to 90 seconds.

4.1.3.3.34.1.3.4.3 Retries

Menu Tree: Main Set-Up / System / Access Control / Tacacs+ / Retries

This defines the number of attempts the FCM9003 unit will make when trying to access the TACACS+ server. The valid range is 1 to 10.

4.1.3.3.44.1.3.4.4 Server

Menu Tree: Main Set-Up / System / Access Control / Tacacs+ / Server

This defines the IP address of the TACACS+ Authentication server. When a login attempt is made, this server will be accessed.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.3.3.54.1.3.4.5 Backup Server

Menu Tree: Main Set-Up / System / Access Control / Tacacs+ / Backup Server

This defines the IP address of the TACACS+ Backup Authentication server. When a login attempt is made, should the main server be unavailable then this server will be accessed for authentication.

4.1.3.3.64.1.3.4.6 Encryption Key

Menu Tree: Main Set-Up / System / Access Control / Tacacs+ / Encryption Key

This key is used by both the FCM9003 and the TACACS+ server(s) to provide a secure, encrypted password exchange and authentication. This must be set the same on both FCM9003 and Server(s). For security, the key is hidden.

Note, when the encryption key is not defined, it shows a blank entry.

Note, where main and backup servers are used they must share a common secret encryption key.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.3.44.1.3.5 Welcome Screen

Menu Tree: Main Set-Up / System / Access control / weLcome screen

This menu allows for a user defined welcome screen to be used rather than the standard Metrodata screen. By default the user defined screen is disabled but once enabled it is configured line by line as shown:


WELCOME SCREEN

Welcome screen Enabled

1st line This is an example

2nd line of a customised

3rd line Welcome Screen

4th line

5th line You may define upto

6th line 8 lines of text

7th line

8th line Here is line number 8

Clear all text

Display Screen <display>



Once the welcome screen has been defined, it may be displayed for checking by selecting display screen.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.3.54.1.3.6 Display Screen

Menu Tree: Main Set-Up / System / weLcome screen / Display Screen

This menu displays the welcome screen as it will be seen by users attempting to log on to the unit.


WELCOME SCREEN

--------------

This is an example

of a customised

Welcome Screen

You may define upto

8 lines of text

Here is line number 8

<escape> - exit, other key - refresh

4.1.4 Software Version Menu Tree: Main Set-Up / System / Software version

This display item shows the version of application and boot code running on the unit.

When reporting problems with units, it is useful to include the software versions as part of the fault reports.

4.1.5 Serial Number

Menu Tree: Main Set-Up / System / Serial Number

This display item displays the unit hardware serial number which is also displayed on the base label.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.6 Warm Start

Menu Tree: Main Set-Up / System / Warm start

A warm start will force the unit to reboot and reload the configuration stored in the EEPROM. Note, any changes to the configuration made that have not been saved WILL be lost.

When a TELNET/SSH user issues a warm start request, the FCM9003 will indicate that a warm start is about to take place, and then close the connection.

4.1.7 Auto Warm Start

Menu Tree: Main Set-Up / System / aUto warm start

When accessing the FCM9003 remotely it is possible to disconnect access when making configuration changes, for example changing the IP address or management VLAN. Often the reason for disconnection is an inadvertant change which has the unintended consequence of disconnection.

In order to mitigate this possiblilty, the Auto Warm Start offers an automatic configuration reload after a timeout. This allows the user to initiate an auto reboot in 10 minutes, then start the reconfiguration and if successful, save the config updates and cancel the reload, or if disconnected wait for the timeout for the previous running configuration to be reloaded and access be restored.

When required, the timeout is defined as follows:

10m 10 minutes

10 10 seconds

0 Cancel the auto warm start

4.1.8 Cold Start Menu Tree: Main Set-Up / System / Cold Start

A Cold Start will erase the configuration EEPROM and return the unit to the factory default condition as defined by the bit switch settings.

Note, that a cold start will erase all IP addresses and routing table entries and it is highly likely that remote access will be lost following a cold start.

Due to the drastic nature of a cold start, the command requires user confirmation before cold starting.

Note, the cold start will not clear the provider id used by the beacon system.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.9 Maintenance

Menu Tree: Main Set-Up / System / Maintenance

In order to reduce the number of items on the system menu screen, the Event logs and Config load/store have been moved into the maintenance menu which is shown below:


MAINTENANCE

System event log <display>

Alarm event log <display>

Config. event log <display>

Full event log <display>

Output config <display>

Input config

CAPITAL letter - select item


4.1.9.1 System Event Log

Menu Tree: Main Set-Up / System / Maintenance / System event log

The system event log gives the time of system level events such as system restarts, or NTP updates.


--- System Event Log ---

12/11/2012 10:37:22 clock set via NTP

12/11/2012 09:26:05 NTP failed

12/11/2012 09:23:00 performance log cleared

12/11/2012 09:23:00 rtc needs to be set

12/11/2012 09:23:00 config restored

12/11/2012 09:23:00 event logs cleared

press any key to continue

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.9.2 Alarm Event Log

Menu Tree: Main Set-Up / System / Maintenance / Alarm event log

The Alarm event log lists the time of all alarm events including start and finish time.


--- Alarm Event Log ---

12/11/2012 09:26:45 Minor OFF Flow2

12/11/2012 09:26:45 Minor OFF Flow1

12/11/2012 09:26:45 Major OFF WAN

12/11/2012 09:23:38 Major ON WAN

12/11/2012 09:23:35 Minor ON Flow2

12/11/2012 09:23:35 Minor ON Flow1


4.1.9.3 Config Event Log

Menu Tree: Main Set-Up / System / Maintenance / Config event log

The config event log shows the time of all configuration changes, though not the actual changes made. It is often the case that things stopped working after a configuration change.


--- Config Event Log ---

12/11/2012 09:26:45 Config. updated

12/11/2012 09:26:45 Config. updated

12/11/2012 09:26:45 Config. updated

12/11/2012 09:23:38 Config. updated

12/11/2012 09:23:38 Config. updated

12/11/2012 09:23:35 Default config. set


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.9.4 Full Event Log

Menu Tree: Main Set-Up / System / Maintenance / Full event log

The full event log shows all events in time order, this log can get quite large so the individual logs may prove more informative.


--- Full Event Log ---

12/11/2012 10:37:22 clock set via NTP

12/11/2012 09:26:45 Config. updated

12/11/2012 09:26:45 Config. updated

12/11/2012 09:26:45 Config. updated

12/11/2012 09:26:45 Minor OFF Flow2

12/11/2012 09:26:45 Minor OFF Flow1

12/11/2012 09:26:45 Major OFF WAN

12/11/2012 09:26:05 NTP failed

12/11/2012 09:23:38 Config. updated

12/11/2012 09:23:38 Config. updated

12/11/2012 09:23:38 Major ON WAN

12/11/2012 09:23:35 Minor ON Flow2

12/11/2012 09:23:35 Minor ON Flow1

12/11/2012 09:23:38 Major ON WAN

12/11/2012 09:23:35 Minor ON Flow2

12/11/2012 09:23:35 Minor ON Flow1

12/11/2012 09:23:35 Default config. set

12/11/2012 09:23:00 performance log cleared

12/11/2012 09:23:00 rtc needs to be set

12/11/2012 09:23:00 config restored

12/11/2012 09:23:00 event logs cleared


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.9.5 Output Config

Menu Tree: Main Set-Up / System / Maintenance / Output config

This menu item allows the user to output the ASCII configuration file to the screen. If a text capture is enabled the file my be saved and reused to reload the configuration at a later date if necessary.

When the output config option is selected the following screen appears


Start capture then press a key

After transfer, stop capture then press another key

At this point enable the text capture and then press a key to continue.

The configuration file will be output to the screen in an ASCII form, readable but not really understandable as shown by the extract from a config file shown below:

# Metrodata DSU Configuration Dump #

cfmep.0.ma=0

cfmep.0.mid=101

cfmep.0.if=11

cfmep.0.d=1

cfmep.0.e=1

cfmep.0.s=1

rt.0.d=192.168.0.0

rt.0.i=1

rt.0.ty=3

rt.0.p=2

rt.0.m=255.255.255.0

rt.0.ti=2

rt.1.i=1

rt.1.n=192.168.0.254

rt.1.ty=4

rt.1.p=2

snmp.n=FCM9003

snmp.l=Test Network

welcome.0=This is an example

welcome.1=of a customised

welcome.2=Welcome Screen

welcome.4=You may define upto

welcome.5=8 lines of text.

welcome.8=Here is line number 8

To return the main system menu, stop the text capture and hit any key to proceed.

Note, following the ouotput of the config file, it must be trimmed to remove extra lines before the opening # Metrodata DSU Configuration Dump # and after the final config item SNMP.26.i=xxx. Without trimming, the file will give errors when it is loaded.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.9.6 Input Config

Menu Tree: Main Set-Up / System / Maintenance / Input config

If a config file has been captured it may be reloaded to the unit using the Input Config command.

Selecting Input Config gives the following message:

Send File. Esc to end.

Use a send text file option from the terminal package, and select the stored configuration file. Once the file has been sent, type ESC to finish.

Once loaded the unit will reboot to load the configuration.

If errors are detected in the configuration file, the first error will be reported with the line number.

Note, when using HyperTerm or similar it is necessary to add a 1ms character delay to prevent character loss.

4.1.10 Zero Touch Configuration Menu Tree: Main Set-Up / System / Zero-Touch Config

The FCM9003 supports a zero touch configuration mode of operation whereby the unit will power up, listen for a beacon on the management channel and then automatically request an IP address using DHCP and configuration using TFTP.

The ZTC menu is as shown below:


ZERO-TOUCH CONFIG

Provider id

State Inactive

s/w Upgrade time Never



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.10.1 Provider ID

Menu Tree: Main Set-Up / System / Zero-Touch Config / Provider id

The provider ID is used during zero touch configuration and is used to identify the beacons that should be used when multiple beacons are present.

If the provider ID is left blank, the FCM9003 will listen for any beacon whatever the provider ID, whilst if a value is entered, only beacons with a matching ID will be used.

The provider ID is not cleared by a cold start, and must be cleared manually if necessary.

The provider ID is a string of upto 16 characters.

4.1.10.2 Zero Touch State

Menu Tree: Main Set-Up / System / Zero-Touch Config / State

This menu item serves as both an enable, and a status display for the units progress during zero touch configuration.

To enable Zero Touch, which is the normal factory default, select Zero Touch and toggle the state to START which will initiate the process of checking for a beacon, and then loading a config file.

To disable the Zero Touch Configuration, change the state to INACTIVE.

The possible states that the zero touch configuration may be in are listed below:

INACTIVE Zero Touch Configuration is disabled.

START Zero Touch Configuration is intialising

LISTENING Zero Touch Configuration is listening for the beacon on the network port.

FOUND A beacon has been detected and an IP address has been obtained.

CONFIGURING Zero Touch Configuration is downloading, or trying to download, the configuration file from the supplied TFTP server.

CONFIGURED Zero Touch Configuration is complete

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.1.10.3 Software Upgrade Time

Menu Tree: Main Set-Up / System / Zero-Touch Config / s/w Upgrade time

Part of the Zero Touch Configuration Beacon protocol is to indicate the current software revision. When a new software revision has been checked out and is ready to release the file should be loaded to the TFTP server. The beacon software version number should be updated and then units that are enabled to automatically update their software will do so at a pre determined time. To prevent all units attempting to upgrade at once the time may be defined for each unit.

The options are:

NEVER Do not automatically upgrade the firmware.

RANDOMIZED Wait a random time of between 0 and 256 minutes from the beacon.

FIXED Perform the upgrade the defined time.

IMMEDIATELY Perform the upgrade immediately on receiving a beacon indicating a new version of code is available.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2 Management Entity

Menu Tree: Main Set-Up / Management Entity

The Management Entity menu is where the remote access to the FCM9003 is configured. The top level management entity menu is as below:


MANAGEMENT ENTITY

intErface <menu>

Ip <menu>

Udp <menu>

tCp <menu>

sNmp <menu>

Telnet/SSH/HTTP <menu>

tFtp <menu>

tWamp <menu>

Ping <display>



4.2.1 Interface

Menu Tree: Main Set-Up / Management Entity / intErface

The interface menu configures the unit management interface.

The interface menu is shown below, and allows for independent IP settings for all physical ports and Flows.


MGMT INTERFACES

---------------

# Name St Mode DHCP IP Net Mask C-VLAN

-------------------------------------------------------------------------

- aux Up IP Off 169.254.42.42 255.255.0.0 None

5 LAN1 Up Dis

6 LAN2 Up Dis

7 LAN3 Up Dis

8 LAN4 Up Dis

9 SFP Up Dis

A WAN Up Dis

B Flow1 Up IP On --- --- None

<Esc> - exit, 1.. - details, <Enter> - refresh

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

Typically, the FCM9003 will be managed either via out of band via a dedicated user port, or via a Flow on the WAN port. The interface menu allows an IP address to be applied to each individual port and flow. The FCM9003 does not provide a routing function between ports and IP networks, the multiple networks are available to provide an IP terminaton point for either provisioning L3 RFC2544 test, or in service L3 TWAMP performance monitoring.

By default, LAN4 also provides the AUX port access and has default IP address 169.254.42.42. This IP address may be accessed regardless of port or flow allocations and may share the untagged setting of either and allocated port or flow management over LAN4.

To allocate an IP end point address, select the port or flow, using the selection number/letter in the left hand column, that you wish to configure, As an example for Flow1, type ‘b’ and this will lead to the following menu, however all ports and flows have the same configuration parameters:


MGMT INTERFACE, FLOW1

Mode Normal IP

phys. address 00:c0:81:00:17:e3

Dhcp On

Ip addr 0.0.0.0

Net mask 0.0.0.0

At table <display>

default gateWay none

c-Vlan Auto(None)

s-vlan 0

taG priority 0



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.1.1 Mode

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / Mode

The mode setting defines the operational state of this port/flow. The options are as follows:

Normal IP This mode allocates an IP end point address which my be used for management or test purposes.

Proxy Client This mode force the port to operate in Proxy Client mode using a proprietry OAM based protocol controlled by a remote proxy server.

Proxy Server This mode forces the port to operate as a proxy server and will provide the IP configuration for the remote proxy client.

Disabled This mode disables the port and forces the administrative state to down.

4.2.1.1.1 Mode: Normal IP

Normal IP mode configures a new IP stack on this port/flow. The parameters and connectivity are defined using the following menu options:

4.2.1.1.1.1 Physical Address

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / Phys. address

This is a display item only, and shows the unit MAC Address.

4.2.1.1.1.2 DHCP

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / DHCP

DHCP allows the FCM9003 to get an IP address automatically from a centrally administered server.

DHCP can be enabled, or disabled where the IP address must be manually configured on each unit.

When DHCP is enabled, a unit powers up and broadcasts a DHCP request for an address. Once a server hears the request, it will respond with an address the unit can use.

DHCP is always enabled when ZTC is used.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.1.1.1.3 IP Address

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / IP Addr

In order to access the FCM9003 remotely it must be configured with an IP address. This may be obtained either using DHCP, in which case this will be configured automatically, or Manually if DHCP is disabled.

The IP address should be entered in the format AA.BB.CC.DD

By default, the aux port on LAN4 assumes the IP address 169.254.42.42 with DHCP disabled.

4.2.1.1.1.4 Net Mask

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / Net Mask

The network mask is used to differentiate the network address from the host address.

If DHCP is enabled, the net mask is served by the DHCP server and is configured automatically.

4.2.1.1.1.5 AT Table

Menu Tree: Main Set-Up / Management Entity / intErface / Lan 4 / AT table

The AT Table display allows the user to view the device ARP table. This may be useful when devices are having problems communicating. The ARP table is shown as below:


AT TABLE

--------

IP Address Ethernet Address Age

--------------------------------------------------

192.168.0.254 0.60.3e.99.f.e2 11231

192.168.0.100 0.9.5b.1c.2e.a8 6967

<Escape> - exit, other key – refresh

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.1.1.1.6 Default Gateway

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / default gateWay

The default gateway for the port/flow is defined to give the gateway IP address for access to off subnet hosts.

When DHCP is enabled, the default Gateway is normally supplied by the server along with the IP address and network mask.

Note, each IP endpoint is treated as a separate network and there is no routing between ports.

4.2.1.1.1.7 C-VLAN

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / c-VLAN

This is the value of IEEE 802.1q TAG that is used by the manager when transmitting or receiving frames.

When frames are to be sent with a TAG, the acceptable values are in the range 1 to 4095.

When frames are to be sent untagged, the value is NONE.

A further option of AUTO allows the management IP to automatically use a different VID if the physical port is changed to push tags.

4.2.1.1.1.8 S-VLAN

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / S-VLAN

This value defines the outer tag that will be used. Acceptable values for tagged frames are 1 to 4095, or NONE for untagged.

Note, the Ethertype used for the S-VLAN is configurable, but defaults to 9100.

QinQ/S-Vlan value is only configurable when the unit is operating in S-Tag or Dual Tag modes.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.1.1.1.9 Tag Priority

Menu Tree: Main Set-Up / Management Entity / intErface / B (Flow1) / taG priority

When the manager transmits tagged frames, they are sent with the configured priority.

0 Low Priority to 7 Highest Priority

4.2.1.1.2 Mode : Proxy Client


Metrodata FCM9003 "" Alarms: Major

FLOW1

Mode Proxy Client

Learn servers No

ip addr ---

net mask ---



When configured as a proxy client, the manager will receive the management via the L2 protocol OAM. All IP level configuration is performed on the Proxy Server device.

4.2.1.1.2.1 Learn Servers

Menu Tree: Main Set-Up / Management Entity / intErface / B (flow1) / Learn servers

To further ease remote configuration of the proxy client, if this is enabled it will automatically assume the proxy server configuration for TFTP, NTP, SNMP servers

4.2.1.1.2.2 IP Address / NET Mask

These two menu items are display only, and will display the proxied IP address and Mask used by the client.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.1.1.3 Mode : Proxy Server



FLOW1

Mode Proxy Server

Host interface Flow 1

phys. address 00:c0:81:00:18:50

Dhcp On

ip addr ---

net mask ---



When configured as a PROXY SERVER, the unit will serve a remote client with the IP management configuration and through the use of the OAM protocol will operate with no configuration of the remote unit.

4.2.1.1.3.1 DHCP

For Proxy Server operation, DHCP should be disabled.

4.2.1.1.3.2 IP Address

This is the IP address served to the Proxy Client at which it may be accessed.

4.2.1.1.3.3 Net Mask

This is the IP net mask served to the Proxy Client.

4.2.1.1.4 Mode : Disabled


Setting the mode to disabled will force the port IP to the administrative DOWN state and it will not be accessible.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.2 IP Configuration

Menu Tree: Main Set-Up / Management Entity / IP

The IP configuration menu is as shown below:


IP

default TTL 32

DSCP priority 0

Routing table <display>

Forwarding Disabled

Stats. <display>



4.2.2.1 Default TTL

Menu Tree: Main Set-Up / Management Entity / IP / default TTL

When packets are generated by the FCM9003 manager, they will be transmitted with the value configured here. It is unlikely that the default value of 32 will need to be changed, though it may be set in the range 1 to 255 bearing in mind that the TTL value is decremented by 1 for each router on the route.

4.2.2.2 DSCP Priority

Menu Tree: Main Set-Up / Management Entity / IP / DSCP priority

When packets are transmitted by the FCM9003 manager, they will be transmitted with the configured DSCP ( Differentiated Services Code Point ) value. DSCP may be specified in the range 0 to 63 with 0 being best effort.

The exact meaning and priority of DSCP values are network dependant , though the following table usually applies for traffic classification.

Discard Probability

Class 1 Class 2 Class 3 Class 4

Low DSCP 10 DSCP 18 DSCP 26 DSCP 34

Medium DSCP 12 DSCP 20 DSCP 28 DSCP 36

High DSCP 14 DSCP 22 DSCP 30 DSCP 38

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.2.4 Routing Table

Menu Tree: Main Set-Up / Management Entity / IP / Routing table

In order to operate within a routed network, and access hosts that are not located on the same subnet, the routing table must be configured. The FCM9003 supports static routing only.

The routing table menu is as shown below:


ROUTING TABLE

Display table <display>

1 - 0.0.0.0 <menu>

2 - 192.168.0.0 <menu>

Add entry <menu>



4.2.2.4.1 Display Table

Menu Tree: Main Set-Up / Management Entity / IP / Routing table / Display table

The routing table menu is as shown below:


Destination Next Hop I/F Type Prot. Age Mask

---------------------------------------------------------------------

0.0.0.0 192.168.0.254 LAN4 ind local 12046 0.0.0.0

192.168.0.0 0.0.0.0 LAN4 direct local 1350 255.255.255.0

<Esc> - exit, <Enter> - refresh

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.2.4.2 Editing Routes

Menu Tree: Main Set-Up / Management Entity / IP / Routing table / 1-X

To edit a previously defined route entry, select the route number and the edit route menu will be displayed as shown:


ROUTING TABLE ENTRY

Destination 0.0.0.0

Mask 0.0.0.0

Next-hop 192.168.0.254

Interface LAN4

type Indirect

protocol Local

dElete entry



4.2.2.4.3 Adding Routes

Menu Tree: Main Set-Up / Management Entity / IP / Routing table / Add entry

A new route may be added by selecting Add Entry.

4.2.2.5 Forwarding

Menu Tree: Main Set-Up / Management Entity / IP / Forwarding

The FCM9003 does not support routing between its ports, only switching and therefore Forwarding is disabled.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.2.6 IP Statistics

Menu Tree: Main Set-Up / Management Entity / IP / Stats.

The manager provides a full set of SNMP statistics for the IP layer as shown below:


IP Statistics

-------------

ipInReceives 3031

ipInHdrErrors 0

ipInAddrErrors 0

ipForwDatagrams 0

ipInUnknownProtos 0

ipInDiscards 0

ipInDelivers 3031

ipOutRequests 2861

ipOutDiscards 0

ipOutNoRoutes 0

ipReasmReqds 0

ipReasmOKs 0

ipReasmFails 0

ipFragOKs 0

ipFragFails 0

ipFragCreates 0

ipRoutingDiscards 0


The following two screens display the ICMP protocol statistics

icmpInMsgs 362

icmpInErrors 0

icmpInDestUnreachs 0

icmpInTimeExcds 0

icmpInParmProbs 0

icmpInSrcQuenchs 0

icmpInRedirects 0

icmpInEchos 362

icmpInEchoReps 0

icmpInTimestamps 0

icmpInTimestampReps 0

icmpInAddrMasks 0

icmpInAddrMaskReps 0

icmpOutMsgs 362

icmpOutErrors 0

icmpOutDestUnreachs 0

icmpOutTimeExcds 0

icmpOutParmProbs 0

icmpOutSrcQuenchs 0

icmpOutRedirects 0


icmpOutEchos 0

icmpOutEchoReps 364

icmpOutTimestamps 0

icmpOutTimestampReps 0

icmpOutAddrMasks 0

icmpOutAddrMaskReps 0

FCM9003 USER MANUAL

76-02-100 Rev.A of 216


4.2.3 UDP Menu Tree: Main Set-Up / Management Entity / UDP

The FCM9003 uses UDP for SNMP management. This menu displays the port numbers used and statistics.


UDP

snmp Port 161

snmp Trap port 162

Stats <display>



4.2.3.1 SNMP Ports

Menu Tree: Main Set-Up / Management Entity / UDP / snmp Port

Menu Tree: Main Set-Up / Management Entity / UDP / snmp Trap port

As defined by the IANA, the standard UDP port numbers are

SNMP 161

SNMP Trap 162

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.3.2 Statistics

Menu Tree: Main Set-Up / Management Entity / UDP / Stats

The FCM9003 provides the SNMP UDP layer mib statistics


UDP Statistics

--------------

udpInDatagrams 2340

udpNoPorts 323

udpInErrors 0

udpOutDatagrams 2071


4.2.4 TCP Menu Tree: Main Set-Up / Management Entity / tCP

The TCP menu gives information relating to the TCP layer


TCP

Stats. <display>

Conn. table <display>



TCP is a connection orientated protocol and the conn table gives information relating to current TCP sessions, whilst the stats menu shows the SNMP MIB TCP statistics.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.4.1 Statistics

Menu Tree: Main Set-Up / Management Entity / tCP / Stats

The TCP statistics available are as shown:


TCP Statistics

--------------

tcpActiveOpens 7

tcpPassiveOpens 0

tcpAttemptFails 0

tcpEstabResets 0

tcpInSegs 450

tcpOutSegs 550

tcpRetransSegs 0

tcpInErrs 0

tcpOutRsts 0


4.2.4.2 Connection Table

Menu Tree: Main Set-Up / Management Entity / tCP / Conn Table

The Connection table displays the list of the currently open sessions as shown


TCP CONNECTION TABLE

--------------------

State LocalAddress Loc Port RemAddress Rem Port

------------------------------------------------------------

established 192.168.0.13 23 192.168.100.48 2711

synReceived 192.168.0.13 23 192.168.100.48 2687


The FCM9003 supports eight concurrent Telnet or other TCP protocol sessions. An attempt to open a ninth session will be rejected by the FCM9003

Due to the session limit, it is vitally important that a timeout value is used for Telnet to force close them after a period of inactivity.

Note, When tested with NMAP port scanning software under Linux, where the correct sequence of SYN/ACK/RST is used the connections are used and freed up continuously. When running under windows, the connections will all be used and slowly timeout due to NMAP sending repeated SYN requests and not closing them once acknowledged.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.5 SNMP

Menu Tree: Main Set-Up / Management Entity / sNmp

The FCM9003 supports management access via SNMP V1 or V2c, which may be configured using the SNMP menu,


SNMP

Read community public

Write community public

Trap community public

Managers <menu>

contact Person Metrodata Limited,Laxton House,

Crabtree Office Village,Eversl..

Node name FCM9003

Location Test Network

Stats. <display>

trap Alarms <menu>



4.2.5.1 Communities

Menu Tree: Main Set-Up / Management Entity / sNmp / Read community

Menu Tree: Main Set-Up / Management Entity / sNmp / Write community

Menu Tree: Main Set-Up / Management Entity / sNmp / Trap community

The FCM9003 supports separate communities for Read, Write and Trap access. Communities provide a limited level of security within SNMP V1 as only requests with the correct community name will be actioned.

By default, all communities are set to PUBLIC.

The community names must be changed to match those used by the network management system.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.5.2 Managers

Menu Tree: Main Set-Up / Management Entity / sNmp / Managers

The FCM9003 supports upto 4 separate SNMP Managers which may be configured using the managers menu system. Only SNMP polls and get/set requests from configured managers will be accepted.

The managers menu is as below:


MANAGERS

1 - 192.168.100.45 <menu>

2 - 192.168.100.70 <menu>

Add manager <menu>



Here there are two managers currently configured which may be selected for viewing, editing by typing the manager number, in this case 1 which will then display the parameters for this manager:


1 - 192.168.100.45

IP address 192.168.100.45

Access rights Read-Write

receives Traps Yes

snmp Version SNMPv2c

Remove manager



The parameters required for an SNMP manager are the IP address. Note, that the routing table must be configured where the manager is not on the same subnet as the FCM9003.

The manager configuration controls the access rights that the manager has, which may be NONE, READ-ONLY, or READ-WRITE.

The manager may also be set up for traps, if enabled the FCM9003 will generate traps destined for this manager when alarm events occur.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

The FCM9003 supports SNMP V1 or V2c on a per manager basis.

If a manager is no longer required, the it maybe removed.

4.2.5.2.1 Dying Gasp Trap

When multiple managers are configured, the FCM9003 will issue the dying gasp trap to each manager in turn starting with manager 1.

As there is limited time to generate the Dying Gasp Trap it is quite likely that higher numbered managers will not receive this trap as the power will have failed by then.

4.2.5.3 Contact Person

Menu Tree: Main Set-Up / Management Entity / sNmp / contact Person

The SNMP Contact person is the RFC-1213 MIB-2 SysContact MIB definition. This item is a string of upto 255 characters.

4.2.5.4 Node Name

Menu Tree: Main Set-Up / Management Entity / sNmp / Node name

The SNMP Node Name is the MIB-2 SysName MIB definition. This item is a string of up to 255 characters.

4.2.5.5 Location

Menu Tree: Main Set-Up / Management Entity / sNmp / Location

The SNMP Location is the MIB-2 SysLocation MIB definition. This item is used to show the detailed location of the device. This item is a string of upto 255 characters.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.5.6 SNMP Statistics

Menu Tree: Main Set-Up / Management Entity / sNmp / Stats

The FCM9003 provides a display of the MIB-2 SNMP statistics as shown:


SNMP Statistics

---------------

snmpInPkts 2165

snmpOutPkts 2216

snmpInBadVersions 0

snmpInBadCommunityNames 0

snmpInBadCommunityUses 0

snmpInASNParseErrs 0

snmpInTooBigs 0

snmpInNoSuchNames 0

snmpInBadValues 0

snmpInReadOnlys 0

snmpInGenErrs 0

snmpInTotalReqVars 6023

snmpInTotalSetVars 0

snmpInGetRequests 2018

snmpInGetNexts 147

snmpInSetRequests 0

snmpInGetResponses 0

snmpInTraps 0

press any key to continue:

snmpOutTooBigs 0

snmpOutNoSuchNames 322

snmpOutBadValues 0

snmpOutGenErrs 0

snmpOutGetRequests 0

snmpOutGetNexts 0

snmpOutSetRequests 0

snmpOutGetResponses 2166

snmpOutTraps 51


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.5.7 Trap Alarms

Menu Tree: Main Set-Up / Management Entity / sNmp / trap Alarms

The Trap Alarm Menu allows the user to control which of the wide range of possible alarms generated by the FCM9003 should generate traps.

Under this menu are all the port and other sources of alarms and each alarm is listed and may be set to generate a Trap, or if it is deemed unimportant, No-Trap.

The alarm types supported by the FCM9003 are listed below:

LKDN Link Down

LLF Link Loss Forwarding

FEFI Far End Fault Indication, 100BaseFX only

OAM Loss of link OAM connectivity messages

LOS Loss of Optical Signal

NF SFP Not Fitted

RDI Receiving Service CFM RDI indications

NP No CFM peer MEP discovered

XCON Misconnected CFM MEP

ERR Errored CFM messages

REM Loss of remote CCM messages

MAC Remote user port failure

RDI Remote Defect Indication

SLA SLA not being met

SFPA SFP Diagnostic Alarm

SFPW SFP Diagnostic Warning

OTDR SFP OTDR value available

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.6 Telnet/SSH/HTTP

Menu Tree: Main Set-Up / Management Entity / Telnet/SSH/HTTP

The FCM9003 supports remote access using either TELNET, HTTP or the more secure encrypted SSH V2. The menu is shown below:


TELNET/SSH/HTTP

tElnet Enabled

SSH Enabled

HTTP Enabled

Timeout 600



4.2.6.1 TELNET

Menu Tree: Main Set-Up / Management Entity / Telnet/SSH/HTTP / tElnet

If the TELNET option is enabled, then the insecure Telnet protocol is available for remote management of the FCM9003. If Telnet is disabled, then no access is possible remotely without using SSH.

4.2.6.2 SSH

Menu Tree: Main Set-Up / Management Entity / Telnet/SSH/HTTP / SSH

If SSH access is enabled, upto 8 concurrent sessions are supported.

The FCM9003 SSH V2 server has been verified with several of the more popular SSH clients including:

PUTTY

TeraTerm TTSSH

BitVise SSH Client

Note, when connecting to the FCM9003 SSH server there will be a delay of upto 15 seconds whilst the secure key calculation and key exchange process occurs. Once this is completed, the user interface operates as normal.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.6.3 HTTP

Menu Tree: Main Set-Up / Management Entity / Telnet/SSH/HTTP / HTTP

The FCM9003 may be accessed via a simple HTTP web interface. The fundamental layout and funtionality of the interface is the same as for the menu based interface.

4.2.6.4 Timeout

Menu Tree: Main Set-Up / Management Entity / Telnet/SSH/HTTP / Timeout

To ensure that Telnet/SSH sessions are not left open, an inactivity timer is provided which will automatically shut down the session if it is not being used.

The default setting in 60 seconds, however a more practical value is 600, 10 minutes.

Setting the timeout to 0, disables the timer – however this must be done with care as unwanted Telnet/SSH sessions will never be cleared.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.7 TFTP

Menu Tree: Main Set-Up / Management Entity / tFtp

The FCM9003 uses the TFTP protocol to enable file transfers into or out of the device. TFTP is a client/server protocol and the FCM9003 is capable of operating as either client or server.

4.2.7.1 Client Mode

Menu Tree: Main Set-Up / Management Entity / tFtp / Mode

In client mode, an external TFTP server must be running on a machine somewhere that is accessible at the configured address.


TFTP

Mode Client

remote IP 192.168.0.100

Get new software <display>

Boot s/w upgrade <display>

get Config.

Put config.

put Report



4.2.7.1.1 Remote IP

Menu Tree: Main Set-Up / Management Entity / tFtp / remote IP

This is the IP address of the remote TFTP server which must be running in order for a TFTP transfer to take place.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.7.1.2 Get New Software

Menu Tree: Main Set-Up / Management Entity / tFtp / Get new software

This menu item is used to upgrade the system application firmware. Selecting this option will lead to the following display:


TFTP Software Upgrade

CAUTION: Proceding further will mean that the unit must be re-started,

and the performance log may be cleared, even if the upgrade is

unsuccessful. Are you sure you wish to continue?

At the prompt, confirm the action by typing <Y>, for Yes. The menu will now prompt for the file name.

Enter the file name.

The file will now download, with a block count to show activity and will then prompt the user to verify that the correct file has been downloaded

File name: FCM9003.90

Blocks received: 8818

File received successfully, length 4514620.

File contains:

Unit Description: FCM9003

Software Version: 9.0.[mh].1.421 12/08/2015 10:14:24 unreleased

This will replace:

Unit Description: FCM9003


The software will now be updated.

Are you sure this is what you want to do?

If this is correct, confirm <Y>, otherwise type <N> to stop the download. If the download is stopped, the system must be restarted.

Once the firmware upgrade has completed, the unit will automatically restart with the new firmware image and reload the configuration from EEPROM.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.7.1.2.1 Failsafe Upgrade

The system software upgrade procedure uses a failsafe mechanism to prevent a system becoming unusable. When a unit is shipped from the factory, the base version of the application is stored in a locked portion of the flash memory. When a new version is loaded via TFTP it will be programmed into flash as a second image and once verified will also then be copied and programmed into the backup image. When the system reboots, the boot software compares the loaded versions of firmware and executes the most up to date version.

4.2.7.1.3 Boot Software Upgrade

Menu Tree: Main Set-Up / Management Entity / tFtp / Boot s/w upgrade

There may be occasions when new features added to the main application code cannot be supported without changes to the boot loader code. The Boot S/W upgrade facility enables the boot software to be upgraded, and also installs a new base application.

Selecting the Boot Upgrade option will lead to the prompt:

Metrodata FCM9004 "FCM9004_left" Alarms: Major

TFTP Boot Software Upgrade

CAUTION: Proceding further will mean that the unit must be re-started,

and the performance log may be cleared, even if the upgrade is

unsuccessful.

Are you sure you wish to continue? y

File name: FCM9004b.821

Blocks received: 5268

File received successfully, length 2697124.

File contains:

Unit Description: fcm9004


This will replace:

Unit Description: fcm9004


The software will now be updated.

Are you sure this is what you want to do?

Confirming Y at the prompt, and the system will reprogram the flash and then restart with the new boot and application code.

Note, Please ensure that the unit is not powered down during the boot programming process as this may corrupt the boot software and prevent the system from operating.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.7.1.4 Get Config

Menu Tree: Main Set-Up / Management Entity / tFtp / get Config

To load a configuration file that has been saved on the TFTP server use the Get Config command. Enter the file name for the configuration file and it will then be loaded, validated and stored in EEPROM. The system will then be rebooted with the new configuration.

4.2.7.1.5 Put Config

Menu Tree: Main Set-Up / Management Entity / tFtp / Put config

To save the running configuration use the Put Config command to load the file onto the tftp server. Enter the filename and perform the transfer.

4.2.7.1.6 Put Report

Menu Tree: Main Set-Up / Management Entity / tFtp / put Report

When the SAM 1564 service activation test has been performed, a birth certificate report is produced. The put report command will automatically store this report to the current TFTP server.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.7.2 Server Mode

Menu Tree: Main Set-Up / Management Entity / tFtp / Mode

The FCM9003 can also be operated in TFTP server mode by setting Mode to server, as shown:


TFTP

Mode Server

remote IP 192.168.0.100

Software file name software

Config. file name config



4.2.7.2.1 Remote IP

Menu Tree: Main Set-Up / Management Entity / tFtp / remote IP

The IP address is that of the remote client which will perform the transfer. In the event that the client sits behind a NAT enabled firewall, the external IP address is the one that must be configured.

4.2.7.2.2 Software File Name

Menu Tree: Main Set-Up / Management Entity / tFtp / Software file name

This is the filename of a file that if downloaded, will be assumed to be a new software load.

When this file is downloaded, the unit will verify the transfer and then program the new firmware. Once upgraded the unit will restart automatically.

From a windows pc, the tftp transfer command would be as below

tftp –i device_ip_address put application_filename device_filename

4.2.7.2.3 Config File Name

Menu Tree: Main Set-Up / Management Entity / tFtp / Config file name

This is the filename that will be uploaded/downloaded from the FCM9003 as a configuration file. When a new configuration file is PUT onto the device, once loaded the unit will automatically restart.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.2.8 TWAMP

Menu Tree: Main Set-Up / Management Entity / tWamp

TWAMP, Two Way Active Measurement Protocol is a performance monitoring tool that allows for accurate ( sub uS ) measurement of round trip delay and variation over an IP network. The FCM9003 includes hardware based timestamping to accurately timestamp ingress/egress packets. TWAMP is a UDP protocol running over IP.

This menu defines the UDP port which the FCM9003 will listen for TWAMP messages when operating as a reflector, and as the transmit port number for send messages.

The default setting is UDP Port 900

It is necessary that the UDP port number matches at the sender and reflector units.

4.2.9 Ping

Menu Tree: Main Set-Up / Management Entity / Ping

To provide connectivity checking capability the FCM9003 can generate ICMP ping requests to a configured IP address.

Once the ping is running, the display is as below:


Destination: 192.168.0.100

press any key to stop test

sending...okay, time=3.4ms








FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.3 V.24 Set-up

Menu Tree: Main Set-Up / V.24 set-up

The default setting for the V24 terminal port is

19200, 8bit, No Parity, 2 Stop Bits

The V.24 menu configures the terminal port for local access to the FCM9003.


V.24 SET-UP

Usage Console

Console set-up <menu>



4.3.1 Usage Menu Tree: Main Set-Up / V.24 set-up / Usage

To provide security for the unit the local terminal interface may be disabled to prevent access.

Usage Console The external console port is active

Usage Disabled The external console port is disabled

4.3.2 Console set-up

Menu Tree: Main Set-Up / V.24 set-up / Console set-up

The console setup menu defines the parameters for the serial port and also for the display mode.

Note, that when Zero Touch mode is enabled, the console port will be disabled from power up.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.3.2.1 Terminal Type

Menu Tree: Main Set-Up / V.24 set-up / Console set-up / Terminal type

To give maximum flexibility and interoperability with most terminals / terminal emulator programs the display may take the following modes:

TTY Simple scrolling menu system

VT100/VT220 Cursor controlled menu system

ANSI Cursor controlled, and highlighted menu system.

4.3.2.2 Via Modem

Menu Tree: Main Set-Up / V.24 set-up / Console set-up / via Modem

When the FCM9003 is connected via a dial up modem, the unit may be configured to close the management session when the modem drops DTR.

No Terminal ignores the state of DTR

Yes Management Session closed when DTR negated.

4.3.2.3 Baud Rate

Menu Tree: Main Set-Up / V.24 set-up / Console set-up / Baud rate

The default terminal baud rate is 19200 baud. It is possible to configure the terminal to support alternate rates including:

19200

2400

4800

9600

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.3.2.4 Parity

Menu Tree: Main Set-Up / V.24 set-up / Console set-up / Parity

The parity defaults to NONE, however options include

NONE

EVEN

ODD

4.3.2.5 Data Bits

Menu Tree: Main Set-Up / V.24 set-up / Console set-up / Data bits

The terminal port defaults to 8 bit characters. The options are

7

8

4.3.2.6 Stop Bits

Menu Tree: Main Set-Up / V.24 set-up / Console set-up / Stop bits

The terminal defaults to 2 stop bits, the options are

1

2

4.3.2.7 Load New Config

Menu Tree: Main Set-Up / V.24 set-up / Console set-up / Load new config

Once all the terminal communications parameters have been configured, the Load New Command will perform the configuiration changes at which point the actual terminal must be changed.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4 Port Set Up Menu

Menu Tree: Main Set-Up / Port set-up

The data port menu is where all configuration relating to the physical ports and the traffic flow parameters are configured. The top level data port menu is shown below:


PORT SET-UP

lan1 <menu>

lan2 <menu>

lan3 <menu>

lan4 <menu>

SFP <menu>

WAN <menu>



The menu is divided into several sections. LAN1 through LAN4 and the SFP refer to the physical user ports on the rear of the unit. The WAN port configures the network port.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1 User LAN Port Configuration

Menu Tree: Main Set-Up / Port set-up / (1-4)

The LAN port configuration defines the physical operating parameters for the four 10/100/1000BaseT ports on the rear of the unit.

The LAN port menu is as shown below:


LAN1

interface Name LAN1

State Up

link status Up

pOrt Management <menu>

negotiated 1000M/FD

laYer 2 Management <menu>

linK Loss Fwding Disabled

sUppress All Alarms No

Rate Limiting <menu>

Counters <display>



4.4.1.1 Interface Name

Menu Tree: Main Set-Up / Port set-up / (1-4) / interface Name

The interface name is used to define the SNMP OID IfAlias for the IF-MIB, IfXTable display item.

This name should be used to label the port to assist with circuit identification.

4.4.1.2 State

Menu Tree: Main Set-Up / Port set-up / (1-4) / State

The LAN Port State configuration item defines the administrative state of the port. The port states may be:

UP Port enabled, normal operation

DOWN Port disabled, alarm handling disabled

It is best practice to set ports to the DOWN state when they are not being used and have no flows defined, as they will then not generate link down traps or show in the alarmed state.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.3 Link Status

Menu Tree: Main Set-Up / Port set-up / (1-4) / link status

The Link Status displays the operational state of the LAN port.

4.4.1.4 Port Management

Menu Tree: Main Set-Up / Port set-up / (1-4) / pOrt Management

The port management menu allows the physical operating parameters to be defined for the LAN port. The Port Management menu is shown below:


PORT MANAGEMENT

caBle Tester <display>

max spEed 1000M

max Duplex Full

Auto-negotiation Enabled

negotiated ---

MDI/MDIX Auto



4.4.1.4.1 Cable Tester

Menu Tree: Main Set-Up / Port set-up / (1-4) / pOrt Management / caBle Tester

The cable test menu enables a TDR check of the cabling attached to this port. When two 1000BaseT interfaces are correctly connected the test results are as shown below:


Cable Tester LAN1

------------

Pair Result Distance (m)

-----------------------------------

0 ok

1 ok

2 ok

3 ok

<Esc> - exit, T - Test

Where problems are detected by the TDR, distance to the fault, and the affected pair will be displayed.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.4.2 (max) Speed

Menu Tree: Main Set-Up / Port set-up / (1-4) / pOrt Management / spEed

The Speed parameter has two meanings depending upon whether auto negotiation is enabled or not.

When Auto Negotiation is disabled, the Speed setting sets the operating speed of the port with valid options of:

10M 10 Base T

100M 100 Base T Fast Ethernet

1000M 1000 Base T Gigabit Ethernet

when Auto Negotiation is enabled, the speed setting defines the maximum speed advertised to the link partner and the menu item changes to max speed. The options are as below:

10M Advertise 10M

100M Advertise 10M, 100M

1000M Advertise 10M, 100M, 1000M

4.4.1.4.3 Duplex

Menu Tree: Main Set-Up / Port set-up / (1-4) / pOrt Management / Duplex

The Duplex parameter has two meanings depending upon whether auto negotiation is enabled or not.

When Auto Negotiation is disabled, the Duplex setting sets the operating mode of the port with valid options of:

Half Half Duplex

Full Full Duplex

When Auto Negotiation is enabled, the duplex setting defines the maximum mode advertised to the link partner and the option changes to max duplex. The options are as below:

Half Advertise Half Duplex

Full Advertise Half Duplex, Full Duplex

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.4.4 Auto Negotiation

Menu Tree: Main Set-Up / Port set-up / (1-4) / pOrt Management / Auto-negotiation

Auto Negotiation allows the port to automatically determine the best operating parameters for the port. If both link partners support auto negotiation then they will select the best mode that is supported by both devices.

If one link partner does not support auto negotiation, an auto negotiating link partner will be able to determine the link speed, however it will be unable to determine the duplex mode so will default to the half duplex state.

An auto port connected to a non auto port is a very common fault on networks leading to errors on the line when significant traffic is flowing, but appearing to operate normally when diagnostics like ping are used to test the link.

4.4.1.4.5 Negotiated

Menu Tree: Main Set-Up / Port set-up / (1-4) / pOrt Management / negotiated

When auto negotiation is enabled, the negotiated display item shows the operating mode that has be negotiated between the link partners.

10M/HD 10 Base T / Half Duplex

10M/FD 10 Base T / Full Duplex





FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.5 MDI / MDIX

Menu Tree: Main Set-Up / Port set-up / (1-4) / pOrt Management / MDI/MDIX

There are two possible pin outs for the RJ45 physical ports, one is defined as MDI and is typically found on data sources such as PC’s or Laptops. The other is defined as MDIX, or MDI Crossover is typically found on switches. In order to use a straight through patch cable, an MDI port must connect to an MDI-X port otherwise crossover cables are required.

The FCM9003 LAN ports support auto switching technology whereby the port will automatically detect whether it should be MDI or MDIX and will configure itself accordingly. With auto switching ports, only straight patch cables are required.

The options are:

AUTO Auto switching enabled

MDI Port fixed in MDI configuration

MDIX Port fixed in MDIX configuration

4.4.1.6 Negotiated

Menu Tree: Main Set-Up / Port set-up / (1-4) / negotiated








FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7 Layer 2 Management

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management

The layer 2 management menu defines the layer 2 elements of port operation such a tag push/pop and L2CP management.

The Layer 2 Management menu is shown below:


L2 MANAGEMENT, LAN1

Tagging & Priority <menu>

L2CP Management <menu>

OAM <menu>



4.4.1.7.1 Tagging and Priority

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / Tagging and Priority

The tagging and priority menu selects the actions to be taken with untagged frames.


TAGGING & PRIORITY, LAN1

Add C-Tag to Untagged

c-tag VID 4095

Priority Source C-Tag, Default

Default Priority 0



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.1.1 Add C-Tag to

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / Tagging and Priority / Add C-Tag to

This menu item defines the tagging action to take when a frame arrives at the port. The possible actions are

None Pass frame unchanged

Untagged Add the default tag as defined to untagged frames only, pass tagged frames unchanged

All Add default tag to all frames received whether tagged or untagged

Note, that the default tag ID value must be within the range of ID’s allocated in flows assigned to this port, otherwise it will be discarded.

Note, in S-Tag mode this option is fixed at NONE since an S-Tag rather than C-Tag will be pushed as defined in the flow configuration.

Note, the C-Tag VID must be defined before the c-tag action can be changed.

4.4.1.7.1.2 C-Tag VID

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / Tagging and Priority / c-tag VID

This menu item defines the default VLAN ID to add to frames ingressing this port when the action is set to Add Default Tag.

The available values are in the range 1 to 4095

Note, the VID value is shown in brackets when it is configured but the action is not to push the tag and the Add C-Tag to item is set to None. The VID must be defined before the action may be changed.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.1.3 Priority Source

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / Tagging and Priority / Priority Source

The priority source selects the priority for the pushed TAG. The options are

Default Use the default setting for the port

C-Tag,Default Inherit the priority from the incoming c-tag if present, otherwise use the default value.

DSCP,Default Inherit the priority from the incoming DSCP marker if present, otherwise use the default.

C-Tag, DSCP, Default Inherit the priority from C-Tag if tagged, otherwise DSCP if present or use the default.

4.4.1.7.1.4 Default Priority

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / Tagging and Priority / Default Priority

This menu item sets the value to be used as the p-tag value within the pushed VLAN Tag.

Available values are 0 to 7

Note, if the source is set to default, then all frames passing through this port will have their PCP overwritten with the default priority PCP setting.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.2 L2CP Management

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management

L2CP, Layer 2 Control Protocols are interactions between nodes on the same network segment, and as such are generally blocked by switches or bridges. The purpose of L2CP management is to enable these link layer protocols to be “tunneled” across the wide area network and regenerated at the remote location.

There are a number of layer 2 protocols and the FCM9003 offers individual controls for each with the following options:

Discard Discard the Layer 2 Control Protocol on ingress to the FCM9003.

Tunnel Receive the L2CP packet, encapsulate and then transfer to the remote end of the link where it can be recovered and transmitted.

Peer Protocols that the FCM9003 supports may be peered, ie terminate and generate responses.

L2CP is a proprietary protocol and works by replacing the standard multicast address which may be blocked or peered by intermediate equipment with the Metrodata Multicast address 01:C0:81:00:01:02 which will not be blocked and will be received by an associated FCM9003 unit which will then regenerate the original L2CP packet.

The L2CP Management Menu is as below:


L2CP MANAGEMENT, LAN1

Bridge Group <menu>

GARP Group <menu>

Cisco <menu>

Metrodata <menu>

Other <menu>

L2CP Flow None



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.2.1 Bridge Group

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / Bridge Group

The bridge group of protocols use the generic multicast destination address range:

01:80:C2:00:00:00 to 01:80:C2:00:00:0F

Within this range the following protocols are handled by the L2CP management process:

4.4.1.7.2.1.1 OAM

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / Bridge Group / 1

The IEEE 802.3 clause 57 (ah) OAM packets are part of the generic slow protocols group.

Address 01:80:C2:00:00:02

Etype 8809 Slow Protocols

Subtype 3 – OAM

The FCM9003 offers options to Discard, Tunnel or Peer with OAM layer 2 control packets.

4.4.1.7.2.1.2 STP/RSTP/MSTP


The STP/RSTP/MSTP BPDU’s use the following addresses

Address 01:80:C2:00:00:00

The FCM9003 offers options to Discard or Tunnel BPDU frames.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.2.1.3 LACP / LACP Marker

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / Bridge Group / 4-5

LACP, Link Aggregation Control Protocol packets are part of the generic slow protocols group:

Address 01:80:C2:00:00:02

Etype 8809

Subtype 01 – LACP

Subtype 02 – LACP Marker

The FCM9003 offers options to Discard or Tunnel LACP frames

4.4.1.7.2.1.4 MD Proxy


The Metrodata proxy management uses OSSP, Organisational Specific Slow Protocols which are part of the generic slow protocols group:

Address 01:80:C2:00:00:02

Etype 8809

Subtype 10 – OSSP

The FCM9003 offers options to Discard or Tunnel OSSP frames.

4.4.1.7.2.1.5 LLDP


LLDP, Link Layer Discovery Protocol uses the following

Address 01:80:C2:00:00:0E

Etype 88CC - LLDP

The FCM9003 offers the option of Discard or Tunnel for LLDP frames.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.2.1.6 Other Bridge


The Other Bridge protocols cover those protocols using multicast addresses in the range 01:80:C2:00:00:0x not specifically mentioned above as well as unrecognized protocols on those addresses already covered.

4.4.1.7.2.2 GARP Group

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / GARP Group

The GARP, Generic Attribute Registration Protocols group uses the range of multicast addresses

01:80:C2:00:00:20 to 01:80:C2:00:00:2F

Within this group there are some well know protocols which are dealt with individually.

4.4.1.7.2.2.1 GMRP

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / GARP Group / 1

GMRP, GARP Multicast Registration Protocol uses the following

Address 01:80:C0:00:00:20

The FCM9003 provides options to Discard or Tunnel GMRP frames.

4.4.1.7.2.2.2 GVRP


GVRP, GARP VLAN Registration Protocol uses the following

Address 01:80:C2:00:00:21

The FCM9003 provides options to Discard or Tunnel GVRP frames

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.2.2.3 Other GARP


The other Garp options allows for tunneling of packets with multicast addresses in the range 01:80:C2:00:00:22 to 01:80:C2:00:00:CF.

The FCM9003 provides options to Discard or Tunnel these frames.

4.4.1.7.2.3 Cisco Group

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / Cisco

The Cisco Group of Layer 2 protocols may be enabled for tunneling or for discard and the protocols supported are:

CDP Cisco Discovery Protocol 01:00:0C:CC:CC:CC 2000

VTP VLAN Trunk Protocol 01:00:0C:CC:CC:CC 2003

DTP Dynamic Trunking Protocol 01:00:0C:CC:CC:CC 2004

PAgP Port Aggregation Protocol 01:00:0C:CC:CC:CC 0104

UDLD Unidirectional Link Detection 01:00:0C:CC:CC:CC 0111

PVSTP Per VLAN Spanning Tree 01:00:0C:CC:CC:CD 010B

UplinkFast 01:00:0C:CD:CD:CD 200A

L2PT, Layer 2 Protocol Tunnel 01:00:0C:CD:CD:D0

Other Cisco 01:00:0C:xx:xx:xx

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.2.4 Metrodata Group

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / Metrodata

The Metrodata group of layer 2 protocols include the following to enable book ending of devices.

4.4.1.7.2.4.1 Beacon

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / Metrodata / 1

The Metrodata Beacon protocol may be discarded, tunneled or peered.

Address 01:C0:81:00:01:01

Etype 88B7

OUI 00C081

4.4.1.7.2.4.2 L2CP Tunnel


The Metrodata L2CP tunnel protocol may be discarded or Tunnelled

Address 01:C0:81:00:01:02

EType 88B7

OUI 00C081

4.4.1.7.2.4.3 Other Metrodata


This option will allow for discard or tunnel action for the following range of Mutlicast addresses

01:C0:81:00:01:03 to 01:C0:81:00:01:0F

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.2.5 Other Group

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / Other

The other group provides tunnel control for customer CFM packets. There is the option to discard, peer or tunnel CFM received on the user ports.

When user CFM is tunneled it is tunneled to the far end and therefore there is no requirement to use specific domains or associations and be compatible with the underlying core network.

CFM peering relies on the customer using a domain level which is higher than the underlying network.

If CFM tunnelling is used, one way delay measurement using multicast CCM messages will be delayed significantly, Y.1731 DMM/DMR and LMM/LMR will not be affected as they are unicast.

4.4.1.7.2.6 L2CP Flow

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / L2CP Management / L2CP Flow

In order to tunnel the L2CP frames to the remote end they must be allocated to a flow that has previously been configured. Only 1 flow may be allocated and it must be allocated to the particular user port.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.3 OAM

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / OAM

The LAN ports support IEEE802.3 Clause 57 ( 802.3ah ) link OAM for peering or tunneling with L2CP.

The OAM menu is as below:


OAM, LAN1

Mode Active

Status <display>

counTers <display>

Events <display>



4.4.1.7.3.1 OAM Mode

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / OAM / Mode

The operating mode of the OAM on this port may be defined here. The valid operating states are:

Disabled Do not generate or respond to OAM packets and discard all OAM packets received.

Tunnel Do not generate or respond to OAM packets, simply tunnel all OAM packets received using L2CP

Active Generate and Respond to OAM packets

Passive Respond to OAM packets

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.3.2 OAM Status

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / OAM / Status

The OAM Status display shows the current state of OAM on this link as shown below:


OAM STATUS

----------

| Local | Local | Peer | Peer | Peer | Peer

| Status | Support | Mode | MAC address | VendorInfo | Support

------+----------+---------+------+-------------+------------+--------

LAN1 ActiveLoc L

Remote Status

-------------

Not available


4.4.1.7.3.3 OAM Statistics

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / OAM / counTers

The OAM statistics show the counts for the various OAM packet types as shown:


OAM Statistics

--------------

Rx Tx

Unsupported Codes 0 0

Information 0 755

Unique Event 0 0

Duplicate Event 0 0

Variable Request 0 0

Variable Response 0 0

Loopback Control 0 0

Organisation Specific 0 0

<Escape> - exit, C - clear, other key – refresh

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.7.3.4 OAM Events

Menu Tree: Main Set-Up / Port set-up / (1-4) / laYer 2 Management / OAM / Events

This display lists OAM events that have occurred since the unit was powered up.

4.4.1.8 Link Loss Forwarding

Menu Tree: Main Set-Up / Port set-up / (1-4) / linK Loss Fwding

Link Loss Forwarding enables the port state to reflect the status of the full end to end link status rather than simply the cabled connection between local link partners.

When a port enters the Link Loss Forwarding alarm state, the port will be forced to the Link Down state such that the attached equipment will see there is a problem with this network connection allowing for protocols such as RSTP or LACP to remove this link from their network map and enable link restoration by alternative backup links if available.

The Link Loss may be forwarded from:

WAN If the WAN port is down then force the User Port to the Down state.

Flow The end to end flow state is determined using the CFM Connectivity messages and if these messages are not being received, the link will be forced down.

4.4.1.9 Suppress All Alarms

Menu Tree: Main Set-Up / Port set-up / (1-4) / sUppress All Alarms

This option disables all alarms from being reported for this port. This option is only intended for use where the Aux port is left open for an engineer connection but is normally disconnected. Without suppression LAN port 4 would be reporting the LKDN alarm, however this can be suppressed to cause the unit to appear to be operating normally.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.10 Rate Limiting

Menu Tree: Main Set-Up / Port set-up / (1-4) / Rate Limiting

The rate limiting menu provides a simple single leaky bucket policing function to the traffic ingressing this port. The rate limit may be applied to the entire port, or to the individual priority queues. Additionally, broadcast storm prevention is controlled by this menu.


RATE LIMITING, LAN1

mOde Priority

bRoadcast <menu>

High <menu>

Medium <menu>

Low <menu>

Best-Effort <menu>



4.4.1.10.1 Mode

Menu Tree: Main Set-Up / Port set-up / (1-4) / Rate Limiting / mOde

The rate limiting mode may be set to either

Priority Separate Rate limiting for each priority queue and broadcast frames

Port Rate limit the port

4.4.1.10.2 Broadcast

Menu Tree: Main Set-Up / Port set-up / (1-4) / Rate Limiting / bRoadcast

The broadcast rate limit menu is shown below:


RATE LIMITING, LAN1, BROADCAST

Limiting Enabled

CIR 1M

cBS 0



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

The broadcast rate limiter is used to prevent broadcast storms affecting the operation of the network. Broadcast frames, regardless of VLAN, will be limited by this policer.

4.4.1.10.2.1 Limiting

Menu Tree: Main Set-Up / Port set-up / (1-4) / Rate Limiting / bRoadcast / Limiting

The broadcast rate limiter is enabled/disabled with this menu item. When disabled, broadcast frames are not limited. When enabled, broadcast frames are limited to the configured CIR and CBS settings

4.4.1.10.2.2 CIR

Menu Tree: Main Set-Up / Port set-up / (1-4) / Rate Limiting / bRoadcast / CIR

When the broadcast rate limiter is enabled, broadcast frames will be limited to the configured CIR. The CIR is defined according to the bandwidth mode setting

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / Bandwidth

And may be expressed in terms of

Utilisation Frame + Preamble + IPG

L1 Frame + Preamble

Information Rate Frame

4.4.1.10.2.3 CBS

Menu Tree: Main Set-Up / Port set-up / (1-4) / Rate Limiting / bRoadcast / cBS

When the broadcast rate limiter is enabled, broadcast frames will be limited to burst sizes not exceedinig the CBS setting.

4.4.1.10.3 Priority Queue Settings

The four priority queues, High, Medium, Low and Best Effort can be idividually rate limited on port ingress. Each limiter may be enabled, and then have a CIR and CBS defined.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.1.11 Counters

Menu Tree: Main Set-Up / Port set-up / (1-4) / Counters

The Counters menu shows the RFC-1213 MIB-2 statistics collected for the LAN port as shown below:


Interface Statistics

--------------------

ifInOctets 0 Tunnel In Packets 0

ifInUcastPkts 0 Tunnel In Errors 0

ifInNUcastPkts 0 Tunnel Out Packets 0

ifInDiscards 0 Tunnel Out Errors 0

ifInErrors 0

ifInUnknownProtos 0 OAM In Packets 0

ifOutOctets 0 OAM Out Packets 1308

ifOutUcastPkts 0 OAM Out Discards 0

ifOutNUcastPkts 0

ifOutDiscards 0

ifOutErrors 0

<Esc> - exit, C - clear, <Enter> - refresh

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.2 User SFP Port Configuration

Menu Tree: Main Set-Up / Port set-up / SFP

The SFP port configuration defines the physical operating parameters for the user SFP port on the rear of the unit.

The SFP port menu is as shown below:


SFP

interface Name SFP

State Up

link status Up

sfp type 1000BASE-SX

max spEed 1000M


negotiated 1000M/FD

sFP Management <menu>


linK Loss Fwding Disabled


Rate Limiting <menu>

Counters <display>




Menu Tree: Main Set-Up / Port set-up / Sfp / interface Name



4.4.2.2 State

Menu Tree: Main Set-Up / Port set-up / SFP / State

The SFP Port State configuration item defines the administrative state of the port. The port states may be:



It is best practice to set the SFP port to the DOWN state when it is not fitted, not being used or has no flows defined, as it will then not generate link down traps or show in the alarmed state.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.2.3 Link Status

Menu Tree: Main Set-Up / Port set-up / SFP / link status

The Link Status displays the operational state of the SFP port.

4.4.2.4 SFP Type

Menu Tree: Main Set-Up / Port set-up / SFP / sfp type

The SFP type is read from the SFP module and displays the type of module used.

Note, some cheaper SFP modules are not correctly programmed and in this case the type will be displayed as UNKNOWN.

4.4.2.5 Speed

Menu Tree: Main Set-Up / Port set-up / SFP / (max) spEed

The Speed setting sets the operating speed of the port with valid options of:

100M 100 Base FX Fast Ethernet

1000M 1000 Base X Gigabit Ethernet

Auto In the auto mode, the SFP module is read and the port parameters are set according to the SFP type installed. If a 1000BaseX SFP is installed the port will operate at 1000M, whilst if a 100BaseFX or OC3 SFP is installed, the port will operate at 100M.

4.4.2.6 Duplex

Menu Tree: Main Set-Up / Port set-up / SFP / (max) Duplex

The Duplex parameter is valid for 100M operation only, 1000M ports must operate in full duplex modes.

Half Half Duplex

Full Full Duplex

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.2.7 Auto Negotiation

Menu Tree: Main Set-Up / Port set-up / SFP / Auto-negotiation


1000M operation requires Auto Negotiation is enabled, whilst 100M operation does not support auto negotiation.

4.4.2.8 Negotiated

Menu Tree: Main Set-Up / Port set-up / SFP / negotiated



Note, only 1000M operation supports auto negotiation, and only full duplex operation is supported.

4.4.2.9 SFP Management

Menu Tree: Main Set-Up / Port set-up / SFP / sFP Management

The FCM9004 supports reporting of the SFP device type and diagnostic information. The FCM9004 may also be configured to generate alarms and traps when the diagnostic readings exceed the alarm or warning thresholds.

The SFP Management menu is shown below:

Metrodata FCM9003 "FCM9003" Alarms: none

SFP MANAGEMENT

Device Details <display>

Notifications <menu>



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.2.9.1 Device Details

Menu Tree: Main Set-Up / Port set-up / SFP / sFP Management / Device Details

SFP modules include an EEPROM to identify the module capabilities and these may be read using the SFP device details option. The information display is as shown below:


SFP Info Interface: SFP

--------

Transmit

Status Type Vendor Part No. Wavelength

--------------------------------------------------------------------------

Good 1000BASE-SX HG GENUINE MXPD-248S-F 850nm

Diagnostics

-----------

Tx-Pwr Rx-Pwr Bias Temp Supply

(dBm) (dBm) (mA) (C) (V)

-------------------------------------------

Alrm Hi -1 0 20 85 3.60

Warn Hi -3 -2 15 80 3.50

Warn Lo -10 -15 1 0 3.10

Alrm Lo -12 -17 1 -5 3.00

Value -6 -28 3 25 3.28

Status OK ALARM OK OK OK


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.2.9.2 Notifications

Menu Tree: Main Set-Up / Port set-up / SFP / sFP Management / Notifications

The SFP notifications menu configures the actions for alarm and trap generation when the disagnostic values exceed the alarm or warning threshold values.


NOTIFICATIONS

1 - Temp High Alarm & Warning

2 - Temp Low None

3 - Supply High None

4 - Supply Low None

5 - Bias High None

6 - Bias Low None

7 - Tx Power High None

8 - Tx Power Low None

9 - Rx Power High None

A - Rx Power Low Alarm & Warning

B - SFP Removed None

C - OTDR Fault None



Each diagnostic value may be configured for either:

None No Action

Alarm Generate an Alarm/Trap when the alarm threshold is exceeded.

Alarm & Warning Generate an Alarm/Trap when either the Alarm or Warning thresholds are exceeded.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216


Menu Tree: Main Set-Up / Port set-up / SFP / laYer 2 Management

The layer 2 management menu allows the configuration of the layer 2 functionality for the SFP port. The menu is as shown below:


L2 MANAGEMENT, SFP

Tagging & Priority <menu>

L2CP Management <menu>

OAM <menu>




Menu Tree: Main Set-Up / Port set-up / SFP / laYer 2 Management / Tagging & Priority

For an explanation of the tagging and priority menu please refer to section 4.4.1.7.1

4.4.2.11 L2CP Management

Menu Tree: Main Set-Up / Port set-up / SFP / laYer 2 Management / L2CP Management

For an explanation of the L2CP configuration, please refer to section 4.4.1.7.24.4.1.7.2 of the User LAN port configuration menu.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.2.12 OAM

Menu Tree: Main Set-Up / Port set-up / SFP / OAM

For an explanation of the OAM configuration, please refer to section 4.4.1.7.3 of the User LAN port configuration menu.

4.4.2.13 Link Loss Forwarding

Menu Tree: Main Set-Up / Port set-up / SFP / linK Loss Fwding

Link Loss Forwarding enables the port state to reflect the status of the full end to end link status rather than simply the cabled connection between local link partners.

When a port enters the Link Loss Forwarding alarm state, the port will be forced to the Link Down state such that the attached equipment will see there is a problem with this network connection allowing for protocols such as RSTP or LACP to remove this link from their network map and enable link restoration by alternative backup links if available.

The Link Loss may be forwarded from:

WAN If the WAN port is down then force the User Port to the Down state.

Flow The end to end flow state is determined using the CFM Connectivity messages and if these messages are not being received, the link will be forced down.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.2.14 Counters

Menu Tree: Main Set-Up / Port set-up / SFP / Counters




--------------------





ifInErrors 0




ifOutNUcastPkts 0

ifOutDiscards 0

ifOutErrors 0


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3 WAN Port

Menu Tree: Main Set-Up / Port set-up / WAN

The FCM9003 WAN port supports either Copper ( 10/100/1000BaseT ) or Fibre ( 1000Base-X, 100Base-FX ) connectivity. The WAN menus are as shown below for the two modes:

WAN Copper Interface menu:


WAN

interface Name WAN

State Up

link status Down

Interface Copper

pOrt Management <menu>

negotiated ---



Rate Shaping <menu>

Counters <display>



WAN Fibre/SFP Interface menu:


WAN

Interface Name WAN

State Up

link status Down

Interface SFP

sfp type 1000BASE-LX

max spEed 1000M


negotiated ---

sFP Management <menu>

laYer 2 management <menu>


Rate Shaping <menu>

Counters <display>



FCM9003 USER MANUAL

76-02-100 Rev.A of 216


Menu Tree: Main Set-Up / Port set-up / Wan / interface Name



4.4.3.2 State

Menu Tree: Main Set-Up / Port set-up / WAN / State

The WAN Port State configuration item defines the administrative state of the port. The port states may be:



For normal operation, the WAN port must be in the UP state.

4.4.3.3 Link Status

Menu Tree: Main Set-Up / Port set-up / WAN / link status

The Link Status displays the operational state of the WAN port.

4.4.3.4 Interface

Menu Tree: Main Set-Up / Port set-up / WAN / Interface

The FCM9003 WAN interface supports both copper and fibre options. The interface is selected with this item, the options are

Copper 10/100/1000BaseT Interface Enabled

SFP 100BaseFX, 1000Base-X Interface Enabled

Depending on the interface selection, some of the following menu items have different functions.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.5 Port Management ( Copper Only )

Menu Tree: Main Set-Up / Port set-up / WAN / pOrt Management

The port management menu is used to configure the physical parameters for the interface.

The port management menu is shown below:


PORT MANAGEMENT

caBle Tester <display>

max spEed 1000M

max Duplex Full


negotiated ---

MDI/MDIX Auto



4.4.3.5.1 Cable Tester

Menu Tree: Main Set-Up / Port set-up / WAN / pOrt Management / caBle Tester

The cable test menu enables a TDR check of the cabling attached to this port. When two 1000BaseT interfaces are correctly connected the test results are as shown below:


Cable Tester WAN

------------

Pair Result Distance (m)

-----------------------------------

0 ok

1 ok

2 ok

3 ok

<Esc> - exit, T - Test

Where problems are detected by the TDR, distance to the fault, and the affected pair will be displayed.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.5.3 (max) Speed

Menu Tree: Main Set-Up / Port set-up / WAN / pOrt Management / (max) spEed

The Speed parameter has two meanings depending upon whether auto negotiation is enabled or not.

When Auto Negotiation is disabled, the Speed setting sets the operating speed of the port with valid options of:

10M 10 Base T

100M 100 Base T Fast Ethernet

1000M 1000 Base T Gigabit Ethernet

when Auto Negotiation is enabled, the speed setting defines the maximum speed advertised to the link partner. The options are as below:

10M Advertise 10M

100M Advertise 10M, 100M

1000M Advertise 10M, 100M, 1000M

4.4.3.5.4 Duplex

Menu Tree: Main Set-Up / Port set-up / WAN / pOrt Management / (max) Duplex

The Duplex parameter has two meanings depending upon whether auto negotiation is enabled or not.

When Auto Negotiation is disabled, the Duplex setting sets the operating mode of the port with valid options of:

Half Half Duplex

Full Full Duplex

When Auto Negotiation is enabled, the duplex setting defines the maximum mode advertised to the link partner. The options are as below:

Half Advertise Half Duplex

Full Advertise Half Duplex, Full Duplex

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.5.5 Auto Negotiation

Menu Tree: Main Set-Up / Port set-up / WAN / pOrt Management / Auto-negotiation


If one link partner does not support auto negotiation, an auto negotiating link partner will be able to determine the link speed, however it will be unable to determine the duplex mode so will default to the half duplex state.

An auto port connected to a non auto port is a very common fault on networks leading to errors on the line when significant traffic is flowing, but appearing to operate normally when diagnostics like ping are used to test the link.

4.4.3.6 Negotiated

Menu Tree: Main Set-Up / Port set-up / WAN / pOrt Management / negotiated






100M/FD 100 Base FX / Full Duplex



1000M/FD 1000Base-X / Full DUplex

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.7 MDI / MDIX

Menu Tree: Main Set-Up / Port set-up / WAN / pOrt Management / MDI/MDIX

There are two possible pin outs for the RJ45 physical ports, one is defined as MDI and is typically found on data sources such as PC’s or Laptops. The other is defined as MDIX, or MDI Crossover is typically found on switches. In order to use a straight through patch cable, an MDI port must connect to an MDI-X port otherwise crossover cables are required.

The FCM9003 LAN ports support auto switching technology whereby the port will automatically detect whether it should be MDI or MDIX and will configure itself accordingly. With auto switching ports, only straight patch cables are required.

The options are:

AUTO Auto switching enabled

MDI Port fixed in MDI configuration

MDIX Port fixed in MDIX configuration

4.4.3.8 SFP Type

Menu Tree: Main Set-Up / Port set-up / WAN / sfp type

The SFP type is read from the SFP module and displays the type of module used.

Note, some cheaper SFP modules are not correctly programmed and in this case the type will be displayed as UNKNOWN.

4.4.3.9 Max Speed ( SFP Mode )

Menu Tree: Main Set-Up / Port set-up / WAN / (max) spEed

The Speed setting sets the operating speed of the port with valid options of:

100M 100 Base FX Fast Ethernet

1000M 1000 Base X Gigabit Ethernet

Auto In the auto mode, the SFP module is read and the port parameters are set according to the SFP type installed. If a 1000BaseX SFP is installed the port will operate at 1000M, whilst if a 100BaseFX or OC3 SFP is installed, the port will operate at 100M.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.10 Max Duplex (SFP Mode )

Menu Tree: Main Set-Up / Port set-up / WAN / (max) Duplex

The Duplex parameter is valid for 100M operation only, 1000M ports must operate in full duplex modes.

Half Half Duplex

Full Full Duplex

4.4.3.11 Auto Negotiation (SFP Mode )

Menu Tree: Main Set-Up / Port set-up / WAN / Auto-negotiation


1000M operation requires Auto Negotiation is enabled, whilst 100M operation does not support auto negotiation.

4.4.3.12 Negotiated

Menu Tree: Main Set-Up / Port set-up / WAN / negotiated


For copper mode the possible outcomes are





100M/FD 100 Base FX / Full Duplex



1000M/FD 1000Base-X / Full DUplex

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

For the SFP mode the option is


Note, only 1000M operation supports auto negotiation, and only full duplex operation is supported.

4.4.3.13 SFP Management

Menu Tree: Main Set-Up / Port set-up / WAN / sFP Management

The FCM9003 supports reporting of the SFP device type and diagnostic information. The FCM9003 may also be configured to generate alarms and traps when the diagnostic readings exceed the alarm or warning thresholds.

The SFP Management menu is shown below:


SFP MANAGEMENT

Device Details <display>

Notifications <menu>



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.13.1 Device Details

Menu Tree: Main Set-Up / Port set-up / WAN / sFP Management / Device Details

SFP modules include an EEPROM to identify the module capabilities and these may be read using the SFP device details option. The information display is as shown below:


SFP Info Interface: WAN

--------

Transmit


--------------------------------------------------------------------------

Good 1000BASE-SX HG GENUINE MXPD-248S-F 850nm

Diagnostics

-----------

Tx-Pwr Rx-Pwr Bias Temp Supply

(dBm) (dBm) (mA) (C) (V)

-------------------------------------------

Alrm Hi -1 0 20 85 3.60

Warn Hi -3 -2 15 80 3.50

Warn Lo -10 -15 1 0 3.10

Alrm Lo -12 -17 1 -5 3.00

Value -6 -26 3 22 3.28



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.13.2 Notifications

Menu Tree: Main Set-Up / Port set-up / WAN / sFP Management / Notifications

The SFP notifications menu configures the actions for alarm and trap generation when the disagnostic values exceed the alarm or warning threshold values.


NOTIFICATIONS

1 - Temp High Alarm & Warning

2 - Temp Low None

3 - Supply High None

4 - Supply Low None

5 - Bias High None

6 - Bias Low None

7 - Tx Power High None

8 - Tx Power Low None

9 - Rx Power High None

A - Rx Power Low Alarm & Warning

B - SFP Removed None

C - OTDR Fault None



Each diagnostic value may be configured for either:

None No Action

Alarm Generate an Alarm/Trap when the alarm threshold is exceeded.

Alarm & Warning Generate an Alarm/Trap when either the Alarm or Warning thresholds are exceeded.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.13.3 OTDR SFP module Support

Menu Tree: Main Set-Up / Port set-up / WAN / sFP Management / Device Details

The FCM9003 supports the OpticalZonu SFP modules which have an integrated OTDR measurement facility. When the OTDR SFP modules are used both fibre length while operational, and distance to fault measurements are provided.

The Optical ZONU SFP integrates a distance measuring OTDR module along with the normal SFP optical transceiver. On power up, and whenever Loss of Signal is reported, the OTDR will transmit high power pulses and measure the power and transit time for reflections. Using the results a fibre length measurement can be made.

Note, when used with short fibres it may well be the case that there is insufficient attenuation of the OTDR pulse causing it to report multiple reflections, and a cable length of a multiple of the real length. To counter this, where short fibre runs of less that 10km are used, a 10dB attenuator should be fitted inline.

When an OTDR SFP module is in use the SFP Device Details menu displays additional information when in a fault condition as shown below:


SFP Info Interface: WAN

--------

Transmit


--------------------------------------------------------------------------

Good 1000BASE-LX OpticalZonu,Corp AF6-151G1-SU 1510nm

Diagnostics

----------- OTDR Log

Tx-Pwr Rx-Pwr Bias Temp Supply --------

(dBm) (dBm) (mA) (C) (V) Time/Date Length

(m)

------------------------------------------- ---------------------------

---

Alrm Hi 3 3 70 85 3.63 00:00:02 1/1/2000 0

Warn Hi 2 2 60 75 3.49

Warn Lo -5 -19 4 -35 3.10

Alrm Lo -7 -25 2 -45 2.97

Value 0 -40 36 16 3.22



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.13.3.1 OTDR Log

When the SFP module first powers up, it performs an OTDR distance measurement and reports the measured cable length.

The log will be updated whenever the measured distance changes by more than 1%

The OpticalZonu OTDR SFP modules provide the distance measurement accurate to within +/- 10m.

4.4.3.13.3.2 OTDR SFP Trap Support

In the SFP notifications menu, option C enables the OTDR trap generation for Alarms. The trap definitions may be found in the MET_SFP MIB file.

There are 2 traps generated,

MetSfpOTDRFaultStart This trap is generated when an OTDR fault is first detected. The trap parameters include the distance in metres to the fault.

MetSfpOTDRFaultClear The trap is generated when the OTDR fault is cleared. The trap parameters include the system up time for both start and clearance of the fault condition.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216


Menu Tree: Main Set-Up / Port set-up / WAN / laYer 2 Management

The layer 2 management menu defines the layer 2 functionality for the WAN port. When the FCM9003 is operating in C-VLAN mode, only OAM options are available. When in S-Tag, or Double Tag mode there is an option for defineing the programmable ethertype for the S-Tag.


Menu Tree: Main Set-Up / Port set-up / WAN / laYer 2 Management / Tagging & Priority

The tagging and priority menu is only available in S-Tag or Double Tag modes.

The tagging and priority menu allows the Ethertype for Service VLAN / QinQ tags to be defined. The default setting is 9100.

Some alternative values include:

8100 QinQ VLAN in VLAN

88A8 Provider Bridge

In order to support the maximum number of applications the service tag may be configured and it is important that both ends of a link match.

4.4.3.14.2 OAM

Menu Tree: Main Set-Up / Port set-up / WAN / laYer 2 Management / OAM

The LAN ports support IEEE802.3 Clause 57 ( 802.3ah ) link OAM.

The OAM menu is as below:


OAM, WAN

Mode Active

Status <display>

counTers <display>

Events <display>



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.14.3 OAM Mode

Menu Tree: Main Set-Up / Port set-up / WAN / laYer 2 Management / OAM / Mode

The operating mode of the OAM on this port may be defined here. The valid operating states are:

Disabled Do not generate or respond to OAM packets and discard all OAM packets received.

Active Generate and Respond to OAM packets

Passive Respond to OAM packets

4.4.3.14.4 OAM Status

Menu Tree: Main Set-Up / Port set-up / WAN / laYer 2 Management / OAM / Status

The OAM Status display shows the current state of OAM on this link as shown below:


OAM STATUS

----------

| Local | Local | Peer | Peer | Peer | Peer

| Status | Support | Mode | MAC address | VendorInfo | Support

-------+----------+---------+------+-------------+------------+--------

WAN SendAny L active 00c081001368 00000046 L

Remote Status

-------------

Unit: FCM8000

Node name: ""

Interface: LAN2

Interface AdSt OpSt

LAN1 Up Down

SFP Up Up


Note, Remote Status information is only available when directly connected to a member of the Metrodata MetroConnect product range as this used the Enterprise extension facility of OAM.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.14.5 OAM Statistics

Menu Tree: Main Set-Up / Port set-up / WAN / laYer 2 Management / OAM / counTers

The OAM statistics show the counts for the various OAM packet types as shown:


OAM Statistics

--------------

Rx Tx

Unsupported Codes 0 0

Information 0 755

Unique Event 0 0

Duplicate Event 0 0

Variable Request 0 0

Variable Response 0 0

Loopback Control 0 0

Organisation Specific 0 0

<Escape> - exit, C - clear, other key – refresh

4.4.3.14.6 OAM Events

Menu Tree: Main Set-Up / Port set-up / WAN / laYer 2 Management / OAM / Events

This display lists OAM events that have occurred since the unit was powered up.

4.4.3.15 Suppress All Alarms

Menu Tree: Main Set-Up / Port set-up / WAN / sUppress All Alarms

This value must be left set to NO.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.4.3.16 Rate Shaping

Menu Tree: Main Set-Up / Port set-up / WAN / Rate Shaping

The WAN port has the capability of limiting the egress traffic and effectively shaping the traffic on the WAN port. When shaping is enabled, it affects the entire WAN port and is not flow based. The shaper utilises the priority queues and internal buffers to allow shaping whilst still maintaining QOS.

By default, shaping is disabled, but once enabled the menu offers the following options:


RATE SHAPING, WAN

Shaping Enabled

Rate 1M



When enabled the rate for the shaper may be defined in bits per second. The rate is defined according to the Bandwidth Mode setting in the operational mode menu which may be set to either Utilisation, L1 Rate or Information Rate.

4.4.3.17 Counters

Menu Tree: Main Set-Up / Port set-up / WAN / Counters




--------------------





ifInErrors 0




ifOutNUcastPkts 0

ifOutDiscards 0

ifOutErrors 0


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5 Operational Modes

Menu Tree: Main Set-Up / Operational Modes

The operational menu allows the settings of many parameters relating to the Flow configuration. The operational modes menu is shown below:


OPERATIONAL MODES

VLAN Mode C-Tag

L2CP Tunnel Mode Metrodata ( single m/c )

Max frame size 10k

sla/Policing <menu>

pri Translation <menu>

CFM Domains <menu>



4.5.1 VLAN Mode

Menu Tree: Main Set-Up / Operational Modes / VLAN Mode

The VLAN mode setting defines the operating mode of the FCM9004. There are three options:

S-Tag Add a Service VLAN Tag to all incoming frames.

C-Tag Add a VLAN Tag to all incoming frames, or pass incoming frames tagged within the allocated range.

Double Tag Add a Service VLAN Tag to all incoming frames, and add/pass VLAN Tag to all incoming frames.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.1.1 VLAN Mode – STag


In S-Tag mode a service VLAN Tag is pushed onto the user packets and ingress and removed/popped on egress. The S-Tag has the Ethertype as defined in the WAN port setup traffic management menu, (0

FCM9003 USER MANUAL

76-02-100 Rev.A of 216


Menu Tree: Main Set-Up / Port set-up / WAN / laYer 2 Management

The layer 2 management menu defines the layer 2 functionality for the WAN port. When the FCM9003 is operating in C-VLAN mode, only OAM options are available. When in S-Tag, or Double Tag mode there is an option for defineing the programmable ethertype for the S-Tag.

Tagging and Priority). By default this is set to 9100.

In S-Tag mode, packets ingressing user ports may be untagged, or tagged with normal or alternative Service VLAN Tags giving rise to packets with multiple tags as shown below:

Where:

DA Destination Address

SA Source Address

ET EtherType

FCS Frame Check Sequence

CT IEEE 802.1q VLAN Tag, Etype 8100

ST Service VLAN Tag, default Etype 9100

In S-Tag mode, each port can support the full range of available C-Tags (1-4095) with the ability to allocate S-Tags based on the incoming C-Tag, or range of C-Tags.




Push C-Tag

Push S-Tag

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.1.3 VLAN Mode – CTag


In C-Tag mode, all user packets egress the WAN port with a C-Tag. Optionally , the FCM9003 may push/pop a single C-Tag to untagged only or all packets.

In C-Tag mode, the FCM9004 supports the full range of available VLAN ID’s in the range 1-4095, but each ID may only be allocated to a single user port.

Packets ingressing already tagged will either pass unchanged, if the tag ID is contained within a flow allocation or be discarded. They may also have an extra tag pushed to form a QinQ frame.

The action taken on ingress of an untagged frame may be selected from DISCARD, or push a default Tag.

4.5.1.4 VLAN Mode – Double Tag


In Double Tag mode the FCM9003 can push both an S-Tag and C-Tag to user packets.

In Double Tag mode, the FCM9003 supports the full range of VLAN ID’s 1-4095, however each ID may only be used once, unlike the S-Tag mode where each port supports the full range.

Packets ingressing already tagged will have the S-Tag added, if the tag ID is contained within a flow allocation.

The action taken on ingress of an untagged frame may be selected from DISCARD, or push both a default C-Tag and S-Tag.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.2 L2CP Tunnel Mode

Menu Tree: Main Set-Up / Operational Modes / L2CP Tunnel Mode

The FCM9003 supports layer 2 control protocol tunneling in several different modes.

Single M/C All L2CP tunnels are sent using the same multicast destination address

Multiple M/C Each L2CP is sent using a separate multicast address for each protocol tunneled.

Transparent L2CP packets are passed through unchanged

4.5.3 Max Frame Size

Menu Tree: Main Set-Up / Operational Modes / Max frame size

The Maximum frame size may be defined for the FCM9003. The options for packet size are

1522 Max size is 1518 bytes for untagged, and 1522 bytes for tagged frames.

2048 Maximum packet size is 2048Bytes

10k Maximum packet size is 10k bytes

Note, 10k frames are only supported on GE ports, packet loss may occur when ports are configured as 10 or 100M.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.4 SLA/POLICING

Menu Tree: Main Set-Up / Operational Modes / sla/Policing

This menu controls many of the parameters used by the policer module and by the SLA verification tools.


SLA/POLICING

Count CFM No

count L2CP No

Bandwidth Information Rate

include S-Tag Yes

Include C-Tag Yes

cOupling Disabled

colour Mode Blind

colour mArking <menu>

Delay percentile 95%

eXternal Tags 0

mTU 1518



4.5.4.1 Count CFM

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / Count CFM

The Count CFM control selects whether CFM packets are included in the user flow SLA measurements.

By default, CFM packets are not included as they are “internal” control packets used by the operator to monitor the circuit, rather than being customer traffic. As such if the customer has an SLA offering a CIR of 10Mbps, it should only be the customer traffic that is included.

The CFM packets are excluded for bandwidth calculations, policing and Y.1731 Loss measurement.

4.5.5 Count L2CP

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / count L2CP

The Count L2CP control selects whether L2CP packets are included in the user flow SLA measurements.

The L2CP packets are excluded for bandwidth calculations, policing and Y.1731 Loss measurement.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.5.1 Bandwidth

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / Bandwidth

In the SLA definitions, the bandwidth is expressed in bits per second. The bandwidth configuration item defines what is actually included in the bandwidth calculations:

Information Rate Packet from DA to FCS

L1 Rate Preamble + Packet ( DA to FCS )

Utilisation Preamble + Packet ( DA to FCS ) + IPG

4.5.5.2 Include S-Tag

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / include S-Tag

In S-Tag or Double Tag mode the FCM9003 is adding the S-Tag to the user frames. Since these 4 bytes are added by the operator and are not customer traffic, this option enables the 4 byte STag to be excluded from the bandwidth and policing measurements.

YES Include the S-Tag as part of the frame

NO Reduce packet size by four bytes for bandwidth calculations.

DA SA ET Payload FCSPREAMBLE IPG

Information Rate

L1 Rate

Utilisation

8 bytes 12 bytes64 to 10k bytes

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.5.3 Include C-Tag

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / Include C-Tag

In C-Tag or Double Tag mode the FCM9003 is adding the C-Tag to the user frames. Since these 4 bytes are added by the operator and are not customer traffic, this option enables the 4 byte CTag to be excluded from the bandwidth and policing measurements.

YES Include the C-Tag as part of the frame

NO Reduce packet size by four bytes for bandwidth calculations.

4.5.5.4 Coupling

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / cOupling

The coupling configuration controls the operation of the dual leaky bucket policer. Coupling only the effect of using the excess CIR tokens to increase the available EIR bandwidth.

4.5.5.5 Colour Mode

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / colour Mode

The policer is normally operated in a colour blind mode where all incoming packets are treated the same and first compared against the CIR, and then the EIR.

In colour aware mode, only green packets are checked against the CIR, whilst excess green and yellow packets are checked against the EIR.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.5.6 Colour Marking

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / colour mArking

When the policer is enabled with a defined EIR then frames not conforming to the CIR but within the EIR setting will be marked as yellow frames. Frames exceeding both CIR and EIR will be marked RED and discarded.

The colour marking menu defines the method of colour marking and assigns values to both green and yellow frames.

The colour marking menu is as shown below:


COLOUR MARKING

Mode PCP

PCP->Green 4-7

Yellow->PCP 0

Green->PCP 4



4.5.5.6.1 Mode

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / colour mArking / Mode

Colour marking may be carried out in different ways depending upon whether S-Tag/Double Tag or C-Tag mode is used.

The options are as follows:

PCP The frame colour is indicated by the TAG priority PCP

DEI The frame colour is indicated by the TAG DEI. This mode should only be used for S-Tag or Double Tag modes, as DEI is a redefinition of the CFI marker in the C-Tag which is always set to 0 for Ethernet.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.5.6.2 PCP->Green

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / colour mArking / PCP->Green

When PCP mode is used for colour marking, this setting defines which PCP levels are considered green frames. The value may be entered as comma delimited or range values

Eg 4-7, 4,5,6,7

4.5.5.6.3 Yellow->PCP

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / colour mArking / Yellow->PCP

When PCP mode is being used, this setting defines the PCP value that will be written to frames marked yellow.

4.5.5.6.4 Green->PCP

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / colour mArking / Green->PCP

When PCP mode is being used, this setting defines the PCP value for GREEN frames when the Y.1564 test mode is being used.

4.5.5.7 Delay Percentile

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / Delay percentile

This parameter is used by the Y.1731 SLA monitoring and Y.1564 test module and defines the pass criteria for delay measurement. The delay percentile defines what percentage of frames must be within the SLA defined maximum delay for a test to be considered a pass.

The purpose of this parameter is to prevent a single frame which experiences a significant delay in excess fo the setting, while all other frames were within the required SLA causing the test to fail.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.5.8 External Tags

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / eXternal Tags

This parameter is used by the Y.1564 test module and is used to account for external network conditions.

In some cases, a 100M service is offered over a 100M circuit, however S-Tags are pushed to all frames for customer identification. In this case, a Y.1564 test will fail due to packet loss if testing is carried out at 100% of the CIR. One option would be to reduce the bandwidth for the test, alternately, the test generator module can be configured to assume that the external network will add an extra tag and account for this when setting the packet rate.

4.5.5.9 MTU

Menu Tree: Main Set-Up / Operational Modes / sla/Policing / mTU

This parameter is used by the Y.1564 test module and is used to account for external network conditions.

The FCM9054 has a configurable maximum packet size which is used to define the maximum packet size that can traverse the device. However, it is quite possible, especially where jumbo frames are used that the core network does not support the full 10240 byte packet size that the FCM9054 supports.

The MTU setting is used to define the maximum MTU for the network as a whole and needs to be set to the lowest supported packet size.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.6 Priority Management

Menu Tree: Main Set-Up / Operational Modes / prioriTy Management

The priority management menu enables the unit priority schemes to be defined and the menu is shown below:


PRIORITY MANAGEMENT

DSCP->C-Tag Mapping <menu>

Queue Priorities <menu>

VLAN Override <menu>

Scheduling Mode Weighted Round-Robin



4.5.6.1 DSCP->C-Tag Mapping

Menu Tree: Main Set-Up / Operational Modes / prioriTy Management / DSCP->C-Tag Mapping

When a port is pushing an S-Tag or C-Tag onto a previously untagged frame the tag priority may be sourced from the IP DSCP marker. However, since DSCP has 64 possible values and the Tag priority only has 8, a mapping is provided to support the different traffic classes.


DSCP->C-TAG PRIORITY MAPPING

C-Tag Priority: From DSCP:

6/7 48-63

4/5 32-47

2/3 16-31

0/1 0-15

Restore Defaults



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.6.2 Queue Priorities

Menu Tree: Main Set-Up / Operational Modes / prioriTy Management / Queue Priorities

The FCM9003 has four levels of priority queue internally and this configuration allows the priority of each PCP level to be assigned. The menu is shown below


C-TAG->QUEUE PRIORITY MAPPING

Queue Priority: C-Tag Priority:

High 6,7

Medium 4,5

Low 2,3

Best-Effort 0,1

Restore Defaults



4.5.6.3 VLAN Override

Menu Tree: Main Set-Up / Operational Modes / prioriTy Management / VLAN Override

The FCM9003 has the ability to override the incoming PCP value to allow for promotion/demotion of received frames. Typically this is used for promoting management traffic to ensure remote access is maintained in the presence of traffic overload. The menu is shown below:


VLAN-BASED PRIORITY OVERRIDE

C-Tag Priority: VLAN(s):

7 101

6 -

5 -

4 -

3 -

2 -

1 -

0 -

Clear All



In the example above, ingress frames with VID 101 will be promoted to PCP level 7. All other VID’s will be unchanged.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.6.4 Scheduling Mode

Menu Tree: Main Set-Up / Operational Modes / prioriTy Management / Scheduling Mode

The FCM9003 supports 4 levels of priority queues internally. The egress queues may be serviced in one of two modes:

Weighted Round Robbin The high priority queue is serviced first at all times, but the remaining queues are serviced in a fair way.

Strict Priority The priority queues are serviced in priority order.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.7 CFM Domains

Menu Tree: Main Set-Up / Operational Modes / CFM Domains

The global CFM, Continuity and Fault Management configuration menus allow for the configuration of the global parameters such as Maintenance Domains, MD and also for viewing the status of the CFM connections

CFM uses Maintenance Domains to indicate the span of the circuit to be monitored as shown below:

Here a service provider is using the FCM9003 as the EDD for the provision of a point to point network service for a customer. Connectivity to one customer site utilizes a tail circuit supplied by an alternative carrier. In this case, two CFM maintenance domains need to be defined, the segment domain to allow for monitoring of the tail circuit, and the End to End domain to monitor the complete customer circuit.

The Maintenance Domain configuration menu is as shown:


CFM DOMAINS

Multicast Addr IEEE 802.1 (01:80:c2:00:00:3x)

1 - "Metrodata" <menu>

Add MD <menu>



Service Provider

Core Network

Alternate

Provider

Tail Circuit

End to End Domain

Segment Domain

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.7.1 Multicast Address

Menu Tree: Main Set-Up / Operational Modes / CFM Domains / Multicast Addr

The IEEE 802.1ag CFM standard defines the range of multicast addresses to use the following:

01:80:C2:00:00:3x where x represents the Domain level.

In applications where the core network does not support CFM, or is not willing to peer the option to use an alternate multicast address is supported. The alternative Metrodata address range may be selected:

01:C0:81:00:01:3x where x represents the Domain level.

4.5.7.2 Add Maintenance Domain

Menu Tree: Main Set-Up / Operational Modes / CFM Domains / Add MD

The add domain menu allows the configuration of a new domain. The menu is shown below.


MAINTENANCE DOMAIN

Name ""

name Format String

Level 0

Status Summary <display>

Remove MD



4.5.7.2.1 Domain Name

Menu Tree: Main Set-Up / Operational Modes / CFM Domains / Add MD / Name

The name allocated to the Maintenance domain should be meaningful and express the coverage of the domain.

The combined domain name and association name must not exceed 44 characters.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.7.2.2 Domain Name Format

Menu Tree: Main Set-Up / Operational Modes / CFM Domains / Add MD / name Format

The domain name may be defined in several formats as defined in IEEE802.1ag and Y.1731 as follows

String Character String

None No name defined

DNS Like Name based on DNS name

MAC and Int Name based on the unit MAC address + a 16 bit integer.

4.5.7.2.3 Domain Level

Menu Tree: Main Set-Up / Operational Modes / CFM Domains / Add MD / Level

Where Maintenance Domains overlap, for example End to End, and Segment Domains, they must be allocated different levels. The Domain may be assigned a level in the range 0 to 7 with the level indicating the span of the domain, the greater the span, the higher the level.

Typically,

Level 0,1,2 Core Network Operator

Level 3,4 Service Provider

Level 5,6,7 Customer

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.7.2.4 Domain Status Summary

Menu Tree: Main Set-Up / Operational Modes / CFM Domains / Add MD / Status Summary

This display shows a summary of all the MA/MEP’s within the domain as shown below:


CFM STATUS

----------

Domain "Metrodata_core", level 5

Association Interface Loc-MEP Rem-MEP Defect

-------------------------------------------------------------------------

"Customer1" Flow1 201 101 None

"Customer2" Flow2 202 102 None


4.5.7.2.5 Remove Domain

Menu Tree: Main Set-Up / Operational Modes / CFM Domains / Add MD / Remove MD

If a domain is no longer required, it may be deleted by selecting the Remove Domain menu item.

Note, that if a domain is deleted, all associations and end points defined within this domain will also be deleted.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.5.7.3 Edit a Domain

Menu Tree: Main Set-Up / Operational Modes / CFM Domains / 1

Once a domain has been defined it may be edited, or monitored. Domains are listed in the order that they were defined.


CFM DOMAINS

Multicast Addr IEEE 802.1 (01:80:c2:00:00:3x)

1 - "Metrodata" <menu>

Add MD <menu>



Select the domain to edit by typing the domain number,


MAINTENANCE DOMAIN

Name "Metrodata"

name Format String

Level 5

Status Summary <display>

Remove MD



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6 Flow ( Services )

Menu Tree: Main Set-Up / Flows (services)

In the FCM90034, Flows define how user traffic traverses the device. The Flow defines the Tag values that will be pushed as well as the SLA parameters.

The FCM90034 supports a maximum of 16 flows, however the actual number available in any application is dependant upon the complexity of the C-Tag range allocations.

The top level flow menu is as below:


FLOWS

-----

# Name St S-Tag Port C-VLANs CIR EIR

---------------------------------------------------------------------

1 Gold Service Up 1 LAN1 1-4095 10M 10M

2 Silver Service Up 2 LAN2 1-4095 10M 10M

<Esc> - exit, 1.. - view/edit/remove, N - new, <Enter> - refresh

4.6.1 Add New Flow or View / Edit / Remove Flow

Menu Tree: Main Set-Up / Flows (services) / New

Menu Tree: Main Set-Up / Flows (services) / 1-F

The New Flow menu will automatically get the next available flow number and allow the user to create a new flow definition.

Selecting a current flow number 1 to F, will allow the user to View/Modify/Remove a previously created flow.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

On entry to the Flow menu for either New or View/Modify/Remove the menu is as shown below:


FLOW1

Name Gold Service

State Up

s-VLAN ID 1

User Port LAN1

c-vlan Alloc 1-4095

coNtrol C-VLAN 1

sLA/Policing <menu>

cFM <menu>

Counters <display>

Remove Flow



4.6.1.1 Flow Number

Menu Tree: Main Set-Up / Flows (services) / N or 1-F

At the top of the screen the flow number (1-16 ) is shown. When adding a new flow, this is automatically generated. For edits, the Flow indicates the flow number selected.

4.6.1.2 Flow Name

Menu Tree: Main Set-Up / Flows (services) / N or 1-F / Name

To improve useability, each flow may be named with a name that represents the flow in a more understandable manner than the flow number. The name is a string of upto 31 characters.

The name will be displayed as the SNMP OID IfAlias in the IF-MIB

4.6.1.3 Flow State

Menu Tree: Main Set-Up / Flows (services) / N or 1-F / State

The flow state defines the administrative state of the flow.

UP Flow Enabled, traffic can pass

DOWN Flow disabled, all traffic discarded.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.4 S-VLAN ID

Menu Tree: Main Set-Up / Flows (services) / N or 1-F / S-VLAN ID

In S-Tag or Double Tag mode, each flow has a single S-TAG pushed and this item defines the value in the range 1 – 4095.

This item is not present in C-Tag mode.

In S-Tag mode, all flows must have different S-Tag ID’s as this is the flow marker, however in Double Tag mode multiple flows may use the same S-Tag ID as it is the internal C-Tag which defines the flow.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.5 User Port

Menu Tree: Main Set-Up / Flows (services) / N or 1-F / User Port

The FCM9003 has four copper user ports along with an SFP port. This config item defines which of the 5 ports the user frames will ingress for this flow.

Options:

None This flow will terminate inside the device and is used for management

LAN1 This flow will terminate at LAN port 1




SFP This flow will terminate at SFP port

Note, where the FCM9003 is to be managed in-band from the core over the WAN port the flow should be defined with the user port set to none to prevent management traffic being visible externally

4.6.1.6 C-VLAN Allocation

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / c-vlan Alloc

Customer traffic may be tagged or untagged.

In S-Tag mode, the full range of VLAN ID’s ( 1-4095 ) are available per port, however in the C-Tag or Double Tag modes the full range of VLAN’s are available for the unit, such that each ID may only be allocated to one port.

If a flow is to pass untagged frames, the allocation should include ‘0’, to only pass tagged frames exclude 0 from the list.

In C-Tag, or Double Tag mode the untagged action is defined on a per port basis and may be set to either

DISCARD

Add default Tag

This action is defined in the port traffic management menu.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.7 Control C-Vlan

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / Control C-VLAN

The control VLAN is used to transmit CFM frames for the flow. The control C-VLAN must be included within the Allocation for the flow. The ID selected for the control C-VLAN may be one that will be used by the user, or alternatively be one generated by the FCM9004.

4.6.1.8 SLA/Policing Definition

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing

For each flow, SLA parameters may be defined. If bandwidth parameters are defined, then the policer will be enabled for this flow to enforce this traffic profile. The remaining items are used by the Y.1731 monitoring module to determine adherence to the defined SLA.

The SLA/Policing bandwidths are calculated according to the bandwidth setting in the Operational Mode Menu (4.5.5.1) and may be defined in terms of:

Information Rate Frame contents from DA to FCS

L1 Rate Preamble + Frame ( DA to FCS )

Utilisation Min IPG + Preamble + Frame ( DA to FCS )

Note, that a 100Mbps Utilisation will only yield an Information rate of only 76Mbps due to overheads.

The SLA/Policing menu is shown below:


SLA/POLICING, FLOW1

CIR 10000000

cBS 10000

EIR -

ebS -

max Frame Loss 1.000%

max Delay 100us

max delay Var 100us

Availability 95.000%

Policing Enabled



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.8.1 CIR

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / CIR

CIR, or Committed Information Rate is the guaranteed bandwidth that will be supplied to the customer.

CIR is defined in bits per second and may range from 100k through to 1G

User traffic that is within the CIR will be marked by the police as GREEN, and transported. Traffic exceeding the CIR will either be processed as Yellow against the EIR, or discarded as non conformant

4.6.1.8.2 CBS

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / cBS

CBS, or Committed Burst Size is the guaranteed burst size that will be supplied to the customer.

CBS is defined in bytes and ranges from the max packet size to 64kbytes.

User traffic upto and including the CBS will be passed, if within the CIR otherwise it may be marked yellow or discarded depending upon the EBS setting.

4.6.1.8.3 EIR

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / EIR

EIR, or Excess Information Rate is an amount of extra bandwidth that the operator may, but does not guarantee to, provide to the user.

EIR is defined in bits per second and may range from 100k through to 1G - CIR

User traffic that exceeds CIR but is within the EIR will be marked by the police as YELLOW, and transported otherwise it will be discarded as non conformant

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.8.4 EBS

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / ebS

EBS, or Excess Burst Size is extra burst capability that may be supplied to the customer.

EBS is defined in bytes and ranges from the max packet size to 64kbytes.

User traffic exceeding the CBS but within the EBS will be passed and marked yellow otherwise it will be discarded.

4.6.1.8.5 Maximum Frame Loss

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / max Frame Loss

This defines the maximum allowable Frame Loss Ratio which may be validated using the Y.1731 Loss Measurement Mechanism.

The FLR is defined as a percentage and is calculated according to MEF10.2 as the ratio of frames lost to the frames transmitted marked green. If the Y.1731 monitoring determines that the FLR has been exceeded alarm processing will begin.

4.6.1.8.6 Max Delay

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / max Delay

The FCM9003 uses Y.1731 to measure the round trip delays and makes the assumption that the link is symmetrical. The FCM9003 does not support direct measurement of one way delays since it does not support clock synchronization to GPS or other such master clock.

Y.1731 uses the DMM/DMR frames to determine the actual packet flight times for the round trip, and reports the delays to sub microsecond accuracy.

The Max Delay configuration item defines the maximum one way delay ( half round trip delay ) allowed by the SLA, above this delay and the device will generate an alarm to indicate violation of the SLA.

In order to prevent a single frame which was excessively delayed from causing the SLA to be violated, the Delay Percentile configuration item is used to determine the percentage of violating frames are required before an SLA alarm is raised.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.8.7 Max Delay Variation

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / max delay Var

The FCM9003 uses Y.1731 to measure the round trip delay, and uses a comparison of the flight time of the current frame to the previous frame to determine the variation.

The Max Delay Variation configuration item defines the maximum variation allowed by the SLA, above this amount of variation and alarms will be generated to indicate a violation of SLA.

4.6.1.8.8 Availability

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / Availability

The availability is calculated according to MEF10.2 and is a measure of the ability to comply with the SLA, An available second is defined as a second during which the link is available, and that the FLR, Delay and DV are all compliant.

4.6.1.8.9 Policing

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / sLA/Policing / Policing

Policing is enabled when either the CIR or EIR are configured as non zero. This parameter is for information to inform the user that the policer is enabled.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.9 Flow CFM Configuration

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM

The Flow CFM menu allows for the configuration of the CFM parameters required per flow. In the data port CFM menu, the Maintenace Domains used in the network are defined, these are global across all flows. The Flow CFM menu configures the association and end points that are flow specific.


CFM, FLOW1

MA <menu>

mEP <menu>



Per flow, there may be one instance of an MA ( Maintenance Association ), and one MEP ( Maintenance End Point ) defined for each MD ( Maintenance Domain) that has been defined.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.9.1 MA, Maintenance Association Configuration

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / MA

An MA, Maintenance Association is defined as a group of MEP’s that exist on a flow. Under Y.1731 terminology, the MA corresponds to the MEG or Maintenance Entity Group.

To configure the MA, the menu is as shown:


CFM MA, FLOW2

Name "Silver Service"

name Format String

Domain "Metrodata"



4.6.1.9.1.1 MA Name

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / MA / Name

The Name given to the Maintenance Association is there to make it recognizable and should be in the format defined in the Name Format.

The length of the MA Name is limited by the requirement for the combined length of the MD name, and MA name to not exceed 44 characters

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.9.1.2 MA Name Format

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / MA / name Format

This item defines the required format for the MA Name, the options are

String ASCII Character String

None Blank Entry

Primary VLAN Id Use the specified control vlan ID

Int16 2 octet Number

VPN ID RFC 2685 VPN ID

ICC Y.1731 ITU Carrier Code

4.6.1.9.1.3 MA Domain

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / MA / Domain

The MA must be assigned to be part of a previously defined Maintenance Domain. Scroll through the list of available domains and select the required domain.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.9.2 MEP, Maintenance End Point Configuration

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / mEP

A Maintenance End Point, MEP is defined for each end of a flow, and defines how the end point will perform. The configuration menu is shown below:


CFM MEP, FLOW1

MEP Id 101

State Up

CCM Enabled

LMM Enabled

SLM Enabled

DMM Enabled



4.6.1.9.2.1 MEP ID

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / mEP / MEP Id

This is an ID given to this end point in the range 1 to 8191. Each MEP assigned to the flow must have a unique ID within the MA.

In a point to point connection, there will be two MEP’s defined, one on each end point device and the MEP ID used must be different.

eg Device A, MEP ID = 101

Device B, MEP ID = 102

4.6.1.9.2.2 MEP State

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / mEP / State

This item defines the administrative state for the MEP.

UP Transmit CCM,DMM, SLM and LMM messages if enabled

DOWN Do not generate CFM packets, or generate alarms for failure conditions.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.9.2.3 MEP CCM

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / mEP / CCM

This item defines whether the MEP will generate a CCM, Continuity Check Message once per second.

If an MEP is in the UP state, and does not receive a CCM for 3 seconds, then the CFM Link Down Alarm will be generated.

Options

Enabled Send CCM once per second

Disabled Do not send CCM

4.6.1.9.2.4 MEP LMM

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / mEP / LMM

This item defines whether the MEP will generate the Y.1731 LMM, Loss Measurement Messages at a rate of once per second.

If the MEP is in the up state, it will respond to a received LMM with an LMR response regardless of the state of the LMM enable control.

Options

Enabled Send LMM once per second

Disabled Do not send LMM

In order to verify the SLA parameter frame loss ratio, LMM packet generation must be enabled in order that the real time frame counters may be accessed.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.9.2.5 MEP SLM

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / mEP / slM

This item defines whether the MEP will generate the Y.1731 SLM, Synthetic Loss Measurement PDU at a rate of once per second.

If the MEP is in the up state, it will respond to a received SLM with an SLR response regardless of the state of the SLM enable control.

Options

Enabled Send SLM once per second

Disabled Do not sendSLM

In order to verify the SLA parameters Availability, SLM packet generation must be enabled.

4.6.1.9.2.6 MEP DMM

Menu Tree: Main Set-Up / Flows (services) / N, 1-F / cFM / mEP / DMM

This item defines whether the MEP will generate the Y.1731 DMM, Delay Measurement Messages at a rate of once per second.

If the MEP is in the up state, it will respond to a received DMM with an DMR response regardless of the state of the DMM enable control.

Options

Enabled Send DMM once per second

Disabled Do not send DMM

In order to verify the SLA parameters Delay and Delay Variation, DMM packet generation must be enabled in order that the real time frame egress/ingress timestamps may be accessed.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.6.1.9.3 Counters

Menu Tree: Main Set-Up / Flows (services) / Add / Counters

This display shows the counters for the flow traffic flow as shown below:


Flow Statistics

---------------

Out Bytes 0 CFM In Packets 0

Out Packets 0 CFM Out Packets 0

In Bytes 0 CFM Out Discards 0

In Packets 0

Green Bytes 0

Green Packets 0

Yellow Bytes 0

Yellow Packets 0

Discarded Bytes 0

Discarded Packets 0


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

In the flow statistics display the following items are counted:

Bytes Total bytes traversing the WAN port for this flow. The byte count is defined by the bandwidth mode ( may include preamble, and or IPG)

Frames Total frames traversing the WAN port for this flow. may or may not include CFM/Y.1731 control frames

In Bytes/Frames Received on the WAN port for this flow.

Out Bytes/Frames Transmitted on the WAN port for this flow

Green Bytes/Frames transmitted which are marked green as conforming with the CIR/CBS traffic profile.

Yellow Bytes/Frames transmitted which are marked yellow to indicate these exceed the CIR, but are within EIR/EBS

Discarded Bytes/Frames exceeding the traffic profile and discarded.

4.6.1.9.4 Remove Flow

Menu Tree: Main Set-Up / Flows (services) / Add / Remove Flow

If a flow is no longer required, it may be deleted by selecting the remove Flow menu option.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7 Performance Monitoring

Menu Tree: Main Set-Up / peRf monitoring

The FCM9003 supports multiple performance monitoring sessions which may operate at layer 2 using Y.1731, or at Layer 3 using TWAMP.

Y.1731 utilises DMM/DMR packets to measure round trip delays and one way variations, and LMM/LMR and SLM/SLR packets to measure packet loss in order to determine the SLA Frame Loss Ratio.

TWAMP will allow for the measurement of round trip delay, and one way latency.

Both 1731 and TWAMP are supported with hardware timestamping to give sub micro second accuracy.

The performance monitoring menu is as follows:


Performance-Monitoring Peers

----------------------------

# Name St Type Interf Address

----------------------------------------------------------------------

1 Customer_1731 Up Y.1731 Flow1

2 Customer_TWAMP Up TWAMP Flow2 10.10.10.2

<Esc> - exit, 1.. - view/edit/remove, N - new, <Enter> - refresh

In a manner similar to the flow configuration, the options are now:

N New PM Session Definition

1 to F View / Edit / Remove a current PM session

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1 Adding a New, or Editing a Current PM Session

Menu Tree: Main Set-Up / peRf monitoring / N, 1-F

When you select to add a new PM session, the menu is as below:


NEW PM PEER

Name

State Down

Type L2/Y.1731

Flow 1

Y.1731 performance <display>

Remove



4.7.1.1 Adding/Editing a Layer 2 PM Session

For a layer 2, Y.1731 performance monitoring session the configuration menu is as shown below:


PEER1

Name Customer_1731

State Up

Type L2/Y.1731

Flow 1

Y.1731 performance <display>

Remove



4.7.1.1.1 Name

The NAME parameter is used to identify the performance monitoring session.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.1.2 State

The STATE parameter is used to enable/disable the PM session.

UP The PM session is up and for an L2 session the Y.1731 DMM/LMM messages will be transmitted. The SLA will be monitored and alarms/traps will be generated if violated.

DOWN The PM session is down, and the SLA is not monitored.

4.7.1.1.3 Type

The TYPE parameter is used to determine whether the session operates at layer 2 or Layer 3

L2/Y.1731 Y.1731 DM messages to monitor the latency and variation, and LM messages to monitor frame loss

L3/TWAMP TWAMP is used to monitor the round trip latency and variation.

4.7.1.1.4 Flow

Layer 2, Y.1731 PM sessions are linked directly to a flow, and the FLOW parameter selects which flow is to be monitored.

Flow Select flow, 1 to 16

With an L2 PM session, the SLA parameters are defined as part of the flow definition.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.1.5 Y.1731 Performance Display

The Y.1731 performance monitor display shows the measured performance of the selected flow:

The Y.1731 performance is displayed as shown below:


Y.1731 Performance Statistics Flow1

-----------------------------

Outbound Inbound SLA

Time (s) 8068 8068

Unavailable (s) 8068 8068

Availability (%) 0.000 0.000 95.000

Sent Frames 0 0

Lost Frames 0 0

Frame Loss Ratio (%) 0.000 0.000 1.000

Maximum Delay (us) 0.0 0.0 100

Maximum Delay Variation (us) 0.0 0.0 100

<Escape> - exit, C - clear, other key - refresh

Y.1731 allows for the measurement of the following performance values:

Time This shows the time over which the Y.1731 performance has been monitored.

Unavailable This shows the amount of time that the link has been unavailable

Availability The availability is calculated as per MEF 10.2 as a ratio of the total seconds, versus the time of non conformance to the flow SLA

Sent Frames This value is retrieved from the Y.1731 LMR messages

Lost Frames This value is calculated using the LMR messages

Frame Loss Ratio This is the ratio of transmitted frames to frames lost traversing the network to the remote end point.

Maximum Delay Y.1731 allows for measurement of the round trip delay and this display shows the inbound/outbound delay as half the round trip delay.

Max Delay Variation The variation is measured on the round trip delay and is compared frame by frame to the previous frame delay.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2 Adding/Editing a Layer 3 PM Session

For a layer 3,TWAMP performance monitoring session the configuration menu is as shown below:


PEER2

Name Customer_TWAMP

State Up

Type L3/TWAMP

Peer ip 10.10.10.2

tWamp setup <menu>

sLa <menu>

rEports <menu>

Remove



4.7.1.2.1 Name

The NAME parameter is used to identify the performance monitoring session.

4.7.1.2.2 State

The STATE parameter is used to enable/disable the PM session.

UP The PM session is up and for an L3 session the TWAMP messages will be transmitted. The SLA will be monitored and alarms/traps will be generated if violated based on packets received from a reflector

DOWN The PM session is down, and the SLA is not monitored.

4.7.1.2.3 Type

The TYPE parameter is used to determine whether the session operates at layer 2 or Layer 3

L2/Y.1731 Y.1731 DM messages to monitor the latency and variation, and LM messages to monitor frame loss

L3/TWAMP TWAMP is used to monitor the round trip latency and variation.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2.4 Peer IP

TWAMP is an IP protocol which requires a peer IP address of a reflector device. The flow / port that is used for the testing is determined by the port / flow IP address configuration

Once the state is up, the PM session will arp to discover the peer device, once discovered the session will start and the peer to peer connection will be monitored against the configured SLA.

If the peer is unavailable, or does not support the TWAMP reflector protocol the connection will be declared UNAVAILABLE.

4.7.1.2.5 TWAMP Setup

The TWAMP setup menu defines the TWAMP Light sender parameters. The default settings are correct when the Metrodata FCM9003 or FCM9003 is acting as the reflector. When interworking with other vendor reflectors these parameters may need adjusting to be compatible.

The twamp setup menu is as below:


TWAMP SETUP

Dscp 0

Message length 44

pAdding Pseudo-Random

transmit Rate 1s

receive timeOut 3s



4.7.1.2.5.1 DSCP

The DSCP parameter defines the priority to be used by the TWAMP messages.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2.5.2 Message Length

The message length parameter defines the length of the TWAMP payload. The frame will also include the required MAC, IP and UDP overhead giving an actual packet size of

MAC DA + SA + ETYPE + FCS 18 bytes

MAC VLAN Tags ( optional ) single 4 bytes, QinQ 8 bytes

IP Header 20 Bytes

UDP Header 8 Bytes

Total Overhead 46 bytes ( + optional tags 4/8 )

Therefore total packet size is

Total Overhead + Message Length 100bytes (default)

The minimum supported message length is 44 bytes which supports the full TWAMP reflector payload, with 3 padding bytes ( 0x00 )

Setting the message length in excess of 44 bytes will increase the packet size with the additional padding filled as defined by the padding parameter.

4.7.1.2.5.3 Padding

The padding parameter defines the contents of the additional paylaod padding added when the message length is increased beyond 44 bytes. The padding options are:

Psuedo Random The payload will be filled with psuedo random bytes

Zero The payload wil be filled with zeros

4.7.1.2.5.4 Transmit Rate

The transmit rate defines the rate at which TWAMP packets will be transmitted. The options are

1s Transmit packet once per second

100mS Transmit a packet once every 100mS, 10 per second.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2.5.5 Receive Timeout

If a transmitted packet has not been received within the receive timeout period it is classed as a lost packet.

The default setting is 3 seconds.

4.7.1.2.6 SLA

The SLA menu allows the SLA to be defined for this particular peer to peer connection. The SLA definition menu is as shown below:


SLA

Cir -

cBs -

Eir -

ebS -

Availability <menu>

Flr <menu>

fTd <menu>

Ifdv <menu>



The four SLA parameters that may be monitored by TWAMP are as shown along with the bandwidth profile used by Y.1564, and for each parameter the menu allows for definition of the value/threshold, alarm generation and also the time periods for integration.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2.6.1 Availability

The SLA Availability is configured using the following menu,


L3 SLA AVAILABILITY

Threshold(%) 99.99

Sla alarm Enabled

Integration period 24 hours

min Data 24 hours



4.7.1.2.6.1.1 Threshold

The threshold defines the percentage availability required, and this is calculated over the defined integration period.

99.99 approx 3 seconds in 24hours / 260 seconds in 30 days

99.999 approx 1 second in 24 hours / 26 seconds in 30 days

4.7.1.2.6.1.2 SLA Alarm

The SLA alarm setting defines whether this parameter will be monitored and if violated and alarm/trap will be raised.

ENABLED Alarm/Trap Issued

DISABLED SLA reported but not monitored

4.7.1.2.6.1.3 Integration Period

The integration period defines the time period over which the SLA will be monitored. For availability, the options are

24 hours

30 days

For availability, the recommended setting is 30 days.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2.6.1.4 Minimum Data

The minimum data defines how long the connection must have been monitored for before the initial SLA monitoring will begin. The purpose of this parameter is to prevent an initial unavailabilty due to the link being established then forcing an SLA violation alarm to be generated.

For availabilty, the default setting is 24 hours, but in order to get a more rapid response shorter periods are available.

4.7.1.2.6.2 Frame Loss Ratio, FLR

The SLA FLR is configured using the following menu,


L3 SLA FLR

Threshold(%) 0.01

Sla alarm Enabled


min Data 24 hours



4.7.1.2.6.2.1 Threshold

The threshold defines the percentage frame loss that is acceptable, and this is calculated over the defined integration period. The FLR is dependant upon the packet transmissin rate and the integration periods.

0.01% 8 lost packets in 24 hours, 260 lost packets in 30 days

0.001% 1 lost packet in 24 hours, 26 packets in 30 days

Note, that when monitoring packet loss using TWAMP, the low packet rate 1pps or 10pps will exagerate the FLR when measured over short periods.

4.7.1.2.6.2.2 SLA Alarm




FCM9003 USER MANUAL

76-02-100 Rev.A of 216



24 hours

30 days

For FLR, the recommended setting is 30 days.




4.7.1.2.6.3 Frame Transfer Delay, FTD

The SLA FTD is configured using the following menu,


L3 SLA FTD

Max value(us) 10000

Threshold(%) 95

Sla alarm Enabled


min Data 24 hours



4.7.1.2.6.3.1 Maximum Value

The maximum value, defined in micro seconds (uS) defines the maximum round trip transfer delay that is acceptable within the terms of the SLA.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2.6.3.2 Threshold

The threshold defines the percentage of frames which must be within the defined latency value for the SLA to be met.

The purpose of the threshold is to prevent a single packet delayed excessively, or lost forcing the SLA to be violated for transfer delay. The SLA defines the percentage of complient frames.

4.7.1.2.6.3.3 SLA Alarm






24 hours

30 days




FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.7.1.2.6.4 Inter Frame Delay Variation, IFDV

The SLA IFDV is configured using the following menu,


L3 SLA IFDV

Max value(us) 10000

Threshold(%) 95

Sla alarm Enabled


min Data 24 hours



4.7.1.2.6.4.1 Maximum Value

The maximum value, defined in micro seconds (uS) defines the maximum inter frame variation, measured in both directions that is acceptable within the terms of the SLA.

4.7.1.2.6.4.2 Threshold

The threshold defines the percentage of frames which must be within the defined variation value for the SLA to be met.

The purpose of the threshold is to prevent a single packet delayed excessively, or lost forcing the SLA to be violated forpacekt variationy. The SLA defines the percentage of complient frames.

4.7.1.2.6.4.3 SLA Alarm




FCM9003 USER MANUAL

76-02-100 Rev.A of 216



24 hours

30 days




4.7.1.2.7 Reports

The PM session will monitor the parameters and presents the following set of reports showing the results:


REPORTS

1 - temp <display>

2 - current 15min <display>

3 - last 15min <display>

4 - 24hr totals <display>

5 - current 24hr <display>

6 - last 24hr <display>

7 - 30-day totals <display>

8 - all 15min <display>

9 - all 24hr <display>



4.7.1.2.8 Remove

The remove option will remove the PM session and free the resources to be reused again.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8 Circuit / Flow Tests

Menu Tree: Main Set-Up / circuit/flow Tests

The Testing menu serves two functions, it give access to the Layer 1 port loopback functions and also gives access to the SAM ( Service Assurance Module ) functions.

The top level testing menu is shown below,


CIRCUIT/FLOW TESTS

SAM Mode Loopback

Udp port 7

Flow Loops <menu>

port Loops <menu>

first CAPITAL - select item


4.8.1 Port Loops Menu Tree: Main Set-Up / circuit/flow Tests / port Loops

This menu gives access to the port loopback controls and enables the use to apply a physical layer, layer 1 loopback to the user port or SFP port. The loops are physical layer loops and simply loop frames back as they are received.

To apply a loopback simply select the port to which the loop is to be applied. Then use the toggle function to select between:

NONE No Loopback applied

XLL External loopback plug fitted, loop transmit back to receiver

OL Remote Loop, Loop back receive to transmitter

OAM Generate OAM loopback request to remote unit

WARNING:

Physical layer loops MUST be used with great care as they can introduce loops and

therefore cause traffic instability on a live network. These loops are only intended for use with LAN Test Equipment.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2 SAM Flow Testing, Service Assurance Module

Menu Tree: Main Set-Up / circuit/flow Tests

The Service Assurance Module provides the FCM9003 with a highly flexible, multi stream traffic generation, and Layer 2 ( DA/SA swap ) and Layer 3 (IP DA/SA swap) loopback functions.

By default, the FCM9003 has the loopback function enabled and will loopback test packets sent to the user defined loopback MAC address.

From factory default, the SAM test menu is as below:


CIRCUIT/FLOW TESTS

SAM Mode Loopback

Udp port 7

Flow Loops <menu>

port Loops <menu>



4.8.2.1 SAM Mode

Menu Tree: Main Set-Up / circuit/flow Tests / SAM Mode

The Mode menu item selects the operating mode of the SAM module. The item is a toggle item and has the following options:

LOOPBACK The loopback function is enabled, and any packets received on the WAN port with the WAN loop address, or User port with the USER loop address will be looped back with the MAC Destination and Source Addresses swapped.

TESTER Enable the multi-stream traffic generator to generate test traffic streams to validate the SLA parameters of the provisioned flows.

DISABLED The SAM module is disabled, neither loopback or traffic generation capabilities are available.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.2 Loopback Operation

When the SAM module is configured in the LOOPBACK mode, an always on wirespeed loopback function is available as follows:

4.8.2.2.1 Layer 2 Loopback

The FCM9003 will direct packets to the loopback module where the MAC source and destination addresses will be swapped, when they are received with the following MAC addresses

WAN Port

00:C0:81:FF:00:00 or 00:C0:81:8x.xx.xx where x.xx.xx is unit address

USER Port

00:C0:81:FF:00:01

Note, that for the WAN port, wither the default, or a unique unit specific address may be used for the loopback function dependant on the underlying network capabilities.

4.8.2.2.2 Layer 3 Loopback

The FCM9003 will direct packets addressed this unit using the configured loopback UDP port number, by default the loopback port is defined as 7, UDP echo.

The layer 3 loop will perform the following:

MAC Source/Destination Swap

IP Source/Destination Swap

IP TTL Replacement

IP Checksum Recalculate

UDP Source/Destination Swap

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.3 Flow Testing

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing

The SAM Flow testing menu is as shown below:


FLOW TESTING

test Regime Manual Control

test Duration 0:00

maNual Setup <menu>

tEst Summary <display>

State Stopped



4.8.2.4 SAM Test Regime

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test Regime

The test regime selects how the traffic generator is to be controlled. The options are as below:

MANUAL Manual Mode allows the traffic generator to be configured manually, and perform specific tests under user control.

Y.1564 Y.1564 Test Mode selects an automated test methodology which enables traffic flow SLA’s to be verified in the presence of background traffic.

RFC2544 RFC2544 Test mode enables a test mode to measure the throughput and latency of the WAN port.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5 Y.1564 Testing

The testing standard ITU Y.1564 defines a methodology to verify the Service Level Agreements applied to customer services may be achieved. Y.1564 is an improvement over RFC-2544 which was targeted at simply finding the maximum throughput of a link, in that it uses multiple traffic flows to verifiy SLA parameters in the presence of background traffic.

When the SAM mode is set to Tester and the Regime Y.1564 is selected the menu changes to the following:


FLOW TESTING

test Regime Y.1564

test pArameters <menu>

report Header <menu>

Flows -

State Stopped

View Results <display>

report file Name FCM9003_00c0810013ae.rep

Send Report



4.8.2.5.1 Test Parameters

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters

The test parameters control the general operating parameters for the Y.1564 test mode. The menu is as below:

Metrodata FCM9003 "" Alarms: none

TEST PARAMETERS

Layer L2

Flows -

background Rate 10% of CIR

colour-Aware Yes

Stop on fail Yes

Frame size/mix d (512)

User-defined size 1518

remote MAC 00:c0:81:ff:00:00

Configuration Test <menu>

Performance Test <menu>



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.1.1 Layer

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Layer

The layer selection determines whether a basic layer 2 or layer 3 IP test will be performed.

At layer 2, the testing is based on MAC address so either uses the ‘magic’ address or the unique loop address if known. The L2 test uses theflow SLA definitions for operation.

At layer 3, an IP address forms the destination and through the use of ARP the remote MAC address is discovered. The test packets will be UDP and the SLA is taken from the TWAMP peer definition.

4.8.2.5.1.2 Flows/Peers

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Flows

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Peers

For layer 2, a flow must be allocated to the test in order to give the SLA parameters, while for layer 3, an Perfromance monitoring Peer is required.

4.8.2.5.1.3 UDP Port

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / uDp port

When in L3 test mode, the UDP port number must be defined. By default the UDP Echo service, Port 7, is configured. This port number must match the port defined on the associated loopback unit.

4.8.2.5.1.4 Background Rate

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / background Rate

One of the benefits of Y.1564 is that it verifies the configured SLA for flows and services. When multiple flows are allocated to the 1564 test one of these flows will beused for generating background traffic. This ensures that a flow CIR can be achieved in the presence of other traffic.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.1.5 Colour Aware

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / colour-Aware

Policers generally have two modes of operation. They may be colour aware where green and yellow traffic flows are treated seperately, or colour blind where all frames are treated the same.

If colour aware mode is set to yes, then EIR/EBS testing will generate separate flows for green at CIR and yellow at EIR.

If colour aware mode is set to no, then a single green traffic stream is generated at a rate equal to the CIR + EIR.

4.8.2.5.1.6 Stop on Fail

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Stop on fail

This config item will cause the Y.1564 test to stop if any test fails. This is useful when longer test periods are used such that a configuration error may be discovered and corrected quickly.

4.8.2.5.1.7 Frame Size / Mix

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Frame size/mix

To simulate real world traffic, the test traffic may comprise up to 5 packet sizes which are sent in a repeating sequence.

The packet sizes supported are as per the Y.1564 specification

A 64 bytes

B 128 bytes

C 256 bytes

D 512 bytes

E 1024 bytes

F 1280 bytes

G 1518 bytes

H MTU, defined using the MTU setting

U User Defined

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

The packet size is defined excluding tags, such that where a 64 byte packet size is requested, the actual packet may be

Untagged 64 Bytes

Single Tag 68 Bytes

Double Tag 72 Bytes

When defining the packet size/mix either the numerical value, or assigned letter may be used as below: 64, 128, 1024 Send sequence of three packets with size 64/128/1024

acdeh Send a sequence of five packets with frame sizes 64/256/512/1024 and MTU

4.8.2.5.1.8 User Defined Size

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / User-Defined size

The user defined frame size defaults to 1518 bytes but may be set to any value between 64 and upto and including the MTU

4.8.2.5.1.9 Remote MAC

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / remote MAC

By default, the FCM9004 uses the “magic” loopback address which is atomatically looped back by any FCM9004 or FCM9002 which receives it when loopback is enabled.

00:C0:81:FF:00:00 WAN Port Loopback

00:C0:81:FF:00:01 User Port Loopback

In networks where multiple remote sites exist it may not be desirable to use the magic address and instead the MAC address of the remote unit may be entered to ensure a single path is followed.

Where the OUI matches Metrodata ( 00:C0:81 ) then bit 24 will be automoatically set to define the unique WAN port loop address for the remote device.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.1.10 Configuration Test

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Configuration Test

The configuration test phase is intended to be a rapid check of the defined SLA and performs a sereies of short tests to validate it. The configuration test menu is as shown below:


CONFIGURATION TEST

Test time 3s

CIR test Step-Load

eIR test Perform

Policing test Perform

cBS test Perform

EBS test Perform



4.8.2.5.1.10.1 Test Time

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Configuration Test / Test Time

During the configuration test phase, each test will run for this period. The purpose of the configuration tests are to validate that the basic SLA can be achieved so this time should be fairly short, but long enough to give a valid view of the network.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.1.10.2 CIR Test

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Configuration Test / CIR Test

The CIR test verifies that traffic may be generated at the configured CIR and meet the frame loss configuration.

The options for CIR test are

STEP LOAD Start the test at 25% of CIR and gradually ramp up to 100% CIR

SIMPLE Start the test at 100% CIR

SKIP Do not perform the CIR test

4.8.2.5.1.10.3 EIR Test

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Configuration Test / eIR Test

The EIR test verifies that traffic may be generated at the configured CIR + EIR and that the received traffic at least meets the CIR rate and frame loss configuration.

The options for EIR test are

PERFORM Start the test at 100% CIR + EIR

SKIP Do not perform the EIR test

The EIR test will be automatically skipped if no EIR is defined.

4.8.2.5.1.10.4 Policing Test

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Configuration Test / Policing Test

The Policing test verifies that traffic may be generated at the configured CIR 125% of the configured EIR. The test will pass provided traffic is received which complies with the CIR rate and frame loss configuration.

The options for Policing test are

PERFORM Perform the Policing Test

SKIP Do not perform the Policing test

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.1.10.5 CBS Test

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Configuration Test / cBS Test

The CBS test verifies that traffic may be generated at the configured CIR with bursts of size CBS and meet the frame loss configuration.

The options for CBS test are

PERFORM Perform the CBS test

SKIP Do not perform the CBS test

4.8.2.5.1.10.6 EBS Test

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Configuration Test / EBS Test

The BBS test verifies that traffic may be generated at the configured CIR + EIR with bursts of size CBS + EBS and meet the frame loss configuration.

The options for EBS test are

PERFORM Perform the EBS test

SKIP Do not perform the EBS test

4.8.2.5.1.11 Performance Test

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Performance Test

The performance test is run over an extended period and verifies that the network provides a service which is complient with the defined SLA

The menu is as shown below:


PERFORMANCE TEST

Performance Test Perform

Test time 15:00

Green Rate 100% of CIR

gReen Burst 100% of CBS

Yellow Rate 0% of EIR

yEllow Burst 0% of EBS



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.1.11.1 Performance Test

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Performance Test / Performance Test

The performance test may be performed or skipped.

If the test is performed, it is run for the configured test time.

4.8.2.5.1.11.2 Test Time

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Performance Test / Test Time

The performance test is performed for the test time. The longer the test runs then the more confidence is gained that the network meets the required SLA.

The test time must be entered in whole minutes using the format minutes:0

Eg 10:0 for 10 minutes

24:0:0 for 24 hours

4.8.2.5.1.11.3 Green Rate

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Performance Test / Green Rate

Green test traffic will be generated at this percentage of the CIR. By default this is set to 100%, however, it may be desirable to reduce this during debug of a network problem.

4.8.2.5.1.11.4 Green Burst

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Performance Test / gReen Burst

Green test traffic will be generated at this percentage of the CBS. By default this is set to 100%, however, it may be desirable to reduce this during debug of a network problem.

4.8.2.5.1.11.5 Yellow Rate

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Performance Test / Yellow Rate

Yellow test traffic will be generated at this percentage of the CIR. By default this is set to 0%,

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.1.11.6 Yellow Burst

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / Performance Test / yEllow Burst

Yellow test traffic will be generated at this percentage of the CBS. By default this is set to 0%,

4.8.2.5.2 Report Header

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report Header

This menu allows for a user defined header to be added to the top of the test report. By default the user defined header is disabled but once enabled it is configured line by line as shown:


REPORT HEADER

1st line

2nd line

3rd line

4th line

5th line

6th line

7th line

8th line

Clear all text

Display header <display>




FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.2.1 Display Screen

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report Header / Display header

This menu displays the report header as it will be appear


Test Report Header

------------------

***************************************************

Metrodata Service Confiuration Test

Test Method: Y.1564

Customer:CustomerA

Link:London-NewYork

Tester: A.N.Engineer

***************************************************


4.8.2.5.3 State

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / State

This setting controls the state of the tester,

STOPPED Test not running, or completed

RUNNING Test running

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.4 View Results

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / View Results

While the test is running, or has completed the view results allows the test report to be viewed as it is compiled. An example of the test report is shown below:

***************************************************


Test Method: Y.1564

Customer:CustomerA

Link:London-NewYork


***************************************************

unit node name: "FCM9004_CO"

test regime: Y.1564

---

Flow 1 "Customer1"

Bandwidth profile: CIR (bps): 50M

CBS (bytes): 20k

EIR (bps): 50M

EBS (bytes): 20k

Bandwidth profile mode: Utilisation

Colour-aware: On

Colour method: PCP, Yellow: 0-3

Green: 4-7

Service acceptance criteria: FLR (%): 0.001

FTD (us): 10000

FDV (us): 1000

AVAIL (%): 99.999

MTU: 10240

Local MAC address: 00:c0:81:00:13:ae

Remote MAC address: 00:c0:81:00:13:ad

S-VLAN ID: none

C-VLAN ID: 102

Configuration Test phase time: 0:03

Frame Size (bytes): 68,260,516,799,1522

Date and time of test: 16:47:23 Thu 30/10/2014

Y.1564 Configuration Test

-------------------------

time IR FL FTD FDV

test (s) (Mbps) count FLR (%) ave(us) good(%) ave(us) good(%)

-----------------------------------------------------------------------

CIR

st 1 3 12.11 0 0.000 117.4 100.000 102.3 100.000 pass

st 2 3 24.23 0 0.000 117.5 100.000 102.3 100.000 pass

st 3 3 36.34 0 0.000 130.3 100.000 88.8 100.000 pass

st 4 3 48.46 0 0.000 143.0 100.000 76.7 100.000 pass

EIR

grn 3 48.46 0 0.000 230.7 100.000 86.5 100.000 pass

Pol

grn 3 48.46 0 0.000 225.3 100.000 86.9 100.000 pass

CBS 3 48.46 0 0.000 143.0 100.000 76.7 100.000 pass

EBS 3 48.46 0 0.000 143.0 100.000 76.7 100.000 pass

---

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

Flow 2 "Customer2"

Bandwidth profile: CIR (bps): 50M

CBS (bytes): 20k

EIR (bps): 0

EBS (bytes): 0

Bandwidth profile mode: Utilisation

Colour-aware: On

Colour method: PCP, Yellow: 0-3

Green: 4-7

Service acceptance criteria: FLR (%): 0.010

FTD (us): 1000

FDV (us): 1000

AVAIL (%): 99.990

MTU: 10240

Local MAC address: 00:c0:81:00:13:ae

Remote MAC address: 00:c0:81:00:13:ad

S-VLAN ID: none

C-VLAN ID: 1001

Configuration Test phase time: 0:03

Frame Size (bytes): 68,260,516,799,1522

Date and time of test: 16:47:56 Thu 30/10/2014

Y.1564 Configuration Test

-------------------------

time IR FL FTD FDV

test (s) (Mbps) count FLR (%) ave(us) good(%) ave(us) good(%)

-----------------------------------------------------------------------

CIR

st 1 3 12.11 0 0.000 117.4 100.000 102.3 100.000 pass

st 2 3 24.23 0 0.000 117.5 100.000 102.3 100.000 pass

st 3 3 0.00 0 0.000 130.3 100.000 88.8 100.000 pass

st 4 3 0.00 0 0.000 143.0 100.000 76.7 100.000 pass

EIR skip

Pol skip

CBS 3 0.00 0 0.000 143.0 100.000 76.7 100.000 pass

EBS skip

Performance Test duration: 1:00

Date and time of test commencement: 16:48:19 Thu 30/10/2014

Y.1564 Performance Test

-----------------------

IR FL FTD FDV AVAIL

Fl (Mbps) count FLR (%) ave(us) good(%) ave(us) good(%) (%)

------------------------------------------------------------------------

1 48.46 0 0.000 216.1 100.000 85.9 100.000 100.000 pass

2 48.46 0 0.000 216.6 100.000 85.6 100.000 100.000 pass

Date and time of test completion: 16:50:22 Thu 30/10/2014

---

testing complete

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.5.5 Report File Name

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report file Name

This option defines the report file name which will be used for TFTP. By default the name comprises the unit type and MAC address for identification.

When a test has completed, the report will be automatically sent to the defined TFTP server.

4.8.2.5.6 Send Report

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / sEnd Report

Once a report has been generated, the send report command will use TFTP to upload the test report.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.6 Manual Mode Testing

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing

Whilst Y.1564 testing allows for semi automated validation of the SLA defined per flow, it may be desirable to perform a more detailed or tightly controlled test to diagnose a network, or service problem and this is the purpose of the Manual Mode tester.

Manual mode may be used to assist with diagnosing a problem with the 1564 test or for simply performing a manual test. When the manual mode is selected following a 1564 test the parameters are all inherited from the 1564 test. Additionally, the test summary also shows the last portion of the 1564 test that was performed.

The manual mode test setup menu is shown below:


FLOW TESTING

test Regime Manual Control

test Duration 0:03

maNual Setup <menu>

tEst Summary <display>

State Stopped



4.8.2.6.1 Test Duration

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test Duration

The manual tester will run for the configured time. The time is entered in the format:

Hours : Minutes : Seconds

Note, the duration must include all three parameters, such that a 30 second test is configured as 0:0:30

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.6.2 State

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / State

When the test traffic is configured, clear the results and then change the state to Running. The test will then run for the defined test period.

Stopped Test Not Running

Running Test Running

4.8.2.6.3 Manual Setup

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup

The Manual Setup Menu configures the tester parameters. The menu is shown below:

Metrodata FCM9004 "FCM9004_CO" Alarms: none

MANUAL SETUP

Frame Content <menu>

frame Rates <menu>

Monitor <menu>



FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.6.3.1 Frame Content

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content

This menu is used to define the test frame to use and is shown below:


FRAME CONTENT

Remote MAC 00:c0:81:ff:00:00

Local MAC 00:c0:81:00:13:ae

Flow 1

S-VLAN None

C-VLAN 102

PCP 0

dEI -

frAme Size(s) 516

paYload MD

DSCP -



4.8.2.6.3.1.1 Remote MAC

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / Remote MAC

This is the MAC address used as the destination address within the test packets. By default it is set to the Metrodata WAN Loopback address.

00:C0:81:FF:00:00 WAN Loopback Address

00:C0:81:FF:00:01 User Port Loopback Address

Where another FCM9004 is not available at the remote end, but another device is providing the MAC DA/SA swapping function this address may be changed.

Where another address is used, if the OUI is metrodata ( 00:C0:81 ) then bit 24 is automatically set to select the loopback port of the remote device.

4.8.2.6.3.1.2 Local MAC

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content /

Local MAC

This is the MAC address of this unit. It is a fixed value, and is used as the Source Address for all test packets.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.6.3.1.3 Flow

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / Flow

In order for a test to be performed, at least one flow must have been configured. When the flow number is entered, the S/C-Tag information is retrieved and used for the test traffic stream.

4.8.2.6.3.1.4 S-VLAN / C-VLAN

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / s-VLAN

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / c-vLAN

This menu item shows the Tag structure for the test packets.

By default, the C-VLAN will assume the ID of the Control VLAN as defined in the flow configuration. This may be changed to use any other ID that is part of the flow definition.

4.8.2.6.3.1.5 PCP

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / PCP

Where the test frame is tagged, this defines the PCP tag priority of the outer tag.

4.8.2.6.3.1.6 DEI

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / dEI

Where the test frame is S-tagged, this defines the DEI value, effectively marking the frame green or yellow.

4.8.2.6.3.1.7 Frame Size(s)

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / frAme Size(s)

To simulate real world traffic, the test traffic may comprise up to 5 packet sizes which are sent in a repeating sequence.

The packet sizes supported are as per the Y.1564 specification

A 64 bytes

B 128 bytes

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

C 256 bytes

D 512 bytes

E 1024 bytes

F 1280 bytes

G 1518 bytes

H MTU, defined as Max Packet Size

The packet size is defined excluding tags, such that where a 64 byte packet size is requested, the actual packet may be

Untagged 64 Bytes

Single Tag 68 Bytes

Double Tag 72 Bytes

When defining the packet size/mix either the numerical value, or assigned letter may be used as below:

64, 128, 1024 Send sequence of three packets with size 64/128/1024

acdeh Send a sequence of five packets with frame sizes 64/256/512/1024 and MTU

4.8.2.6.3.1.8 Payload

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / paYload

The payload used in the test frame may be a metrodata layer 2 test frame structure with an incrementing payload, or alternatively an RFC2544 complient IP/UDP echo reply frame.

4.8.2.6.3.1.9 DSCP

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / Frame Content / DSCP

When the payload is set to IP, the DSCP value may be defined here.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.6.3.2 Frame Rates

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup / frame Rates

This menu is used to define the test traffic generation rates and burst sizes as shown below:


FRAME RATES

rate Type CIR/CBS

frame Rate 2937

IR 25.188% of CIR

Frames/Burst 1

BS 2.680% of CBS



4.8.2.6.3.2.1 Frame Rate

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup/ frame Rates / frame Rate

The transmission rate for the test may be defined by directly entering the packet per second rate.

4.8.2.6.3.2.2 Information Rate (IR)

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup/ frame Rates / IR

Where a flow has an SLA configured, the option to set the transmit rate to be a percentage of the CIR is available to simplify test setup.

4.8.2.6.3.2.3 Frames/Burst

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup/ frame Rates / Frames/Burst

The Test generator can send traffic as either a constant, evenly spaced traffic stream or as bursty traffic sending bursts of packets.

1 Constant Rate Traffic

2+ Burst of 2+ packets at a time with the burst spaced such that the bandwidth/packet rate is adhered to.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.6.3.3 Burst Size (BS)

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup/ frame Rates / BS

Where a flow has an SLA configured, the option to setup the burst size as a % of the CBS is available to simplify configuration.

4.8.2.6.3.4 Monitor

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / maNual Setup/ Monitor

The monitor menu defines the delay and variation thresholds for a packet to be declared good. The values are entered in uS.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.6.4 Test Summary

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / tEst Summary

The results of the test are displayed in the test summary display as shown below:


Test Summary Running Time: 0:01

------------

Flow/SLA Test Results

-------------------------------- ------------------------------

Flow 1 Tx Frames 4088

S-VLAN - Tx Bandwidth (fps) 2898

C-VLAN 102 Tx Bytes 2191168

Frame Size (bytes) 516 Tx Bandwidth (bps) 12427047

CIR (bps) 50M Tx Bandwidth (%CIR) 24.854

CBS (bytes) 20000 Rx Frames 4088

EIR (bps) 50M Rx Bandwidth (fps) 2898

EBS (bytes) 20000 Rx Bytes 2191168

Rx Bandwidth (bps) 12427047

Rx Bandwidth (%CIR) 24.854

Lost Frames 0

Frame Loss (%) 0.001 Frame Loss (%) 0.000

Delay max (us) 1000 Delay min/ave/max (us) 18.6/18.7/19.1

Delay Good (%) 100.000

Delay Var max (us) 1000 DV min/ave/max (us) 0.0/0.0/0.5

DV Good (%) 100.000


The running time shows the time that the test has been running for and will keep incrementing on each refresh until the test duration is complete.

Whilst a test is in progress, the Lost Frame count includes both Lost Frames and Frames currently in transit. While a test is running, it is likely that the lost frames count will show a number of packets, if this is increasing it means packets are being lost, if it stays constant then these are packets in flight.

At the completion of the test, the lost frame count truly reflects the number of frames lost during the test.

4.8.2.6.5 Clear Results

Before running a test, the results should be cleared.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.7 RFC2544 Testing

The FCM9003 supports testing the throughput and latency of the WAN port connection according to the RCF2544 standard at either Layer 2, or Layer 3.

The menu to configure the RFC2544 test is as follows:


FLOW TESTING

test Regime RFC2544

test pArameters <menu>

report Header <menu>

State Stopped

View Report <display>

report file Name fcm9004_00c0810013ae.rep

sEnd Report



4.8.2.7.1 Test Parameters

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters

The RFC2544 test may be controlled using this menu,


TEST PARAMETERS

Layer L2

Flows -

remote Mac 00:c0:81:ff:00:00

throughput test:

1 - time 60s

2 - retries 0

latency test:

3 - rate 90% of Throughput

4 - time 60s



The RFC2544 test has two phases, the first tests the throughput by measuring the maximum rate at which no packets are lost, and the second measures the latency across the link.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.7.1.1 Layer

The FCM9003 supports performing the RFC2544 test at either layer 2, where the target is defined by MAC address, or at layer 3, where the target is defined by IP address.

Regardless of L2/L3 selection, the packet payload is UDP as defined in the RFC2544 standard.

4.8.2.7.1.2 Flows

When the RFC2544 test uses layer 2 mode, the test must be attached to a flow to determine the end to end VLAN configuration.

4.8.2.7.1.3 Remote MAC

When the RFC2544 test uses layer 2 mode the target loopback is defined by MAC address. For a Metrodata FCM900x EDD peer, the following target MAC addresses should be used

00:C0:81:FF:00:00 Generic Remote WAN Loopback

00:C0:81:8x.xx.xx Unique Remote WAN Loopback

00:C0:81:FF:00:01 Generic User Port Loopback

4.8.2.7.1.4 Remote IP

When the RFC2544 test uses layer 3 mode the target loopback is defined by IP address. The tester will use the device IP routing table to determine the flow, or port to use for this test to determine VLAN requirements.

The test will ARP to discover the remote device. Should ARP fail the test will abort.

4.8.2.7.1.5 UDP Port

When running RFC2544 in L3 mode, the UDP port needs to be defined and must match the loopback UDP port. By default this is set to UDP 7 (Echo).

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.7.1.6 Throughput Test Time

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / test pArameters / 1

During the throughput test the test will start by sending frames at 100% utilisation of the configured WAN speed. If packets are lost then the rate is backed off by 50%. The test then uses a binary search method to home in on the maximum rate at which no packets are lost. During this search phase each test is performed for 10 seconds.

Once the maximum rate at which no packets are lost is found, the test is run at that rate but for the configured throughput test time. The longer the time the more valid the test is.

Sometimes it is possible that packet buffers prevented packet loss during the 10 second search, but the longer throughput test causes buffer overflow and packet loss in which case the rate is backed off by 1% and rerun until a loss less test is performed.

4.8.2.7.1.7 Throughput Test Retries


The throughput test is always run once, however if it fails it may be retried again. This parameters defines how many retries are attempted. Once the test passes, it moves onto the next phase.

4.8.2.7.1.8 Latency Test Rate


In most real networks, the throughput figure will involve some packet buffering and as such gives a much higher latency reading. The rate allows for a lower rate to be used to measure latency due to an uncongested link.

4.8.2.7.1.9 Latency Test Time


The latency test time defines the period over which the latency is measured. Whilst 2544 calls for one packet every so often to be measured, the FCM9004 measures the latency of every packet.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.7.2 Report Header

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report Header

This menu allows for a user defined header to be added to the top of the test report. By default the user defined header is disabled but once enabled it is configured line by line as shown:


REPORT HEADER

1st line

2nd line

3rd line

4th line

5th line

6th line

7th line

8th line

Clear all text

Display header <display>




4.8.2.7.2.1 Display Screen

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report Header / Display header

This menu displays the report header as it will be appear


Test Report Header

------------------

***************************************************


Test Method: RFC2544

Customer:CustomerA

Link:London-NewYork


***************************************************


FCM9003 USER MANUAL

76-02-100 Rev.A of 216

4.8.2.7.3 Flows

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report Header / Flows

Since RFC2544 tests the throughput of the WAN port, only a single flow should be tested at a time.

4.8.2.7.4 State

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report Header / State

This menu item controls the state of the test.

4.8.2.7.5 View Results

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report Header /View Results

While the RFC2544 test is running, or once completed, the view results command displays the test report as it is generated. An example test report is shown below:

***************************************************


Test Method: RFC2544

Customer:CustomerA

Link:London-NewYork


***************************************************

test regime: RFC2544

unit node name: "FCM9003"

unit mac address: 00:c0:81:00:13:ae

start time: 13:13:49 Mon 3/11/2014

---

testing Flow1 "Customer1"

RFC2544 Throughput Test:

frame time rate utilisa- lost frames

size (s) (fps) tion (%) count (%) result

--------------------------------------------------------

68 10 1420455 100.000 0 0.000 pass

68 60 1420455 100.000 600 0.001 fail

68 60 1404494 98.876 0 0.000 pass

128 10 844595 100.000 0 0.000 pass

128 60 844595 100.000 220 0.000 fail

128 60 838926 99.329 0 0.000 pass

256 10 452899 100.000 0 0.000 pass

256 60 452899 100.000 0 0.000 pass

512 10 234962 100.000 0 0.000 pass

512 60 234962 100.000 0 0.000 pass

1024 10 119732 100.000 0 0.000 pass

1024 60 119732 100.000 0 0.000 pass

1280 10 96154 100.000 0 0.000 pass

1280 60 96154 100.000 0 0.000 pass

1518 10 81274 100.000 0 0.000 pass

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

1518 60 81274 100.000 2 0.000 fail

1518 60 80438 98.970 0 0.000 pass

RFC2544 Throughput Test result summary:

media max measured

information

packet speed throughput throughput utilisation utilisation rate

size (Mbps) (fps) (fps) (Mbps) (%) (Mbps)

-------------------------------------------------------------------------

68 1000 1420455 1404494 988.76 98.876 764.04

128 1000 844595 838926 993.29 99.329 859.06

256 1000 452899 452899 1000.00 100.000 927.54

512 1000 234962 234962 1000.00 100.000 962.41

1024 1000 119732 119732 1000.00 100.000 980.84

1280 1000 96154 96154 1000.00 100.000 984.62

1518 1000 81274 80438 989.70 98.970 976.83

RFC2544 Round-Trip Latency Test:

frame time rate utilisa- latency (us) variation (us)

size (s) (fps) tion (%) min max ave max ave

------------------------------------------------------------------

68 60 1262626 88.889 4.7 6.1 4.8 1.3 0.0

128 60 753012 89.157 6.7 8.8 6.7 2.0 0.0

256 60 407166 89.902 10.8 12.9 10.8 2.0 0.0

512 60 211506 90.017 19.0 20.1 19.0 1.0 0.0

1024 60 107759 90.000 35.3 36.8 35.4 1.3 0.0

1280 60 86565 90.028 43.5 44.8 43.6 1.1 0.0

1518 60 72380 89.056 51.1 52.2 51.2 0.9 0.0

---

testing complete

The report is divided into three sections, the first section details the search process whilst the test determines the maximum throughput. The next two sections summarise the results of the throughput and latency tests.

4.8.2.7.6 Report File Name

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / report file Name

This option defines the report file name which will be used for TFTP. By default the name comprises the unit type and MAC address for identification.

When a test has completed, the report will be automatically sent to the defined TFTP server.

4.8.2.7.7 Send Report

Menu Tree: Main Set-Up / circuit/flow Tests / flow Testing / sEnd Report

Once a report has been generated, the send report command will use TFTP to upload the test report.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

APPENDIX 1 Initial Serial Connection to the FCM9003

The FCM9004 is equipped with a standard RS-232/V.24 terminal interface presented on a 9 way D-Female connector. The pin out of the connector is standard, and as such allows for direct connection to a PC serial port, or USB to serial adaptor.

The pin out of the connector is as shown below:

Pin Direction Signal

1

2 Out Receive Data

3 In Transmit Data

4 In DTR

5 Signal Ground

6

7

8

9

The default setting for the terminal port is as below:

Baud Rate 19200Baud

Bits 8 bit

Parity None

Start Bits 1

The default password for the unit is “FCM9003”

Should the terminal display “Console Disabled” this indicates that the Zero Touch Config, ZTC option is enabled. To default the unit into normal boot mode move bit 7 and 8 to the OFF position and power cycle. Once the terminal has displayed the main setup menu, return switch 8 to the default ON position.

FCM9003 USER MANUAL

76-02-100 Rev.A of 216

APPENDIX 2 Initial LAN connection to FCM9003

Following a cold start, it is possible to access the FCM9003 using LAN Port 4 which will be configured for management access using either TELNET, HTTP or SSH.

The default IP address for access via LAN4 is 169.254.42.42

LAN4 is connected to the Auxiliary Port of the Management Entity and provides a method of configuring the device regardless of VLAN or Flow settings.

By default, the password is “FCM9003”, however once configured the aux port uses the same password or TACACS security as the main management interface.

When multiple units are being configured via the auxilliary port using the default IP address the ARP table will need to be cleared after completing configuration of one device and starting the next. For a windows PC, open a DOS/CMD window and then issue an “arp –d 169.254.42.42” command.

When configuring devices over the Aux port, the first parameter to configure is the Timeout found under the TELNET/SSH/HTTP menu. It is normal to set this parameter to 300 to give a 5 minute UI timeout.

When configuring the FCM9003 using the aux port, certain parameters will force LAN port 4 to the down state, however the software will recover and continue with the management session..

FCM9003 User Manual Version 9 · 2016. 7. 12. · FCM9003 USER MANUAL 76-02-100 Rev.A Page 1 of 216...

Documents

Transcript of FCM9003 User Manual Version 9 · 2016. 7. 12. · FCM9003 USER MANUAL 76-02-100 Rev.A Page 1 of 216...