ADTRAN Vanta 1335 User Manual download pdf (Page 10)

US

8,380,828

B1

7

pared

to

hunting

the

offending

network

device

by

manually

logging

onto

each

network

switch

and

working

through

the

network

sequentially

by

logging

into

each

switch.

In a

preferred

aspect,

a

user-de?ned

?eld

is

added

into

the

LLDP

frame.

This

user-de?ned

?eld

is

a

command

that indi

cates

that

information

should

be

given

by

a

network

switch

concerning

knowledge

about

stored

MAC

addresses.

The

query

is

sent

to

each

network

switch

and

device

and

requests

whether

information

is

known

about

a

particular

MAC

address.

Information

is

sent

back.

The

query

propagates

through

the

network

and

the

modi?ed

frame

includes

a

com

mand

to

shut

down

the

offending

network

device,

for

example,

by

shutting

down

the

port.

FIG.

3A

shows

an

IEEE

802.3

LLDP

frame

100

that

includes

an

LLDP

multicast

address

102

such

as

six

bytes

(octets)

as

a

destination

address

and

a

MAC

address

104

of

about

six

bytes

(octets)

and

an

LLDP

ethertype

106

of

about

two

bytes

(octets)

and

the

LLDPDU

108

(Link

Layer

Discov

ery

Protocol

Data

Unit)

that

is

data

plus

padding

and

typically

is

about

1500

bytes

(octets)

and

the

PCS

110

as

the

frame

control

sequence

of

about

four

bytes

(octets).

The

LLDPU

?eld

typically

contains

the

TLV’s

as

a

chassis

ID, port

ID,

TTL

and

similar

items.

In

one

non-limiting

aspect,

it

is

pos

sible

that

the

LLDP

multicast

address

102

equals

01

-80-C2

00-00-0E

that

is

the

same

as

the

STP

except

for

the

last

octet.

The

information

?elds

in

each

frame

are

contained

in

the

LLDPU

as

the

protocol

data

unit as

a

sequence

of

short,

variable

length,

information

elements

known

as

TLV’s

that

include

the

type,

length

and

value

?elds

and

is

modi?ed

for

use

with

the

system

and

method

as

described.

The

type

iden

ti?es

typically

what

kind

of

information

is

being

sent.

The

length

indicates

the

length

of

the

information

string

in

octets

and

the

value

is

the

actual

information

that

needs

to

be

sent.

The

LLDPU

120

format

is

shown

in

one

non-limiting

example

in

FIG.

3B.

Mandatory

TLV’s

that

are

required

are

illustrated.

Mandatory

TLV’s

include

a

chassis

ID

TLV

122,

a port

ID

TLV

124,

a

time

to

live

TLV

126,

and

an

end

of

LLDPDU

TLV

128.

The

optional

TLV’s

130

are

illustrated.

A

frame

for

TLV

format

140

is

shown

in

FIG.

3C

and

shows

the

TLV

type

142

of

about seven

(7)

bits

and

the

TLV

infor

mation

string

length

144

of

about

nine

(9)

bits

and

the

TLV

information

string

146

that

is

typically

0§n§5ll

bytes

(oc

tets).

The

TLV

type

142

and

TLV

information

144

form

a

TLV

header

148.

The

chassis

and

port

ID

TLV’s

122,

124

represent

the

connected

system’s

chassis

identi?cation

and

the

identi

?cation

of

the

speci?c

port

that

transmitted

the

LLDP

frame.

The

receiving

LLDP

agent

combines

the

chassis

ID

and

port

ID

to

represent

an

entity that

sent

the

LLDPU.

The

time

to

live

(TLV)

represents

for

how

long

information

contained

in

the

received

LLDPU

should

be

valid.

The

end-of-LLDPU

TLV

marks

the

end

of an

LLDPDU.

The

TLV

type

?eld

occupies

the

seven

most

signi?cant

bits

of

the

?rst

octet

of

the

TLV

format.

The

least

signi?cant

bit

in

the

?rst

octet

of

the

TLV

format

is

the

most

signi?cant

bit

of

the

TLV

information

string

length

?eld. Typically,

the

TLV

type

?eld

identi?es

a

speci?c

TLV

from

the

LLDP

basic

management

set

or

par

ticular

set

of TLV’s.

Typically,

an

LLDP

agent

can

advertise

different

TLV’s.

There

could

be

a port

description,

system

name,

system

description,

system

capabilities

and

management

address

TLV.

A

port

description

TLV

identi?es the port

in

which

the

LLDP

agent

transmitted

the

frame

and

the

system

name

TLV

represents the

system’s

administratively

assigned

name.

It

describes

a

textural

description

of

a

network

entity.

An

example

format

for

the

modi?ed

frame

is

shown

in

FIGS.

4A

and

4B.As

noted

before,

the

LLDP

frame

as

known

typically

contains

an

LLDP

multicast

address,

destination

20

25

30

35

40

45

50

55

60

65

8

address,

MAC

address,

LLDP

ether

type,

LLDPU

with

data

and

padding

and

the

PCS.

The

modi?ed

frame

includes

the

query

command

in

a

new

user

de?ned

?eld

as

a

command

that

propagates

through

the

network

and

sent

to

each

network

device

as

necessary

to

request

information

about

a

MAC

address

and

shut

that

MAC

address

down

if

located.

There

now

follows

greater

details

regarding

organiZation

ally

speci?c

TLV

extensions.

These

extensions

can

be

de?ned

by

different

organizations

or

vendors

and

concern

imple

mented

functionality

within

the

network

forming

the

commu

nications

system.

The

TLV

structure

of

LLDP

allows

a

?ex

ible

protocol

and

permits

advanced

discovery

options

to

be

created.

Vendors

and

companies

and

other

organizations

can

de?ne

TLV’s

that

advertise

information

to

remote

entities

attached

to

the

same

media

that

typically

is

a

one-way

adver

tisement

and

usually

independent

from

information

from

a

remote

port.

Usually,

the organiZationally

de?ned

extension

for

the

TLV

set

includes

associated

LLDP

MIB

extensions

and

associated

TLV

selection

management

variables

and

MIB/TLV

cross-reference

tables.

The

TLV

type value

of

127

as

shown

in

FIG.

4A

is

used

for

organiZationally

de?ned

TLV’s.

IEEE

802.1

TLV

extensions

can

have

different

attributes

with

a

Virtual

Local

Area

Network

(VLAN)

such

as

a port

VLAN

ID

TLV,

port

and

protocol

VLAN

ID

TLV,

VLAN

name

TLV,

and

protocol

identity

TLV.

The

prot

VLAN

ID

TLV

allows

a

bridge

port

to

advertise

the

port’s

VLAN

identi?er

(PVID)

that

is

associated

with

untagged

or

priority

tagged

frames.

The

port

and

protocol

VLAN

ID

TLV

allows

a

bridge

to

advertise

whether

it

supports

protocol

VLAN’s

and

what

the

protocols

are

associated.

The

VLAN

name

TLV

allows

a

bridge

to

advertise

the

textural

name

of

any

VLAN

with

which

it

is

con?gured.

The

protocol

identity

TLV

allows

a

bridge

to

advertise

particular

protocols

accessible

through

its

port.

An

802.3

LAN

interface

can

have

TLV

extensions

such

as

the

MAC/PHY

con?guration/

status

TLV

and

power

via

MDI

TLV

and

length

aggregation

TLV

and

maximum

frame

siZe

TLV.

The

MAC/PHY

con?guration/status

TLV

advertises

a

bit-rate

and

duplex

capability

of

a

node and

current

duplex

and

bit-rating

of

a

sending

node.

It

can

advertise

whether

the

settings

were

the

result

of

auto-negotiation

during

link

initia

tion

or

manual

override.

The

power

via

MDI

TLV

advertises

power-via-MDI

capabilities.

The

length-aggregation

TLV

advertises

whether

the

link

is

capable

of

being

aggregated

and

whether

it

is

currently

in

an

aggregation,

and

if

it

is,

the port

of

the

aggregation.

The

maximum

frame

siZe

TLV

advertises

the

maximum

supported

802.3

frame

siZe

of

a

sending

port

or

station.

In

accordance

with

a

non-limiting

example,

an

organiZa

tionally-speci?c

TLV

is

used,

?lling

in

the

OUI

(0x00

0xA0

0xCA)

then

populating

the

de?ned

information

string

with

the

MAC

address

and

action.

An

example

is

a

frame

that

is

sent

from

one

network

switch

and

meant

to

be

propagated

to

all

other

switches

via

LLDP.

The

“action”

may

be

for

the

receiving

switch

to

block

all

traf?c

from

this

MAC

address.

The

action

could

also

be

to

reply

to

the

originating

network

switch

with

information

about

the

MAC

address,

i.e.,

what

port

it

is

connected

to.

FIG.

4A

shows

there

is

an

LLDP

organiZationally-speci?c

TLV

that

is

de?ned

so

that

an

organiZation

can

extend

the

LLDP

to

?t

their

needs.

The

OUI

(organiZationally

unique

identi?er)

is

included

so

that

each

organiZation

can

differen

tiate

between

their

own

special

TLV’s

and

the

organiZation’

s

TLV’s.

This

special

TLV

is

used

to

de?ne

the

MAC

address

of

the

faulty

device.

As

shown

in

FIG.

4A,

the

TLV

type

equals

127

and

is

about

seven

bits

in

this

example.

The

TLV

information

string

length

1 2 ... 5 6 7 8 9 10 11 12 13

Comments to this Manuals

No comments