LMI Status messages are used to inform the router about the DLCI's of the defined VC's. as well as the status of each VC.

They are also used as keepalives for the link, if the router misses 3 LMI heartbeats, the link is presumed dead.

HTH>

Sarah,

What exactly do you mean by "configuring a DLCI statically on a router"? Note that what you configure is either a IP/DLCI mapping with the "frame-relay map" command, or a specific DLCI configuration using the "frame-relay interface-dlci" but none of these in fact configure some DLCI statically. They only say something about a particular DLCI but if that DLCI is not configured on your FR switch (and the LMI is on) then that DLCI will be reported as Deleted. On the other hand, if you turn off the LMI, that very same DLCIs that have been either Active, Inactive or Deleted will be immediately moved to the Static column.

A static DLCI is simply a DLCI whose existence and status can not be confirmed nor refuted by LMI because the LMI is turned off. But note that this same DLCI may move from the Static column to any other else if the LMI tells so.

Best regards,

Peter

When dlci is mapped statically, the you see the following from the outputs:

-show frame-relay map:

Serial0/0/0 (up): ip 10.0.0.1 dlci 201(0xC9,0x3090), static,

CISCO, status defined, active

-show frame-relay pvc:

R2#show fram pvc

PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)

Active Inactive Deleted Static

Local 1 0 0 0

Switched 0 0 0 0

Unused 0 4 0 0

DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0

input pkts 758 output pkts 59 in bytes 228133

out bytes 2356 dropped pkts 0 in pkts dropped 0

out pkts dropped 0 out bytes dropped 0

in FECN pkts 0 in BECN pkts 0 out FECN pkts 0

out BECN pkts 0 in DE pkts 0 out DE pkts 0

out bcast pkts 54 out bcast bytes 1836

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

pvc create time 11:38:45, last time pvc status changed 11:38:45