8408 - IONOS-NMS - FMX - éd Aout 2011 - A.pdf

IONOS-NMS For FMX

Training Handbook

AET/TAC/ 8408 July 2011 issue

8408 IONOS-NMS for FMX July 2011 issue

Page ii IONOS-NMS for FMX Training handbook

DISCLAIMER Documents supplied during the training sessions are not contractual. Descriptions, schematics, diagrams and figures are for illustration only and can be changed without notice. For contractual figures, please refer to official documentation.


IONOS-NMS Training handbook Page iii

SUMMARY

MODULE 1

To be able to configure FMX for IONOS-NMS management


Page iv IONOS-NMS for FMX Training handbook

IONOS-NMS for FMX Training handbook Page 1-1

IONOS-NMS for FMX

Module 1.

Goal : To be able to configure FMX for IONOS-NMS

management

MODULE 1. 1-1

1.1. FMX MANAGEMENT 1-3 1.1.1. FRAME RELAY 1-5 1.1.2. GIE-P / GIE-S 1-10 1.2. SNMP 1-11 1.2.1. FMX HEADER WITH GIE-S 1-13 1.2.2. FMX HEADER WITH GIE-P 1-14 1.3. FMX NETWORK CONFIGURATION 1-18


Page 1-2 IONOS-NMS for FMX Training handbook

1.3.1. PARAMETERS OF CONFIGURATION 1-19 1.3.2. PROXY CONFIGURATION (GIE-P) 1-25 1.3.3. GIE-S CONFIGURATION 1-28 1.4. FMX NETWORK EXAMPLE 1-33 1.5. FMX NETWORK MANAGEMENT WITH IONOS-NMS 1-36 1.6. EXERCISE : NETWORK OF FMX 1-41 1.6.1. CORRECT VERSION 1-45 1.7. PROCESS 1-49 1.7.1. ATLANTIS CARD CONFIGURATION ON PC PROXY 1-49 1.7.2. CREATION OF A FMX (GIE-P HEADER) ON IONOS-NMS 1-51 1.7.3. GIE-S CARD CONFIGURATION IN HEADER MODE 1-52 1.7.4. GIE-S CARD CONFIGURATION IN NON-HEADER MODE 1-53



1.1. FMX management Slide 2

2| AET/TAC 8408 | July 2011

IONOS-NMS : Operation and management

The LCT provides all operation and monitoring functions of local or remote FMX :

Set up of shelves, cards, synchronization parameters.

Display of defaults, alarms and performances.

Maintenance operations such as loopbacks and inventories.

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 3

3| AET/TAC 8408 | July 2011

IONOS-NMS : Operation and management Its possible from a local FMX to manage a remote FMX. A FMX network is composed of FMX connected together via

management channels ( DLCI):

LCT(local)

Network of FMX

Local FMX

Remote FMX

Local connection :- Direct,

- Via MODEM.

______________________________________________________________________________________________

___________________________________________________________________________________________



1.1.1. Frame Relay Slide 4

4| AET/TAC 8408 | July 2011

IONOS-NMS : Frame Relay

from 1 to 9FMX

FMX

from 1 to 8FMX

Up to :64 FMX and/or SAGEM 2048.Only 50 FMX when using snmpLCT (IONOS-NMS).

over a maximum of 10 levels.FMX

FMX FMX

FMX Header

LCT

* To reduce bandwidth consumption, management of the remote FMX is performedvia TS0 (7 directions) + 2 x 64kbps TS.

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 5

5| AET/TAC 8408 | July 2011

Frame Relay (2Mb/s G704) : 8 Kbps (2 bits of the odd TS0s). 64 Kbps (any IT).

P1/P2 : 64 Kbps V24/V11. Used to interconnect 2 Frame Relay FMX subnetworks .

DLCI (Data Link Connection Identifier).


______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 6

6| AET/TAC 8408 | July 2011

IONOS-NMS : Frame RelayFMX 2

(Remote)

GIE-S

Frame relayFunction

CARTE COB

Orderwire

Network of FMX

FMX 1(Local)

COBGIE-SLCT(local)

Connection :

- LOCAL- VIA MODEM

COB A2S

A2S

Frame relayFunction Orderwire

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 7

7| AET/TAC 8408 | July 2011


G704orderwireFR

GIE

COB

DLCI

IP-IS

O

To the manager

GIE

LCT

COB

To an other FMX

FMX1 FMX2

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 8

8| AET/TAC 8408 | July 2011

FMX Header : Between IONOS-NMS and others FMX of the Frame Relay

management network

FMX none Header.

IONOS-NMS : Management Network

______________________________________________________________________________________________

___________________________________________________________________________________________



1.1.2. GIE-P / GIE-S Slide 9

9| AET/TAC 8408 | July 2011

The GIE card manages the communication between the FMX Header and IONOS-NMS :

GIE-P (P4.3B/P4.3C) : None SNMP card. Use of a Proxy-FMX to translate the SNMP protocol in

proprietary Sagem-FMX protocol.

GIE-S (P4.4A) : SNMP card.

IONOS-NMS : Management Network

______________________________________________________________________________________________

___________________________________________________________________________________________



1.2. SNMP Slide 10

10| AET/TAC 8408 | July 2011

IP

StructureManagementInformation

describesManagementInformation

Base

Management station

NEswith

Embedded SNMP agents

IONOS-NMS based on SNMP

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 11

11| AET/TAC 8408 | July 2011

SNMP Protocol specifies the language used by agents and management stations to communicate.

Protocol : type asynchronous question/answer. Connectionless. over UDP (User Datagram Protocol).

SNMP system handles three kinds of requests :

GET SET TRAP

IP

GET var

GET ANSW

var=5

SET ANSW

var

SET var

=3

TRAPTRAP

Simple Network Management Protocol (SNMP)

______________________________________________________________________________________________

___________________________________________________________________________________________



1.2.1. FMX header with GIE-S Slide 12

12| AET/TAC 8408 | July 2011

1 GIE-S in each FMX Header, other version (GIE-P) possible in others FMX.

IONOS-NMS : FMX Header with GIE-S

IONOSNMS

FMXGROUP

(remote FMX)

IP

Ethernet

FMXHeaderlocal

GIE-

S

FMXGROUP

(remote FMX)FMXHeaderlocal

GIE-

S

J129 connector with RJ45 adaptation.

______________________________________________________________________________________________

___________________________________________________________________________________________



1.2.2. FMX header with GIE-P

Slide 13

13| AET/TAC 8408 | July 2011

PROXY

IP

GET

TRAP iso-IP

GET A

NSW

%&$*#(*!&$

SET

))(@&^$

@#@#^&89

SET A

NSW

H&^9&

*#$

TRAP

IONOS-NMS : FMX Header with GIE-P

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 14

14| AET/TAC 8408 | July 2011

Management by IONOS-NMS using an external proxy. A proxy can manage 50 FMX. FMX Header : 1 for 20 FMX. The FMX Header has to be configured in mode Gateway. FMX none Headers part of the Group are configured none gateway.

IONOSNMS

FMX Group IP

PROXY

PROXY

PC PROXY

EthFMXHeader

GIE-

P

X25

J129

IONOS-NMS : FMX Header with GIE-P

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 15

15| AET/TAC 8408 | July 2011

PROXY

X.25

G704

G704

IONOS-NMS : Example physical presentation

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 16

16| AET/TAC 8408 | July 2011

PROXY

X.25

DLCI 1

DLCI 2

DLCI 3

DLCI 4

IONOS-NMS : Example logical presentation

______________________________________________________________________________________________

___________________________________________________________________________________________



1.3. FMX network configuration Slide 17

17| AET/TAC 8408 | July 2011

FMX network configuration :

IONOS-NMS

______________________________________________________________________________________________

___________________________________________________________________________________________



1.3.1. Parameters of configuration Slide 18

18| AET/TAC 8408 | July 2011

Parameters of configuration :

FMX : An IP/ISO address for each FMX (6 bytes, decimal value < 256 separated by a .). An interface type for each FMX (with the neighbour FMX) : P1, P2 or Frame Relay. An identifier (DLCI) for each Frame Relay communication between two FMX

IP/ISO Addresses : The setting of a frame relay network management for FMX equipment using the

embedded channels of TS0 in the 2 Mbps links requires to take precautions with the IPiso adress on the FMX equipment as follows :

In every FMX of a given frame relay management subnetwork, including the header FMX and those connected via PI/P2 interfaces, The first element of the IPiso address (Network ID) must be UNIQUE.

If there is a mix of P4.4a (GIE-S) FMX equipment and P4.3c (GIE-P) in the subnetwork, the second element of the IPiso adress (Depth) must be ZERO.

IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 19

19| AET/TAC 8408 | July 2011

Parameters of configuration :

FMX Header : FMX with GIE-P card :

An IPv4 address for the Proxy used by the header. X25 parameters (address, clock, DCE/DTE) of the link with the Proxy.

FMX with GIE-S card : An IPv4 address for the header Ethernet parameters (IP address, mask, default gateway, physical

configuration) Managers IP addresses


______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 20

20| AET/TAC 8408 | July 2011

Header using the GIE-P card (P4.3B or P4.3C) : 2 steps :

FMX configuration : Declaration of IP/ISO addresses and interfaces (FR, P1/P2). Creation of Frame Relay connections. Configuration of Gateways (X25, P1/P2).

Proxy configuration : Reading of the current configuration (Load Command). Modification of the configuration (Modify and Build). Loading of the configuration in the Proxy (Send).


______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 21

21| AET/TAC 8408 | July 2011

Management network equipments (GIE-P) :IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 22

22| AET/TAC 8408 | July 2011

Frame Relay connections (GIE-P) :IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 23

23| AET/TAC 8408 | July 2011

FMX Header configuration (GIE-P) :IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________



1.3.2. Proxy configuration (GIE-P) Slide 24

24| AET/TAC 8408 | July 2011

Proxy configuration (GIE-P) :IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________

Slide 25



25| AET/TAC 8408 | July 2011

IONOS-NMS : FMX network configuration Proxy configuration (GIE-P) :

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 26

26| AET/TAC 8408 | July 2011

IONOS-NMS : FMX network configuration Proxy configuration (GIE-P) :

______________________________________________________________________________________________

___________________________________________________________________________________________



1.3.3. GIE-S Configuration Slide 27

27| AET/TAC 8408 | July 2011

Header using the GIE-S card (P4.4A) :

FMX configuration :

Declaration of IP/ISO addresses, interfaces (FR, P1/P2) and identification number ( ID FMX ).

Creation of Frame Relay connections.

Configuration of IPv4 addresses ( Ethernet port, managers list ).


______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 28

28| AET/TAC 8408 | July 2011

Management network equipments (GIE-S) :IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 29

29| AET/TAC 8408 | July 2011

Frame Relay connections (GIE-S) :IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 30

30| AET/TAC 8408 | July 2011

Ethernet port and/or P1/P2 (GIE-S) :IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 31

31| AET/TAC 8408 | July 2011

Managers IP addresses (GIE-S) :IONOS-NMS : FMX network configuration

______________________________________________________________________________________________

___________________________________________________________________________________________



1.4. FMX network example Slide 32

32| AET/TAC 8408 | July 2011

IONOS-NMS : FMX network example (GIE-S)

FR

P2 P1

Ethernet

IONOS NMS

FR

FR

1 2

3 4 5

IP iso = 1.0.1.0.0.0 IP iso = 1.0.2.0.0.0

IP iso = 1.0.3.0.0.0 IP iso = 1.0.4.0.0.0 IP iso = 1.0.5.0.0.0

IPv4 = 192.168.0.172

IPv4 = 192.168.0.1

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 33

33| AET/TAC 8408 | July 2011

Equipment table 1 :

IP iso interface ID Name1.0.1.0.0.0 1 FMX 11.0.2.0.0.0 P2 next 2 FMX 21.0.4.0.0.0 P2 4 FMX 41.0.5.0.0.0 P2 5 FMX 5 1.0.3.0.0.0 FR 3 FMX 3 255.0.0.0.0.0 FR 0 Manager NB : 255.0.0.0.0.0 Type :other = Manager

ROLE : HEADER

TMN - P2 codirectional

Equipment table 2 :

IP iso interface ID Name1.0.2.0.0.0 0 FMX 21.0.1.0.0.0 P1 next 0 FMX 1255.0.0.0.0.0 P1 0 Manager1.0.4.0.0.0 FR 0 FMX 41.0.5.0.0.0 FR 0 FMX 5

P1 codirectional - P2 codirectional


______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 34

34| AET/TAC 8408 | July 2011

Equipment table 3 :

IP iso interface ID Name 1.0.3.0.0.0 0 FMX 3 1.0.1.0.0.0 FR 0 FMX 1 255.0.0.0.0.0 FR 0 Manager P1 codirectional - P2 codirectional

Equipment table 4 : 1.0.4.0.0.0 0 FMX 4 1.0.2.0.0.0 FR 0 FMX 2 1.0.1.0.0.0 FR 0 FMX 1 All equipments 1, 2, 3, 4 and 5 are Gateway 255.0.0.0.0.0 FR 0 Manager P1 codirectional - P2 codirectional

Equipment table 5 : 1.0.5.0.0.0 0 FMX 5 1.0.4.0.0.0 FR 0 FMX 4 1.0.2.0.0.0 FR 0 FMX 2 1.0.1.0.0.0 FR 0 FMX 1 255.0.0.0.0.0 FR 0 Manager P1 codirectional - P2 codirectional


Caution : In case of PC Proxy (with GIE-P)

equipments 3-4-5 are None gateway.

______________________________________________________________________________________________

___________________________________________________________________________________________



1.5. FMX network management with IONOS-NMS Slide 35

35| AET/TAC 8408 | July 2011

FMX network management with IONOS-NMS :

IONOS-NMS

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 36

36| AET/TAC 8408 | July 2011

IONOS-NMS manages on FMX equipments only : FMX configuration/operation. Alarms management.

2Mbps links between FMX are not managed in IONOS-NMS. They can be created in the network topology view. Its only a graphic and static view of the link (no specific alarm

for the link).

IONOS-NMS

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 37

37| AET/TAC 8408 | July 2011

Create subnetworks.

Create a network element (FMX).

Create links between FMX.


______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 38

38| AET/TAC 8408 | July 2011

FMX configuration and exploitation (card, ports, connections,) with the LCT :IONOS-NMS : FMX network exploitation

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 39

39| AET/TAC 8408 | July 2011

Alarms log :

IONOS-NMS : management of Alarms

Current alarms

______________________________________________________________________________________________

___________________________________________________________________________________________



1.6. Exercise : Network of FMX Slide 40

40| AET/TAC 8408 | July 2011

Exercise : Network of FMX Address plan of FMX with GIE.S :

GIE.SIP iso : 1.0.1.0.0.0

GIE.SIP Add : 192.168.0.1/16IP iso : 1.0. 3.0.0.0

GIE.SIP iso : 1.0.2.0.0.0

GIE.SIP iso : 1.0.4.0.0.0

A2 S

Slot14

A2 S

Slot12

A2 S

Slot13

A2 SSlot11

FMX 2

FMX 1 FMX 3

FMX 4

Header1

22

1

1 1

PC Server192.168.0.140255.255.0.0

Eth.

DLCI 1

DLCI 3

DLCI 2

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 41

41| AET/TAC 8408 | July 2011

Management network equipment : Table FMX 1 :

IP iso interface ID Name

Table FMX 2 :IP iso interface ID Name



Exercise : Network of FMX

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 42

42| AET/TAC 8408 | July 2011

FR frames relay connections :DestinationSourceDLCI FMX 1 :

DestinationSourceDLCI

DestinationSourceDLCI

FMX 2 :

FMX 3 :

DestinationSourceDLCI FMX 4 :

Exercise : Network of FMX

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 43

43| AET/TAC 8408 | July 2011

Configuration of the FMX Header (FMX 3) : IP link and P1-P2 link configuration of FMX 3 : Choose : RGT/P2 contra or codirectional IP v4 address : Subnetwork Mask : Default gateway :

Manager Addresses : For the FMX Header :

Exercise : Network of FMX IP link and P1/P2 link configuration :

______________________________________________________________________________________________

___________________________________________________________________________________________



1.6.1. Correct version Slide 44

44| AET/TAC 8408 | July 2011

GIE.SIP iso : 1.0.1.0.0.0

GIE.SIP Add : 192.168.0.1/16IP iso : 1.0. 3.0.0.0

GIE.SIP iso : 1.0.2.0.0.0

GIE.SIP iso : 1.0.4.0.0.0

A2 S

Slot14

A2 S

Slot12

A2 S

Slot13

A2 SSlot11

FMX 2

FMX 1 FMX 3

FMX 4

DLCI 2 DLCI 3

DLCI 1

DLCI 3

Header1

22

1

1 1

PC Server192.168.0.140255.255.0.0

Eth.

DLCI 2DLCI 1DLCI 2

Address plan of FMX with GIE.S :Correct version : Network of FMX

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 45

45| AET/TAC 8408 | July 2011

Table FMX 1 :IP iso interface ID Name1.0.1.0.0.0 0 FMX 11.0.3.0.0.0 FR 0 FMX 3255.0.0.0.0.0 FR 0 Manager


Table FMX 3 :IP iso interface ID Name1.0.1.0.0.0 1 FMX 11.0.2.0.0.0 FR 2 FMX 21.0.3.0.0.0 FR 3 FMX 31.0.4.0.0.0 FR 4 FMX 255.0.0.0.0.0 FR 0 Manager


Correct version : Network of FMX Management network equipment :

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 46

46| AET/TAC 8408 | July 2011

A2S ; Slot14 ; port 2; bits 7 and 8 (8Kbps)1.0.2.0.0.0


2


GIE (64Kbits/s)1.0.1.0.0.0

1DestinationSourceDLCI FMX 1 :


GIE (64Kbits/s)1.0.2.0.0.0

2DestinationSourceDLCI


GIE (64Kbits/s)1.0.3.0.0.0

3


GIE (64Kbits/s)1.0.3.0.0.0

2


GIE (64Kbits/s)1.0.3.0.0.0

1DestinationSourceDLCI

FMX 2 :

FMX 3 :


GIE (64Kbits/s)1.0.4.0.0.0

3DestinationSourceDLCI FMX 4 :

Correct version : Network of FMX FR frames relay connections :

______________________________________________________________________________________________

___________________________________________________________________________________________



Slide 47

47| AET/TAC 8408 | July 2011

Correct version : Network of FMX IP link and P1/P2 link configuration :

Configuration of the FMX Header (FMX 3) : IP link and P1-P2 link configuration of FMX 3 : Choose : RGT/P2 contra or codirectional IP v4 address : 192.168.0.1 Subnetwork Mask : 255.255.0.0 Default gateway : 192.168.0.140 (router @).

Manager Addresses : For the FMX Header : 192.168.0.140

______________________________________________________________________________________________

___________________________________________________________________________________________



1.7. Process 1.7.1. ATLANTIS card configuration on PC Proxy

Access path to ATLANTIS card parameters :

Start > Settings > Control Panel Double click on Network Connections icon > Service > ATLANTIS- Header X25/ISDN (Prima P2) > Properties.

Click on VOIE A & Then on 2 Inside the tools bar.

Type of data circuit DB25

Type of protocol X25

Type of Network Transpac-(FR)

Type of behaviour TERM / DTE or DCE

Recovery block nX25

Disconnections on exit appli Transmission of nX25

Timer of network disconnection Reception of nX25

Transmission of NUI

Click on 4 To see the second window

n of assigned VL 1 Flow ctrl parameters

Number of CVP 0 Transmitted block window 2

Number of incoming VL 0 Received block window 2

n of low mixed VL 1 Transmitted block size 256

n of high mixed VL 128 Received block size 256

n of low outgoing VL

n of high outgoing VL



Click on 4

Link layer: Physical layer:

K Frame window 7 Clock External x If DTE

N2 meter 10 Internal x If DCE

T1 Temporisation 20 Speed rate 64000

Disc before SABM Line interface V24/V28

Transmission of XID Management command

Management signal DTR

Waiting tempo DSR 3

Management signal RI



1.7.2. Creation of a FMX (GIE-P Header) on IONOS-NMS

I Creation of NE on IONOS-NMS : - Open NMS Client. - Create a NE. - Type : FMX P4.3C. - Give a name. - Give a Equipment number ( has to be unique ). - Give the PC Proxy IP address. - Tick the under Proxy box. - Create 2Mbps interface ( virtual, only for style of drawing ).

II PC Proxy configuration :

1. Launch Proxy Configuration from a PC Client.

2. Verify FTP PROFILE

- Click on A then on Modify . - Give the PC Proxy address. - Give User, password and port of the PC Proxy ( ex : administrator ; SaGeM ; 21 ).

3. Make a Load to load all information from the PC Proxy to the PC client. (systematic if we dont want to run over the Proxy configuration)

4. Verify the Configuration

- Proxy : X25@ = 00141 - Manager : IP@ of PC server; ex : 192.168.0.140 - BMX : Configuration of FMX; Make ADD to add one FMX. - ID : Has to correspond to the equipment number of FMX given at the creation of

the NE on IONOS-NMS. - Name : name of the FMX. - @X25 : X25 address of the FMX in gateway mode; ex : 00541 - @IP : IPiso address of the FMX; ex : 1.0.0.0.0.1

5. If we did some modifications ( ex : add FMX )

Make a Built ( we have to be in FTP Profile to turn accessible Built, Load and Send keys).

Then make a Send : Tick the Proxy Reboot box ( modifications will take in count only after a

reboot of the PC Proxy ) Send



1.7.3. GIE-S card configuration in header mode

1- Menu Configuration / general parameters select Gateway

2- Menu management network / TMN link and P1-P2 link configuration

Select TMN/P2

Give the IP address of the FMX Ethernet port ( J129 ) mask and gateway.

3- Menu management network / Manage network Equipment :

4- Change the FMX address ( by default 1.0.0.0.0.0 )

5- Give a FMX ID ( It will be the same one used when creating the NE on IONOS )

6- Add all FMX reachable by this equipment ( address + ID + (type = FMX )+ name + (interface = Frame relay or P2 ))

7- Add NMS ( type other ; ID = 0 ; @ IPv6= 255.0.0.0.0.0 and a name)

8- Menu Management network / Managers Address

Add all NMS IP addresses managing this equipment.

9- Menu Management network / Frame relay connections

Add all frame relay connection

A- Give a name and a DLCI number ( 1 to 1024 )

B- Give IP iso addresses for source and destination entities

C- Select a rate ( 8kbits/s = 2 bits of TS0; 64 kbits/s = GIE or TS different of TS0 )

D- Select source and destination entities ( GIE is always already relayed )

In any case GIE will be always selected as a source.



1.7.4. GIE-S card configuration in non-header mode

1- Menu Configuration / general parameters select Gateway

2- Menu management network / TMN link and P1-P2 link configuration

Select P1/P2 (ex: P1 co-directional /P2 co-directional )

3- Menu management network / Manage network Equipment :

4- Change the FMX address ( by default 1.0.0.0.0.0 )

5- Give a FMX ID = 0

6- Add all FMX reachable by this equipment ( address + ID=0 + type = FMX + name + interface = Frame relay or P1 or P2 )

7- Add NMS ( type other ; ID = 0 ; @ IPv6= 255.0.0.0.0.0 and a name)

8- Menu Management network / Managers Address

No need to put NMS address ( done by the header ).

9- Menu Management network / Frame relay connections

A- Add all frame relay connection

B- Give a name and a DLCI number ( 1 to 1024 )

C- Give IP iso addresses for source and destination entities

D- Select a rate ( 8kbits/s = 2 bits of TS0; 64 kbits/s = GIE or TS different of TS0 ) for source and destination

E- Select source and destination entities ( GIE is always already relayed )

In any case GIE will be always selected as a source.

Date post:	07-Nov-2015
Category:	Documents
Upload:	nscg2011
View:	238 times
Download:	8 times