Multiple NICs, same subnet

I am building a test device requiring 6 IP addresses on the same subnet, unique 4th octets (xxx.xxx.xxx.101,102,103,...). I am using 6 pxi 8231 NICs., 8108 controller, and 1045 PXI chaasis. MAX will allow the target to configure 3 channels with an odd 4th octet, using 255.255.255.254. The even IP addresses are disabled with the message one device per subnet. The mask 255.255.255.255 is defined as an invalid mask by MAX. Are there any suggestions to resolve this? Can it be done using a hub or switch and a single card (NIC)by tricking up the mask (255.255.255.0)? I have also attempted this programmatically but could not confirm the IP addresses that have been set on the NICS
Thanks,
Phil.

The use of the 255.255.255.254 was recommended by the NI engineer who is attempting to help me resolve this problem. I have attempted to use several masks without success. I understand the mask is currently inhibiting my ability to load the even ip addresses.

Similar Messages

Multiple NICs on same server

Hey Guys!
I'm trying to configure some iSCSI connections on a server with 2 NICs. Now i also have two separate SAN boxes so i was thinking of dedicating one nic to each box.
I've read that there can be issues if these nics are on the same subnet but if i configure the iscsi connections specifically for one nic to one target would those issues still happen?
So i guess the question is should i go for this 1-1 setup plan? Should I seperate them into different subnets? Or scrap everything and go with MPIO?

Hey Guys!
I'm trying to configure some iSCSI connections on a server with 2 NICs. Now i also have two separate SAN boxes so i was thinking of dedicating one nic to each box.
I've read that there can be issues if these nics are on the same subnet but if i configure the iscsi connections specifically for one nic to one target would those issues still happen?
So i guess the question is should i go for this 1-1 setup plan? Should I seperate them into different subnets? Or scrap everything and go with MPIO?
MPIO is a preferred way as it will give you best performance and fastest possible failover time. It's up to your SAN vendor should you have one subnet or multiple.
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Multiple SSID's on the same subnet?

Can you have Multiple SSID's on the same subnet?
SSID1 authenticates clients via radius.
Our corporation bought printers with wireless cards that only support WPA-PSK so we created SSID2 for the printers. We can connect to both SSID's and ping from SSID1 to SSID2 but we can not perform other functions such as view the printer management interface with a browser. Should it be possibe to communicate between SSID1 and SSID2 on the same subnet?

Yes you should have no issue, but the only thing is that you are using a lower security method... so either you put them on different subnets so you can control the traffic via acl's or might as well use the same security method to make it easier. The fact that you can ping sounds like you should be able to http to the device.

Multiple Scopes for the same subnet with Cisco CNR

I have a requeriment from my internal client that he wants to have multiple scopes within the same /21 subnet , but he wants to have different scopes for each group of servers ( in the /21 subnet).
We have 2 Cisco CNR ( I dont know the version they are running because they are managed by an external vendor) but they are in active / standby mode.
My question is .. it is posible to make the CNR have different scopes (ranges of IP's) for the same subnet ( /21) and assign those based on the client ( I dont know what criteria can be followed .. maybe Mac Address ???).
I appreciate any help or pointing to the right documentation
Thank you in advanced

I don't know that you would want a separate PO print. You can print the same PO print twice to provide a copy for the freight vendor. I think it should be okay as long as it is clear that the PO is with the vendor for the products but there is a condition specifying the freight deal. The second vendor (say the freight vendor) should be okay with this PO as well. I don't remember how the standard SAP PO forms handled the vendor condition but it should be enough I would think. I never came across a separate PO for freight since it is usually an value added service that is an integrated part of shipping goods and the paper-work usually is leveraged from PO, bill-of-lading, etc. SAP will make it difficult if you do need a separate PO since there is no way to use account assignment to material and therefore would need to manually account code and invoice verification, post to a clearing account in FI for re-class to material or charge to internal order with settlement to material or something like this.
I would just make sure that the PO print makes sense in terms of being able to see the freight charge and maybe the vendor name or something (look at the standard SAP PO form to see what the best practice is).

Multiple 11gR2 Clusterware installations on the same subnet using GNS

Hi,
I am hoping someone could shed some light on an issue I appear to have regarding the installation of 11gR2 Clusterware.   The main issue is that I have a host-vip.subdomain that fails to startup on installation. This is my 3rd cluster in my environment; the other 2 installed/configured ..fine.   This install fails because the host-vip.subdomain does not resolve with its own GNS service.
Further investigation lead me down a path involving my other clusters.   I found in my DNS server /var/log/messages file that the host-vip.subdomain was trying to resolve to host-vip.subdmain.subdomain_clust1 on IP xx.xxx.130.20.   However, this cluster's GNS service is listening on xx.xxx.130.22
More detail on the environment:
I currently have in production, two 2-node clusters.   Not RAC..just 2-node linux clusters; On the production clusters, I do have a single-instance database running in a 'warm failover' configuration.   I do use SCAN to access each of the database on their respective clusters.
I am using GNS and DHCP (obviously) to generate the VIPs for each cluster.    Cluster1 GNS IP - xx.xxx.130.20 ; Cluster2 GNS IP xx.xxx.130.21.   Both are configured in DNS and resolve the SCAN address to each of the VIPs on that server.
When testing SCAN access to the database, I noticed that a tnsping DB1 - which uses SCAN-name1.subdomain1 connects fine.   Also, tnsping to DB2 using SCAN-name2.subdomain2 connects fine as well.
However, the weird part is that if I use each others subdomain..they still connect ...ie....tnsping DB1 using SCAN-name1.subdomain2 ...still connects to DB1.. albeit , it takes about 10x longer to get a response.
This has lead me to the idea that since GNS is basically a mDNS service, broadcasting on the subnet .130...could it be possible that ANY GNS service on that subnet could resolve a name lookup request for any other GNS on the same subnet , and during installation of a new server, cause a new VIP to go to the wrong GNS service ?
So, my question is this : Is there any requirement I may have missed that state multiple Clusters using GNS / SCAN MUST BE on different subnets, as to not interfere with each other's lookup requests ?
Any info would be helpful
~ Allan

Was able to override the multicast address thru the command line and have just P1 work with
the following overrides.
-Dtangosol.coherence.clusteraddress=P1Cluster -Dtangosol.coherence.clusterport=11111
where p1Cluster=224.2.1.99 (say)
Thanks,
Vipin

Can I change which nic is used for a cluster network when more than one nic on the node is on same subnet?

This cluster has been up and working for maybe a year and a half the way it is. There are two nodes, running Server 2012. In addition to a couple network interfaces devoted to VM traffic each node has:
Management Interface: 192.168.1.0/24
iSCSI Interface: 192.168.1.0/24
Internal Cluster Interface: 192.168.99.0/24
The iSCSI interfaces have to be on same subnet as management interfaces due to limitations in the shared storage. Basically if I segregate it I wouldn't be able access the shared storage itself for any kind of management or maintenance tasks.
I have restricted the iSCSI traffic to only use the one interface on each cluster node but I noticed that one of the cluster networks is connecting the management interface on one cluster node member with the iSCSI interface on the other cluster node member.
I would like for the cluster network to be using the management interface on both cluster node members so as not to interfere with iSCSI traffic. Can I change this?
Binding order of interfaces is the same on both boxes but maybe I did that after I created the cluster, not sure.

Hi MnM Show,
Tim is correct, if you are using ISCSI Storage and using the network to get to it, it is recommended that the iSCSI Storage fabric have a dedicated and isolated network. This
network should be disabled for Cluster communications so that the network is dedicated to only storage related traffic.
This prevents intra-cluster communication as well as CSV traffic from flowing over same network. During the creation of the Cluster, ISCSI traffic will be detected and the network
will be disabled from Cluster use. This network should set to lowest in the binding order.
The related article:
Configuring Windows Failover Cluster Networks
http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Multiple Clusters on the same subnet

Hi,
We have two separate projects using coherence (3.5.2) in our location.
Unfortunately they will be deployed on the same subnet.
We use ExtencdTCP on the client side to connect to the cluster.
What steps should be taken so that Project1 (P1) is kept separate from P2...
We only have control over P1 or is there something that can be done purely from P1 config that will achieve this aim?
The config for the client is given below, since we can restrict the hostnames and the ports in the tcp-initiator elements, we can easily force the client to connect only to the relevant P1 machines.
+<cache-config xmlns="http://schemas.tangosol.com/cache">+
+<caching-scheme-mapping>+
+<cache-mapping>+
+<cache-name>dist-*</cache-name>+
+<scheme-name>extend-direct</scheme-name>+
+</cache-mapping>+
+</caching-scheme-mapping>+
+<caching-schemes>+
+<remote-cache-scheme>+
+<scheme-name>extend-direct</scheme-name>+
+<service-name>ExtendTcpCacheService</service-name>+
+<initiator-config>+
+<tcp-initiator>+
+<remote-addresses>+
+          <socket-address>+
+<address>P1.1</address>+
+<port>8078</port>+
+</socket-address>+
+               <socket-address>+
+                    <address>P1.2</address>+
+                    <port>8078</port>+
+               </socket-address>+
+               +
+          </remote-addresses>+
+</tcp-initiator>+
+<outgoing-message-handler>+
+               <heartbeat-interval>50s</heartbeat-interval>+
+               <heartbeat-timeout>35s</heartbeat-timeout>+
+               <request-timeout>30s</request-timeout>+
+          </outgoing-message-handler>+
+</initiator-config>+
+</remote-cache-scheme>+
+</caching-schemes>+
+</cache-config>+
On the server(s) there are
a.ExtendTCPService running on each
b.Mulitple cache servers with a distributed scheme running
The cache-config for the server is given below, how can we restrict the hosts that it searches for for clusters to join?
We noticed the configuration elements clusterport etc. that seem to be able to do this also authorized-hosts? Can this be done in the cache-config element or only in the cluster-config element.
+<?xml version="1.0"?>+
+
+<!DOCTYPE cache-config SYSTEM "cache-config.dtd">+
+<cache-config>+
+     <logging-config>+
+     <destination>cache-server.log</destination>+
+     <destination>stderr</destination>+
+     </logging-config>+
+<caching-scheme-mapping>+
+<cache-mapping>+
+<cache-name>dist-*</cache-name>+
+<scheme-name>dist-default</scheme-name>+
+</cache-mapping>+
+<cache-mapping>+
+<cache-name>repl-*</cache-name>+
+<scheme-name>repl-default</scheme-name>+
+</cache-mapping>+
+</caching-scheme-mapping>+
+<caching-schemes>+
+<distributed-scheme>+
+<scheme-name>dist-default</scheme-name>+
+<serializer>+
+          <class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>+
+          <init-params>+
+          <init-param>+
+               <param-type>string</param-type>+
+               <param-value>custom-types-pof-config.xml</param-value>+
+          </init-param>+
+          </init-params>+
+     </serializer>+
+<backing-map-scheme>+
+<local-scheme/>+
+</backing-map-scheme>+
+<autostart>true</autostart>+
+</distributed-scheme>+
+<replicated-scheme>+
+<scheme-name>repl-default</scheme-name>+
+<backing-map-scheme>+
+<local-scheme/>+
+</backing-map-scheme>+
+<autostart>true</autostart>+
+</replicated-scheme>+
+<proxy-scheme>+
+<service-name>ExtendTcpProxyService</service-name>+
+<thread-count>5</thread-count>+
+<acceptor-config>+
+<tcp-acceptor>+
+<local-address>+
+<address>localhost</address>+
+<port>8078</port>+
+</local-address>+
+</tcp-acceptor>+
+<serializer>+
+<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>+
+<init-params>+
+<init-param>+
+<param-type>string</param-type>+
+<param-value>custom-types-pof-config.xml</param-value>+
+</init-param>+
+</init-params>+
+</serializer>+
+</acceptor-config>+
+<autostart>true</autostart>+
+</proxy-scheme>+
+</caching-schemes>+
+</cache-config>+
Thanks for your response,
Vipb

Was able to override the multicast address thru the command line and have just P1 work with
the following overrides.
-Dtangosol.coherence.clusteraddress=P1Cluster -Dtangosol.coherence.clusterport=11111
where p1Cluster=224.2.1.99 (say)
Thanks,
Vipin

Multiple content switches on same subnet

Can anyone confirm if there is an issue having two pairs of content switches (11500s) on the same subnet? The circuit addressing, interface redundancy and VIPs all use the same subnet. Wondering if there would be any issues with the redundancy, arps, etc.. Am stuck with this arrangement during the migration phase of the project.
Appreciate your input.
Rob

Rob,
they can be on the same subnet but they must use different VIP ip addresses.
For the VRRP protocol, you should use different group number on each pair to avoid collision.
Otherwise, that is no problem. I have many pairs like this in the lab sharing the same subnets and this is ok.
Gilles.

Bonjour not finding anything from PC with Multiple NICs

We have two Network Interface Cards in each workstation at work to access two separate Physical Networks. Both networks provide access to ZeroConf (Bonjour) IP Printers.
Bonjour discovery fails intermittently on the two different networks. Occasionally Printers on one network, the other network, both or neither are visible from various workstations.
Is mDNSResponder aware of multiple NICs? Is there a way to force mDNSResponder to only search for printers on a particular subnet?

The second network adapter was installed after the VPC, indeed.
In the dropdown menu in the VPC networking settings there was only one network adapter to chose because the description for both physical network cards were the same. Therefore I cannot assign for virtual NICs different physical network adapters.
Finally I coped with the problem:
- I uninstalled one of the adapters (removing the drivers, too),
- edited the INF file in the adapter drivers and changed the description of the adapter
- I reinstalled the adapter with the altered driver (with the INF file changed).
Then, in the VPC networking settings both physical adapters appeared (one with the altered description).
I Wonder if that will cause any problems later ;)
Thanks for your replies :)

ISE 1.2 - Multiple NICs/Load Balancing for DHCP Probe

Hello guys
Just prepping an ISE 1.2 patch 8 setup in our organization. I am going for the virtual appliances with multiple NICs. It will be a distributed deployment with 4 x PSNs behind a load balancer and there is no requirement for wireless or guest user at the moment. I've got 2 points I will like to get some guidance on:
Our DC has a dedicated mgmt network and I plan to IP the gig0 interface of the PANs, MNTs and PSNs from this subnet. All device admin, clustering, config replication, etc will be over this interface. However, RADIUS/probe/other user traffic to the ISE PSNs will be over the gig1 interface which will be addressed from another L3 network. Is this a supported configuration in ISE?
I intend to use the DHCP probe as part of device profiling and will ideally like to have just an additional ip helper to add to our switch SVI config. Also, it will appear that WLCs can only be configured for 2 DHCP servers for a given network so another consideration for when we bringing our WLAN in scope. We however use ACE load balancers within our DC and from what I have read, they do not support DHCP load balancing. Are there any workarounds to using the DHCP probe with multiple PSNs without having to add each node as an ip helper/DHCP server on the NADs?
Thanks in advance
Sayre

Hello Sayre-
For Question #1:
Management is restricted to GigabitEthernet 0 and that cannot be changed so you should be good there
You can configure Radius and Profiling to be enabled on other interfaces
Even though you are not using guest services yet, you can dedicate an interface just for that. As a result, you can separate guest traffic completely from your production network
Take a look at this link for more info:
http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/installation_guide/ise_ig/ise_app_c-ports.html
For Question #2
If you are using a Cisco WLC and running code 7.4 and newer you don't need to mess with the IP helper configurations.
The controller can be configured to act as a collector for client profiling and interact with the DHCP thread along with the RADIUS accounting task that is running on the controller. The controller receives a copy of the DHCP request packet sent from the DHCP thread and parses the DHCP packet for two options:
–Option 12—HostName of the client
–Option 60—The Vendor Class Identifier
After this information is gathered from the DHCP_REQUEST packet, a message is formed by the controller with these option fields and is sent to the RADIUS accounting thread, which is in turn transmitted to the ISE in the form of an interim accounting message.
Both DHCP and HTTP profiling settings are located under the "Advanced" configuration tab in the WLC
On the other hand, you can also use Anycast for profiling. You can check out some of Cisco Live's sessions for more info on that. Here is one that is from a couple of years (There are more recent ones that are available as well):
http://www.alcatron.net/Cisco%20Live%202013%20Melbourne/Cisco%20Live%20Content/Security/BRKSEC-3040%20%20Advanced%20ISE%20and%20Secure%20Access%20Deployment.pdf
I hope this helps!
Thank you for rating helpful posts!

Problem accessing another public ip in same subnet

Hi,
I have searched around for a previous post regarding this but can't find an issue similar to mine (or I'm just too stupid to understand that it is )
I have a Cisco 5505 at a small business that I help. The problem is that the ISP are providing public IPs to multiple customers in a /24 subnet. The ASA has a single public IP configured 8.8.8.8 (not really, just for the examples sake) with a subnet mask of 255.255.255.0.
The webserver I have to access is not managed by me and is located in a different location (same town though) has 8.8.8.115, it is located in the same subnet as the ASA.
How would I make this work? I have tried to configure a static arp entry for the web server but it just won't work. If i place a computer directly on the outside interface I have no problem accessing the web server.
I am running ASA version 8.2, but I could upgrade if it would help me solve the problem.
Any help with this issue is much appreciated.

The ISP only specify one gateway in that range and that is 8.8.8.1 so any other would not let me access internet.
Once again thank you for your time.
: Saved
ASA Version 8.2(1)
hostname ciscoasa
domain-name XXXXXXX
enable password XXXXXXX encrypted
passwd XXXXXXX encrypted
names
name 8.8.8.8 Outside_IP
name 192.168.20.2 Server
name 192.168.20.11 rav-dc01
name 192.168.20.12 rav-ms01
name 192.168.20.13 rav-rds01
interface Vlan1
nameif inside
security-level 100
ip address 192.168.20.1 255.255.255.0
interface Vlan2
nameif outside
security-level 0
ip address Outside_IP 255.255.255.0
interface Ethernet0/0
switchport access vlan 2
interface Ethernet0/1
interface Ethernet0/2
interface Ethernet0/3
interface Ethernet0/4
interface Ethernet0/5
interface Ethernet0/6
interface Ethernet0/7
boot system disk0:/asa821-k8.bin
ftp mode passive
dns server-group DefaultDNS
domain-name XXXXXXX
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object-group protocol TCPUDP
protocol-object udp
protocol-object tcp
access-list inside_nat0_outbound extended permit ip any 192.168.25.0 255.255.255.0
access-list RemoteVPNSplittunnel standard permit 192.168.20.0 255.255.255.0
access-list outside_access_in extended permit tcp host 100.100.100.228 interface outside eq 3389
access-list outside_access_in extended permit tcp any interface outside eq smtp
access-list outside_access_in extended permit udp any interface outside eq 4125
access-list outside_access_in extended permit tcp any interface outside eq 4125
access-list outside_access_in extended permit tcp any interface outside eq https
access-list outside_access_in extended permit tcp any interface outside eq pptp
access-list outside_access_in extended permit tcp any interface outside eq 444
access-list outside_access_in extended permit gre any interface outside
access-list outside_access_in extended permit udp any interface outside eq 444
access-list outside_access_in extended permit tcp any interface outside eq www
access-list inside_access_in extended permit tcp host rav-ms01 any eq smtp
access-list inside_access_in extended deny tcp any any eq smtp
access-list inside_access_in extended permit ip any any
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
ip local pool RemoteVPNPool 192.168.25.100-192.168.25.200 mask 255.255.255.0
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-621.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 0.0.0.0 0.0.0.0
static (inside,outside) udp interface 4125 Server 4125 netmask 255.255.255.255
static (inside,outside) tcp interface 4125 Server 4125 netmask 255.255.255.255
static (inside,outside) tcp interface https rav-ms01 https netmask 255.255.255.255 dns
static (inside,outside) tcp interface pptp Server pptp netmask 255.255.255.255
static (inside,outside) tcp interface 3389 rav-rds01 3389 netmask 255.255.255.255 dns
static (inside,outside) tcp interface smtp rav-ms01 smtp netmask 255.255.255.255
static (inside,outside) udp interface 444 Server 444 netmask 255.255.255.255
static (inside,outside) tcp interface 444 Server 444 netmask 255.255.255.255
static (inside,outside) tcp interface www Server www netmask 255.255.255.255 dns
access-group inside_access_in in interface inside
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 8.8.8.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
aaa-server rav_Intern protocol radius
aaa-server rav_Intern (inside) host rav-dc01
key CiscoAsa5505RAV2012
radius-common-pw CiscoAsa5505RAV2012
http server enable 8080
http 192.168.20.0 255.255.255.0 inside
http 192.168.25.0 255.255.255.0 inside
http 100.100.101.128 255.255.255.192 outside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
sysopt connection timewait
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto dynamic-map outside_dyn_map 20 set pfs
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-SHA
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption aes-256
hash sha
group 2
lifetime 86400
telnet 192.168.20.0 255.255.255.0 inside
telnet timeout 5
ssh 192.168.20.0 255.255.255.0 inside
ssh timeout 5
console timeout 0
management-access inside
dhcpd auto_config outside
dhcpd address 192.168.20.190-192.168.20.200 inside
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ntp server rav-dc01 source inside
webvpn
group-policy RemoteVPN internal
group-policy RemoteVPN attributes
wins-server value 192.168.20.11
dns-server value 192.168.20.11
vpn-tunnel-protocol IPSec
split-tunnel-policy tunnelspecified
split-tunnel-network-list value RemoteVPNSplittunnel
default-domain value rav.nu
split-dns value rav.nu
username SupportVPN password XXXXXXX encrypted privilege 0
username SupportVPN attributes
vpn-group-policy RemoteVPN
tunnel-group RemoteVPN type remote-access
tunnel-group RemoteVPN general-attributes
address-pool RemoteVPNPool
authentication-server-group rav_Intern
accounting-server-group rav_Intern
default-group-policy RemoteVPN
tunnel-group RemoteVPN ipsec-attributes
pre-shared-key *
class-map inspection_default
match default-inspection-traffic
policy-map global_policy
class inspection_default
inspect pptp
inspect icmp
inspect icmp error
service-policy global_policy global
prompt hostname context
Cryptochecksum:8481ab3aa01b23bad17bacb2aca7197a
: end
asdm image disk0:/asdm-621.bin
no asdm history enable

Weblogic Cluster on a machine with multiple NIC

Out Setup
          One Quad Machine
          2 NIC - one ip address on each
          Two weblogic installations
          Each Instance is listening on one address and port 7001.(managed servers)
          Admin Server on one of the ip and port 8001
          Both managed servers part of a cluster.
          While i check weblogic console i see both the managed server
          having almost same number of frames incoming and outgoing.
          If i check 4 processers all 4 of them working eqaully same
          during out load test..(almost 85%)
          But i check NICs only one of them seems to be working really hard..
          and another one so..so.. what could be the problem??


          Weblogic 7 has a new concept called network channel, where there is a section talking
          about clustering over multiple NIC cards. I was confused by the cluster address in
          customized network channel (no example there). I tried to use multiple NIC cards
          for the purpose of network failover, but failed in clustering environment, although
          I succeed in single server environment.
          Kumar Allamraju <[email protected]> wrote:
          >You can set Interface address via admin console's
          >Cluster >> {Cluster Name }
          >
          >on the right hand side you will find InterfaceAddress box.
          >
          >--
          >Kumar
          >
          >zevit wrote:
          >
          >>>It's the JVM & OS who will take adv. of multiple NIC's. We don't have
          >>>anything in WLS that does this thing.
          >>>
          >>>Alternatively you can bind each WLS instance to a specific NIC card
          >>>to effeciently utilize each NIC card.
          >>>
          >>
          >> thank u kumar.. Could u please tell me how do i bind each WSL instance
          >> to a specific NIC ?
          >>
          >

Ip in the same subnet gets routed Why?

Hi
In windows 2008 server R2, it is connecting to production network through the teamed network adapter.Ip of the teamed adapter is 10.157.86.31 255.255.255.0 and its gateway is 10.157.86.1
And the server is getting backed up with the backup interface configured with 10.128.141.64 255.255.248.0 in one of the nic in the server connected to the NAS Drive with the ip address 10.128.141.28 .The backup was happening perfectly as the backup is a non-routed
network.
Once the motherboard of the server is changed, suddenly the backup stopped worked failing in authentication to the NAS drive because in NAS Drive authentication is setup based on the ip addresses of the servers connected to the NAS Drive.
What I have found is that even though the server's backup ip address is not changed , still the NAS drive ip 10.128.141.28 is reached via another network gateway 10.157.86.31 even though the NAS DRive is connected in the same subnet.
Since the NAS DRive is reached by the server through the ip address of the gateway 10.157.86.31, the authentication fails with the NAS drive because it expects the ip address to be as 10.128.141.64
how to force the traffic to the ip 10.128.141.28 to initiate through the nic 10.128.141.64 ?
Any suggestions please
Below is the answer for the problem ; already implemented and backup is working
But needed the clarification
Below is the solution too:
In spite of rebuild of the server from scratch by freshly installing the operating system , the backup vlan is not connected.So I decided to connect the cable coming from the switch port to the unused nic port of the server and it solved the issue by reconfiguring
the ip address to the new nic port.
But needed one clarification here:
Before swapping the cable to spare nic the picture is below
Highlighted above is the nic connected to the backup vlan through which no communication happens.
So decided to swap the cable from lan1 (backup) which is a separate nic to the spare nic available in the server which is higlighted below
After configuring the backup ip address to the new spare nic also resulted in the traffic routed the production vlan which should not be the case.And moreover my observation from the above screeshot , why swapping the cable from the lan1(non-teamed adapter)
is showing that lan4 (teamed adapter)as disconnected .
And moreover , currently the setup is working as below with the backup traffic happening through the backup vlan when it is configured in the above manner
Thanks & Regards S.Swaminathan Live & let others live!!!

Did you set the interface binding order correctly or to match the previous server?
DNS: Valid network interfaces should precede invalid interfaces in the binding order
http://technet.microsoft.com/en-us/library/dd391967(v=WS.10).aspx
Modify the protocol bindings and network provider order
http://technet.microsoft.com/en-us/library/cc732472(v=WS.10).aspx
An incorrect IP address is returned when you ping a server by using its NetBIOS name in Windows Server 2008 or in Windows Server 2008 R2
http://support2.microsoft.com/kb/981953
You can view your current binding order by using this script, but please note, that I haven't tried this script, yet:
Show NIC Binding Order
http://gallery.technet.microsoft.com/scriptcenter/Get-NIC-Binding-Order-a2dc8087
Also, prior to setting up the teams, make sure that the NIC is set to obtain IP automatically and not have a static entry on it. I've seen this cause problems in the past.
If you have any unused NICs, such as Local Area Connection 2, don't just unplug them. You must disable them, otherwise they will try to register the APIPA in DNS and that will cause problems.
Make sure that the correct DNS are on the interfaces that you need to use, too.
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

WOL question. SCCM server with multiple nics.

Hi,
I have a sccm server with multiple nics, I can wake up any machine using a 3ed party magic packet utility, if I set a schedule and use sccm wol functionally the machine never wakes up. As I pointed out my server has multiple nics, does anyone have a sccm
server with multiple nics with sccm built in wol functionally working?. I am curious on how you achieved this.

Hey Garth,
Yes the problem is solved but we had to buy a 3rd party power management utility to accomplish WOL. Because we have many different subnets in our environment we found that this was the fastest way to get WOL working,
So out of the box SCCM would not work for us, with a 3rd party utility that had an SCCM plugin WOL now works flawlessly.

Multiple NICs?

Hey; can miggui handle source and target servers with multiple NICs/IP addresses? I have a DNS/DHCP server to migrate that services two separate VLANs, and I want to make sure I'm not going to blow the whole thing sky-high.
Thanks.

The Migration DHCP leases file issue has been fixed in the jumbo patch that just went into the oes2sp1 and sp2 updated channels a couple days ago. (bug 561928 - issue below).
Steps to Reproduce:
1. Setup NW server (6.5 SP 7 in this case)
2. Setup OES server in the same tree. Remove edir replicas.
3. Setup DHCP on both servers. NW should be configured with a range of 2
address. OES should have the dhcp server setup.
4. Run a windows client with one nic. Get a DHCP address and note the ip
address given.
5. Run the Novell Migration for DHCP (transfer ID option). Choose the
server-level migration.
6. Run the migration, and then run the post migration step per the
documentation.
7. Start DHCP on the OES box and watch the /var/log/messages. Restart or
/release /renew the address from the client. It will not get the same address
as before, but the second address in the pool. Drop the client and add a v-nic
(if vmware), or have another client try and grab an address. The DHCP server
will say it is out of leases, when in reality the first lease is not being
honored.
Actual Results:
See above
Expected Results:
Expected the first client to get its original DHCP assigned address back,
therefore leaving the remaining addresses in the pool open to new clients.

Multiple NICs, same subnet

Similar Messages

Maybe you are looking for