Raqueeb Hassan wrote:
> On Mar 5, 6:55 pm, James Carlson <james.d.carl...@sun.com> wrote:
>
>>"Raqueeb Hassan" <widean...@gmail.com> writes:
>>
>>>Initially only one of it's 4 ethernet interfaces was configured for
>>>the network connectivity. Recently, all types of communication ends up
>>>freezing (ssh, ftp) and the ping replies are intermittent. The cable
>>>connection and the switch ports are okay.
>>
>>Please provide "netstat -nr" and "ifconfig -a" output from the Solaris
>>system and some basic information about your network. (Is the netmask
>>really 255.255.0.0? Are all the machines on that network configured
>>that way?)
>>
>>
>>>Just to check whether the settings are staying or not, I rebooted the
>>>whole system. The "ifconfig -a" doesn't return any IP address as
>>>configured. We can't communicate with the system unless we use this
>>>command:
>>
>>># ifconfig bge1 10.1.1.2 netmask 255.255.0.0 broadcast 10.1.255.255
>>>plumb up
>>
>>That's not going to work. You're telling the system to configure a
>>non-existent interface, and then plumb it afterwards. That should be:
>>
>># ifconfig bge1 plumb 10.1.1.2 netmask 255.255.0.0 \
>> broadcast 10.1.255.255 up
>>
>>Or, equivalently, and more concisely:
>>
>># ifconfig bge1 plumb 10.1.1.2/16 broadcast + up
>
>
> Thanks for the replies. After the reboot, the ifconfig -a returns
>
> lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index
> 1
> inet 127.0.0.1 netmask ff000000
> bge1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
> inet 10.1.1.2 netmask ff000000 broadcast 10.255.255.255
> ether x:x:xx:xx:xx:xx
> bge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
> index 2
> inet 192.168.100.3 netmask ffffff00 broadcast 192.168.100.255
> ether x:x:xx:xx:xx:xx
>
> Here I configured annex to be connected to bge2. You are right. The
> broadcast seems to be a issue here. How do I change that? What should
> be the value of /etc/netmasks for network 10.1.1.0?
>

How many addresses are you using in that address space?

Remember that the netmask is logically "anded" with an IP address to
determine whether the address is "local" or not. There are potentially
2^24-1 addresses in that space. If you are using 10.1.1.0 through
10.1.1.255 then your netmask would be 255.255.255.0. Since that address
space is designated as an RFC-1918 private network you could assign all
2^24-1 addresses and use 255.0.0.0 as a netmask if you wish.