ADTRAN Vanta 1335 Manual de usuario descargar pdf (Pagina 8)

US

8,443,065

B1

3

FIG.

4A

is

a

diagram

showing

an

example

frame

format

for

a

Link

Layer

Discover

Protocol

(LLDP)

organizationally

spe

ci?c

TLV

that

can

be

modi?ed

and

used

in

accordance

with

a

non-limiting

example.

FIG.

4B

is

a

diagram

showing

an

example

frame

format

for

a

MAC

address

TLV

that

can be

modi?ed

and

used

in

accor

dance

with

a

non-limiting

example.

FIG.

5

is

an

example

of

a

communications

system

that

could

incorporate

the

method

as

described

and

showing

vari

ous

components

and

the

methodology

and

uses

the

modi?ed

frame

formats

as

shown

in

FIGS.

3A-3C

and

4A

and

4B

in

accordance

with

a

non-limiting

example

for

locating

an

offending

network

device

and

maintaining

network

integrity.

DETAILED

DESCRIPTION

Different

embodiments

will

now

be

described

more

fully

hereinafter

with

reference

to

the

accompanying

drawings,

in

which

preferred

embodiments

are

shown.

Many

different

forms

can

be

set

forth

and

described

embodiments

should

not

be

construed

as

limited

to

the

embodiments

set

forth

herein.

Rather,

these

embodiments

are

provided

so

that

this

disclo

sure

will

be

thorough

and

complete,

and

will

fully

convey

the

scope

to

those

skilled

in

the

art.

In

accordance

with

a

non-limiting

example,

a

technical

solution

to

this

problem

addressed

above

is

to

have

a

newly

deployed

network

device

learn

its

physical

network

connec

tivity

as

location

information

from

at

least

one

existing

neigh

boring

network

device

it

is

connected

to

using

a

discovery

protocol

such

as

a

one-way

discovery

protocol.

The

newly

deployed

network

device

could

receive

this

location

information using

a

discovery

protocol

via

numerous

Layer

2

means,

including

but

not

limited

to,

LLDP

and

Link

Layer

Ethernet

OAM

messages.

A

minimum

set

of

informa

tion

typically

to

be

relayed

between

the

new

device

and

its

existing

link

peer

includes:

1)

the

physical

and/

or

logical

location

of

the

new

device

connection

point,

which

may

include

information

such

as

the

physical

slot

and

port

and

of

the

device

to

which

the

new

device

is

connected

to

or the

ID

of

a

logical

EFM

bonding

group,

etc.;

and

2)

information

uniquely

identifying

the

existing

device,

which

may

include

the

device’s

IP

address,

node

number,

or

other

data

regarding

unique

characteristics.

Data

also

is

sent

to

the

new

device

regarding

the

Layer

2

address

on

the

network

manager

to

allow

the

new

device

to

contact

the

network

manager.

In

one

example,

the

new

device

may

be

provided

a

plurality

of

addresses

to

contact

in

the

event

some

addresses

are

unreachable

or

potentially

may

be

provided

no

address.

In

the

event

no

address

is

given,

the

newly

deployed

network

device

may

elect

to

use

Layer

2

broadcast

messages

to

announce

itself.

Once

the

newly

deployed

network

device

has

received

its

connectivity

data,

the

newly

deployed

network

device

may

announce

itself

to

the

network

manager

and

include

this

con

nectivity

data,

which

will

allow

the

network

manager

to

deter

mine

the location

of

the

newly

deployed

network

device.

With

the

location/

identity

of

the

new

device

known

to

the

network

manager,

automated

systems

and/

or

the

network

manager

as

part

of

a

Network

Management

System

(N

MS)

could

have

its

operators

send

the

required

provisioning

information

to

the

newly

deployed

network

device

using

Layer

2

methods.

Once

the

newly

deployed

network

device has

received

this

provi

sioning

information

and

acted

on

this

information,

it

may

function

and

interact

with

the

network

manager

and

other

network

elements

using

traditional

methods.

In

one

non-limiting

example,

a

LLDP

organizationally

speci?c

TLV

can

be

changed

such

that

the

LLDP

packet

is

20

25

30

35

40

45

50

55

60

65

4

modi?ed

to

obtain the

minimum

set

of

information

to

be

relayed

as

described

above.

It

should

be

understood

that

link

layer

Ethernet

OAM

messages

can

be

similarly

modi?ed.

LLDP

and

Ethernet

OAM

include

and

support

vendor

spe

ci?c

extensions.

It

is

possible

to

use

a proprietary

protocol

to

drive

underneath

the

Ethernet

layer,

which

could

be

made

a

public

protocol

and

not

speci?cally

relegated

to

manufacturer

devices.

It

is

possible

for

the

newly

deployed

network

device

to

announce

itself

to

the

network

manager

using

different

tech

niques,

for

example,

by

sending

a

“Hello”

packet

with

the

Layer

2

MAC

address

and

other

information.

The

network

manager

will

receive

the

Hello

packet

and

process

the

infor

mation.

For

example,

the data

could

indicate

that

the

newly

deployed

device

is

of

“type

X”

and

connected

to

port

W

on

the

other

known

device,

which

could

be

newly

deployed.

Because

the

network

manager

knows

the

architecture

of

the

network

and

understands

when

the

existing

neighboring

net

work

device

was

plugged

in,

it

will

know

its

IP

address.

It

is

also

possible

that

the

network

manager

could

construct a

Layer

2

packet

as

a

proprietary

format

riding

behind

the

provider

Ethernet

to

transmit

information

back

to

the

newly

deployed

network

device.

It

is

also

possible

for

the

network

manager

to

transmit

back

a

Layer

3

address

to

that

device,

which

typically

in

the past

has

been

statically

assigned

or

use

DHCP.

This

Layer

3

address

could

be

assigned

based

on

the

provisioning

that

occurred

in

the

network

manager

at

some

point

previous

to

when

the

device

was

connected.

Once

the

network

manager

has

transmitted

the

Layer

3

address

back

to

the

device,

the

device

would

turn

on

its

IP

stack

and

would

now

have

a

Layer

3

presence

in

the

network

and

the

device

could

be

managed

by

traditional

techniques.

It

is

also

possible

that

the

at

least

one

existing

neighboring

network

device

is

con?gured

to

determine

the

physical

net

work

connectivity

of

the

newly

deployed

network

device

and

propagate

a

discovery

protocol

frame

that

comprises

a

?eld

having

a

query

that

solicits

the

physical

network

connectivity

of

the

newly

deployed

network

device

within

the

communi

cations

network.

The

network

connectivity

data

is

transmitted

to

the

network

manager,

which

then

transmits

provisioning

data

to

the

newly

deployed

network

device

based

on

the

received

physical

network

connectivity

data.

Thus,

while

the

newly

deployed

device

could

send

a

query

over

LLDP

as

previously

described,

this

embodiment

may

have

the

existing

device

sending

the

required

location

and

addressing

informa

tion

within

LLDP

TLV’s

all

the

time

without

requiring

the

new

device

to

send

the

query.

FIG.

1

is

a

high-level

?owchart

illustrating

a

method

in

accordance

with

a

non-limiting

example.

The

process

starts

(block 10)

and

a

discovery

protocol

frame

is

propagated

to

at

least

one

existing

neighboring

device

(block

12).

This

discov

ery

protocol

frame

typically

includes

a

?eld

having

a

query

that

solicits

from

the

existing

neighboring

network

device

the

physical

network

connectivity

data

of

the

newly

deployed

device within

the

communications

network.

In

response

to

this

query,

the

newly

deployed

network

device

receives

from

the

existing

device

the

physical

connectivity

data

of

the

newly

deployed

network

device

(block

14).

The

discovery

protocol

frame

in

one

example

comprises

a

Link

Layer

Discovery

Protocol

(LLDP)

frame

or a

link

layer

Ethernet

OAM

mes

sage

for

discovering

the

physical

network

connectivity

of

the

newly

deployed

network

device.

Other

examples

can

be

included.

The

physical

network

connectivity

data

in

one

example

is

at

least

one

of

physical

and

logical

location

con

nection

data

of

the

newly

deployed

network

device

and

data

uniquely

identifying

the

existing

connective

device.

This

data

could

be

a

physical

slot

and

port

of

the

existing

neighboring

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Comentarios a estos manuales

Sin comentarios