Virtual Interface IP address

Hi,
In all Cisco documentation 1.1.1.1 is always specified as Virtual Interface IP address.
Here is my concern. When wireless client gets an IP address (through DHCP), 1.1.1.1 is entered as DHCP server which means that at 50% lease time client will attempt DHCP Request to 1.1.1.1
1.1.1.1 is not routable on the wired network, but controller makes sure that it is accessible on the wireless network.
The problem is if you have both wired and wireless connected, default gateway through wired connection wil have less cost, so client will attempt to send traffic to 1.1.1.1 using wired interface and will obviously fail.
At 83.5% of lease time client will attempt full DHCP process starting from Discovery and I guess this is when the IP on wireless NIC will be renewed, cause those Discovery messages are to 0.0.0.0....
Is my understanding correct?
Thanks!
David

Hi,
With both wired and wireless active at the same time (when laptop is docked for example)DHCP Request to 1.1.1.1 will fail cause it will be sent using wired interface and not wireless (default route metric in the host's routing table). This will cause this DHCP Request to fail at 50% lease time.
Next step is DHCP Discover at 83.5% of lease time. Destination IP will be 255.255.255.255 and it will be generated specifically on wireless interface, since this in the interface that needs to renew the IP.
This is exactly my question. Will this Discover to 255.255.255.255 go through wireless interface, cause this is the interface that needs IP addresses renewed. If so, I assume it will succeed and client's IP address will be renewed.
A bit worse than renewing at 50% lease time as a normal DHCP process, but better than loosing the IP at all when 100% lease time hits. 83.5% is somewhere in between...
Comments?
Can you also advise how do you disable DHCP Relay function on the controller? Do you need to remove DHCP IP addresses in WLAN configs?
Another question is about needing WLAN for Management interface. Is it needed for any reason? WLANs are always documented to be bound to Dynamic Interfaces and not Management, however Management interface does appear in the drop down menu under WLAN configuration. Thoughts?
Thanks!
David

Similar Messages

CSS- traffic orignating from real server + Virtual interface

Hi all,
I am designing a solution at the moment, in which I shall have 2 servers behind a pair of CSS & their default gateway will be the Virtual Interface ip address of CSS.
Is there any problem forseen in traffic getting initiated from the server to any other subnet in the network and the return traffic to the server.
Servers shall connect to a pair of 3750 being used as L2 in stack .
The Stacked 3750's shall be placed below the CSS pair & the CSS pair shall further connects to a single 6509 upstream....
Each 3750-L2 connects single port to each CSS
(3750-L2-1 to CSS1 &
3750-L2-2 to CSS 2)
Both CSS connect to the SINGLE 6509 on diff blades. for better redundency.
The CSS shall not be connected to each other directly.
Both 3750-L2 connect to each other as well
IIS-1---L2_Sw1---CSS1---6509---Othr_Subent
IIS-1---L2_Sw2---CSS2---6509---Othr_Subent
Note: I shall have VIP/Virtual Interface config on my CSS's.
Appreciate validation and recomendations on this design.
Many Thanks,
gagan

Hi Gilles,
Many thanks for the confirmation.
Request verification on the below as well~
1. With the above scenario; I do not require any group (NAT) configuration, either for my servers initiating traffic for going out or for clients hitting the VIP to reach servers. The client & server shall be in diff VLAN?s of course.
2. With VIP & Virtual Interface configuration & couple of server VLAN's below on server side, I should be able to use both the gigabit interfaces on the 11503 to connect up and down stream as TRUNK. I mean to ask Virtual intf. & VIP has no problems working on the same TRUNK interface?
3. I understand that Fate sharing and critical service helps full failover (client & server side).
As an upstream router or L3 switch fails or the upstream connecting gigabit interface on CSS fails, the failover happens.
Will the same be applicable to downstream L2 switch & CSS interface failure? If any of these on the downstream fails will the CSS failover to the standby unit.
I think this above should work, just need confirmation coz I have not done this before.
Thanks a lot again,
Gagan

WLC Virtual Interface config for a public SSL cert for Web Authentication

I'm trying to get a cert loaded on my 5508 WLC running 7.6.130.0 so when a Web-Auth users tries to authenticate they don't get the SSL cert error.
In the document "Generate CSR for Third−Party Certificates and
Download Chained Certificates to the WLC"
Document ID: 109597 it states the following
"Note: It is important that you provide the correct Common Name. Ensure that the host name that is
used to create the certificate (Common Name) matches the Domain Name System (DNS) host name
entry for the virtual interface IP on the WLC and that the name exists in the DNS as well. Also, after
you make the change to the VIP interface, you must reboot the system in order for this change to take
effect.
Here are my questions.
1. I have always had 1.1.1.1 as the address of the Virtual interface, should that change or can I leave it as 1.1.1.1?
2. In the "DNS Host Name" Field do I simply put the domain or the FQDN? Example. Company.com or hostname.company.com

Hi,
1) You can change that if you want. Normally it is non-Public and non-routable in your network.
2) Put the Host name for which you are going to give in your company DNS server where that Host name would be mapped to the Virtual ip address.
Regards
Dhiresh
** Please rate helpful posts**

WLAN Controller learning IP/MAC on wrong virtual interface

Hello
I believe since I upgraded my WiSM to 7.0.250.0 is it learning a MAC address on the wrong virtual interface.
The setup:
- a Linux server with 2 virtual interfaces, both use the same MAC address, one is the gateway of VLAN 116 and one is the gateway of VLAN 240
- a WiSM with several virtual interfaces, including one in 116 and one in 240
Here the arp table with the problem:
    MAC Address        IP Address     Port   VLAN   Type
00:50:56:BD:32:92   172.16.240.9     29     240    Host
00:1E:4A:FA:87:8B   172.16.102.12    29     0      Permanent
00:1E:4A:FA:50:0B   172.16.102.13    29     0      Permanent
00:1E:4A:FA:81:2B   172.16.102.14    29     0      Permanent
00:50:56:BD:32:92   172.16.116.9     29     240    Host
00:1D:E0:31:55:23   172.16.116.185   29     116    Client
58:94:6B:68:50:E8   172.16.118.201   29     116    Client
1C:B0:94:B7:38:08   172.16.118.234   29     116    Client
And here after I made a PING from the controller to the listed ip address:
    MAC Address        IP Address     Port   VLAN   Type
00:50:56:BD:32:92   172.16.240.9     29     240    Host
00:1E:4A:FA:87:8B   172.16.102.12    29     0      Permanent
00:1E:4A:FA:50:0B   172.16.102.13    29     0      Permanent
00:1E:4A:FA:81:2B   172.16.102.14    29     0      Permanent
00:50:56:BD:32:92   172.16.116.9     29     116    Host
00:1D:E0:31:55:23   172.16.116.185   29     116    Client
38:E7:D8:D3:7C:FA   172.16.118.92    29     116    Client
58:94:6B:68:50:E8   172.16.118.201   29     116    Client
1C:B0:94:B7:38:08   172.16.118.234   29     116    Client
18:AF:61:12:E9:FB   192.168.1.59     29     117    Client
Has anybody else the same problem?
The host 172.16.116.9 is also the configured DHCP server on VLAN 116.
Is there a way to statically configure this IP address on that VLAN? Because it causes every few days a service outage on that VLAN (which is bound to an SSID).

Yup, I'd say still valid. Seeing as it is the gateway, if it had different mac addresses per interface, it might still work.
No, clients in the same subnet can communicate, but it is not recommended to 'bridge' wired and wireless with a WLC. The WLC doesn't like to bridge the communication by default, though there are work arounds.
I might also say that as it uses the same MAC address for both virtual interfaces L2 is going to be messed up as each time there were an ARP the entry would change.
Take a look and see if you can manually change the mac for one of the interfaces and test again.
HTH,
Steve

Help required - mac address table, virtual pc/ip addressing issue

Hi, hope someone out there can help?
This is the scenario
SW1 (WS-C2960G-48TC-L) port gig0/1 has a PC connected to it with ip address 10.182.8.6 and a Virtual IP address 10.182.8.107
SW2 (WS-C2960-24TT-L) port gig 0/1 has a PC connected to it with ip address 10.182.8.106
The system is designed so that if there is an issue with the PC connected to SW1, the PC on SW2 will take over the Virtual IP address and continue working.
We have a couple of other PC's in different subnets to the above PC's that use the Virtual IP (VIP) address to communicate with the PC that is 'on line'.
Unfortunately, the vendors software doesn't currently gratuitously refresh the arp to advertise the change of mac address for the VIP.
Is there anyway we can get the 2 dcnsw to 'refresh' on a regular time period to capture when the VIP changes to the other PC?

Hi Stephen
Without meaning to sound rude, the software which uses a VIP is not very well designed if it is not capable of sending a Gratuitous ARP one the Active one fails.
The default ARP cache timeout is 4 hours so an ARP entry will remain in the table and once the timeout is up, the switch will send an ARP to check if the device is still alive and if not, remove the entry from the table.
You could look at reducing the ARP timeout on a per port basis:
#interface gi1/0/1
#arp timeout 60
This will change the ARP cache timeout to 60 seconds for that port but having not used this before, I am not 100% this will address your issue. I would not advise trying to change the global ARP cache timeout for a production switch as this will increase ARP traffic and could cause problems if reduced to a small value.

Why virtual interfaces added to ManagementOS not visible to Cluster service?

Hello All,
I"m starting this new thread since the one before is answered by our friend Udo. My problem in short is following. Diagram will be enough to explain what I'm trying to achieve. I've setup this lab to learn Hyper-V clustering with 2 nodes. It is Hyper-V
server 2012. Both nodes have 3x physical NIcs, 1 in each node is dedicated to managing the Node. Rest of the two are used to create a NIC team. Atop of that NIC team, a virtual switch is created with -AllowManagementOS
$False. Next I created and added following virtual interfaces to host partition, and plugged them into virtual switch created atop of teamed interface. These virtual interfaces should serve the purpose of various networks available.
For SAN i'm running a Linux VM which has iSCSI target server and clustering service has no problem with that. All tests pass ok.
The problem is......when those virtual interfaces added to hosts; do not appear as available networks
to cluster service; instead it only shows the management NIC as the available network to leverage.
This is making it difficult to understand how to setup a cluster of 2x Hyper-V Server nodes. Can someone help please?
Regards,
Shahzad.

Shahzad,
I've read this thread a couple of times and I don't think I'm clear on the exact question you're asking.
When the clustering service goes out to look for "Networks", what it does is scan the IP addresses on each node. Every time it finds an IP in a unique subnet, that subnet is listed as a network. It can't see virtual switches and doesn't care about
virtual vs. teamed vs. physical adapters or anything like that. It's just looking at IP addresses. This is why I'm confused when you say, "it won't show virtual interfaces available as networks". "Networks" in this context are IP subnets.
I'm not aware of any context where a singular interface would be treated like a network.
If you've got virtual adapters attached to the management operating system
and have assigned IPs to them, the cluster should have discovered those networks. If you have multiple adapters on the same node using IPs in the same subnet, that network will only appear once and the cluster service will only use
one adapter from that subnet on that node. The one it picked will be visible on the "Network Connections" tab at the bottom of Failover Cluster Manager when you're on the Networks section.
Eric Siron Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
"Every relationship you have is in worse shape than you think."
Hello Eric and friends,
Eric, much appreciated about your interest about the issue and yes I agree with you when you said... "When the clustering service goes out to look for "Networks",
what it does is scan the IP addresses on each node. Every time it finds an IP in a unique subnet, that subnet is listed as a network. It can't see virtual switches and doesn't care about virtual vs. teamed vs. physical adapters or anything like that. It's
just looking at IP addresses. This is why I'm confused when you say, "it won't show virtual interfaces available as networks". "Networks" in this context are IP subnets. I'm not aware of any context where a singular interface would be treated
like a network."
By networks I meant to say subnets. Let me explain what I've configured so far:
Node 1 & Node 2 installed with 3x NICs. All 3 NICs/node plugged into same switch.
Node1: 131.107.0.50/24
Node2: 131.107l.0.150/24
A Core Domain controller VM running on Node 1: 131.107.0.200/24
A JUMPBOX (WS 2012 R2 Std.) VM running on Node 1: 131.107.0.100/24
A Linux SAN VM running on Node 2: 10.1.1.100/8
I planed to configured following networks:
(1) Cluster traffic: 10.0.0.50/24 (IP given to virtual interface for Cluster traffic in Node1)
Cluster traffic: 10.0.0.150/24 (IP given to virtual interface for Cluster traffic in Node2)
(2) SAN traffic: 10.1.1.50/8 (IP given to virtual interfce for SAN traffic in Node1)
SAN traffic: 10.1.1.150/8 (IP given to virtual interfce for SAN traffic in Node2)
Note: Cluster service has no problem accessing the SAN VM (10.1.1.100) over this network, it validates SAN settings and comes back OK. This is an indication that virtual interface is
working fine.
(3) Migration traffic: 172.168.0.50/8 (IP given to virtual interfce for
Migration traffic in Node1)
Migration traffic: 172.168.0.150/8 (IP given to virtual interfce for
Migration traffic in Node2)
All these networks (virtual interfaces) are made available through two virtual switches which are configured EXACTLY identical on both Node1/Node2.
Now after finishing the cluster validation steps (which comes all OK), when create cluster wizard starts, it only shows one network; i.e. network of physical Layer 2 switch i.e. 131.107.0.0/24.
I wonder why it won't show IPs of other networks (10.0.0.0/8, 10.1.1.0/8 and 172.168.0.0/8)
Regards,
Shahzad

Ability to ping redundant interface IP address

Hi,
I have this setup for our content switches.
Primary F/W --> Primary CSS --> Local Switches
| |
| |
Secondary F/W --> Secondary CSS --> Local Switches
This is the relevant configuration.
Primary CSS
circuit VLAN4
ip address 192.168.76.4 255.255.255.0
ip virtual-router 4 priority 101 preempt
ip redundant-interface 4 192.168.76.254
Secondary CSS
circuit VLAN4
ip address 192.168.76.5 255.255.255.0
ip virtual-router 4 priority 90
ip redundant-interface 4 192.168.76.254
The problem is that the Secondary F/W can not ping the redundant interface IP address via the secondary path when all devices are in normal mode.
Is this normal?
The ping is occuring for firewall failover checking.
Thanks,
Ben

it should work.
Your diagram does not display very well, so I don't know where are the | links.
What should be the path of traffic from secondary firewall redundant-interface ?
Is the traffic going to 1 CSS and being bridge to the 2nd CSS ?
If that's the case, you need the command 'ip uncond-bridging' on both CSS to force CSS to bridge first and then route.
Regards,
Gilles.

WLC Mobility and Interface IP Address

Hello,
I am in the process of adding an additional WLC to an environment that currently has only 1 WLC. I am going to set up a single mobility group. Do the IP addresses of the vlan interfaces on both WLCs need to be the same value? I realize that the virtual interface does need to be the same, but not sure about the vlan interfaces.
Any comments are appreciated.
Thanks.
JT

Hi,
no they don't need to be the same. You don't even need your WLCs to have interfaces in the same subnets. They can have all interfaces completley different. Just the virtual interface needs to be the same.
Nicolas
===
Don't forget to rate answers that you find useful

AP Manager interface and Virtual Interface

What do each of these interfaces do on the 526 WMAC? I am not sure I understand the functionality and did not find the answer to this in the documentation.
Thanks

Well from a WLC, the management is used to access and manage the wlc. It is also used for communication with the mobility group. AP-Manager is the interface the wlc and the ap's use and the virtual interface is used by internal dhcp, mobility group, webauth, etc. The virtual interface is not routable in your network, it is mainly used by the wlc's for various features.
Here is from a Cisco Doc:
The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA server. If the service port is in use, the management interface must be on a different subnet than the service port.
The AP-Manager interface is used as the source IP address for all Layer 3 communications between the controller and the lightweight access points. The AP-Manager must have a unique IP address and should be on the same subnet as the management interface.
The virtual gateway interface is used to support mobility management, DHCP relay, and embedded Layer 3 security, like guest web authentication and VPN termination. The virtual interface must be configured with an unassigned and unused gateway IP address. If multiple controllers are configured in a mobility group, the virtual interface must be the same on all controllers for seamless roaming.
The service-port interface is mapped only to the physical service port. The service port interface must have an IP address on a different subnet from the management and AP-Manager interfaces. A default-gateway cannot be assigned to the service-port interface, but static routes can be defined through the controller command-line interface for remote network access to the service port.

Using Virtual interface in jumpstart

Hi All,
I have a jumpstart server on which virtual VLANs have been configured.
When net installation of a server in VLAN is started the RARP request is received on the the virtual interface on which VLAN has been configured, but no reply is sent.
What can be the problem? Sorry if this has been asked before.
Command used to create virtual interface:
ifconfig bge110001 plumb
ifconfig bge110001 a.b.c.d netmask 255.255.255.224
ifconfig bge110001 up
This created interface bge110001, VLAN 110 and is associated to bge1 (physical interface)

I know you see it in snoop, but does in.rarpd recognize it as an address that it owns? Is it seeing the packet at all? Running in debug mode should give that information.
Yes, RARP packets are broadcasts.
Darren

How do virtual interfaces work?

I've got two servers Sun Fire V210 already configured. But I can't figure out what does virtual interfaces mean? How should I configure Catalyst 2950 to support them?
priems# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.154.223.10 netmask ffffff00 broadcast 10.154.223.255
ether 0:3:ba:dc:48:77
eri0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.153.122.10 netmask ffffff00 broadcast 10.153.122.255
eri1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.154.224.10 netmask ffffff00 broadcast 10.154.224.255
ether 0:3:ba:dc:48:78
eri1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.153.123.10 netmask ffffff00 broadcast 10.153.123.255
I'm actually newby in Solaris, so please, help me/

sergrfghnnbnnnfn wrote:
I've got two servers Sun Fire V210 already configured. But I can't figure out what does virtual interfaces mean?Normally one IP address is associated with a network interface. A virtual interface allows multiple IP addresses to be used on the same port simultaneously.
How should I configure Catalyst 2950 to support them? I'm not sure what you're asking. Is there a problem you're running into? Your additional IP addresses appear to be on separate subnets. So whatever your network environment is needs to provide both subnets to the port. That might be done by putting VLANs on a port, but really that's up to whatever you and your hardware can accomplish.
Darren

Virtual interface ip of Wireless controller

Hi,
In our wireless controller, there is a virtual interface having ip 192.168.100.1.
when tracing the packets, we saw this ip being reflected in sniffer as dhcp server address instead of original dhcp server ip.
The controller interfaces of ssid have original dhcp server ip ( 172.16.31.2 ) mentioned in them, this is where clients get there ip from.
In this case, why does virtual interface ip (192.168.100.1) is seen as dhcp server in sniffer traces instead of original dhcp server 172.16.31.2
Appreciate all inputs to help me understand this.

If you have dhcp proxy enabled in the WLC, which is default, the WLC will proxy dhcp and it uses the virtual IP address. If you look at a client that is connected to the wireless and on a windows machine you look at the ipconfig /all, you will also see that the dhcp server is the virtual IP address if the WLC. Dhcp proxy can be disabled as long as you dint have the WLC being used as the dhcp server, or else it it's required to have dhcp proxy enabled.
Virtual IP is also used for mobility and guest portal page.
Sent from Cisco Technical Support iPhone App

Not pinging virtual interface

Dear All,
I have got new cisco ASA 5580 running 7.2(4) on it when i am trying to configured Virtual interface on vlan 400 in Gi0/0.400 to LBASE.now the problem is
from my MZ zone 10.242.107.17 to Lbase virtual interface 10.242.103.1 iam not able to ping.
Please suggest.
Many Thanks
Srini

Hi Varun,
Thanks for reply
iam configuring SNMP on my serverload balancer and my SLB v-lan is 400 and igiven virtual interface ip 10.242.105.1 on my ASA.
In my asa my snmp server is 10.242.103.42 now iam unable to ping from my snmp server to ace virtual ip 10.242.105.1 to discover ace on my snmp server.
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.1 255.255.255.0
management-only
interface Management0/1
description LAN Failover Interface
management-only
interface GigabitEthernet3/0
nameif OUTSIDE
security-level 0
ip address 223.27.122.19 255.255.255.240 standby 223.27.122.20
interface GigabitEthernet3/1
nameif DMZ
security-level 50
ip address 10.242.104.1 255.255.255.0 standby 10.242.104.2
interface GigabitEthernet3/2
nameif INSIDE
security-level 0
no ip address
interface GigabitEthernet3/2.200
vlan 200
nameif MZ
security-level 80
ip address 10.242.103.1 255.255.255.0 standby 10.242.103.2
interface GigabitEthernet3/2.300
vlan 300
nameif NOC
security-level 79
ip address 10.242.101.100 255.255.255.0 standby 10.242.101.101
interface GigabitEthernet3/2.310
vlan 310
nameif DB-NETW-1
security-level 75
ip address 10.242.110.1 255.255.255.0
interface GigabitEthernet3/2.400
vlan 400
nameif LBACE
security-level 90
ip address 10.242.105.1 255.255.255.0 standby 10.242.105.2
interface GigabitEthernet3/2.500
vlan 500
nameif DC-USERS
security-level 60
ip address 10.242.109.1 255.255.255.0
interface GigabitEthernet3/2.800
vlan 800
nameif DMZ-ACC
security-level 48
ip address 10.242.107.1 255.255.255.0 standby 10.242.107.2
interface GigabitEthernet3/2.900
vlan 900
nameif MZ-ACC
security-level 49
ip address 10.242.108.1 255.255.255.0 standby 10.242.108.2
interface GigabitEthernet3/3
shutdown
no nameif
no security-level
no ip address
2) ACE conf:
snmp-server community nglsnmp group Network-Monitor
snmp-server host 10.242.103.42 traps version 2c nglsnmp
snmp-server host 10.242.103.43 traps version 2c nglsnmp
snmp-server host 10.242.103.44 traps version 2c nglsnmp
snmp-server host 10.242.103.45 traps version 2c nglsnmp
snmp-server enable traps slb serverfarm
snmp-server enable traps snmp coldstart
snmp-server enable traps slb vserver
snmp-server enable traps slb real
snmp-server enable traps syslog
snmp-server enable traps snmp authentication
snmp-server enable traps snmp linkup
snmp-server enable traps snmp linkdown
please help me
srini

Virtual Interface generation bug in NetWeaver ?

I use the Web Service generation wizard to generate a virtual interface which exposes methods in an EJB. As one of the parameters I pass a simple java bean, lets say:
public class StatusCode
private String name;
private boolean buggy;
public String getName() {...}
public void setName(String newName){...}
public boolean isBuggy() {...}
public void setBuggy(boolean trueOrFalse){...}
When I look at the virtual interface generated, especially at the Types tab, my boolean attribute is not included.
If I change the getter to "getBuggy()", the attribute is included in the VI. The only problem is that the typical Java Bean framework, say from sun or ibm, always map 'boolean' getters to 'isSomething()' and not 'getSomething()'.
Is this a bug with NW? Is there a fix or workaround for this ?
My version of NW:
Version: 2.0.7
Build id: 200407270250
Thanks in advance,
Mark
I posted this question also in the NW development forum, but so far no replies.

I try to login by use:
username : Administrator
password : <master password> (at least 1 number)
I try to login many times but it always fails.
(I am very sure about my password since i also try to reinstall many times - 10th. both J2EE 1.4 and Java EE 5)
Ivaylo Ivanov, do you sure that you test with this new edition. (Not the previous edition)
I see the other persons get the result like me:
Telnet Administration
SAP J2EE Engine v7.100
User name: Administrator
Password:
The user account is either expired, or not valid yet.
Login failed. Reason: The user account is either expired, or not valid yet.
Connection to host lost.
if my login is not correct, it will tell the other messags.
Telnet Administration
SAP J2EE Engine v7.100
User name: f
Password:
Cannot authenticate the user.
Login failed. Reason: Cannot authenticate the user.

Virtual Interface generation bug with NetWeaver ?

I use the Web Service generation wizard to generate a virtual interface which exposes methods in an EJB. As one of the parameters I pass a simple java bean, lets say:
public class StatusCode
    private String name;
    private boolean buggy;
    public String getName() {...}
    public void setName(String newName){...}
    public boolean isBuggy() {...}
    public void setBuggy(boolean trueOrFalse){...}
When I look at the virtual interface generated, especially at the Types tab, my boolean attribute is not included.
If I change the getter to "getBuggy()", the attribute is included in the VI. The only problem is that the typical Java Bean framework, say from sun or ibm, always map 'boolean' getters to 'isSomething()' and not 'getSomething()'.
Is this a bug with NW? Is there a fix or workaround for this ?
My version of NW:
Version: 2.0.7
Build id: 200407270250
Thanks in advance,
Mark
(If this is not the right forum, could someone suggest where I can post this question?)

Hi. As of Netweaver 2004s, the virtual interface piece has be absorbed into the creation of the web service definition, so there is no need to create it as well.   When you are getting the 403, how are you trying to run this, using the Web Service Homepage? If so, you will need to configure what j2e engine that you want to use to use. You can do this in WSADMIN under the Administration settings.   Check that this is set. YOu must know the URL of your j2e engine.
Regards,
Rich Heilman

Virtual Interface IP address

Similar Messages

Maybe you are looking for