[j-nsp] ATM2 pic connected to another M7i cannot get ISIS adjatency ; (
Xavier Beaudouin
kiwi at oav.net
Sat Jul 9 11:19:38 EDT 2011
Hi Stefan,
Le 7 juil. 2011 à 18:22, Stefan Fouant a écrit :
> You have both sides doing clocking internal?
show interfaces at-0/3/0 extensive | grep clock
Link-level type: ATM-PVC, MTU: 9192, Clocking: Internal, SONET mode,
Yes.
> Also, what is the config under [protocols isis]?
It is quite simple for now :
> show configuration protocols isis
inactive: traceoptions {
file isis;
flag error;
flag general;
flag normal;
}
export export-statics;
level 2 wide-metrics-only;
interface at-0/3/0.0;
interface at-0/3/1.0;
interface lo0.0;
Just trying to bring up ISIS, then I will see :)
Xavier
> Stefan Fouant
> GPG Key ID: 0xB4C956EC
>
> Sent from my HTC EVO.
>
> ----- Reply message -----
> From: "Xavier Beaudouin" <kiwi at oav.net>
> Date: Thu, Jul 7, 2011 10:51 am
> Subject: [j-nsp] ATM2 pic connected to another M7i cannot get ISIS adjatency ; (
> To: <juniper-nsp at puck.nether.net>
>
> Hi there,
>
> I have 2 M7i with pic :
> PIC 3 REV 08 750-005724 CN5430 2x OC-3 ATM-II IQ, MM
>
> Since I don't use ATM, I wanted to use this as interrouter connection using :
>
> jun-m7i-1 at-0/3/0 <-> jun-m7i-2 at-0/3/0
> jun-m7i-1 at-0/3/1 <-> jun-m7i-2 at-0/3/1
>
> I finaly found a way to make the communication (ipv4) between the routers, but it doesn't seems to work with ISIS.
>
> Here is jun-m7i-1 base configuration :
>
> interfaces {
>
> at-0/3/0 {
> description "To jun-m7i-2_at-0/3/0";
> mtu 9192;
> clocking internal;
> encapsulation atm-pvc;
> atm-options {
> pic-type atm2;
> vpi 1;
> }
> unit 0 {
> encapsulation atm-snap;
> vci 1.100;
> oam-period 3;
> oam-liveness {
> up-count 3;
> down-count 3;
> }
> family inet {
> address xx.xx.xx.125/30;
> }
> family iso;
> }
> }
> at-0/3/1 {
> description "To jun-m7i-2_at-0/3/1";
> mtu 9192;
> clocking internal;
> encapsulation atm-pvc;
> atm-options {
> pic-type atm2;
> vpi 1;
> }
> unit 0 {
> vci 1.100;
> family inet {
> address xx.xx.xx.121/30;
> }
> family iso;
> }
> }
>
> lo0 {
> description Loopback;
> unit 0 {
> family inet {
> no-redirects;
> primary;
> address xx.xx.xx.1/32 {
> primary;
> preferred;
> }
> }
> family iso {
> address 49.0001.0xxx.xxxx.xxx1.00;
> }
> }
> }
> }
>
> On jun-m7i-2 :
>
> interfaces {
> at-0/3/0 {
> description "To jun-m7i-1_at-0/3/0";
> mtu 9192;
> clocking internal;
> encapsulation atm-pvc;
> atm-options {
> pic-type atm2;
> vpi 1;
> }
> unit 0 {
> encapsulation atm-snap;
> vci 1.100;
> oam-period 3;
> oam-liveness {
> up-count 3;
> down-count 3;
> }
> family inet {
> address xx.xx.xx.126/30;
> }
> family iso;
> }
> }
> at-0/3/1 {
> description "To jun-m7i-1_at-0/3/1";
> mtu 9192;
> clocking internal;
> encapsulation atm-pvc;
> atm-options {
> pic-type atm2;
> vpi 1;
> }
> unit 0 {
> encapsulation atm-snap;
> vci 1.100;
> family inet {
> address xx.xx.xx.122/30;
> }
> family iso;
> }
> }
> lo0 {
> description Loopback;
> unit 0 {
> family inet {
> no-redirects;
> primary;
> address xx.xx.xx.xx/32 {
> primary;
> preferred;
> }
> }
> family iso {
> address 49.0001.0xxx.xxxx.xxx2.00;
> }
> }
> }
> }
>
>
> show isis interface
> IS-IS interface database:
> Interface L CirID Level 1 DR Level 2 DR L1/L2 Metric
> at-0/3/0.0 3 0x1 Point to Point Point to Point 10/10
> at-0/3/1.0 3 0x1 Point to Point Point to Point 10/10
> lo0.0 0 0x1 Passive Passive 0/0
>
> Any clues, ideas ?
>
> Kind regards,
> Xavier
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
More information about the juniper-nsp
mailing list