Starting with the 3.0 Release for GigaPlus it becomes possible to do IBM with vlan tagged traffic or untagged traffic. This also applies to ApexPlus when used with OMU HW ID 2 which started shipping in late 2012.
Setting up the In-Band-Management (IBM)
Trango pre-configures the links with IBM already set up and enabled, with tagging off, however it will typically be necessary to change the IBM IP addresses used to fit the application management network . This section covers the setup of the IBM.
Display the IBM settings. In the example below the IBM is off.
(CLI-config)# ibm
IBM Enable: off
IBM Tagging: off
IBM Vlan ID: 100
IBM IP address: 172.16.1.1
IBM Netmask: 255.255.0.0
SUCCESS
Enable IBM using the settings preloaded.
(CLI-config)# ibm enable on
IBM enable: on
SUCCESS
Change the IBM IP address and subnet mask. Each end of the link should have a different IP address, and in the case of multiple daisy chained links, the IPs should all be different.
(CLI-config)# ibm ip 172.16.1.2 255.255.255.0
IBM IP Address: 172.16.1.2
IBM netmask: 255.255.255.0
SUCCESS
Verify the settings are correct.
(CLI-config)# ibm
IBM Enable: on
IBM Tagging: off
IBM Vlan ID: 100
IBM IP address: 172.16.1.2
IBM Netmask: 255.255.255.0
Verify the connection to the other end of the link by entering the debug node and using the ping command inside the GigaPlus. In the example, the other end of the link has an IP address of 172.16.1.1.
(CLI-config)# debug
Ping the other side of the link using the ping command from within the debug node of the radio.
debug> ping 172.16.1.1
PING 172.16.1.1 (172.16.1.1): 56 data bytes
64 bytes from 172.16.1.1: seq=0 ttl=64 time=6.672 ms
64 bytes from 172.16.1.1: seq=1 ttl=64 time=1.001 ms
64 bytes from 172.16.1.1: seq=2 ttl=64 time=0.979 ms
--- 172.16.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.979/2.884/6.672 ms
Note: Besides ping , It should be noted that from the debug prompt a telnet session can be run to configure the far end if desired. It should be kept in mind that any change that would break the link will result in loss of control to the far side. Changes to parameters like frequency, speed, or opmode should be done with care.
Return to the command line interface using the cli command. Upon returning from the debug prompt, the system will be in the view node, so the user must log into the config node if any further changes are required.
debug> cli
Trango System: TrangoLINK GigaPlus Command Line Interface v3.0.0
Return to the config node using the config command
(CLI-view)# config
Password: trango
IBM may function with VLAN tagging enabled or disabled. With IBM tagging on, a VLAN must be used to access the radio via IBM. With IBM tagging off, traffic that is not tagged with a VLAN will reach the radio via the data ports. While IBM can be used in either method, Trango’s recommendation is that IBM be used with a dedicated management VLAN with the highest CoS setting on this VLAN to ensure critical management traffic is never dropped due to traffic flooding conditions.
After changing the IBM tagging state, the config must be saved and the radio must be rebooted for the setting to take effect.
(CLI-config)# ibm tagging on
IBM Tagging: on
(CLI-config)# config save
New configuration saved
SUCCESS
(CLI-config)# reboot
Comments
0 comments
Please sign in to leave a comment.