The IBM configuration is fairly easy, you just need to configure the IPs on each radio and specify the vlan. The IPs should be in a different subnet than the OBM.
To use IBM from another device, you will need to configure your switch to send tags on that vlan.
We strongly recommend that you have a dedicated management vlan and set the cos accordingly so that your management traffic will have priority over all other traffic in the event of broadcast storm or other incident that might make managing the radios impossible.
If you want to use IBM as your primary management, you’ll want to set your default gateway accordingly. It can either be set to be an IP on the OBM subnet or on the IBM subnet.
Below is a sample configuration from a Cisco IOS switch and GigaPlus for IBM:
TopSwitch#sh run int f0/21
interface FastEthernet0/21
description GigaPlus .52
switchport trunk encapsulation dot1q
switchport mode trunk
end TopSwitch#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Vlan1 192.168.100.1 YES NVRAM up up
Vlan2 10.14.1.64 YES NVRAM up up
Vlan100 172.16.1.1 YES NVRAM up up TopSwitch#sh int status Port Name Status Vlan Duplex Speed Type
Fa0/21 GigaPlus .52 connected trunk a-full a-100 10/100BaseTX
On the Trango radio:
(.52-view)# ibm
IBM Enable: on
IBM Tagging: on
IBM Vlan ID: 100
IBM IP Address: 172.16.1.52
IBM Netmask: 255.255.255.0
(.52-view)# ipconfig
IP Address: 10.14.1.52
Subnet Mask: 255.255.254.0
Gateway IP: 10.14.0.1
Test pinging from the switch to the radio:
TopSwitch>ping 172.16.1.52 Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.52, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/200/1000 ms
With the 3.0 release for GigaPlus and ApexPlus with AP-OMU-2, it is possible to do IBM without the use of a VLAN tag. This is covered in the article IBM tagging.
Comments
1 comment
Below is a diagram of a GigaPlus IDU and shows how the CPU's two Ethernet interfaces are connected. The Mgmt port goes to the port on the front (this is referred to as eth1 in debug node) and the IBM port (eth2) goes to the internal switch which can then be accessed if programmed properly through the data ports or across the RF link.
Please sign in to leave a comment.