i think adjust the PADO Delay will help. Does the erx support that? Thanks
发件人： gdxnfx 发送时间： 2010-07-23 16:21:17 收件人： [email protected] 抄送： 主题： multiple PPPoE servers (erx Junos10) Hi All, I have 2 PPPoE servers on the same vlan. PPPoE server 1 is erx1410, MAC = Unispher_40:08:a1 ,PPPoE Server 2 is erx1440,mac = Unispher_41:eb:42 . See the PPPoE log below,I am wondering why the ERX1440 send the PADR to PCs and not ERX1410? Does the Junose support "delay―Number of seconds that the PPPoE underlying interface waits after receiving a PADI packet from the client before sending a PADO packet in response."? Anybody know how to implement 2 PPPoE servers? one as primary, one as backup? 144 109.606151 Intel_83:4f:b3 Broadcast PPPoED Active Discovery Initiation (PADI) 145 109.606740 Unispher_41:eb:42 Intel_83:4f:b3 PPPoED Active Discovery Offer (PADO) AC-Name='ERX1440-LNS2-erx2' 146 109.606779 Intel_83:4f:b3 Unispher_41:eb:42 PPPoED Active Discovery Request (PADR) 147 109.609564 Unispher_40:08:a1 Intel_83:4f:b3 PPPoED Active Discovery Offer (PADO) AC-Name='ERX1410-LNS1-erx1' 148 109.708460 Unispher_41:eb:42 Intel_83:4f:b3 PPPoED Active Discovery Session-confirmation (PADS) 149 109.737316 Intel_83:4f:b3 Unispher_41:eb:42 PPP LCP Configuration Request 150 109.809762 Unispher_41:eb:42 Intel_83:4f:b3 PPP LCP Configuration Request 151 109.809865 Unispher_41:eb:42 Intel_83:4f:b3 PPP LCP Configuration Reject 152 109.824677 Intel_83:4f:b3 Unispher_41:eb:42 PPP LCP Configuration Ack 153 109.829249 Intel_83:4f:b3 Unispher_41:eb:42 PPP LCP Configuration Request 154 109.829903 Unispher_41:eb:42 Intel_83:4f:b3 PPP LCP Configuration Ack 155 109.845212 Intel_83:4f:b3 Unispher_41:eb:42 PPP LCP Identification 156 109.845315 Intel_83:4f:b3 Unispher_41:eb:42 PPP LCP Identification 157 109.845546 Intel_83:4f:b3 Unispher_41:eb:42 PPP PAP Authenticate-Request 158 110.008150 Unispher_41:eb:42 Intel_83:4f:b3 PPP PAP Authenticate-Ack 159 110.015315 Intel_83:4f:b3 Unispher_41:eb:42 PPP CCP Configuration Request 160 110.015464 Intel_83:4f:b3 Unispher_41:eb:42 PPP IPCP Configuration Request 161 110.015739 Unispher_41:eb:42 Intel_83:4f:b3 PPP LCP Protocol Reject 162 110.016237 Unispher_41:eb:42 Intel_83:4f:b3 PPP IPCP Configuration Reject 163 110.025478 Intel_83:4f:b3 Unispher_41:eb:42 PPP IPCP Configuration Request 164 110.025938 Unispher_41:eb:42 Intel_83:4f:b3 PPP IPCP Configuration Nak 165 110.040954 Intel_83:4f:b3 Unispher_41:eb:42 PPP IPCP Configuration Request 166 110.041395 Unispher_41:eb:42 Intel_83:4f:b3 PPP IPCP Configuration Ack 167 110.209895 Unispher_41:eb:42 Intel_83:4f:b3 PPP IPCP Configuration Request 168 110.259887 Intel_83:4f:b3 Unispher_41:eb:42 PPP IPCP Configuration Ack delay―Number of seconds that the PPPoE underlying interface waits after receiving a PADI packet from the client before sending a PADO packet in response. In networks with mesh topologies, you might want to designate a primary PPPoE server and a backup PPPoE server for handling a particular service request. In such a scenario, you can configure a delay for the associated service name tag on the backup PPPoE server to allow sufficient time for the primary PPPoE server to respond to the client with a PADO packet. If the primary server does not send the PADO packet within the delay period configured on the backup server, then the backup server sends the PADO packet after the delay period expires. http://www.juniper.net/techpubs/en_US/junos10.1/information-products/topic-collections/config-guide-network-interfaces/topic-40403.html http://www.juniper.fr/techpubs/software/erx/erx51x/swconfig-link/html/pppoe-config9.html Thanks Terry _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
