I am new to setting up T1 point-to-point connections. I was trying to setup a Netvanta 3200 3rd Gen with a dual T1 card in bridge mode to connect two other Netvanta 3200 3rd Gen with the single T1 card in them. I can get one or the other to work but not all of them at the same time. Please help me with the configuration of this device. Scenario is a main location (A) with two remote offices (B & C). All need to be on the same network. Location A has a Netvanta 3200 3rd Gen with a dual T1 card and Location B & C both have a Netvanta 3200 3rd Gen with the single T1 card. We have a T1 that runs from location A to B and location A to C.
Current Config:
hostname "Dual.P2P.Bridge"
enable password password
!
!
ip subnet-zero
ip classless
no ip routing
!
!
!
!
no auto-config
!
event-history on
no logging forwarding
no logging email
!
no service password-encryption
!
username "admin" password "password"
!
banner motd #
****** Important Banner Message ******
Enable and Telnet passwords are configured to "password".
HTTP and HTTPS default username is "admin" and password is "password".
Please change them immediately.
****** Important Banner Message ******
#
!
ip policy-timeout tcp telnet 14400
!
no ip firewall alg msn
no ip firewall alg mszone
no ip firewall alg h323
!
!
!
!
!
!
!
no dot11ap access-point-control
!
!
!
!
!
bridge 1 protocol ieee
!
!
!
!
!
interface eth 0/1
speed 100
bridge-group 1
no shutdown
!
!
!
!
interface t1 1/1
tdm-group 1 timeslots 1-24 speed 64
no shutdown
!
interface t1 1/2
tdm-group 1 timeslots 1-24 speed 64
no shutdown
!
interface ppp 1
bridge-group 1
no shutdown
cross-connect 1 t1 1/1 1 ppp 1
cross-connect 2 t1 1/2 1 ppp 1
!
!
!
!
!
!
!
!
!
!
!
no tftp server
no tftp server overwrite
no ip http server
no ip http secure-server
no snmp agent
no ip ftp server
no ip scp server
no ip sntp server
!
!
!
!
!
!
!
!
ip sip udp 5060
ip sip tcp 5060
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
line con 0
no login
!
line telnet 0 4
login local-userlist
password password
no shutdown
line ssh 0 4
login local-userlist
no shutdown
!
!
!
!
!
end
I also tried:
hostname "Dual.P2P.Bridge"
enable password password
!
!
ip subnet-zero
ip classless
no ip routing
!
!
!
!
no auto-config
!
event-history on
no logging forwarding
no logging email
!
no service password-encryption
!
username "admin" password "password"
!
banner motd #
****** Important Banner Message ******
Enable and Telnet passwords are configured to "password".
HTTP and HTTPS default username is "admin" and password is "password".
Please change them immediately.
****** Important Banner Message ******
#
!
ip policy-timeout tcp telnet 14400
!
no ip firewall alg msn
no ip firewall alg mszone
no ip firewall alg h323
!
!
!
!
!
!
!
no dot11ap access-point-control
!
!
!
!
!
bridge 1 protocol ieee
!
!
!
!
!
interface eth 0/1
speed 100
bridge-group 1
no shutdown
!
!
!
!
interface t1 1/1
tdm-group 1 timeslots 1-24 speed 64
no shutdown
!
interface t1 1/2
tdm-group 2 timeslots 1-24 speed 64
no shutdown
!
interface ppp 1
bridge-group 1
no shutdown
cross-connect 1 t1 1/1 1 ppp 1
!
interface ppp 2
bridge-group 1
no shutdown
cross-connect 2 t1 1/1 2 ppp 2
!
!
!
!
!
!
!
!
!
!
no tftp server
no tftp server overwrite
no ip http server
no ip http secure-server
no snmp agent
no ip ftp server
no ip scp server
no ip sntp server
!
!
!
!
!
!
!
!
ip sip udp 5060
ip sip tcp 5060
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
line con 0
no login
!
line telnet 0 4
login local-userlist
password password
no shutdown
line ssh 0 4
login local-userlist
no shutdown
!
!
!
!
!
end
brt013:
Thank you for posting your question, and supplying the configuration. For further reference and advanced bridging configuration examples you can view the "Configuring Bridging in AOS" document.
Configuring IRB in AOS firmware release after 17.07.00 requires the completion of the following tasks:
• Enabling IRB
• Configuring the bridge group
• Configuring the BVI interface
• Removing IP addresses from all interfaces that will be added to the bridge group
• Assigning interfaces to the bridge group
You have accomplished most of these tasks in the first configuration you posted above, but there are a few things you will need to add or change.
When you have completed this, your configuration should look similar to the output below:
ip routing
!
bridge irb
!
bridge 1 protocol ieee
!
interface eth 0/1
bridge-group 1
bridge-group 1 vlan-transparent
no ip address
no shutdown
!
interface t1 1/1
clock source internal
tdm-group 1 timeslots 1-24 speed 64
no shutdown
!
interface ppp 1
bridge-group 1
bridge-group 1 vlan-transparent
no ip address
ppp bcp tagged-frame
mtu 1524
no shutdown
cross-connect 1 t1 1/1 1 ppp 1
!
interface bvi 1
ip address X.X.X.X Y.Y.Y.Y (If you enter an IP address and subnet mask for management)
no shutdown
I hope that makes sense, but please, do not hesitate to reply to this post with any questions or additional information, I will be happy to help in any way I can.
Levi
brt013:
Thank you for posting your question, and supplying the configuration. For further reference and advanced bridging configuration examples you can view the "Configuring Bridging in AOS" document.
Configuring IRB in AOS firmware release after 17.07.00 requires the completion of the following tasks:
• Enabling IRB
• Configuring the bridge group
• Configuring the BVI interface
• Removing IP addresses from all interfaces that will be added to the bridge group
• Assigning interfaces to the bridge group
You have accomplished most of these tasks in the first configuration you posted above, but there are a few things you will need to add or change.
When you have completed this, your configuration should look similar to the output below:
ip routing
!
bridge irb
!
bridge 1 protocol ieee
!
interface eth 0/1
bridge-group 1
bridge-group 1 vlan-transparent
no ip address
no shutdown
!
interface t1 1/1
clock source internal
tdm-group 1 timeslots 1-24 speed 64
no shutdown
!
interface ppp 1
bridge-group 1
bridge-group 1 vlan-transparent
no ip address
ppp bcp tagged-frame
mtu 1524
no shutdown
cross-connect 1 t1 1/1 1 ppp 1
!
interface bvi 1
ip address X.X.X.X Y.Y.Y.Y (If you enter an IP address and subnet mask for management)
no shutdown
I hope that makes sense, but please, do not hesitate to reply to this post with any questions or additional information, I will be happy to help in any way I can.
Levi
That worked for me. Thank you so much!
How do you set this up so that down stream devices can be managed with management vlan?
Thank you for asking this question in the support community. If I understand the question properly, by default, downstream devices should be able to be managed in this configuration, because the ADTRAN is going to pass this traffic through. Please, feel free to expand on this question, with additional information, and I will be happy to help in any way I can.
Levi