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

Similar Messages

How the idoc interfaces works..

Hi...
When we design a interfaces using Idocs... what is the actual process so that data get updated in SAP..
I want to know the flow of the process...
I have created Idoc structure in the system....but how the data will get into this...and from Idoc what makes the data to get updated into system....
Just few lines will be helpfull..

Hi,
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
1) Outbound Process
2) Inbound Process
There are basically two types of IDOCs.
1) Basic IDOCs: Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
2) Extended IDOCs: Extending the functionality by adding more segments to existing Basic IDOCs.
For creating a IDOC
see the below steps for outbound processing IDOCS..
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
name of the segment type must start with Z1 , and have a maximumThe of eight characters.
Enter description and enter the relevant field names and data elements.
The segment should represent a structure in the program so each field in the segment a field name and a data element must befor defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
PERFORM populate_Control_structure USING c_mestyp
c_SEGMENT_type1.
The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
PERFORM transfer_Parent_data_to_seg.
The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
PERFORM master_idoc_distribute.
NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
The ALE Layer handles the sending of the IDOC to the receiving system.
Error Handling (see Step 7b).
Commit work.
Project SpecificStep 7b Error Handling
Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
Declare a structure of type MCMAILOBJ for sending instructions.
Enter values for the internal table based on structure MCMAILOBJ
For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
Enter your message type and execute.
Status should be green, double click on one of the Idocs you have created to view its contents.
If a problem has occurred click on Status which will give you a description of the error.
Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
Click on each individual segment and view the content to check that the correct data has been read.
If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
hi,
2.2 Inbound Interface
Follow steps 1 to 5 inclusive as detailed above in outbound interface.
Step 6
Write a custom function module to handle custom inbound processing. This custom function module must
Check for the correct message type
Read the IDoc data segment
Perform data conversion and validate the data as appropriate
Post the data to the database
Handle any error situations
Set the correct return values for the status record
Note that the Function Module must not make a commit to the database. This is because the status record is not written until control returns to the ALE layer. So if you commit work in the Function Module and an error occurs in returning to the ALE Layer, the status record must not be updated with a successful outcome.
The commit work is executed in the ALE Layer after the status records are updated, via the standard SAP function module IDOC_INBOUND_PROCESS. This attributes of this function module are set up in (Transaction BD51), click on New Entries and fill in data; the main input parameters being Input Type and Dialog Allowed.
Take care as some standard SAP transactions contain a Commit Work as part of their processing. Therefore using a BDC to process inbound data to SAP may not be acceptable. You need to check that the SAP transaction is ALE enabled.
Step 7
(Transaction WE57)
Assign the custom function module to the IDoc type and the message type.
Set function module to type F and direction 2 for inbound.
Step 8
(Transaction WE42)
Create a new process code and assign it to the function module. The process code determines how the incoming IDoc is to be processed in SAP.
Step 9
(Transaction BD67)
Assign the function module to the process code created above. Got to New Entries and enter the process code and the function module name.
Step 10
(Transaction WE20 and Transaction BD64)
Create a partner profile for your message and ensure that in transaction WE20 the process code is the one that points to your function module. (See step 6 of creating Outbound Idocs).
Step 11
Ensure that error handling functionality is present.
Or Check these links.....
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Reward points if useful....
Regards
AK

How to make interface work ?

Hello SDNers,
I have written the below snippet.
Can any one explain now to call the method of the following 2 classes which are implemented within the interdace intf_counter..
REPORT ZNRD_CLASS_INTERFACE1.
interface intf_counter.
methods : set_counter importing value(set_value) type i,
            increment_counter,
            get_counter exporting value(get_value) type i.
endinterface.
class lcl_counter1 definition.
public section.
interfaces intf_counter.
private section.
data : count type i.
endclass.
class lcl_counter1 implementation.
method intf_counter~set_counter.
count = set_value.
endmethod.
method intf_counter~increment_counter.
    add 1 to count.
endmethod.
method intf_counter~get_counter.
    get_value = count.
endmethod.
endclass.
class lcl_counter2 definition.
public section.
   interfaces intf_counter.
private section.
data : count type i.
endclass.
class lcl_counter2 implementation.
method intf_counter~set_counter.
count = ( set_value / 10 ) * 10.
endmethod.
method intf_counter~increment_counter.
if count ge 100.
    write:/ 'Count greater than 100 '.
    count = 0.
else.
    add 10 to count.
endif.
endmethod.
method intf_counter~get_counter.
get_value = count.
endmethod.
endclass.
Regards,
Ranjith N

Hello
Assuming that you interface methods are (public) instance methods you first need to create an instance of your class.
*& Report ZNRD_CLASS_INTERFACE1
REPORT znrd_class_interface1.
*       INTERFACE intf_counter
INTERFACE intf_counter.
METHODS : set_counter IMPORTING value(set_value) TYPE i,
            increment_counter,
            get_counter EXPORTING value(get_value) TYPE i.
ENDINTERFACE.                    "intf_counter
*       CLASS lcl_counter1 DEFINITION
CLASS lcl_counter1 DEFINITION.
PUBLIC SECTION.
    INTERFACES intf_counter.
PRIVATE SECTION.
    DATA : count TYPE i.
ENDCLASS.                    "lcl_counter1 DEFINITION
*       CLASS lcl_counter1 IMPLEMENTATION
CLASS lcl_counter1 IMPLEMENTATION.
METHOD intf_counter~set_counter.
    count = set_value.
ENDMETHOD.                    "intf_counter~set_counter
METHOD intf_counter~increment_counter.
    ADD 1 TO count.
ENDMETHOD.                    "intf_counter~increment_counter
METHOD intf_counter~get_counter.
    get_value = count.
ENDMETHOD.                    "intf_counter~get_counter
ENDCLASS.                    "lcl_counter1 IMPLEMENTATION
*       CLASS lcl_counter2 DEFINITION
CLASS lcl_counter2 DEFINITION.
PUBLIC SECTION.
    INTERFACES intf_counter.
PRIVATE SECTION.
    DATA : count TYPE i.
ENDCLASS.                    "lcl_counter2 DEFINITION
*       CLASS lcl_counter2 IMPLEMENTATION
CLASS lcl_counter2 IMPLEMENTATION.
METHOD intf_counter~set_counter.
    count = ( set_value / 10 ) * 10.
ENDMETHOD.                    "intf_counter~set_counter
METHOD intf_counter~increment_counter.
    IF count GE 100.
      WRITE:/ 'Count greater than 100 '.
      count = 0.
    ELSE.
      ADD 10 TO count.
    ENDIF.
ENDMETHOD.                    "intf_counter~increment_counter
METHOD intf_counter~get_counter.
    get_value = count.
ENDMETHOD.                    "intf_counter~get_counter
ENDCLASS.                    "lcl_counter2 IMPLEMENTATION
DATA:
go_counter    TYPE REF TO lcl_counter1,
gif_counter    TYPE REF TO intf_counter.
START-OF-SELECTION.
CREATE OBJECT go_counter.
CALL METHOD go_counter->intf_counter~set_counter( set_value = 1 ).
" Or:
gif_counter ?= go_counter.
CALL METHOD gif_counter->set_counter( set_value = 1 ).
" Or:
CREATE OBJECT gif_counter type ('LCL_COUNTER1').
CALL METHOD gif_counter->set_counter( set_value = 1 ).
END-OF-SELECTION.
Regards
   Uwe

How are marker interfaces working ?

can we create user defined marker interface ?
Some thing like Serializable.
That is unless and untill a user implements Serializable interface he is not able to store the object to a persistance media.
The compiler shoud show errors if we are not implementing the ''user defined marker Interface'' which is used for some purpose
Something like we should be informing the compiler that if a user is not implementing a ''user defined marker interface'' he is not supposed to use a specific classes or methods in that class
Is it possible?????

Define a marker Interface like
public interface MyMarkerInterface {
}Now, you can use instanceof operator to determine whether a given object implements MyMarkerInterface or not. Like,
if (myObject instanceof MyMarkerInterface) {
System.out.println("Implements");
} else {
System.out.println("doesn't implement");
}

How Virtual Links works on an SCE2020 platform.

I need to undertand how the virtual links work and what they are for.
I read the "Cisco Service Control Application for Broadband User Guide - Release 3.6.x" and this is what I found:
"In Virtual Links mode, template bandwidth controllers are defined for packages. Actual bandwidth parameters are assigned when a subscriber enters the system and depend on the subscriber's package (which defines the template controllers) and the physical link assigned to the subscriber."
"For each service configuration that has Virtual Links mode enabled, there is one default upstream virtual link and one default downstream virtual link. The upstream and downstream interfaces are each assigned one default template global controller."
I honestly don't understand this.
I really appreciate your help.
Thanks in advance, Mauro.

Hi Mauro,
Maybe this one can help. I think it has much more details. VLs are usually used in Cable enviroment.
http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel37x/remote_links/remote_links.html
Thanks,
Minja

How local interfaces work in EJBs

How exactly local interfaces work in EJBs and how should I use them ?
Thank you.

They are simply non-RMI interface implementations that directly delgate to the EJB's implementation. They are called and in turn call the EJB just as you would call any normal class.
As such, there is no RMI or serialization overhead and the interfaces can include methods that update their arguments, something not possible in remote interfaces.
Generally speaking, you should define local interfaces for all entities as one seldom if ever would access entities remotely. You might even consider defining ONLY local interfaces for entities, but that is a tougher call.
You would define local interfaces for session EJB's that are invoked by other session EJB's within the same container. I would normally always define both local and remote interfaces unless there is some reason why I can eliminate one or the other.
Chuck

How can i extract data strings (temp. press. rel.hum etc) using a Virtual interface through an RS-232 connection?

How can i extract data strings (temperature, pressure, relative humidity etc) using a Virtual interface through an RS-232 connection?

Try this. It is in LV 8.5.
Note the double % in the format string. This is so the % in the input string is treated as a percent rather than a code.
You may also have to work with the line feed characters in case they are different in the string coming in compared to how the string shows up in the web browser.
Message Edited by Ravens Fan on 02-12-2008 10:19 PM
Attachments:
Example_BD.png ‏4 KB
Untitled 11.vi ‏9 KB

How to Virtual cube with services works

Hi,
How to Virtual cube with services works.
can anyone provide me a realtime scenerio.
if possible provide some code.
Thanks,
cheta.

For which functinality you are trying to create VC with services.
This is mostly used in SEM BCS.
You have to create cube similar path like normal cube, but select in the properties virtual cube, services.
There is a standard FM which connects the Virtual cube to the required cube in BCS. ( this is done by BCS data basis generation function) and we have to do nothing for FM.
In BCS we use virtual cube only for reporting purpose, since standard BCS cube cannot be used for reporting. hence what we do is create another virtucal cube very smiliar to BCS cube.
Then both the Virtual cube and BCS cube are connected by standard FM.

How to change Virtual interfaces in SE80 for a web service under ECC6.0?

hi
I find a article, "Changing The Function Interface of Web Service Enabled Functions"
http://www.dataxstream.com/2009/11/changing-the-function-interface-of-web-service-enabled-functions/,
But, i cannot find the "Virtual interfaces" menu item under SE80, because its example is ECC5.0, my SAP is ECC6.0.
So, anybody can tell me how to change it under ECC6.0?
Thanks a lot.
Edited by: CSDN2008 on Mar 18, 2010 12:23 PM

Hi,
Please share your solution here as I am having the same issue.
Thank you
Muthaheera

HT5293 how do i get my interfaces working

how do i get my interfaces working?

Which interfaces?
https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/ AppleHIGuidelines/Intro/Intro.html

How to add vlan virtual interface on a Catalyst Using SNMP

Hi,
I need some assistance in locating the mib/variables to allow me to add and remove vlan
virtual interface on Catalyst 3759G. If I understand correctly CISCO-VTP-MIB can not carry
out this requirement.
Is there another way of accomplishing this using SNMP ?
Thanks,
Zhou

You cannot add a new interface directly using SNMP. However, you can use the CISCO-CONFIG-COPY-MIB to copy a config snippet into the running configuration which can create a new VLAN interface. See http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a0080094aa6.shtml for more details.

ABAP Web service - Virtual Interface Not Found

Hi,
I have created a ABAP web service based on RFC. I changed the authentication to "Basic username/password" from SOAMANAGER. Also tested the web service from WSNAVIGATOR (of different portal) using WSDL url. Web service successfully returned response.
Now, I have a AJAX client where I have hardcoded the request (from wsnavigator) and trying to call this web service in SAP BW web template (from HTML/JavaScript). But its not giving error as "Virtual Interface Not Found". Also, i get 500 error. But the end point of the web service if looked up from browser gives response. The SICF service is active and upon tests gives valid response.
Found couple of discussions regarding this:
http://wiki.sdn.sap.com/wiki/display/VC/VirtualInterfacenotfounderror
But i'm not finding the setting to activate virtual interface in SE80. ALso, we have created many such web services and they used to work fine prior to upgrade to Ehp1 SP05 (BI) but the newly created web service is not working.
Any inputs?
Abhijeet

Hi can you please let me know how you resolved this issue?

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

Virtual Interface

Hi All,
1) Is it possible can i able to create virtaul interface for Outlgoing mails in the Ironport c350 box. ?
2) Or - Can I assign a Pool of Ip Address for outgoing interface and the Ironport c350 box will pick any ip address and send the mail?
Anyone help me for above doubts?
Thanks in Advance,
Ram.N

A. To create new virtual gateway's,
We would recommend that you go to the support portal and download the PDF version of the AsyncOS Advanced User Guide. (http://www.ironport.com/support/login.html )
Once you have the PDF of the Advanced User Guide, search for this
"USING VIRTUAL GATEWAY TECHNOLOGY"
This section will get into details on how Virtual Gateways work on the Ironport appliance.
How many virtual gateways can be configured on each appliance?
-- AsyncOS 5.1.x and up
C10/1x0 4 Virtual Gateways
C30/3x0 32 Virtual Gateways
C3x0D 256 Virtual Gateways
C60/6x0 32 Virtual Gateways
X10x0 32 Virtual Gateways
B. To assign the virtual gateway IP's to a group and have delivery go to this group, follow these steps.
Warning: Can only be done from the command line of the appliance
1. After you've created your virtual gateway IPs, type "interfaceconfig"
2. then type, "groups" and add the IP's that you want to this group.
3. Press enter a few times to return to the main prompt and type "commit"
4. Then, type "deliveryconfig" and it will allow you to choose which interface to use. Select the new gorup that you created in the steps above.
5. "commit" changes.
If there are multiple IP's in the group that you create, it will round-robin through the IP addresses.
Hi All,
1) Is it possible can i able to create virtaul interface for Outlgoing mails in the Ironport c350 box. ?
2) Or - Can I assign a Pool of Ip Address for outgoing interface and the Ironport c350 box will pick any ip address and send the mail?
Anyone help me for above doubts?
Thanks in Advance,
Ram.N

Virtual interface (BINDTODEVICE)

I want to bind a socket to one defined virtual interface ( like hme0:10).
In Linux you can use a special socket-option:
int skfd;
struct ifreq interface;
skfd = socket(AF_INET, SOCK_DGRAM, 0);
strncpy(interface.ifr_ifrn.ifrn_name, "eth1", IFNAMSIZ);
if (setsockopt(skfd, SOL_SOCKET, SO_BINDTODEVICE,(char *)&interface, sizeof(interface)) < 0) {
perror("sendpacket: setting SO_BINDTODEVICE");
exit(1);
Is there any equivalent solution for Solaris?

Thanks for your reply.
Well, the use of virtual interaces is part of the customers specification (so he will able to specify different interfaces in the config-file without caring about the physical interfaces underneath).
The SO_BINDTODEVICE is part of the only example I�ve found. I didn�t test it yet.
But if there is no such option in Solaris, I must get the relationship between virtual interface/physical intface 'by hand'.
Any idea how that works?
Thank you
Siegmar

How do virtual interfaces work?

Similar Messages

Maybe you are looking for