frame relay physical interface can't be bought down by EEK?

Hi All,

    As title, if i configure frame relay using physical interface, and there is only one DLCI on the interface.. also EEK is configured for that DLCI..

interface ser1/0
enc frame
ip add 1.1.1.1 255.255.255.0
frame map ip 1.1.1.2 102 br
no frame inv
frame interface-dlci 102
class EEK

   If DLCI 102 fails and EEK down, will ser1/0 interface go down?  I tried and noticed that ser1/0 can't be brought down even with EEK down..(in fact i am trying so hard to bring the ser1/0 down but not successful.. i got a backup interface command on the ser1/0 too.. u know y i tried so hard) not sure whether this is expected.. 

Thanks for the help..

Cheers
Ricky

Comments

  • I agree, multipoint interface can't be brought down by FR EEK mechanics.

  • Hi Ricky,

    Can you post a "show frame-relay pvc | in DLCI" for the interface. You may find there are other PVCs active too.. All DLCI's are assigned to the physical interface by default, so if there are others there (such as 103,104,105 etc) they will probably still be up, and hence the loss of 102 won't bring the interface down.


    If you move it to a sub-interface with only that DLCI assigned - you'll probably see the behaviour you're looking for.

    Cheers

    Dan


    2008/9/21 ricky <[email protected]>

    Hi All,

        As title, if i configure frame relay using physical interface, and there is only one DLCI on the interface.. also EEK is configured for that DLCI..

    interface ser1/0
    enc frame
    ip add 1.1.1.1 255.255.255.0
    frame map ip 1.1.1.2 102 br

    no frame inv
    frame interface-dlci 102
    class EEK

       If DLCI 102 fails and EEK down, will ser1/0 interface go down?  I tried and noticed that ser1/0 can't be brought down even with EEK down..(in fact i am trying so hard to bring the ser1/0 down but not successful.. i got a backup interface command on the ser1/0 too.. u know y i tried so hard) not sure whether this is expected.. 

    Thanks for the help..

    Cheers
    Ricky




    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • The reason why it doesnt work on a physical interface is because once the interface is down it will never receive the keepalives again, causing it to stay down forever.

    With multipoint interfaces it works but all DLCI's have to be down first before it will change the interface state.

     

     

  • Good point Paul!

    2008/9/21 Paul Alexander <[email protected]>

    The reason why it doesnt work on a physical interface is because once the interface is down it will never received the keepalives again, causing it to stay down forever.

    With multipoint interfaces it works but all DLCI's have to be down first before it will change the interface state.

     

     





    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx


  • Good point Paul!


    2008/9/21 Paul Alexander <[email protected]>

    The reason why it doesnt work on a physical interface is because once the interface is down it will never received the keepalives again, causing it to stay down forever.

    With multipoint interfaces it works but all DLCI's have to be down first before it will change the interface state.

     

     





    Internetwork Expert - The Industry Leader in CCIE Preparation
    http://www.internetworkexpert.com

    Subscription information may be found at:
    http://www.ieoc.com/forums/ForumSubscriptions.aspx




     

    Yeap..  thanks for Dan and Paul's input..  I did tried to bring down all DLCI mapped to ser1/0 and still see it up.. but with Paul's point.. it start to make sense.. ^_^. 

Sign In or Register to comment.