koniec wykładu I - tele.pw.edu.plmariusz/lectures/zst_wyklad5.pdf · Institute of...

Post on 21-Jul-2020

1 views 0 download

Transcript of koniec wykładu I - tele.pw.edu.plmariusz/lectures/zst_wyklad5.pdf · Institute of...

Institute of Telecommunications

mariusz@tele.pw.edu.pl

koniec wykładu IV

Institute of Telecommunications

mariusz@tele.pw.edu.pl

MIB-2

LP3S3

S2

LP1 RA1LA1 RP1

LA2 LP2 RA2 RP2

LA3

S1

RA3 RP3

1.3.6.1.2.1.6.13.1.2.LA2.LP2.RA2.RP2

tcpConnTable OBJECT-TYPESYNTAX SEQUENCE OF

TcpConnEntryACCESS not-accessibleSTATUS current DESCRIPTION “”

::= { tcp 13 }

tcpConnEntry OBJECT-TYPESYNTAX TcpConnEntryACCESS not-accessibleSTATUS current DESCRIPTION “”INDEX { tcpConnLocalAddress,

tcpConnLocalPort,tcpConnRemAddress,tcpConnRemPort }

::= { tcpConnTable 1 }

...

(1)tcpConnEntry

tcpConnState (1)

tcpConnLocalAddress (2)

tcpConnLocalPort(3)

tcpConnRemAddress (4)

tcpConnRemPort (5)tcpInErrs OBJECT- TYPE

SYNTAX Counter ACCESS read-onlySTATUS current DESCRIPTION“”

::= { tcp 14 }

1.3.6.1.2.1.6.14.0

mib-2 (1) [1.3.6.1.2.1]

system (1)

interfaces (2)

at (3)

ip (4)

icmp (5)

tcp (6)

udp (7)

egp (8)

transmission (10)

snmp (11)

(14)

(13)

tcpRetransSeg (12)

tcpRtoAlgorithm (1)

tcpConnTable

tcpInErrs

tcpOutRsts (15)

Institute of Telecommunications

mariusz@tele.pw.edu.pl

SNMP SMIStructure of Management Information

Institute of Telecommunications

mariusz@tele.pw.edu.pl

SMI - normalizacja

• SMIv1

• Structure and identification of management information for TCP/IP-based internets

• RFC 1065 – 1988, RFC 1155 – 1990

• Concise MIB definitions

• RFC 1212 – 1991

• Convention for defining traps for use with the SNMP

• RFC 1215 – 1991

• SMIv2

• Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)

• RFC 1442 – 1993, RFC 1902 – 1996, RFC 2578 – 1999

• Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)

• RFC 1443 – 1993, RFC 1903 – 1996, RFC 2579 - 1999

Institute of Telecommunications

mariusz@tele.pw.edu.pl

SMI – typy podstawowe

• Application-wide

• INTEGER (-2147483648..2147483647)

• OCTET STRING(size(0..65535))

• OBJECT IDENTIFIER

• Defined types

• Integer32 ::= INTEGER (-2147483648..2147483647)

• IpAddress ::= OCTET STRING (SIZE (4))

• Counter32 ::= INTEGER (0..4294967295)

• Gauge32 ::= INTEGER (0..4294967295)

• Unsigned32 ::= INTEGER (0..4294967295)

• TimeTicks ::= INTEGER (0..4294967295)

• Opaque ::= OCTET STRING

• Counter64 ::= INTEGER (0..18446744073709551615)

Institute of Telecommunications

mariusz@tele.pw.edu.pl

SMIv2 – struktura definicji MIB

• metka modułu (Module Identity)

• LAST-UPDATED UtcTime

• ORGANIZATION „text”

• CONTACT „text”

• DESCRIPTION „text”

• Revisions

• odwołania do zewnętrznych modułów (IMPORTS)

• definicje typów (Textual Conventions)

• definicje obiektów (Object Type)

• definicje meldunków (Notification Type)

Institute of Telecommunications

mariusz@tele.pw.edu.pl

RFC 2578 - TEXTUAL-CONVENTION

InstancePointer ::= TEXTUAL-CONVENTIONSTATUS obsolete DESCRIPTION "A pointer to either a specific instance of a MIB object or a conceptual row of a MIB

table in the managed device. In the latter case, by convention, it is the name of the particular instance of the first accessible columnar object in the conceptual row. The two uses of this textual convention are replaced by VariablePointer and RowPointer,

respectively."

SYNTAX OBJECT IDENTIFIER

VariablePointer ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A pointer to a specific object instance. For example, sysContact.0 or ifInOctets.3."

SYNTAX OBJECT IDENTIFIER

Institute of Telecommunications

mariusz@tele.pw.edu.pl

OBJECT-TYPE - sysUpTime

sysUpTime OBJECT-TYPESYNTAX Time-TicksACCESS read-onlySTATUS current (dawnej mandatory)DESCRIPTION “Time since the network management portion of the system was last re-initialised.

::= {system 3}

mib-2 (1) [1.3.6.1.2.1]

system (1)

interfaces (2)

at (3)

ip (4)

icmp (5)

tcp (6)

udp (7)

egp (8)

transmission (10)

snmp (11)

1.3.6.1.2.1.1.3

Institute of Telecommunications

mariusz@tele.pw.edu.pl

OBJECT-TYPE ipNetToMediaTable (1)

ipNetToMediaTable OBJECT-TYPESYNTAX SEQUENCE OF IpNetToMediaEntryACCESS not-accessibleSTATUS current (dawnej mandatory)DESCRIPTION

"The IP Address Translation table used for mapping from

IP addresses to physical addresses."

::= { ip 22 }

mib-2 (1) [1.3.6.1.2.1]

system (1)

interfaces (2)

at (3)

ip (4)

icmp (5)

tcp (6)

udp (7)

egp (8)

transmission (10)

snmp (11)

ipNetToMediaTable (22)

ipNetToMediaEntry (1)

ipNetToMediaIfIndex (1)

ipNetToMediaPhysAddress (2)

ipNetToMediaNetAddress (3)

ipNetToMediaType (4)

Institute of Telecommunications

mariusz@tele.pw.edu.pl

NOTIFICATION-TYPE

linkUp NOTIFICATION-TYPE

OBJECTS { ifIndex }

STATUS current

DESCRIPTION "A linkUp trap signifies that the SNMPv2 entity,

acting in an agent role, recognizes that one of the communication links represented in its configuration has

come up."

::= { snmpTraps 4 }

internet (1)

1.3.6.

snmpV2(6)

mib-2 (1)

mgmt( 2)

snmpModules (3)

snmpMIB(1)

snmpMIBObjects(1)

snmpTraps(5)

linkUp(4)

1.3.6.1.6.3.1.1.5.4

Institute of Telecommunications

mariusz@tele.pw.edu.pl

MPLSMulti-protocol Label Switching

Institute of Telecommunications

wybrane (z ponad 100) dokumenty RFC

• MPLS

• RFC3031 Multiprotocol Label Switching Architecture January 2001

• RFC3032 MPLS Label Stack Encoding January 2001

• sygnalizacja

• RFC3209 RSVP-TE: Extensions to RSVP for LSP Tunnels December 2001

• RFC5036 LDP Specification L. Andersson October 2012

• RFC3214 LSP Modification Using CR-LDP January 2002

• RFC3107 Carrying Label Information in BGP-4 May 2001

• VPN

• RFC4364 BGP/MPLS IP Virtual Private Networks (VPNs) February 2006

• RFC4365 Applicability Statement for BGP/MPLS IP Virtual PrivateNetworks (VPNs) February 2006

• RFC2917 A Core MPLS IP VPN Architecture September 2000

Institute of Telecommunications

IP forwarding -- FIB longest match

47.1

47.247.3

IP 47.1.1.1

IP 47.1.1.1

IP 47.1.1.1IP 47.1.1.1

prefix out

47.1 1

47.2 2

47.3 3

prefix out

47.1 1

47.2 2

47.3 3

prefix out

47.1 1

47.2 2

47.3 3

1

2

31

2

1

2

3

IP IP IP

3

Institute of Telecommunications

mpls forwarding

47.1

47.247.3

IP 47.1.1.1

2

100

x

IP 47.1.1.1

prefix FEC

47.1 A

47.2 B

FEC

A

B

out

1

1

label

100

200

out

1

2

label

x

400

in

3

3

label

100

200

in

3

label

x

2

1

prefix out

47.1 1

47.2 2

47.3 3

IP IP IP

MPLS MPLS MPLS

1

2

31

2

1

2

3

3

Institute of Telecommunications

etykieta MPLS Ethernet, PPP

• • • pakiet IP

label sexp TTL

label [20] exp [3] - experimental (DSCPs – różne opcje kodowania)s [1] - bottom of the stackTTL [8] - Time To Live

LNL1

ramka warstwy 2

payload

Institute of Telecommunications

mariusz@tele.pw.edu.pl

label merging (ii)

15

6

13

17

1517

Institute of Telecommunications

mariusz@tele.pw.edu.pl

P1

P2

P3

tunele MPLS (i)

PE1

PE2

PE3

• router wewnętrzny musi utrzymywać FT entry dla każdego wirtualnego łącza (ścieżki MPLS) - słaba skalowalność

• jak ograniczyć liczbę wierszy?

• umieścić łącza w tunelach

Institute of Telecommunications

tunele MPLS (ii)

CE B2

CE A2

PE A P PE B

CE B1

CE A1

15

6

13

12 1217

1522 2217

Institute of Telecommunications

konfigurowanie LSP via SNMP

2

47.1

47.247.3

NMS

A

(MIB)

NMS

Institute of Telecommunications

mariusz@tele.pw.edu.pl

koniec wykładu V